Firebase CrashlyticsFirebase Crashlytics not showing crashes

Rather not fix it yourself? App Fix Ticket starts with a fixed-price diagnosis, then a fixed price for the fix before any fix work.

Why the crash is not in the dashboard, and the fix

1. 01

   The app crashed with the Xcode debugger attached

   “The Xcode debugger prevents crash reports from being sent to Crashlytics.” Firebase, Test your Crashlytics implementation (Apple platforms)

   Running from Xcode keeps the debugger attached, and Firebase says it stops the report from being sent. Build and run once, stop it in Xcode, then open the app from the home screen and crash it there.

2. 02

   The app was not opened again after the crash

   “After your app crashes, restart it so that your app can send the crash report to Firebase.” Firebase, Test your Crashlytics implementation (Android)

   Firebase says to restart the app after it crashes so it can send the crash report. On Android, open it again from the device; on iOS, Firebase’s guide runs it again from Xcode. Then refresh the dashboard.

3. 03

   Automatic collection is turned off

   “In the application block of your AndroidManifest.xml file, add a meta-data tag to turn off automatic collection:” Firebase, Customize your Crashlytics crash reports (Android)

   Crashlytics collects automatically by default. Firebase describes turning that off for opt-in reporting, and then nothing is sent until the code turns collection on for that user. Search your AndroidManifest.xml for firebase_crashlytics_collection_enabled (and Info.plist for FirebaseCrashlyticsCollectionEnabled), and check where setCrashlyticsCollectionEnabled(true) is called.

4. 04

   You cannot tell whether the report was sent

   “If you've refreshed the console and you're still not seeing the test crash after five minutes, try enabling debug logging (next section).” Firebase, Test your Crashlytics implementation (Android)

   Turn on debug logging to see what the SDK does. On Android, set the log tag and watch logcat for the upload message. On iOS, add -FIRDebugEnabled to the scheme’s launch arguments and look for Completed report submission.

   adb shell setprop log.tag.FirebaseCrashlytics DEBUG
   adb logcat -s FirebaseCrashlytics
   # look for: Crashlytics report upload complete

Checked against the vendor’s docs on November 12, 2026: Firebase docs: Test your Crashlytics implementation (Apple platforms); Firebase docs: Test your Crashlytics implementation (Android); Firebase docs: Customize your Crashlytics crash reports (Android); Firebase docs: Customize your Crashlytics crash reports (Apple platforms).

Rather hand it over?

Fixed scope, fixed price, paid upfront. The work happens in writing; no call needed.

• from $450App Fix TicketOne reproducible bug in an existing mobile or web app, diagnosed and fixed.See scope and start
• from $450AI-Built App RescueA Lovable, Bolt or Cursor app checked end to end in 3 days, then its worst problems fixed at a fixed price.No issues worth fixing, no charge. If the Launch Check finds nothing rated medium or higher, Simon refunds the full $450. You keep the report either way. This applies to the first 10 Launch Checks bought after October 30, 2026.See scope and start

Related: Crashlytics “Missing dSYM” · Firebase “No Firebase App [DEFAULT]” · Firebase Remote Config not updating · google-services plugin not found