Firebase Crashlytics 'Error loading your issues' and upload-symbols script error - iOS App using XCode
The solution was to force a crash in my app using fatalError()
. It is not obvious that this is required to finalise the registration of the new SDK with the Firebase Crashlytics backend.
After doing this, all my historical crash data is available like before, and upload-symbols
completes successfully.
iOS and FirebaseCrashlytics
After hours of struggling with this problem finally solved it using this approach:
use this command in Terminal: /path/to/pods/directory/FirebaseCrashlytics/upload-symbols -gsp /path/to/GoogleService-Info.plist -p ios /path/to/dSYMs
Important thing is instead of /path/to/pods/directory
you should enter the path to your pods folder in your application folder, and instead of /path/to
you should enter the path to the GoogleService-Info.plist which is in your project folder too. And the last one is, instead of /path/to/dSYMs
you should enter the path to your archive which has the format of .xcarchive
.
For finding the .xcarchive
path, you should first archive your application, then go to XCode -> Organizer and select your build, then right click on it and select "Show in finder" and then right click on your .xcarchive
file and select "Show package contents". This is it, you can copy this path and paste it instead of /path/to/dSYMs
and then hit enter to start uploading to Firebase Crashlytics.
Check out this link for more information:
Firebase Docs
Xcode build never finishes when using Firebase upload-symbols in Build Phase Run Script
I realised I needed to add an input file for the run script. See below for implementation.
Can I force Crashlytics to call a script run in the current thread?
Instead of using the "run" script, you can call the "upload-symbols" script adding the --build-phase flag:
${BUILD_DIR%Build/*}/SourcePackages/checkouts/firebase-ios-sdk/Crashlytics/upload-symbols --build-phase
This will make the script to upload the dSYMs as part of the build process instead of doing it in the background.
Unable to upload Crashlytics dSYM file during build phase due to script error
dSYM_directory
is just a placeholder in the example script. You need to point the upload-symbols
script to the directory where your apps dSYMs are. Replace dSYM_directory
with the actual path and it will work.
Related Topics
Problem with Swiftui and Foreach on Xcode Playground
Compiling for iOS 10.3, But Module 'swiftuicharts' Has a Minimum Deployment Target of iOS 13.0
How to Grab The Parent Object from a Subview
Create Record Only If Parent Exists in Vapor Using Fluent
Animate UIlabel Width with Fixed Center
Closure Identity in Swift: Unregister Observing Closure
Filter, Closure, Functional Syntax Version of for Loop with Multiple Conditions
Using Font Awesome Dynamically in Swift
Difference Between Any? and Any
Delete Tableview Cell, and Remove Data from Firebase
Why Swift Disallows Weak Reference for Non-Optional Type
Swift: Simple Dispatchqueue Does Not Run & Notify Correctly
How to Use Nscalendar Range Function Within Calendar
Reduce Float Precision Using Regexp in Swift
Swift Compile Error, Subclassing Nsvalue, Using Super.Init(Nonretainedobject:)
How to Separate The Date and Time Components of Nsdate() in Swift
Swift: Get The Compile Time Name of Variable (Referencing to a Class)
Using Scenekit for Hittesting Not Returning a Hit with Scnnode