I am trying to get crash reports working on my ios app. I am getting an error message in the Firebase Crash dashboard that says
Upload symbol file to symbolicate future stack traces for UUID 69696969-7F8H-567E-1ABCD-FAKEID123
I have checked every binary on my machine, and not a single one of them has this UUID. So where is this UUID coming from? I put a fake one in the example above obviously, but how can Firebase be asking for this UUID if it doesn't exist?
Note that this is a test crash. I am calling
FIRCrashMessage("Hey man, you crashed.")
fatalError()
in my app. The build is one I've downloaded from iTunes connect via TestFlight. Is Apple creating a binary that I don't have a dSYM file for? I have bitcode disabled.
I also verified that the run script is working. If I click "Symbol Files", to the right of "Dashboard" on the Firebase Crash Reporting tab I have lots of dSYM files uploaded to the Firebase Crash service, but none match the UUID of the binary I've downloaded from TestFlight.
Related
I tried to setup Firebase Crashlytics for our iOS project but I wasn't able to get valid crash log...
What I did so far:
Created a new "helloworld" iOS project
Added Firebase (Analytics & Crashlytics) by using SwiftPackageManager
Created the project within Firebase
Added the GoogleService-Info file
Called the init within the AppDelegate
Placed a button to force an unwrapping of a null value
Archived the project by using XCode & enterprise certificate
Located the archive and extracted the dSYM-file
Uploaded the dSYM-file by using the upload-symbols tool
Exported the archive as enterprise signed IPA
Installed the enterprise signed IPA on my device
Clicked the button and let the application crash
The crash is displayed within the firebase project and the section dSYM doesn't complain that some of the dSYM files are missing. Even though the crash isn't readable at all...
Has anyone managed to display crashed in firebase with a comparable setup? Just found the information that sometimes it's necessary to uploading the dSYM file provided by App Store Connect (Which is impossible for my enterprise solution...)
I have implemented a Firebase crashlytics in my project, and also I have configured the firebase account with my project. But when I do a crash with the help of Crashlytics.sharedInstance().crash() I will get crash crash report perfectly. But if I do a crash with any other method, it is not showing up the crash report. But some crashes are showing in the dSYMs tab in crashlytics and it is not formatted correctly. I have downloaded the dSYM file from the iTunes store and uploaded to Crashlytics through terminal. But Still I am getting the crashes in the dSYMs tab and not formatted correctly.
This is How I am getting crash report in dSYMs tab in Crashlytics.
Does anybody know what I am doing wrong here?
I could able to implement it in my Swift project and it correctly decrypted the errors and displayed correctly. But when I implemented it into my Objective-C project, I am not getting the correct decrypted report.
When having "optional" missing dSYMs, those are usually related to .frameworks or other third party library being used. If you only have these kinds of missing dSYMs, the dashboardwill show the crash report, but the frames related to those dSYMs won't be symbolized.
DSYMs marked as "required" are related to your main app, when those are missing, the dashboard won't show the crash report.
Usually, when using a .framework, the dSYMs files should also be available, but if not, you'd probably need to get them from the framework owners.
To elaborate Gerardo's answer further, please refer to your Xcode Organizer. There goes a list of your app published with different version. Download the dSYM
reports first and hence follows the procedures given from Google and submit those dSYM to firebase
Make sure you have already installed the latest version of FirebaseCrashlytics via Cocoapods and proper app profile at your Firebase Console.
https://firebase.google.com/docs/crashlytics/get-deobfuscated-reports#upload-dsyms
Question #1:
I am using Crashlytics for one of my commercial iOS Apps. Their service seems very helpful. I wonder if there is any Legal issue of using their services for commercial apps? Is there any limitations for using Crashlytics?
Question #2:
I need to upload .dsym file in their server to get crashlogs symbolicated. Is there any privacy issue. Is it possible to get my code (or any info) back by reverse engineering when they have .dsym file.
Question #3
Sometime some crashes are not showing in the crashlytics dashboard. Is it necessary to be online when crash happens to get crashlog in dashboard? Don't Crashlytics keep logs trace when offline and send logs back to the server when device become online? Any idea how they work?
Mike from Fabric here, but I'm not a lawyer.
1) Fabric and Crashlytics is used in many commercial apps, including our own. There aren't limitations to using Fabric. You can find the Fabric terms of service here.
2) The dSYM is what let's us or any other crash reporter symbolicate the crash report as it contains the symbols that map back to your app's source. None of your source code is uploaded. From Apple's own documentation:
As the compiler translates your source code into machine code, it also
generates debug symbols which map each machine instruction in the
compiled binary back to the line of source code from which it
originated. Depending on the Debug Information Format
(DEBUG_INFORMATION_FORMAT) build setting, these debug symbols are
stored inside the binary or in a companion Debug Symbol (dSYM) file.
The Debug Symbol file and application binary are tied together on a
per-build-basis by the build UUID. A new UUID is generated for each
build of your application and uniquely identifies that build. Even if
a functionally-identical executable is rebuilt from the same source
code, with the same compiler settings, it will have a different build
UUID.
3) Crashes are caught regardless if the app is connected to a network or not. However, crashes are only sent on relaunch of the app and would then be processed.
One thing to note is that if you're testing in the Simulator or with your device connected to Xcode will cause Xcode's debugger to capture the crash instead of us.
Further, if the dSYM hasn't been uploaded, then we're unable to process the crash report and we'll alert you in the Crashlytics dashboard of the missing dSYMs so that you can upload them.
Is there any way to get crash information in iTunes Connect? I notice under App Analytics it displays the number of "Opt-in Only Crashes". I press the number under it (in my case 2). This takes me to a page that only seems to show the days that the crash happened. Is there any way I can see useful crash information, for example line of code, etc.?
To see where is the problem just open your Xcode > Window > Organizer > Crashes from your Application.
You already deployed your app on App Store (or as an Ad Hoc or Enterprise build) then you won't be able to attach Xcode's debugger to deployed app for debugging. To debug problems, you need to analyze Crash Logs and Console output from the device. To read crash reports with backtraces its need to be symbolicated before they can be analyzed. Symbolication is a process which replaces memory addresses with human-readable function names and line numbers.
To understanding and Analyzing Application Crash Reports you can refer Symbolicating Crash Reports, Debugging Deployed iOS Apps or Analyzing Crash Reports.
Overview of the crash reporting and symbolication process.
Set Debug Information Format (DEBUG_INFORMATION_FORMAT) in build settings these debug symbols are stored inside the binary or in a companion Debug Symbol (dSYM) file.
When you archive the application for distribution, Xcode will gather the application binary along with the .dSYM file and store them at a location inside your home folder.
At the time of deploying on the App Store or a beta test using Test Flight, include the dSYM file when uploading your archive to iTunes Connect.
When your application crashes, an unsymbolicated crash report is created and stored on the device.
You can retrieve crash reports directly from their device by following the steps in Debugging Deployed iOS Apps. If you have distributed your application via AdHoc or Enterprise distribution, this is the only way to acquire crash reports from your users.
Crash reports retrieved from a device are unsymbolicated and will need to be symbolicated using Xcode. Xcode uses the dSYM file associated with your application binary to replace each address in the backtrace with its originating location in your source code. The result is a symbolicated crash report.
If the user has opted to share diagnostic data with Apple, or if the user has installed a beta version of your application through TestFlight, the crash report is uploaded to the App Store.
The App Store symbolicates the crash report and groups it with similar crash reports. This aggregate of similar crash reports is called a Crash Point.
The symbolicated crash reports are made available to you in Xcode's Crashes organizer.
Yes, You can view those crashes in Xcode. This can found in apple docs in Analyzing crash reports
I have an app in beta using TestFlight and I have been noticing crash reports appearing.
most of the reports are this
If I click on the button Open in project in the Organizer it takes me no where
This appears to be an internal crash correct?
How can I find out what UIBarButtonItem is causing the crash?
I Hope this will help you: Apple doc Crash Report , as you can see in the doc in the Listing 4 the crash report is fully symbolicated , Listing 6 shows partially symbolicated crash reports which looks like your case
From Apple Doc
You must keep both the application binary and the .dSYM file in order to be able to fully symbolicate crash reports. You should archive these files for every build that you submit to iTunes Connect. The .dSYM and application binary are specifically tied together on a per-build-basis, and subsequent builds, even from the same source files, will not interoperate with files from other builds. If you use Xcode's Build and Archive command then they will be placed in a suitable location automatically. Otherwise any location searchable by Spotlight (such as your home directory) is fine.
For more information about this you can check portion after Listing 6 in Symbolication
you can use crashlytics for identifying where the app is crashed.It will give the Controller name and line number of code also.
https://docs.fabric.io/ios/index.html Document
Easy to add your project also