firebase-android-sdk: Crashes not Showing in Firebase console After Removing Fabric

Hi everyone! Sounds like a lot of questions here around DataTransport and crashes being uploaded. Allow me to demystify some things about the logs you’re seeing.

First of all, as I’d posted on another thread, we have switched the SDK to a different code path for uploading crash reports, which is why you’ve started seeing:

D/FirebaseCrashlytics: Crashlytics report successfully enqueued to DataTransport: 5F706A7603CC00010F23719A69B5416A
D/FirebaseCrashlytics: Crashlytics completed exception processing. Invoking default exception handler.
D/FirebaseCrashlytics: Attempting to send crash report at time of crash...
D/FirebaseCrashlytics: Send to Reports Endpoint disabled. Removing Reports Endpoint report.
D/FirebaseCrashlytics: Removing report at /data/data/***/.com.google.firebase.crashlytics/fatal-sessions/5F706A7603CC-0001-0F23-719A69B5416A.cls

Crashlytics report successfully enqueued to DataTransport confirms that the report was captured and enqueued for submission through our new code path, and is then the cached version for the old code path is being deleted. This is the expected behavior.

Downgrading to 17.1.0 “fixes” this issue only because that version was not yet included in the SDK versions being switched over, so it was engaging the old code path. We’re currently rolling out support for that version on the new code path, so it will very soon start sending through the new code path as well.

All that said, it doesn’t help much if you’re not seeing your crashes in the dashboard! So, to that end, I want to provide a few more tags (in addition to FirebaseCrashlytics) to watch in the logs to see what’s going on. If you also include these tags in your logcat output:

TransportRuntime.SQLiteEventStore, TransportRuntime.JobInfoScheduler, TransportRuntime.CctTransportBackend, and TransportRuntime.DefaultScheduler…

…you’ll be able to see the specifics of how the crashes are being uploaded through the new code path.

Specifically, you’ll want to watch for this:

D TransportRuntime.CctTransportBackend: Making request to: ...
I TransportRuntime.CctTransportBackend: Status Code: 200
I TransportRuntime.CctTransportBackend: Content-Type: application/json; charset=UTF-8
I TransportRuntime.CctTransportBackend: Content-Encoding: gzip

If you see that, your report is being uploaded successfully, and should show up on your dashboard fairly soon afterward.

One thing to note here is that the new upload mechanism no longer sends the report from the crashing process, but enqueues an upload using JobScheduler (on Android 21+) to be sent ~1s after the crash occurs, so generally, the app will close, and the report will be sent soon after.

With all this in mind, if there are crashes that you’re trying to upload and the logs suggest they’re being uploaded but you’re still not seeing them, please post some recent logs and I’ll work with our team to see if there are issues on our backend that may be causing reports not to show up.

Let me know if you have further questions, but I hope that will at least help demystify what you’re seeing. 😃

The fact that you needed to share this huge explanation shows a lot about the current state of the SDK.

From the point of view of a developer who simply attempts to integrate your SDK according to your guidelines, it doesn’t work. Crashes are not reported. I would advise you to design your SDK so that no one ever has to know anything about how and why it works inside, and add clear, descriptive, plain-english logging of what’s actually going on - so countless people won’t have to waste their time knocking their heads against the wall.

With that said - sorry for the ranting but it’s just being asked for - here are my logs, crashes are not reported: https://www.dropbox.com/s/3h02k4jbzzjx9d8/firebase-crashlytics.txt?dl=0

firebaseBomVersion = ‘25.12.0’ RuntimeException throws on app startup after Application.onCreate ends

LogCat filter with regex: (FirebaseCrashlytics|TransportRuntime.SQLiteEventStore|TransportRuntime.JobInfoScheduler|TransportRuntime.CctTransportBackend|TransportRuntime.DefaultScheduler)

UPDATE: Also no reports with 17.1.0… Just lots of log messages that say the crash is being reported.

Up until today, is there a way to fix this. It’s been a month and I can’t track my bug report on firebase crashlytic

Just to throw more logs here as well – Firebase Crashlytics Logs Before and After

I am creating a crash with this method:

try { throw NullPointerException("Caught Crash") } catch (ex: NullPointerException) { CrashlyticsHelper.logException(ex) } throw RuntimeException("Test Crash")

The Caught Crash is always logged into Firebase, but the Test Crash is never sent on App startup and is removed according to the attached logs.

I’ve tried using the Bom library, I’ve tried the individual libraries, I’ve used 17.1.0 to no avail as well. I have opened a ticket with Firebase on this and received a message telling me some 3rd party libraries are unsupported? No list of unsupported libraries could be supplied though.

With this hard deprecation coming on November 15 (a week before Black Friday) it would be nice to have some movement on this issue.

Hi everyone! Sounds like a lot of questions here around DataTransport and crashes being uploaded. Allow me to demystify some things about the logs you’re seeing.

First of all, as I’d posted on another thread, we have switched the SDK to a different code path for uploading crash reports, which is why you’ve started seeing:

D/FirebaseCrashlytics: Crashlytics report successfully enqueued to DataTransport: 5F706A7603CC00010F23719A69B5416A
D/FirebaseCrashlytics: Crashlytics completed exception processing. Invoking default exception handler.
D/FirebaseCrashlytics: Attempting to send crash report at time of crash...
D/FirebaseCrashlytics: Send to Reports Endpoint disabled. Removing Reports Endpoint report.
D/FirebaseCrashlytics: Removing report at /data/data/***/.com.google.firebase.crashlytics/fatal-sessions/5F706A7603CC-0001-0F23-719A69B5416A.cls

Crashlytics report successfully enqueued to DataTransport confirms that the report was captured and enqueued for submission through our new code path, and is then the cached version for the old code path is being deleted. This is the expected behavior.

Downgrading to 17.1.0 “fixes” this issue only because that version was not yet included in the SDK versions being switched over, so it was engaging the old code path. We’re currently rolling out support for that version on the new code path, so it will very soon start sending through the new code path as well.

All that said, it doesn’t help much if you’re not seeing your crashes in the dashboard! So, to that end, I want to provide a few more tags (in addition to FirebaseCrashlytics) to watch in the logs to see what’s going on. If you also include these tags in your logcat output:

TransportRuntime.SQLiteEventStore, TransportRuntime.JobInfoScheduler, TransportRuntime.CctTransportBackend, and TransportRuntime.DefaultScheduler…

…you’ll be able to see the specifics of how the crashes are being uploaded through the new code path.

Specifically, you’ll want to watch for this:

D TransportRuntime.CctTransportBackend: Making request to: ...
I TransportRuntime.CctTransportBackend: Status Code: 200
I TransportRuntime.CctTransportBackend: Content-Type: application/json; charset=UTF-8
I TransportRuntime.CctTransportBackend: Content-Encoding: gzip

If you see that, your report is being uploaded successfully, and should show up on your dashboard fairly soon afterward.

One thing to note here is that the new upload mechanism no longer sends the report from the crashing process, but enqueues an upload using JobScheduler (on Android 21+) to be sent ~1s after the crash occurs, so generally, the app will close, and the report will be sent soon after.

With all this in mind, if there are crashes that you’re trying to upload and the logs suggest they’re being uploaded but you’re still not seeing them, please post some recent logs and I’ll work with our team to see if there are issues on our backend that may be causing reports not to show up.

Let me know if you have further questions, but I hope that will at least help demystify what you’re seeing. 😃

I reported the problem to consultants and they are investigating. When If solutions was came, I will inform to you.

@mrichards @mrwillis21 I am facing an issue with crash log uploads on firebase with our Instant apps. Crash uploads works fine with full version of the app. Also I have noticed that with Instant apps firebase sdk still saves the crash logs but doesn’t upload them. Once we upgrade from instant apps to full version it uploads the crash logs which were saved earlier for instant app. As per my understanding for uploading crash logs firebase crashlytics sdk uses JobSchedulers and as per https://issuetracker.google.com/issues/124267857#comment6 job schedulers don’t work with Instant apps. Is this the reason crash logs are not getting uploaded for instant apps?

For your reference PFB logs for adb logcat -s FirebaseCrashlytics TransportRuntime.SQLiteEventStore TransportRuntime.JobInfoScheduler TransportRuntime.CctTransportBackend TransportRuntime.DefaultScheduler

`08-12 20:23:33.514 8676 9766 D FirebaseCrashlytics: Received Analytics message: 3 Bundle[{params=Bundle[{_o=auto, _et=1242518, _sc=MapActivity, _si=-6399843971024424288}], name=_e, timestampInMillis=1628780013008}]

08-12 20:26:34.036 9848 9848 D FirebaseCrashlytics: Crashlytics automatic data collection ENABLED by global Firebase setting. 08-12 20:26:34.043 9848 9848 D FirebaseCrashlytics: Firebase Analytics is available. 08-12 20:26:34.048 9848 9848 D FirebaseCrashlytics: Firebase Analytics listener registered successfully. 08-12 20:26:34.073 9848 9848 D FirebaseCrashlytics: Reading cached settings… 08-12 20:26:34.074 9848 9848 D FirebaseCrashlytics: No cached settings found. 08-12 20:26:34.075 9848 9848 D FirebaseCrashlytics: No cached settings data found. 08-12 20:26:34.079 9848 9848 D FirebaseCrashlytics: Mapping file ID is: 00000000000000000000000000000000 08-12 20:26:34.079 9848 9848 I FirebaseCrashlytics: Initializing Crashlytics 17.2.1 08-12 20:26:34.081 9848 9848 D FirebaseCrashlytics: Installer package name is: null 08-12 20:26:34.126 9848 9848 D FirebaseCrashlytics: Exception handling initialization successful 08-12 20:26:34.134 9848 9887 D FirebaseCrashlytics: No cached FID; legacy id is null 08-12 20:26:34.134 9848 9887 D FirebaseCrashlytics: Created new Crashlytics IID: 2196d372ed83412ab56602013cff2675 08-12 20:26:34.135 9848 9887 D FirebaseCrashlytics: Opening a new session with ID 611536A2007F-0001-2678-4433F083327D 08-12 20:26:34.183 9848 9887 D FirebaseCrashlytics: Initialization marker file created. 08-12 20:26:34.184 9848 9887 D FirebaseCrashlytics: Registered Firebase Analytics event receiver for breadcrumbs 08-12 20:26:34.184 9848 9887 D FirebaseCrashlytics: Finalizing previously open sessions. 08-12 20:26:34.188 9848 9887 D FirebaseCrashlytics: No open sessions to be closed. 08-12 20:26:34.188 9848 9887 D FirebaseCrashlytics: Closed all previously open sessions 08-12 20:26:34.191 9848 9887 D FirebaseCrashlytics: No reports are available. 08-12 20:26:34.191 9848 9887 D FirebaseCrashlytics: Initialization marker file removed: true 08-12 20:26:34.300 9848 9848 D FirebaseCrashlytics: Crashlytics automatic data collection ENABLED by API. 08-12 20:26:34.614 9848 9888 D FirebaseCrashlytics: Received Analytics message: 3 Bundle[{params=Bundle[{_o=auto, _sid=1628780194}], name=_s, timestampInMillis=1628780194505}] 08-12 20:26:35.644 9848 9888 D FirebaseCrashlytics: Received Analytics message: 3 Bundle[{params=Bundle[{Analytics_Reporting_App=ChargePointInstant, _o=app, Maintenance_Mode=false, Global_Config_Region=NA-US, Analytics_Reporting_Version=15, Cached=false, Launch_Source=Google Play}], name=Global_Config_Fetch, timestampInMillis=1628780195574}] 08-12 20:26:35.774 9848 9890 D FirebaseCrashlytics: Requesting settings from https://firebase-settings.crashlytics.com/spi/v2/platforms/android/gmp/1:53103838140:android:43d04b9beb9c48eb/settings 08-12 20:26:35.775 9848 9890 D FirebaseCrashlytics: Settings query params were: {instance=878f334b3911482b79887416dd7ff9b3dc9ef4fc, build_version=513, display_version=1.0.0-InstantCP-513-0.debug_20210812_18:09, source=1} 08-12 20:26:35.790 9848 9888 D FirebaseCrashlytics: Received Analytics message: 3 Bundle[{params=Bundle[{_o=auto, _sc=MapActivity, _si=1315616320171567843}], name=_vs, timestampInMillis=1628780195750}] 08-12 20:26:36.605 9848 9890 D FirebaseCrashlytics: Settings request ID: null 08-12 20:26:36.605 9848 9890 D FirebaseCrashlytics: Settings result was: 200 08-12 20:26:36.607 9848 9890 D FirebaseCrashlytics: Writing settings to cache file… 08-12 20:26:36.608 9848 9890 D FirebaseCrashlytics: Loaded settings: {“settings_version”:3,“cache_duration”:86400,“features”:{“collect_logged_exceptions”:true,“collect_reports”:true,“collect_analytics”:false,“prompt_enabled”:false,“push_enabled”:false,“firebase_crashlytics_enabled”:false,“collect_anrs”:false},“app”:{“status”:“activated”,“update_required”:false,“report_upload_variant”:2,“native_report_upload_variant”:2},“fabric”:{“org_id”:“54e6b5d34dd4468000000328”,“bundle_id”:“com.coulombtech.debug”},“expires_at”:1628866596607} 08-12 20:26:37.430 9848 9848 D FirebaseCrashlytics: Crashlytics automatic data collection ENABLED by API. 08-12 20:26:37.505 9848 9888 D FirebaseCrashlytics: Received Analytics message: 3 Bundle[{params=Bundle[{User_Type=InstantAppUser, Duration=1794.0, Status=SUCCESS, HTTP_Status_Code=200, Analytics_Reporting_App=ChargePointInstant, _o=app, _sc=MapActivity, _si=1315616320171567843, Global_Config_Region=NA-US, Analytics_Reporting_Version=15, Launch_Source=Google Play}], name=API_Get_Global_Config, timestampInMillis=1628780197373}] 08-12 20:26:39.066 9848 9888 D FirebaseCrashlytics: Received Analytics message: 3 Bundle[{params=Bundle[{User_Type=InstantAppUser, Duration=1180.0, Status=SUCCESS, HTTP_Status_Code=200, Analytics_Reporting_App=ChargePointInstant, _o=app, _sc=MapActivity, _si=1315616320171567843, Global_Config_Region=NA-US, Analytics_Reporting_Version=15, Launch_Source=Google Play}], name=API_View_Station_Detail, timestampInMillis=1628780199008}] 08-12 20:26:39.497 9848 9888 D FirebaseCrashlytics: Received Analytics message: 3 Bundle[{params=Bundle[{User_Type=InstantAppUser, Duration=1467.0, Status=SUCCESS, HTTP_Status_Code=200, Analytics_Reporting_App=ChargePointInstant, _o=app, _sc=MapActivity, _si=1315616320171567843, Global_Config_Region=NA-US, Analytics_Reporting_Version=15, Launch_Source=Google Play}], name=API_Retrieve_Map_Data, timestampInMillis=1628780199395}] 08-12 20:26:40.950 9848 9888 D FirebaseCrashlytics: Received Analytics message: 3 Bundle[{params=Bundle[{User_Type=InstantAppUser, Duration=1164.0, Status=SUCCESS, HTTP_Status_Code=200, Analytics_Reporting_App=ChargePointInstant, _o=app, _sc=MapActivity, _si=1315616320171567843, Global_Config_Region=NA-US, Analytics_Reporting_Version=15, Launch_Source=Google Play}], name=API_Station_List, timestampInMillis=1628780200794}] 08-12 20:26:43.050 9848 9888 D FirebaseCrashlytics: Received Analytics message: 3 Bundle[{params=Bundle[{User_Type=InstantAppUser, Duration=1252.0, Status=SUCCESS, HTTP_Status_Code=200, Analytics_Reporting_App=ChargePointInstant, _o=app, _sc=MapActivity, _si=1315616320171567843, Global_Config_Region=NA-US, Analytics_Reporting_Version=15, Launch_Source=Google Play}], name=API_Station_List, timestampInMillis=1628780202844}]

08-12 20:26:50.594 9848 9848 D FirebaseCrashlytics: Crashlytics is handling uncaught exception “java.lang.RuntimeException: Test Crash” from thread main 08-12 20:26:50.722 9848 9887 D FirebaseCrashlytics: Closing open sessions. 08-12 20:26:50.722 9848 9887 D FirebaseCrashlytics: Closing session: 611536A2007F-0001-2678-4433F083327D 08-12 20:26:50.722 9848 9887 D FirebaseCrashlytics: Collecting session parts for ID 611536A2007F-0001-2678-4433F083327D 08-12 20:26:50.722 9848 9887 D FirebaseCrashlytics: Session 611536A2007F-0001-2678-4433F083327D has fatal exception: true 08-12 20:26:50.722 9848 9887 D FirebaseCrashlytics: Session 611536A2007F-0001-2678-4433F083327D has non-fatal exceptions: false 08-12 20:26:50.725 9848 9887 D FirebaseCrashlytics: Collecting SessionStart data for session ID 611536A2007F-0001-2678-4433F083327D 08-12 20:26:50.726 9848 9887 D FirebaseCrashlytics: Collecting SessionUser data for session ID 611536A2007F-0001-2678-4433F083327D 08-12 20:26:50.726 9848 9887 D FirebaseCrashlytics: Collecting SessionApp data for session ID 611536A2007F-0001-2678-4433F083327D 08-12 20:26:50.726 9848 9887 D FirebaseCrashlytics: Collecting SessionOS data for session ID 611536A2007F-0001-2678-4433F083327D 08-12 20:26:50.727 9848 9887 D FirebaseCrashlytics: Collecting SessionDevice data for session ID 611536A2007F-0001-2678-4433F083327D 08-12 20:26:50.729 9848 9887 D FirebaseCrashlytics: Removing session part files for ID 611536A2007F-0001-2678-4433F083327D 08-12 20:26:50.779 9848 9887 D FirebaseCrashlytics: Opening a new session with ID 611536B2030B-0002-2678-4433F083327D 08-12 20:26:50.782 9848 9887 D FirebaseCrashlytics: Crashlytics automatic data collection ENABLED by API. 08-12 20:26:50.788 9848 10007 D FirebaseCrashlytics: Logging Crashlytics event to Firebase 08-12 20:26:50.789 9848 10007 D FirebaseCrashlytics: Awaiting app exception callback from FA… 08-12 20:26:50.827 9848 9888 D FirebaseCrashlytics: Received Analytics message: 3 Bundle[{params=Bundle[{_o=clx, _r=1, _et=15052, _sc=MapActivity, _si=1315616320171567843, timestamp=1628780210594, fatal=1}], name=_ae, timestampInMillis=1628780210788}] 08-12 20:26:50.828 9848 10007 D FirebaseCrashlytics: App exception callback received from FA listener. 08-12 20:26:50.840 9848 9880 D TransportRuntime.SQLiteEventStore: Storing event with priority=HIGHEST, name=FIREBASE_CRASHLYTICS_REPORT for destination cct 08-12 20:26:50.851 9848 9880 D TransportRuntime.JobInfoScheduler: Scheduling upload for context TransportContext(cct, HIGHEST, MSRodHRwczovL2NyYXNobHl0aWNzcmVwb3J0cy1wYS5nb29nbGVhcGlzLmNvbS92MS9maXJlbG9nL2xlZ2FjeS9iYXRjaGxvZ1xBSXphU3lCcnBTWVQ0RkZMMDlyZUhKaTZIOUZZZGVpU25VVE92Mk0=) with jobId=511521345 in 1000ms(Backend next call timestamp 0). Attempt 1 08-12 20:26:50.853 9848 9888 D FirebaseCrashlytics: Received Analytics message: 3 Bundle[{params=Bundle[{_o=auto, _et=15086, _fr=1, _sc=MapActivity, _si=1315616320171567843}], name=_e, timestampInMillis=1628780210830}] 08-12 20:26:50.869 9848 9887 D FirebaseCrashlytics: Crashlytics report successfully enqueued to DataTransport: 611536A2007F000126784433F083327D 08-12 20:26:50.870 9848 9848 D FirebaseCrashlytics: Crashlytics completed exception processing. Invoking default exception handler. 08-12 20:26:50.872 9848 9887 D FirebaseCrashlytics: Attempting to send crash report at time of crash… 08-12 20:26:50.872 9848 9887 D FirebaseCrashlytics: Send to Reports Endpoint disabled. Removing Reports Endpoint report. 08-12 20:26:50.872 9848 9887 D FirebaseCrashlytics: Removing report at /data/user/0/com.coulombtech.debug/files/.com.google.firebase.crashlytics/fatal-sessions/611536A2007F-0001-2678-4433F083327D.cls

08-12 20:27:53.051 10019 10019 D FirebaseCrashlytics: Crashlytics automatic data collection ENABLED by API. 08-12 20:27:53.057 10019 10019 D FirebaseCrashlytics: Firebase Analytics is available. 08-12 20:27:53.060 10019 10051 D TransportRuntime.JobInfoScheduler: Scheduling upload for context TransportContext(cct, HIGHEST, MSRodHRwczovL2NyYXNobHl0aWNzcmVwb3J0cy1wYS5nb29nbGVhcGlzLmNvbS92MS9maXJlbG9nL2xlZ2FjeS9iYXRjaGxvZ1xBSXphU3lCcnBTWVQ0RkZMMDlyZUhKaTZIOUZZZGVpU25VVE92Mk0=) with jobId=511521345 in 1000ms(Backend next call timestamp 0). Attempt 1 08-12 20:27:53.062 10019 10019 D FirebaseCrashlytics: Firebase Analytics listener registered successfully. 08-12 20:27:53.085 10019 10019 D FirebaseCrashlytics: Reading cached settings… 08-12 20:27:53.096 10019 10019 D FirebaseCrashlytics: Loaded cached settings: {“settings_version”:3,“cache_duration”:86400,“features”:{“collect_logged_exceptions”:true,“collect_reports”:true,“collect_analytics”:false,“prompt_enabled”:false,“push_enabled”:false,“firebase_crashlytics_enabled”:false,“collect_anrs”:false},“app”:{“status”:“activated”,“update_required”:false,“report_upload_variant”:2,“native_report_upload_variant”:2},“fabric”:{“org_id”:“54e6b5d34dd4468000000328”,“bundle_id”:“com.coulombtech.debug”},“expires_at”:1628866596607} 08-12 20:27:53.097 10019 10019 D FirebaseCrashlytics: Returning cached settings. 08-12 20:27:53.100 10019 10019 D FirebaseCrashlytics: Mapping file ID is: 00000000000000000000000000000000 08-12 20:27:53.100 10019 10019 I FirebaseCrashlytics: Initializing Crashlytics 17.2.1 08-12 20:27:53.101 10019 10019 D FirebaseCrashlytics: Installer package name is: null 08-12 20:27:53.143 10019 10055 D FirebaseCrashlytics: Found previous crash marker. 08-12 20:27:53.146 10019 10019 D FirebaseCrashlytics: Exception handling initialization successful 08-12 20:27:53.158 10019 10055 D FirebaseCrashlytics: Found matching FID, using Crashlytics IID: 2196d372ed83412ab56602013cff2675 08-12 20:27:53.160 10019 10055 D FirebaseCrashlytics: Opening a new session with ID 611536F10092-0001-2723-4433F083327D 08-12 20:27:53.200 10019 10055 D FirebaseCrashlytics: Initialization marker file created. 08-12 20:27:53.201 10019 10055 D FirebaseCrashlytics: Registered Firebase Analytics event receiver for breadcrumbs 08-12 20:27:53.201 10019 10055 D FirebaseCrashlytics: Finalizing previously open sessions. 08-12 20:27:53.209 10019 10055 D FirebaseCrashlytics: Closing open sessions. 08-12 20:27:53.209 10019 10055 D FirebaseCrashlytics: Closing session: 611536B2030B-0002-2678-4433F083327D 08-12 20:27:53.209 10019 10055 D FirebaseCrashlytics: Collecting session parts for ID 611536B2030B-0002-2678-4433F083327D 08-12 20:27:53.209 10019 10055 D FirebaseCrashlytics: Session 611536B2030B-0002-2678-4433F083327D has fatal exception: false 08-12 20:27:53.209 10019 10055 D FirebaseCrashlytics: Session 611536B2030B-0002-2678-4433F083327D has non-fatal exceptions: false 08-12 20:27:53.209 10019 10055 D FirebaseCrashlytics: No events present for session ID 611536B2030B-0002-2678-4433F083327D 08-12 20:27:53.210 10019 10055 D FirebaseCrashlytics: Removing session part files for ID 611536B2030B-0002-2678-4433F083327D 08-12 20:27:53.211 10019 10055 D FirebaseCrashlytics: Closed all previously open sessions 08-12 20:27:53.212 10019 10055 D FirebaseCrashlytics: No reports are available. 08-12 20:27:53.213 10019 10055 D FirebaseCrashlytics: Initialization marker file removed: true 08-12 20:27:53.308 10019 10019 D FirebaseCrashlytics: Crashlytics automatic data collection ENABLED by API. 08-12 20:27:54.744 10019 10057 D FirebaseCrashlytics: Received Analytics message: 3 Bundle[{params=Bundle[{_o=auto, _sc=MapActivity, _si=2944307044656855024}], name=_vs, timestampInMillis=1628780274705}] 08-12 20:27:56.545 10019 10057 D FirebaseCrashlytics: Received Analytics message: 3 Bundle[{params=Bundle[{User_Type=InstantAppUser, Duration=1212.0, Status=SUCCESS, HTTP_Status_Code=200, Analytics_Reporting_App=ChargePointInstant, _o=app, _sc=MapActivity, _si=2944307044656855024, Global_Config_Region=NA-US, Analytics_Reporting_Version=15, Launch_Source=Google Play}], name=API_View_Station_Detail, timestampInMillis=1628780276487}] 08-12 20:27:56.676 10019 10057 D FirebaseCrashlytics: Received Analytics message: 3 Bundle[{params=Bundle[{User_Type=InstantAppUser, Duration=1232.0, Status=SUCCESS, HTTP_Status_Code=200, Analytics_Reporting_App=ChargePointInstant, _o=app, _sc=MapActivity, _si=2944307044656855024, Global_Config_Region=NA-US, Analytics_Reporting_Version=15, Launch_Source=Google Play}], name=API_Retrieve_Map_Data, timestampInMillis=1628780276587}] 08-12 20:27:58.322 10019 10057 D FirebaseCrashlytics: Received Analytics message: 3 Bundle[{params=Bundle[{User_Type=InstantAppUser, Duration=1311.0, Status=SUCCESS, HTTP_Status_Code=200, Analytics_Reporting_App=ChargePointInstant, _o=app, _sc=MapActivity, _si=2944307044656855024, Global_Config_Region=NA-US, Analytics_Reporting_Version=15, Launch_Source=Google Play}], name=API_Station_List, timestampInMillis=1628780278217}] 08-12 20:28:00.389 10019 10057 D FirebaseCrashlytics: Received Analytics message: 3 Bundle[{params=Bundle[{User_Type=InstantAppUser, Duration=1213.0, Status=SUCCESS, HTTP_Status_Code=200, Analytics_Reporting_App=ChargePointInstant, _o=app, _sc=MapActivity, _si=2944307044656855024, Global_Config_Region=NA-US, Analytics_Reporting_Version=15, Launch_Source=Google Play}], name=API_Station_List, timestampInMillis=1628780280160}]

`

Absolutely stuck on this one, I arrived here via Google search after following the Fabric migration guide exactly as documented here: https://firebase.google.com/docs/crashlytics/upgrade-sdk?platform=android&authuser=0

After following the guide above, crashes no longer report to the Firebase Console as they did previously under the Fabric implementation.

Thinking I must be missing a step, seeing all of the posts above concerning implementing “FirebaseCrashlytics.getInstance();” in MainActivity.java, I also consulted the official Firebase Crashlytics SDK getting started guide found here: https://firebase.google.com/docs/crashlytics/get-started?platform=android

To my confusion, there is NO documentation stating that Firebase Crashlytics has to be initialized anywhere in MainActivity.java. I added the initilization code in onCreate() in MainActivity.java anyway (hoping it was missing from the documentation), but it has no effect, crashes are still not reported in the Firebase Console.

To be thorough, I have tried the following with no differences:

• Downgraded Crashlytics and Analytics implementation dependencies to 17.10.0 and 17.5.0 respectively - no change
• Changed to the Firebase BoM, removed the versions from the Crashlytics and Analytics dependencies - no change
• Added “FirebaseCrashlytics.getInstance()” to onCreate() in MainActivity.java - no change

Again I confirm that crashes were being reported immediately before changing from Fabric Crashlytics to Firebase Crashlytics SDK; no other source code edits were made during this time and crashes have not shown up in over 2 hours time.

Need help please.

@bmirshafiee Did you make any force crash the app.

Then you need to open the app to see the crashes in crashlytics

Hi folks, the previous Firebase team member left the team a few months ago. I apologize that this issue got lost in the shuffle. We’re digging into it now. The good news is: 1) I was able to reproduce the problem using @smiljkov-pero’s example; and 2) there’s been some recent improvements to Crashlytics’ data transport layer (as well as improved debugging output) that should make this easier to solve than it would have been a few months ago.

The issue appears to be a race condition for very early launch crashes originating in the Application class. The workaround described by @syedaliammar512 did not work in my test case, though catching any exception thrown by the Application class’s onCreate() method and using the recordException() will work correctly from the Application class. This obviously isn’t a viable workaround for everyone so we’ll try to get the issue fixed ASAP.

I had this issue, and given that my devices are not running google play services I was worried that it would never work. Eventually my crashes did show up after following the upgrade guide, but with a few extra notes:

• I re-added the google-services.json file for my app, even though i’d done it once already
• I added <meta-data tools:node="remove" android:name="io.fabric.ApiKey"/> in my app’s manifest file, as the last tag in <application>

After doing that, I noticed that intentional crashes didn’t show up when thrown from the end of my Application classes’ onCreate. It seems that these might be too early in the app’s lifecycle to be properly logged? Seems like a bug, but moving the intentional crash to the end of my Activity’s onCreate did make a difference.

Additionally, I noticed that crash events wouldn’t show up in my Firebase dashboard until the app was opened again without immediately crashing, then it would seem to backfill the dashboard with all the past events that were missing.

If anyone’s having trouble I recommend trying the above to see if it helps.

Experiencing exactly the same issue and same log message. I don’t get my crashes reported since migrating to Firebase Crashlytics and following the migration docs step by step.

@bmirshafiee I believe we are having the same problem. I see the line… Send to Reports Endpoint disabled. Removing Reports Endpoint report.
Within your logs and I see the same thing and not seeing any reports in Crashlytics. Have you been able to find out why this is disabled?

@bmirshafiee Did you make any force crash the app.

Then you need to open the app to see the crashes in crashlytics

Yes I tried restarting it but still no crashes.

Any updates? I’m not getting crashes in the Crashlytics *Upgraded from fabric

project build.gradle

        // Add the Firebase Crashlytics Gradle plugin.
        classpath 'com.google.firebase:firebase-crashlytics-gradle:2.3.0'

app build.gradle

apply plugin: 'com.google.gms.google-services'
apply plugin: 'com.google.firebase.crashlytics'

    // Add the Firebase Crashlytics SDK.
    implementation 'com.google.firebase:firebase-crashlytics:17.2.1'

    // Recommended: Add the Google Analytics SDK.
    implementation 'com.google.firebase:firebase-analytics:17.5.0'

Firebase initialized in application class FirebaseCrashlytics.getInstance();

Logcat

Test Crash throw new RuntimeException("Test Crash");

App is crashing but the crash not reporting in Crashlytics

Replaced google-services.json with the latest one

Hi all, if you attempted to upgrade to the Firebase Crashlytics SDK from the Fabric SDK and you didn’t use this particular guide to do so, could you go through all of the instructions there, and then see if you’re able to get crashes through? It looks like you may have used the Get Started documentation to replace the Fabric SDK, and we’ve seen this result in some setups that haven’t fully removed the old Fabric implementation.

Hi Dear Kevin Yes actually before I open this issue I gone through this Documentation too and have read all the other issues that has been reported here related to not getting crash in firebase.

1.my app is migrated to androidx 2.I have downloaded google-services.json again and replace it in my module app.(no 2 at the end of google-services.json) 3.I have removed all fabric related lines in app’s root-level (project-level) build.gradle and have added “google-services” and “firebase-crashlytics-gradle” 4.in app-level build.gradle I have the two needed plugins. and fabric plugin is removed and I have the these exact dependencies here :

implementation 'com.google.firebase:firebase-crashlytics:17.2.1'
implementation 'com.google.firebase:firebase-analytics:17.5.0'

and this is Removed: implementation 'com.crashlytics.sdk.android:crashlytics:2.10.1

1. and at last I have removed: Fabric.with(this, Crashlytics()) and I have changed all Crashlytics.someAction() to FirebaseCrashlytics.getInstance()

and I have removed the fabric api key in manifest too.

but unfortunately still no result in firebase CrashLytics.

again I am sharing my logs with you :

09-09 09:20:58.706 26912 26912 D FirebaseCrashlytics: Crashlytics automatic data collection ENABLED by API.
09-09 09:20:58.706 26912 26912 D FirebaseCrashlytics: Firebase Analytics is available.
09-09 09:20:58.707 26912 26912 D FirebaseCrashlytics: Firebase Analytics listener registered successfully.
09-09 09:20:58.714 26912 26912 D FirebaseCrashlytics: Reading cached settings...
09-09 09:20:58.717 26912 26912 D FirebaseCrashlytics: Loaded cached settings: {"settings_version":3,"cache_duration":86400,"features":{"collect_logged_exceptions":true,"collect_reports":true,"collect_analytics":false,"prompt_enabled":false,"push_enabled":false,"firebase_crashlytics_enabled":false},"app":{"status":"activated","update_required":true,"report_upload_variant":2,"native_report_upload_variant":2},"fabric":{"org_id":"57943d135680c0485500000f","bundle_id":"org.company.app"},"expires_at":1599711990130}
09-09 09:20:58.717 26912 26912 D FirebaseCrashlytics: Returning cached settings.
09-09 09:20:58.718 26912 26912 D FirebaseCrashlytics: Mapping file ID is: 271eb7be38c94a5c9e5ef71f8c6847d5
09-09 09:20:58.719 26912 26912 I FirebaseCrashlytics: Initializing Crashlytics 17.2.1
09-09 09:20:58.720 26912 26912 D FirebaseCrashlytics: Installer package name is: null
09-09 09:20:58.734 26912 26912 D FirebaseCrashlytics: Exception handling initialization successful
09-09 09:20:58.754 26912 26962 D FirebaseCrashlytics: Found matching FID, using Crashlytics IID: 366bbb7ef2064c7d9255a965a8228eb6
09-09 09:20:58.755 26912 26962 D FirebaseCrashlytics: Opening a new session with ID 5F585F3202DE-0001-6920-AEAF7349CA60
09-09 09:20:58.765 26912 26962 I FirebaseCrashlytics: Crashlytics NDK initialization successful
09-09 09:20:58.780 26912 26912 D FirebaseCrashlytics: Crashlytics automatic data collection ENABLED by API.
09-09 09:20:58.780 26912 26912 D FirebaseCrashlytics: Crashlytics automatic data collection ENABLED by API.
09-09 09:20:58.787 26912 26962 D FirebaseCrashlytics: Initialization marker file created.
09-09 09:20:58.787 26912 26962 D FirebaseCrashlytics: Registered Firebase Analytics event receiver for breadcrumbs
09-09 09:20:58.787 26912 26962 D FirebaseCrashlytics: Finalizing previously open sessions.
09-09 09:20:58.796 26912 26962 D FirebaseCrashlytics: Closing open sessions.
09-09 09:20:58.796 26912 26962 D FirebaseCrashlytics: Closing session: 5F5859C802DC-0001-5392-AEAF7349CA60
09-09 09:20:58.796 26912 26962 D FirebaseCrashlytics: Collecting session parts for ID 5F5859C802DC-0001-5392-AEAF7349CA60
09-09 09:20:58.797 26912 26962 D FirebaseCrashlytics: Session 5F5859C802DC-0001-5392-AEAF7349CA60 has fatal exception: false
09-09 09:20:58.797 26912 26962 D FirebaseCrashlytics: Session 5F5859C802DC-0001-5392-AEAF7349CA60 has non-fatal exceptions: false
09-09 09:20:58.797 26912 26962 D FirebaseCrashlytics: No events present for session ID 5F5859C802DC-0001-5392-AEAF7349CA60
09-09 09:20:58.797 26912 26962 D FirebaseCrashlytics: Removing session part files for ID 5F5859C802DC-0001-5392-AEAF7349CA60
09-09 09:20:58.799 26912 26962 D FirebaseCrashlytics: Closed all previously open sessions
09-09 09:20:58.800 26912 26962 D FirebaseCrashlytics: No reports are available.
09-09 09:20:58.801 26912 26962 D FirebaseCrashlytics: Initialization marker file removed: true
09-09 09:20:58.968 26912 26958 D FirebaseCrashlytics: Received Analytics message: 3 Bundle[{params=Bundle[{_o=auto, _sc=ActSplash, _si=-2020819337397583197}], name=_vs, timestampInMillis=1599627058934}]
09-09 09:20:58.981 26912 26963 D FirebaseCrashlytics: Server says an update is required - forcing a full App update.
09-09 09:20:58.983 26912 26963 D FirebaseCrashlytics: Sending app info to https://update.crashlytics.com/spi/v1/platforms/android/apps/org.company.app
09-09 09:21:00.303 26912 26963 D FirebaseCrashlytics: Update app request ID: 786384ab52aee9eff76252ec38f08714
09-09 09:21:00.303 26912 26963 D FirebaseCrashlytics: Result was 204
09-09 09:21:00.889 26912 26958 D FirebaseCrashlytics: Received Analytics message: 3 Bundle[{params=Bundle[{_o=auto, _et=1885, _sc=ActSplash, _si=-2020819337397583197}], name=_e, timestampInMillis=1599627060817}]
09-09 09:21:00.983 26912 26958 D FirebaseCrashlytics: Received Analytics message: 3 Bundle[{params=Bundle[{_o=auto, _pc=ActSplash, _pi=-2020819337397583197, _sc=ActMain, _si=-2020819337397583196}], name=_vs, timestampInMillis=1599627060937}]
09-09 09:21:03.676 26912 26912 D FirebaseCrashlytics: Crashlytics is handling uncaught exception "java.lang.RuntimeException: Test Crash3" from thread main
09-09 09:21:03.783 26912 26962 D FirebaseCrashlytics: Closing open sessions.
09-09 09:21:03.783 26912 26962 D FirebaseCrashlytics: Closing session: 5F585F3202DE-0001-6920-AEAF7349CA60
09-09 09:21:03.783 26912 26962 D FirebaseCrashlytics: Collecting session parts for ID 5F585F3202DE-0001-6920-AEAF7349CA60
09-09 09:21:03.783 26912 26962 D FirebaseCrashlytics: Session 5F585F3202DE-0001-6920-AEAF7349CA60 has fatal exception: true
09-09 09:21:03.784 26912 26962 D FirebaseCrashlytics: Session 5F585F3202DE-0001-6920-AEAF7349CA60 has non-fatal exceptions: false
09-09 09:21:03.784 26912 26962 D FirebaseCrashlytics: Collecting SessionStart data for session ID 5F585F3202DE-0001-6920-AEAF7349CA60
09-09 09:21:03.785 26912 26962 D FirebaseCrashlytics: Collecting SessionUser data for session ID 5F585F3202DE-0001-6920-AEAF7349CA60
09-09 09:21:03.786 26912 26962 D FirebaseCrashlytics: Collecting SessionApp data for session ID 5F585F3202DE-0001-6920-AEAF7349CA60
09-09 09:21:03.786 26912 26962 D FirebaseCrashlytics: Collecting SessionOS data for session ID 5F585F3202DE-0001-6920-AEAF7349CA60
09-09 09:21:03.787 26912 26962 D FirebaseCrashlytics: Collecting SessionDevice data for session ID 5F585F3202DE-0001-6920-AEAF7349CA60
09-09 09:21:03.788 26912 26962 D FirebaseCrashlytics: Removing session part files for ID 5F585F3202DE-0001-6920-AEAF7349CA60
09-09 09:21:03.824 26912 26962 D FirebaseCrashlytics: Opening a new session with ID 5F585F370338-0002-6920-AEAF7349CA60
09-09 09:21:03.825 26912 26962 I FirebaseCrashlytics: Crashlytics NDK initialization successful
09-09 09:21:03.833 26912 26962 D FirebaseCrashlytics: Crashlytics automatic data collection ENABLED by API.
09-09 09:21:03.837 26912 27233 D FirebaseCrashlytics: Logging Crashlytics event to Firebase
09-09 09:21:03.837 26912 27233 D FirebaseCrashlytics: Awaiting app exception callback from FA...
09-09 09:21:03.887 26912 26962 D FirebaseCrashlytics: Crashlytics report successfully enqueued to DataTransport: 5F585F3202DE00016920AEAF7349CA60
09-09 09:21:03.888 26912 26958 D FirebaseCrashlytics: Received Analytics message: 3 Bundle[{params=Bundle[{_o=clx, _r=1, _et=2942, _sc=ActMain, _si=-2020819337397583196, timestamp=1599627063676, fatal=1}], name=_ae, timestampInMillis=1599627063837}]
09-09 09:21:03.888 26912 27233 D FirebaseCrashlytics: App exception callback received from FA listener.
09-09 09:21:03.889 26912 26912 D FirebaseCrashlytics: Crashlytics completed exception processing. Invoking default exception handler.
09-09 09:21:03.892 26912 26962 D FirebaseCrashlytics: Attempting to send crash report at time of crash...
09-09 09:21:03.892 26912 26962 D FirebaseCrashlytics: Send to Reports Endpoint disabled. Removing Reports Endpoint report.
09-09 09:21:03.893 26912 26962 D FirebaseCrashlytics: Removing report at /data/user/0/org.company.app/files/.com.google.firebase.crashlytics/fatal-sessions/5F585F3202DE-0001-6920-AEAF7349CA60.cls
09-09 09:21:05.096 27287 27287 D FirebaseCrashlytics: Crashlytics automatic data collection ENABLED by API.
09-09 09:21:05.096 27287 27287 D FirebaseCrashlytics: Firebase Analytics is available.
09-09 09:21:05.097 27287 27287 D FirebaseCrashlytics: Firebase Analytics listener registered successfully.
09-09 09:21:05.110 27287 27287 D FirebaseCrashlytics: Reading cached settings...
09-09 09:21:05.112 27287 27287 D FirebaseCrashlytics: Loaded cached settings: {"settings_version":3,"cache_duration":86400,"features":{"collect_logged_exceptions":true,"collect_reports":true,"collect_analytics":false,"prompt_enabled":false,"push_enabled":false,"firebase_crashlytics_enabled":false},"app":{"status":"activated","update_required":true,"report_upload_variant":2,"native_report_upload_variant":2},"fabric":{"org_id":"57943d135680c0485500000f","bundle_id":"org.company.app"},"expires_at":1599711990130}
09-09 09:21:05.112 27287 27287 D FirebaseCrashlytics: Returning cached settings.
09-09 09:21:05.114 27287 27287 D FirebaseCrashlytics: Mapping file ID is: 271eb7be38c94a5c9e5ef71f8c6847d5
09-09 09:21:05.114 27287 27287 I FirebaseCrashlytics: Initializing Crashlytics 17.2.1
09-09 09:21:05.116 27287 27287 D FirebaseCrashlytics: Installer package name is: null
09-09 09:21:05.127 27287 27317 D FirebaseCrashlytics: Found previous crash marker.
09-09 09:21:05.134 27287 27287 D FirebaseCrashlytics: Exception handling initialization successful
09-09 09:21:05.171 27287 27317 D FirebaseCrashlytics: Found matching FID, using Crashlytics IID: 366bbb7ef2064c7d9255a965a8228eb6
09-09 09:21:05.172 27287 27317 D FirebaseCrashlytics: Opening a new session with ID 5F585F390086-0001-6A97-AEAF7349CA60
09-09 09:21:05.198 27287 27287 D FirebaseCrashlytics: Crashlytics automatic data collection ENABLED by API.
09-09 09:21:05.198 27287 27287 D FirebaseCrashlytics: Crashlytics automatic data collection ENABLED by API.
09-09 09:21:05.199 27287 27317 I FirebaseCrashlytics: Crashlytics NDK initialization successful
09-09 09:21:05.218 27287 27317 D FirebaseCrashlytics: Initialization marker file created.
09-09 09:21:05.219 27287 27317 D FirebaseCrashlytics: Registered Firebase Analytics event receiver for breadcrumbs
09-09 09:21:05.219 27287 27317 D FirebaseCrashlytics: Finalizing previously open sessions.
09-09 09:21:05.230 27287 27318 D FirebaseCrashlytics: Server says an update is required - forcing a full App update.
09-09 09:21:05.254 27287 27317 D FirebaseCrashlytics: Closing open sessions.
09-09 09:21:05.267 27287 27317 D FirebaseCrashlytics: Closing session: 5F585F370338-0002-6920-AEAF7349CA60
09-09 09:21:05.267 27287 27317 D FirebaseCrashlytics: Collecting session parts for ID 5F585F370338-0002-6920-AEAF7349CA60
09-09 09:21:05.271 27287 27317 D FirebaseCrashlytics: Session 5F585F370338-0002-6920-AEAF7349CA60 has fatal exception: false
09-09 09:21:05.272 27287 27317 D FirebaseCrashlytics: Session 5F585F370338-0002-6920-AEAF7349CA60 has non-fatal exceptions: false
09-09 09:21:05.272 27287 27317 D FirebaseCrashlytics: No events present for session ID 5F585F370338-0002-6920-AEAF7349CA60
09-09 09:21:05.272 27287 27317 D FirebaseCrashlytics: Removing session part files for ID 5F585F370338-0002-6920-AEAF7349CA60
09-09 09:21:05.298 27287 27318 D FirebaseCrashlytics: Sending app info to https://update.crashlytics.com/spi/v1/platforms/android/apps/org.company.app
09-09 09:21:05.336 27287 27317 D FirebaseCrashlytics: Closed all previously open sessions
09-09 09:21:05.339 27287 27317 D FirebaseCrashlytics: No reports are available.
09-09 09:21:05.342 27287 27317 D FirebaseCrashlytics: Initialization marker file removed: true
09-09 09:21:06.639 27287 27318 D FirebaseCrashlytics: Update app request ID: 6146b93d2b5e5755c2a71fbea70e530b
09-09 09:21:06.639 27287 27318 D FirebaseCrashlytics: Result was 204

pay more attention to your custom exception handlers!!

    //当UncaughtException发生时会转入该函数来处理
    override fun uncaughtException(t: Thread?, e: Throwable?) {
        TLog.d(TAG, "uncaughtException $mDefaultHandler $e")
        if (!handleException(e) && mDefaultHandler != null) {
            //如果用户没有处理则让系统默认的异常处理器来处理
            mDefaultHandler?.uncaughtException(t, e)
  
        }

    }

Hi @OOTPAppsDotCom (and others!)

I’m sorry this has been frustrating for you! It’s definitely unexpected, and not at all what we want for folks. So allow me to clarify a few things, and hopefully we can determine why crashes aren’t showing up for you.

To my confusion, there is NO documentation stating that Firebase Crashlytics has to be initialized anywhere in MainActivity.java

This is because it shouldn’t be necessary. Calling FirebaseCrashlytics.getInstance() doesn’t do any initialization, it just gets you the instance of the FirebaseCrashlytics object so you can do things like call log and recordException. Crashlytics should initialize automatically under normal circumstances, with no code required from you.

You also should not need to call FirebaseCrashlytics.getInstance().setCrashlyticsCollectionEnabled(true), unless you have otherwise explicitly disabled it (e.g. with a manifest flag).

After following the guide above, crashes no longer report to the Firebase Console as they did previously under the Fabric implementation.

That is unexpected, though it seems you’re not the only one experiencing this! We have changed the mechanism by which the SDK sends reports, and we’ve seen that in aggregate, it’s more reliable than the previous mechanism in the Fabric SDK. It uses JobScheduler under the hood, and should send on a ~1 second delay after the crash occurs (whether or not you relaunch the app). But that certainly isn’t what you’re experiencing, and for that I apologize.

We are working hard to get to the bottom of this, and other folks further up the thread have posted logs that we’re digging into right now, but in the interest of gathering more data points, could you please enable debugging output for Crashlytics by running

adb shell setprop log.tag.FirebaseCrashlytics

run, crash, and relaunch your app, then send us the output of

adb logcat -s FirebaseCrashlytics TransportRuntime.SQLiteEventStore TransportRuntime.JobInfoScheduler TransportRuntime.CctTransportBackend TransportRuntime.DefaultScheduler

This should tell us exactly what’s going on with the SDK in your app.

What you should see in the logs is Crashlytics report successfully enqueued to DataTransport. This means that your crash report was captured and that it was enqueued for upload.

If you see Send to Reports Endpoint disabled. Removing Reports Endpoint report afterward, that is completely normal and not an error. It’s saying that the old upload mechanism is disabled, and the SDK is using the new one. It is definitely a bit confusing at the moment when you see that, and it’ll be cleaned up in a future release.

So if you can just let me know two things:

1. How you’ve instrumented the crash, and
2. What you see in the log output

I should be able to help further.

Again, I do apologize that this has been so frustrating. We’re focused on getting it sorted for you.

Hi Guys , I had the same issue make sure you have added the below line //add this line to your activity or Application class FirebaseCrashlytics.getInstance().setCrashlyticsCollectionEnabled(true)`