Firebase crashlytics not able to read crash reports #1559
Assignees
Labels
Comments
|
I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight. |
|
Any updates on this issue @TKBurner ? it currently prevents us from integrating firebase crashlytics into our app. Is there a workaround for that matter? maybe using an older version for the time being? |
|
I'm also seeing this stack trace. Android 10, same Firebase version. |
|
Thanks. Are you doing any cleanup on app shutdown or relaunch that would delete this file? Are you seeing this on all devices? |
|
I'm doing no cleanup of files on startup or shutdown. I currently only have 1 test device, but the reason I found the problem is because 3 users have emailed me saying they're experiencing crashes and none of those crashes have been reported. I have had 1 crash reported, so it's obviously working on some devices, but the ratio of crash emails to crash reports would suggest it's not working on more devices that it is working on. |
|
Hey folks - just wanted to chime in here and thank everyone for reporting this! Definitely seems strange. For those of you seeing it, are you able to reproduce it 100% of the time or does it seem to be transient? |
|
It's 100% of the time on my device. Pixel 3a. Unfortunately all my still working old devices have been adopted by the kids with Family Link accounts that Google wont let me run debug mode on, so I can't test on another device without inducing a meltdown. Would having an APK help you? Happy to link to one with a forced crash in. |
|
@WillCalderwood appreciate the offer! I think I have a sense of what might be happening here, so any corroborating evidence would be helpful. If you could - please enable debug logging on your device by running Thanks again! |
|
@mrwillis21 Sorry for the slow reply. I seem to have a test crash that's appeared on Crashlytics now. I've been trying to work out what's changed/what's going on. That said, I'm still getting the error. Here are the logcat files. One file with everything and one with just Firebase. Do you still want the APK after looking at this? If so, I'll send it over shortly. |
|
@WillCalderwood I'll take a look at those files - thanks! And if you're open to sending across the APK, I'm happy to try it out locally. |
|
@mrwillis21 I've sent a link to an apk via the contact form. Start it up and click "Play" to trigger a crash. |
|
Hi guys, I'm also having the same issue. Will highly appreciate a solution for that, thanks in advance. |
|
I was having a similar issue, I think what was happening for me was we were deleting all files in our app's file dir on logout which includes the firebase session file so next time there was a crash it was still looking for that file but couldn't find it.
Is that expected behavior or should it still retain crashes even if the session file is removed? |
|
I've managed to get another device - still Android 10 though. I get the same error. |
|
I have similar issue. It's persistent 100% of the cases (Nokia 5, Android 9, AS 4.0), I'm crashing app on startup, so don't delete any files. From logs I can see that Firebase Crashlytics is initializing OK: but then right after crash: |
|
For now I've rolled back to Fabric Crashlytics and it's reporting fine to Firebase console. |
|
@mirokolodii Thanks for the report - is this in your full app or in a test project? |
|
@mrwillis21 it's a production app, which I've tried to migrate from Fabric Crashlytics to Firebase. |
|
Hey everyone, it looks like there are a few different issues here, so I wanted to comment on the one that appears most commonly: If you're seeing a log entry for We'll patch this up for the next release so that optional file does not end up polluting the logs this way. For the other files that are missing (including the one from the original post in this thread), that still strikes me as strange, and I'm going to continue investigating. |
|
@moetouban Can I get a little more information about your app, and the context in which you're seeing this error? Is it a test crash? On startup? As @TKBurner had mentioned, are you clearing any app files at any point in your app lifecycle? |
|
@mrwillis21 Yes, exceptions are now being reported, so it wasn't the error in the logcat that was causing the problem, that was a red herring. I stumbled across a base class that was calling |
In my case reports are not sent though. |
|
@mirokolodii Would you be willing to post your logcat so I could take a look? Edit: That is, a full run of the app from startup through app crash. |
|
@mrwillis21 sure, I just need to revert back to Firebase lib first. |
|
@mrwillis21 Our application has a base module and a library module. I have added the dependency for firebase crashlytics in both modules. The crash is being triggered manually by me on a button press on login screen. There aren't any files being deleted. The logs are from running the app on emulator Pixel XL. |
|
|
For test purposes I've created another Firebase project and enabled the Crashlytics SDK there. Then configured the library in the app. Now reports are comming for crashes, but not when I report throwable manually. I have both ways working in the same setup with Fabric lib. Don't bother with Google Maps error in logs. |
|
@mrwillis21 what are your thoughts on this? Are posted logs useful? Right now I've removed the application from Firebase project, which has been migrated from Fabric, as well as migrated API in the app from Fabric to Firebase. So currently have fresh project with Crashlytics SDK enabled. I have two buttons - one crashes the app and another records exceptions. Unfortunately reports are not comming to the console. |
|
@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! |
|
@mrwillis21 it's a Play Store application, so can't really share the code. But is it possible that report is sent to wrong endpoint? I mean, the project was connected to two Firebase projects - one created by migrating from Fabric and where Crashlytics are used, another one created as a new one with other Firebase services enabled. I've removed the migrated one, so only one Firebase project exists now, which is connected to the application. |
|
@mrwillis21 is it possible to say from above logs, whether reports are uploaded correctly to the endpoint? If so, I'll then play with the Firebase project configuration, maybe adding SHA1 certificate fingerprint will help. |
mrwillis21
added a commit
that referenced
this issue
Jun 9, 2020
The user ID file will be missing if no user ID was set, so check if it exists before trying to read from it to avoid unnecessary error logging. Fixes one of the prevalent issues in #1559
mrwillis21
added a commit
that referenced
this issue
Jun 10, 2020
The user ID file will be missing if no user ID was set, so check if it exists before trying to read from it to avoid unnecessary error logging. Fixes one of the prevalent issues in #1559
|
Hi, even I facing the above issue.
|
|
Facing same issue |
@mirokolodii It is. As I'd mentioned before, you should see logs saying |
|
@Manu-Jindal based on your logs, it looks like your reports were uploaded, and you're experiencing the noisy log I'd mentioned earlier: #1559 (comment) @rd7773 based on your logs, you appear to also be seeing the noisy log: #1559 (comment), however, it looks like you may have data collection disabled for your app, which could be causing your crash reports not to be sent. Check this doc for how to configure that: https://firebase.google.com/docs/crashlytics/customize-crash-reports?platform=android |
Thanks @mrwillis21. Looks like removing one of the Firebase projects (the one migrated from Fabric, where Crashlytics was originally enabled) did the trick. Reports are coming now to the console, so issue is resolved. Thanks again. |
|
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: While with Firebase Crashlytics, if I disable the crash collection
|
This is correct, because the value is stored once set so that it persists across app launches. I'll take the feedback to the team that we should make sure this is clarified in the documentation. :) |
|
Hi folks, wanted to follow up on my previous comment and let you know that the latest release of Crashlytics (version 17.1.0) fixes the issue I mentioned here: #1559 (comment) (the Please try it out and let me know what you find. :) |
|
@mrwillis21 with the latest Crashlytics version I don't observe |
|
@mirokolodii Very good! I'm going to close this for now. If anyone else is still experiencing this error with the latest version, please feel free to open a new issue. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
[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:
with the firebase tag.
google group.
of the above categories, reach out to the personalized
Firebase support channel.
[REQUIRED] Step 2: Describe your environment
[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:
Relevant Code:
Just integrate the SDK
The text was updated successfully, but these errors were encountered: