I am trying to implement Firebase Crashlytics in my iOS project. I did all the setups according to Firebase Crashlytics Doucmentation. The crash is performed manually when the button is clicked just to see whether the crashlytics is working.
Crashlytics Mac App Download
This one I used recently to upload my dsym to fabric. I was using fabric with crashlytics SDK not firebase one(which is currently in beta). Just replace your app name for 'APP' and your DSYM path instead of '/Users/ME/Desktop/APP.app.dSYM.
However, for apps with bitcode enabled, the process of uploading dSYMs isn't automatic. Instead, you need to download updated dSYMs from Apple and upload them manually to Crashlytics each time you submit a new version of the app to App Store Connect.
This manual process can be a pain especially since non-technical team members are often responsible for uploading bitcode dSYMs.With fastlane, you can use a single command to automatically download and upload your bitcode dSYMs.
One or more actions can be included in a lane. You can think of a lane as a workflow that is (usually) composed of related tasks. For this Crashlytics workflow, the lane will consist of three actions: downloading dSYMs from Apple, uploading dSYMs to Crashlytics, then cleaning up the files. Each lane also has a name and description.
download_dsyms will do the work of downloading the new dSYM files from Apple. We'll just need to provide the action with either 1) the version number and build for the app version that you want to download dSYMs for or 2) the live and latest version constants to download the live or latest version's dSYMs, respectively. Optionally, you can also specify your app's bundle ID and your App Store Connect username to avoid having to enter them manually when you run the action. All in all, this action will look similar to one of the following:
upload_symbols_to_crashlytics will take the files from download_dsyms and upload them to Crashlytics. This command takes as a parameter the GoogleService-Info.plist file for the app, like so:upload_symbols_to_crashlytics(gsp_path: "path/to/GoogleService-Info.plist")
Note: If you're using Swift Package Manager (instead of CocoaPods), you'll need to download the Crashlytics upload-symbols tool, place it in your project directory, make it executable (chmod +x upload-symbols), then set the binary_path variable in the upload_symbols_to_crashlytics action: upload_symbols_to_crashlytics(gsp_path: "path/to/GoogleService-Info.plist", binary_path: "upload-symbols").
This action allows you to upload symbolication files to Crashlytics. It's extra useful if you use it to download the latest dSYM files from Apple when you use Bitcode. This action will not fail the build if one of the uploads failed. The reason for that is that sometimes some of dSYM files are invalid, and we don't want them to fail the complete build.
After finding the file, follow this step from Firebase crashlytics to upload it manually. Wait for few minutes to let Firebase crashlytics re-process the crash reports again then the issue would be dismissed.
com.google.firebase.crashlytics Version Publish Date Minimum Unity Version Download Dependencies 10.4.0 2023-01 2018.1 .unitypackage .tgz Included com.google.external-dependency-manager com.google.firebase.app 10.3.0 2022-12 2018.1 .unitypackage .tgz Included com.google.external-dependency-manager com.google.firebase.app 10.2.0 2022-11 2018.1 .unitypackage .tgz Included com.google.external-dependency-manager com.google.firebase.app 10.1.1 2022-11 2018.1 .unitypackage .tgz Included com.google.external-dependency-manager com.google.firebase.app 10.1.0 2022-11 2019.1 .unitypackage .tgz Included com.google.external-dependency-manager com.google.firebase.app 10.0.1 2022-10 2019.1 .unitypackage .tgz Included com.google.external-dependency-manager com.google.firebase.app 10.0.0 2022-10 2019.1 .unitypackage .tgz Included com.google.external-dependency-manager com.google.firebase.app 9.6.0 2022-09 2018.1 .unitypackage .tgz Included com.google.external-dependency-manager com.google.firebase.app 9.5.0 2022-09 2018.1 .unitypackage .tgz Included com.google.external-dependency-manager com.google.firebase.app 9.4.0 2022-08 2018.1 .unitypackage .tgz Included com.google.external-dependency-manager com.google.firebase.app 9.3.0 2022-07 2018.1 .unitypackage .tgz Included com.google.external-dependency-manager com.google.firebase.app 9.2.0 2022-07 2018.1 .unitypackage .tgz Included com.google.external-dependency-manager com.google.firebase.app 9.1.0 2022-06 2018.1 .unitypackage .tgz Included com.google.external-dependency-manager com.google.firebase.app 9.0.0 2022-05 2018.1 .unitypackage .tgz Included com.google.external-dependency-manager com.google.firebase.app 8.10.1 2022-05 2017.1 .unitypackage .tgz Included com.google.external-dependency-manager com.google.firebase.app 8.10.0 2022-04 2017.1 .unitypackage .tgz Included com.google.external-dependency-manager com.google.firebase.app 8.9.0 2022-04 2017.1 .unitypackage .tgz Included com.google.external-dependency-manager com.google.firebase.app 8.8.0 2022-01 2017.1 .unitypackage .tgz Included com.google.external-dependency-manager com.google.firebase.app 8.7.0 2021-12 2017.1 .unitypackage .tgz Included com.google.external-dependency-manager com.google.firebase.app 8.6.2 2021-11 2017.1 .unitypackage .tgz Included com.google.external-dependency-manager com.google.firebase.app 8.6.1 2021-11 2017.1 .unitypackage .tgz Included com.google.external-dependency-manager com.google.firebase.app 8.6.0 2021-11 2017.1 .unitypackage .tgz Included com.google.external-dependency-manager com.google.firebase.app 8.5.0 2021-10 2017.1 .unitypackage .tgz Included com.google.external-dependency-manager com.google.firebase.app 8.4.0 2021-10 2017.1 .unitypackage .tgz Included com.google.external-dependency-manager com.google.firebase.app 8.3.0 2021-09 2017.1 .unitypackage .tgz Included com.google.external-dependency-manager com.google.firebase.app 8.2.0 2021-09 2017.1 .unitypackage .tgz Included com.google.external-dependency-manager com.google.firebase.app 8.1.0 2021-07 2017.1 .unitypackage .tgz Included com.google.external-dependency-manager com.google.firebase.app 8.0.0 2021-06 2017.1 .unitypackage .tgz Included com.google.external-dependency-manager com.google.firebase.app 7.2.0 2021-05 2017.1 .unitypackage .tgz Included com.google.external-dependency-manager com.google.firebase.app 7.1.0 2021-03 2017.1 .unitypackage .tgz Included com.google.external-dependency-manager com.google.firebase.app 7.0.2 2020-12 2017.1 .tgz com.google.external-dependency-manager com.google.firebase.app 7.0.1 2020-12 2017.1 .tgz com.google.external-dependency-manager com.google.firebase.app 7.0.0 2020-12 2017.1 .tgz com.google.external-dependency-manager com.google.firebase.app 6.16.1 2020-10 2017.1 .tgz com.google.external-dependency-manager com.google.firebase.app 6.16.0 2020-10 2017.1 .tgz com.google.external-dependency-manager com.google.firebase.app 6.15.2 2020-07 2017.1 .tgz com.google.external-dependency-manager com.google.firebase.app 6.15.1 2020-06 2017.1 .tgz com.google.external-dependency-manager com.google.firebase.app 6.15.0 2020-06 2017.1 .tgz com.google.external-dependency-manager com.google.firebase.app 6.14.1 2020-05 2017.1 .tgz com.google.external-dependency-manager com.google.firebase.app 6.14.0 2020-04 2017.1 .tgz com.google.external-dependency-manager com.google.firebase.app 6.13.0 2020-03 2017.1 .tgz com.google.external-dependency-manager com.google.firebase.app
2) using Xcode locally, I created an application with the same bundle id as used by my Xamarin app. Then, after downloading the Fabric Mac app from , I went thru the app's Crashlytic Kit's on-boarding process. The big thing to take away from this process was the shorter of the two alphanumeric strings (the first argument) used in the Xcode build phase run script it presents to you.
I also chose to copy the file "upload-symbols", from the downloaded (in step 2 above) Fabric.app/Contents/MacOS directory (assessable using 'ls' in a terminal window on my Mac though not in Finder!), in to the same directory as the transferDsymFile.bash file so everything was easily locatable by my script (and in my case kept in Git with the rest of my app).
/Users/David/.nuget/packages/xamarin.firebase.ios.crashlytics/3.10.1/build/Xamarin.Firebase.iOS.Crashlytics.targets(3,3): Error MSB3073: The command "/Users/David/Library/Caches/XamarinBuildDownload/Fbrc-1.7.5/upload-symbols -gsp /Users/David/Xamarin Projects/DND/MyApp/MyApp.iOS/GoogleService-Info.plist -p ios bin/iPhone/Debug/device-builds/iphone7.2-11.4.1/MyApp.iOS.app.dSYM" exited with code 132. (MSB3073) (MyApp.iOS) 2ff7e9595c
Comments