问题
Error Message: Upload missing dSYMs to see crashes from 1 versions. Versions affected: 1.0 (1)
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.
@IBAction func onTestCrashButtonClick(_ sender: UIButton) {
Crashlytics.sharedInstance().crash()
}
But when i tried to see the error report in the firebase console, it shows something like this image.
After reading Get Deobfuscated crash reports I just Set Debug Information Format to DWARF with dSYM File like below but the problem not fixed till now.
回答1:
I have been having this same issue for a while and I was finally able to resolve it, thought I would share what worked for me:
For context, I am working on a larger app which uses several Cocoapods.
I found that same red banner on my Firebase Crashlytics page and after following all of their instructions I was still seeing it.
I tried the "archive/find .dSYMs/upload manually via terminal" solution several times to no avail.
Finally, I decided to download the .dSYMs from iTunesConnect.
[Your App] > Activity > [Desired Build Number] > Download dSYM
I then uploaded those .dSYMs manually and within minutes Firebase Crashlytics was happy and showing the crash reports.
UPDATE
Google has added a swanky .dSYM upload feature on the Firebase Crashlytics dashboard, no more uploading from the terminal.
回答2:
In my case, I have done the following things and it worked:
Select 'Run script only when installing' in Build Phases -> Run Script (Shell = ${PODS_ROOT}/Fabric/run)
Build the app
Now you can find the .dsym file in the path, /Library/Developer/Xcode/DerivedData/XXX-arctjcalvfslmbakanpyivuuxjmm/Build/Products/Release-iphoneos
Upload the zipped .dsym file to firebase console
After few minutes, you can find the crash reports
NOTE:
- I have disabled bitcode while exporting ipa file (Adhoc or Appstore)
- If you need ipa with bitcode enabled, then download dsym file from iTunes connect
回答3:
If you are using the dynamic library is your project using cocoa pods or any other tool then Firebase needs Duplicate Symbol files to locate the faulty code in your library. If you want to read more about dSysms read this : https://stackoverflow.com/questions/3656391/whats-the-dsym-and-how-to-use-it-ios-sdk
To find dsysm folder, you first need the .ipa file on which crash was reported on your firebase. In your case, I suppose you are running on the simulator for testing. To get IPA follow these steps: How to create ipa in xcode 6 without Apple Developer account?
When you reach .iPA then right click and select show package contents, or follow this link: iphone: Where the .dSYM file is located in crash report
There you will find system folder. Upload this folder to firebase crashalytics.
Hope this helps!
回答4:
Find and upload debug symbols for Crashlytics
- Copy the UUID of your missing dSYM and run
mdfind "com_apple_xcode_dsym_uuids == <UUID>"on a terminal window. - The above command will return something like
.../build/ios/Release-Staging-iphoneos/your.app.dSYM - Zip up the package and upload to Crashlytics using Firebase dashboard
Wait for 10-15 minutes before the crashes start to appear on the console.
回答5:
If everything is fine you setup all without missing any step and then also you see Upload missing dSYMs to see crashes error in firebase.
Download the .dSYMs from iTunesConnect only no anywhere else and upload upload those to the Firebase.
After two days of long research and try lots of solutions but no anyone works for me :(
But by this solution Firebase Crashlytics was happy and showing the crash reports within a few minutes.
回答6:
Simple Steps Follow 1 Go to archive and right click on the latest version in which you want to get crash report on firebase 2 see the dsyms folder 3 create the Zip file of dsyms folder 4 finally upload that zip file into the firebase console
来源：https://stackoverflow.com/questions/48296774/firebase-crashlytics-upload-missing-dsyms-to-see-crashes-from-1-versions-ios