question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Firebase crashlytics not able to read crash reports

See original GitHub issue

[READ] Step 1: Are you in the right place?

Issues filed here should be about bugs in the code in this repository. If you have a general question, need help debugging, or fall into some other category using one of these other channels:

  • For general technical questions, post a question on StackOverflow with the firebase tag.
  • For general Firebase discussion, use the firebase-talk google group.
  • For help troubleshooting your application that does not fall under one of the above categories, reach out to the personalized Firebase support channel.

[REQUIRED] Step 2: Describe your environment

  • Android Studio version: 3.6.3_
  • Firebase Component: crashlytics___ (Database, Firestore, Storage, Functions, etc)
  • Component version: 17.0.0_

[REQUIRED] Step 3: Describe the problem

Just integrated firebase crashlytics into our app. Other services, like analytics and remote config are working fine. Invoking a crash from the app doesn’t show on the firebase console. After investigation I found that there is an issue with writing/reading the log files.

Steps to reproduce:

--------- beginning of main
--------- beginning of system
--------- beginning of crash
05-13 14:24:54.353 26520 26520 D FirebaseCrashlytics: Crashlytics is handling uncaught exception "java.lang.RuntimeException: Test Crash" from thread main
05-13 14:24:54.358 26520 26716 D FirebaseCrashlytics: Logging Crashlytics event to Firebase
05-13 14:24:54.364 26520 26716 D FirebaseCrashlytics: Background thread awaiting app exception callback from FA...
05-13 14:24:54.403 26520 26571 D FirebaseCrashlytics: No log data to include with this event.
05-13 14:24:54.431 26520 26718 D FirebaseCrashlytics: AnalyticsConnectorReceiver received message: 3 Bundle[{params=Bundle[{_o=clx, _r=1, _et=158031, _sc=LoginActivity, _si=-1937657330150563214, timestamp=1589397894353, fatal=1}], name=_ae, timestampInMillis=1589397894358}]
05-13 14:24:54.431 26520 26571 D FirebaseCrashlytics: Could not persist event for session 5EBC48E70257000167989D7960C5AFF3
05-13 14:24:54.431 26520 26571 D FirebaseCrashlytics: java.io.FileNotFoundException: /data/user/0/com.freshbooks.andromeda.debug/files/.com.google.firebase.crashlytics/report-persistence/sessions/5EBC48E70257000167989D7960C5AFF3/event0000000000_: open failed: ENOENT (No such file or directory)
05-13 14:24:54.431 26520 26571 D FirebaseCrashlytics:   at libcore.io.IoBridge.open(IoBridge.java:496)
05-13 14:24:54.431 26520 26571 D FirebaseCrashlytics:   at java.io.FileOutputStream.<init>(FileOutputStream.java:235)
05-13 14:24:54.431 26520 26571 D FirebaseCrashlytics:   at java.io.FileOutputStream.<init>(FileOutputStream.java:186)
05-13 14:24:54.431 26520 26571 D FirebaseCrashlytics:   at com.google.firebase.crashlytics.internal.persistence.CrashlyticsReportPersistence.writeTextFile(com.google.firebase:firebase-crashlytics@@17.0.0:461)
05-13 14:24:54.431 26520 26571 D FirebaseCrashlytics:   at com.google.firebase.crashlytics.internal.persistence.CrashlyticsReportPersistence.persistEvent(com.google.firebase:firebase-crashlytics@@17.0.0:152)
05-13 14:24:54.431 26520 26571 D FirebaseCrashlytics:   at com.google.firebase.crashlytics.internal.common.SessionReportingCoordinator.persistEvent(com.google.firebase:firebase-crashlytics@@17.0.0:249)
05-13 14:24:54.431 26520 26571 D FirebaseCrashlytics:   at com.google.firebase.crashlytics.internal.common.SessionReportingCoordinator.persistFatalEvent(com.google.firebase:firebase-crashlytics@@17.0.0:121)
05-13 14:24:54.431 26520 26571 D FirebaseCrashlytics:   at com.google.firebase.crashlytics.internal.common.CrashlyticsController$6.call(com.google.firebase:firebase-crashlytics@@17.0.0:400)
05-13 14:24:54.431 26520 26571 D FirebaseCrashlytics:   at com.google.firebase.crashlytics.internal.common.CrashlyticsController$6.call(com.google.firebase:firebase-crashlytics@@17.0.0:393)
05-13 14:24:54.431 26520 26571 D FirebaseCrashlytics:   at com.google.firebase.crashlytics.internal.common.CrashlyticsBackgroundWorker$3.then(com.google.firebase:firebase-crashlytics@@17.0.0:106)
05-13 14:24:54.431 26520 26571 D FirebaseCrashlytics:   at com.google.android.gms.tasks.zzf.run(Unknown Source:2)
05-13 14:24:54.431 26520 26571 D FirebaseCrashlytics:   at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
05-13 14:24:54.431 26520 26571 D FirebaseCrashlytics:   at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
05-13 14:24:54.431 26520 26571 D FirebaseCrashlytics:   at com.google.firebase.crashlytics.internal.common.ExecutorUtils$1$1.onRun(com.google.firebase:firebase-crashlytics@@17.0.0:60)
05-13 14:24:54.431 26520 26571 D FirebaseCrashlytics:   at com.google.firebase.crashlytics.internal.common.BackgroundPriorityRunnable.run(com.google.firebase:firebase-crashlytics@@17.0.0:27)
05-13 14:24:54.431 26520 26571 D FirebaseCrashlytics:   at java.lang.Thread.run(Thread.java:919)
05-13 14:24:54.431 26520 26571 D FirebaseCrashlytics: Caused by: android.system.ErrnoException: open failed: ENOENT (No such file or directory)
05-13 14:24:54.431 26520 26571 D FirebaseCrashlytics:   at libcore.io.Linux.open(Native Method)
05-13 14:24:54.431 26520 26571 D FirebaseCrashlytics:   at libcore.io.ForwardingOs.open(ForwardingOs.java:167)
05-13 14:24:54.431 26520 26571 D FirebaseCrashlytics:   at libcore.io.BlockGuardOs.open(BlockGuardOs.java:252)
05-13 14:24:54.431 26520 26571 D FirebaseCrashlytics:   at libcore.io.ForwardingOs.open(ForwardingOs.java:167)
05-13 14:24:54.431 26520 26571 D FirebaseCrashlytics:   at android.app.ActivityThread$AndroidOs.open(ActivityThread.java:7255)
05-13 14:24:54.431 26520 26571 D FirebaseCrashlytics:   at libcore.io.IoBridge.open(IoBridge.java:482)
05-13 14:24:54.431 26520 26571 D FirebaseCrashlytics:   ... 15 more
05-13 14:24:54.431 26520 26716 D FirebaseCrashlytics: App exception callback received from FA listener.
05-13 14:24:54.432 26520 26571 E FirebaseCrashlytics: Tried to write a fatal exception while no session was open.
05-13 14:24:54.438 26520 26571 D FirebaseCrashlytics: No open sessions to be closed.
05-13 14:24:54.439 26520 26571 D FirebaseCrashlytics: Opening a new session with ID 5EBC498601B6-0002-6798-9D7960C5AFF3
05-13 14:24:54.455 26520 26571 D FirebaseCrashlytics: Send via DataTransport disabled. Removing DataTransport reports.
05-13 14:24:54.457 26520 26520 D FirebaseCrashlytics: Crashlytics completed exception processing. Invoking default exception handler.

Relevant Code:

Just integrate the SDK

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Reactions:6
  • Comments:41 (14 by maintainers)

github_iconTop GitHub Comments

3reactions
mcaapcommented, Jun 12, 2020

Tip: I struggled with this issue when migrating from Fabric Crashlytics to Firebase Crashlytics. Even I could not see my manual Test crash reports in the console.

I believe this is what happens: Earlier Fabric used to always enable the crash collection every time the app opens and had to be explicitly disabled (CrashlyticsCore…Builder…disabled ) when not collecting crashes (say in Debug mode).

While with Firebase Crashlytics, if I disable the crash collection setCrashlyticsCollectionEnabled(false) and then if later I want to enable it, just commenting out the above line DOES NOT automatically start the collection process if the app has already been installed with ‘false’ flag before.

setCrashlyticsCollectionEnabled(true) needs to be explicitly called again!

1reaction
mrwillis21commented, Jun 5, 2020

@mirokolodii If you’ve got a test project set up that reproduces this issue, and can either publish it here on Github or send it through to https://firebase.google.com/support/troubleshooter/contact, that would be very helpful!

Read more comments on GitHub >

github_iconTop Results From Across the Web

Crashlytics troubleshooting and FAQ - Firebase
Not seeing crash-free users, breadcrumb logs, and/or velocity alerts · Make sure that you've enabled Google Analytics in your Firebase project. · Make...
Read more >
iOS Firebase Crashlytics not showing up crashes in Dashboard
Run your app from Xcode to install it on the simulator or your device · Press the Stop button in Xcode to quit...
Read more >
Firebase Crashlytics implementation in iOS app - Medium
Firebase Crashlytics is a lightweight, realtime crash reporter that helps us to track, prioritize, and fix stability issues that erode your app quality....
Read more >
Crashlytics - React Native Firebase
Crashlytics helps you to collect analytics and details about crashes and errors that occur in your app. It does this through three aspects:...
Read more >
Crash Report in Firebase Crashlytics - Javatpoint
By default, Firebase Crashlytics automatically collects crash reports for all app's users. We can use Opt-in Reporting by enabling more control over the...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found