iOS Firebase Crashlytics not showing up crashes in Dashboard
Solution 1
To someone still struggling with the issue here is what resolved the issue for me.
I deleted the GoogleService-Info.plist and added it again.
I tried the crash on my welcome screen rather than in one of the screens of my tab bar controller as I believe from there it's unable to find GoogleServiceInfo.plist file so it worked.
Solution 2
Try this:
- Run your app from Xcode to install it on the simulator or your device
- Press the Stop button in Xcode to quit it
- Launch your app from the home screen to run it without the debugger
- Press the “Crash” button to trigger the crash
- Run the app again from Xcode so it can deliver the recorded crash to Crashlytics
- Within a few minutes, you should see the crash appear on your Firebase Crashlytics Console.
For reference:
Integrating Firebase and Crashlytics in iOS
Solution 3
I have tried serval things but below steps are worked for me
- Put
FirebaseApp.configure()
to first line ofdidFinishLaunchingWithOptions
- If you have both
Firebase/Crashlytics
andCrashlytics
. RemovedCrashlytics
from pods and update it - Check in Build Phases
Run Script
if you have entry fot"${PODS_ROOT}/FirebaseCrashlytics/run"
. - If you're running app in debug mode make sure you have added
-FIRDebugEnabled
in Project's test scheme. - Run the App From Home Screen(Don't run it from Xcode) and crash it on any button's Action.(you will find the crash in Firebase Console with in 5-10 mins)
Solution 4
After following all the steps as stated in the docs followed below steps:
- Install app using xcode.
- Quit the app.
- Launch the app from home screen - This is important
- Force a crash
They starting showing on the console.
Moaz Khan
I am working as an iOS Software Engineer at Teamo SMC Pvt Ltd. Before that I have worked 3+ years as a freelance Software Engineer at freelancer.com.
Updated on July 21, 2022Comments
-
Moaz Khan almost 2 years
I implemented Firebase Crashlytics in my iOS app. I followed all the steps in firebase documentation. I already ran crashlytics without the debugger by closing the app first and then re run the app so that crash reports can be sent. I even get this message
Crash upload submission succesful
I even added the Run script and set variable to "DWARF with DSYM"
"${PODS_ROOT}/Fabric/run"
I ready somewhere that if DSYM aren't uploaded you won't see your crashes even if they are uploaded successfully. So I went into my pods/Fabric/ and click on "run" CLI. It clearly says DSYM not uploaded because GoogleServiceInfo.plist wasn't found. Although it's there and yes it's included in my target as well as in my bundle.
Here is the screenshot. I have tried all possible steps to include GoogleService-Info.plist but still when I run manually it says this.
Any another thing that I can try ?
-
Srijan Kumar about 6 yearsm having the same issue but it still not get resolved by even deleting and re-adding GoogleService-Info.plist. Its' a bit frustrating now.
-
Moaz Khan about 6 yearsAdd a test crash in the first view controller of your app. After that it will start to show up.
-
Sachintha Udara almost 5 yearshey, this is working on my case, but after set user details using sample codes are providing by fabric, new crashes are not showing in dashboard and there has warning with Missing dSYMs, why is that ? where is wrong
-
Piero Sifuentes almost 5 years@SachinthaUdara try this: Check if Xcode is producing debug symbol files: 1. Open your project in Xcode, and select the project file in the Xcode Navigator. 2. Select your main build target from the Select a project or target dropdown. 3. Open the target's Build Settings tab. 4. Click All near the top of the tab. 5. Search for "debug information format". 6. Set Debug Information Format to DWARF with dSYM File. If that doesn't work, you should add a run upload symbols script manually For reference: medium.com/swlh/…
-
Sachintha Udara almost 5 yearsThanks of your reply, Yes I have done dSYM selecting a part in early of configuration. I don`t know the real reason for it, but when I did the same thing in firebase it work calm. I think this is wrong with fabric SDK.
-
Maxim Golovlev over 3 yearsthanks man, I was trying to understand why activation does not occur, it turns out that you need to launch the application from the home screen, it's a shame that Google cannot write about this in its manual
-
Azin Mehrnoosh about 3 yearsOMG, I spent a day trying to figure this out and this is the only thing that worked! Thanks.
-
Niraj about 3 yearsI have
Crashlytics
,Fabric
andFirebase/Crashlytics
so it was confused. I removed all and keep onlyFirebase/Crashlytics
and it worked. -
Rohit Singh over 2 yearsDid not work for me sorry.
-
Koen over 2 yearsThanks a lot! This part did it for me: 5. Run the App From Home Screen(Don't run it from Xcode) and crash it on any button's Action.(you will find the crash in Firebase Console with in 5-10 mins)
-
Jeremy Piednoel over 2 yearsi was missing the step 5 -> it's important to relaunch the app with xcode and not from the home screen. thanks a lot !