Crash reports are not generated in fabric/ crashlytics for my iOS application. An error (as given in screenshot) is being displayed on fabric dashboard.
As instructed by fabric I tried to search the given UUIDs in spotlight from the machine where the fabric mac app is installed.(where I create build of app.) but could not get any results. Also tried to search using terminal with command : mdfind "com_apple_xcode_dsym_uuids == <UUID>”
(as given in : http://support.crashlytics.com/knowledgebase/articles/376834-missing-dsyms ) but could not get any results there also.
Anybody had this issue before ? Any workarounds to resolve this ?
iOS+ Android Flutter Unity. By default, Firebase Crashlytics automatically processes your debug symbol (dSYM) files to give you deobfuscated and human-readable crash reports. This behavior is set when you add a run script that initializes Crashlytics to your app's build phase.
Crashlytics will log usage data about your app and provide insights into the nature of stability problems. Crashlytics provides a software development kit (SDK) that developers can integrate into an Android, iOS or Unity app. It was created by Fabric.
Crashlytics creates a exception handler that intercepts the exceptions that weren't caught and does something with them but it also sends the exception to the previous exception handler, that's why the app stills crashes.
To continue getting crash reports in the Firebase console, upgrade to use the latest Firebase Crashlytics SDK: v8.10.0 for iOS+ , v18.2.6 for Android, or v8.7.0 for Unity . This page provides troubleshooting help and answers to frequently-asked questions about using Crashlytics.
If your project uses Crashlytics alongside the Google Mobile Ads SDK, it's likely that the crash reporters are interfering when registering exception handlers. To fix the issue, turn off crash reporting in the Mobile Ads SDK by calling disableSDKCrashReporting.
They may be based on the page you’re currently viewing and your account’s saved web and app activity. Firebase Crashlytics, an Android and iOS real time crash reporting tool, helps you prioritize and fix your most pervasive crashes based on the impact on real users. Crashlytics also easily integrates into your macOS, tvOS, watchOS, Unity apps.
This page provides troubleshooting help and answers to frequently-asked questions about using Crashlytics. If you can't find what you're looking for or need additional help, contact Firebase support.
I have after I complete the Fabric setup successfully into my app, the same issue,I tried every solution but the one that worked for me was:
Set the current config
You can get crash reports by generating dSYMs file for particular version of build and upload it on crashlytics.
Follow below steps to generate dSYMs file.
Go to Window Menu -> Organizer in Xcode.
Select the right version of build and click on the button "Download Debug Symbols" on the right panel
Right Click on right version of build and select show in Finder.
Select .xcarchieve file then right click on that and click on Show Package contents
Then Go to **dSYMs folder** and select .dSYM file and compress that file.
Now Final Step is to upload compressed file on fabric.
And then you can get crash report of build.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With