Firebase Crashlytics not showing crash report in console dashboard swift
Solution 1
I took the same steps as you and thought I had an issue until I realized there's a delay for the crashes to show up on the console. In my case it took about 40 minutes to appear.
Here's a blog post about it.
Solution 2
Check run script only when installing
Solution 3
I did everything on stack overflow; my upload was successful, but nothing showed up. After trying to figure out the solution, I tried this, and it worked for me as well as for some other people facing the same issue... might help others who end up here.
I posted it in issues section. Check it out https://github.com/firebase/quickstart-ios/issues/413
One thing that I did was to move my test crash
Crashlytics.sharedInstance().crash()
to the first view controller (e.g., WelcomeViewController),then after the crash I closed and opened my app again. Then just waited for sometime and it appeared.
Before doing all of that my test crash was within a view controller, which was part of a tabBarController as it wasn't the top most view controller. Maybe that's what caused the issue. After my first crash appeared on the firebase console then my other crashes started appearing.
Related videos on Youtube
![salman siddiqui](https://i.stack.imgur.com/QX3tl.jpg?s=256&g=1)
Comments
-
salman siddiqui almost 2 years
I have setup all these steps and bundel id on Firesbase Dashboard and tried crash many times but not getting any report.
- pod 'Firebase/Core' pod 'Fabric', '~> 1.7.2' pod 'Crashlytics', '~> 3.9.3'
- In Build phase added run Script : "${PODS_ROOT}/Fabric/run"
- Debug Inforation Format : DWARF with dSYM File
running in simulator with following steps
(IBAction)crashButtonTapped:(id)sender { [[Crashlytics sharedInstance] crash]; }
Click play_arrow Build and then run the current scheme in Xcode to build your app on a device or simulator.
- Click stop Stop running the scheme or action in Xcode to close the initial instance of your app. This initial instance includes a debugger that interferes with Crashlytics.
- Open your app again from the simulator or device. Touch Crash to crash the app.
-
Alexizamerican over 6 yearsAre you able to share your app's bundle ID so I can take a closer look?
-
salman siddiqui over 6 years@ Alexizamerican com.Salman.Test
-
Alexizamerican over 6 yearsThanks. It looks like crashes are coming through for your app now. Are you seeing them on your end?
-
salman siddiqui over 6 years@Alexizamerican Yes it's showing now in Event Trends graph but in Dashboard display count of Crashes is 0 and In crash reporting its displaying but not recent crashes with Crashes uploaded successfully.
-
Alexizamerican over 6 yearsYeah, there's currently a delay between Firebase analytics and crashes on Crashlytics. Crashes on Crashlytics should appear almost immediately.
-
salman siddiqui over 6 yearsOk, thanks, @Alexizamerican it's now showing after some delay.
-
Alexizamerican over 6 yearsGreat, Salman. I'm glad it's showing up!
-
salman siddiqui over 6 years@Alexizamerican crash report is uploaded on firebase on dash board i am getting [ Test 4506976340 + 65620 ] symbolic form it is not showing my method name.
-
salman siddiqui over 6 years@Alexizamerican one more issue I am getting is I am doing force crash on my app crash report is uploaded but my crashes are showing only 4 of the previous date in Crashlytics section but updating correctly in crash reporting section.
-
Alexizamerican over 6 yearsThere are a couple of things to investigate here and I recommend reaching out to Firebase support so the team can take a closer look.
-
salman siddiqui over 6 years@Alexizamerican ok thank you.
-
Bugs Happen about 5 yearsBut according to their documentation about force a crash, it will appear within 5 minutes...
-
Masashi over 4 yearsThis solution did the trick for me. It seems it does not send a crash report while connected to Xcode or in debug mode. Opened the app, closed it then opened again, viola, I found my forced crash there on dashboard
-
SacWebDeveloper over 4 yearsNope, still nothing after a 24 hours. Followed all the same infinite wisdom.
-
sejn almost 4 yearsAny updates. How long it will take to show the crashed report
-
dobiho over 3 yearsI had a same problems, and I solved it. call Crashlytics.crashlytics().setCrashlyticsCollectionEnabled(true)