Crashes not Showing in Firebase console After Removing Fabric #1944
Comments
|
I am also unable to receive crash in release app. When I run the app in debug mode, I can able to receive fatal errors. But I can't able to receive any crashes in debug or release. Shall I need to change anything here? I made the crash using the |
|
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 1.my app is migrated to androidx and this is Removed:
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 : |
|
@kevinkokomani I can able to get the crashes now. Works fine |
|
@nihp |
|
I am using |
|
@nihp funny I am using the exact same versions but still no results in Crashlytics |
|
@bmirshafiee Did you make any force crash the app. Then you need to open the app to see the crashes in crashlytics |
|
Any updates? I'm not getting crashes in the Crashlytics project build.gradle app build.gradle Firebase initialized in application class Logcat Test Crash App is crashing but the crash not reporting in Crashlytics Replaced |
|
Hi @AllwinJohnson could you please to check if you don't get any log about datatransfer cct like this: I found that this issue happens only when my app is built with DexGuard (in release). My gradle config looks like this: In my dexguard-rules.pro I also added: |
|
Hi @pablopatarca, I checked my log again but couldn't find anything related to FirebaseCrashlytics and I'm using proguard |
|
@AllwinJohnson that error is for the 17.1.0 version of Crashlytics but after upgrading to 17.2.1 version didn't you get any exception like the previous one? |
|
@pablopatarca I changed the version of crashlytics to again upgraded to And I'm not getting any exception after upgrading the sdk. |
|
Facing same issue after upgrading from Fabric to FirebaseCrashlytics. Problem solved after downgrading firebase-crashlytics version to 17.1.0 and now the crashes are reporting: current build.gradle: |
You are right @mrj48
Thanks guys! |
Yes I tried restarting it but still no crashes. |
|
Downgrading to 17.1.0 still not working.I have posted my logs in first comments, anyone see anything wrong with that? |
|
You can get crash with the 17.1.0 version. Did you removed all as per this doc and check the firebase initialization is done in your MainActivity.java file. Note: You need to force crash the app in any of your screen. Then you need to launch the app successfully. (i.e) if you make the app crash while launching the app itself it not give you the crash report. You need to launch the app successfully after you make a force crash. import must be like import com.google.firebase.crashlytics.FirebaseCrashlytics; |
|
We have same issue and find this block. The state always comes CreateReportRequest requestData = new CreateReportRequest(this.organizationId, this.googleAppId, report);
boolean shouldDeleteReport = true;
if (this.dataTransportState == DataTransportState.ALL) {
Logger.getLogger().d("Send to Reports Endpoint disabled. Removing Reports Endpoint report.");
} else if (this.dataTransportState == DataTransportState.JAVA_ONLY && report.getType() == Type.JAVA) {
Logger.getLogger().d("Send to Reports Endpoint for non-native reports disabled. Removing Reports Uploader report.");
} else {
boolean sent = this.createReportCall.invoke(requestData, dataCollectionToken);
Logger.getLogger().i("Crashlytics Reports Endpoint upload " + (sent ? "complete: " : "FAILED: ") + report.getIdentifier());
shouldDeleteReport = sent;
} |
|
@bmirshafiee |
|
The number of times I crashed the app while still receiving the same message ended up being reported on Firebase after hours. Either we still don't properly understand how long it takes for logs to show up, we don't know WHEN the logs are sent OR may be upgrading Android Studio to 4.1 helped. The console message |
|
I reported the problem to consultants and they are investigating. When If solutions was came, I will inform to you. |
|
Experiencing exactly the same issue and same log message. |
No still not working, I saw that by using in application class : |
Yes I've done all, but still no result. |
|
Hi guys! |
|
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:
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
...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: 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. With that said - sorry for the ranting but it's just being asked for - here are my logs, crashes are not reported: firebaseBomVersion = '25.12.0' LogCat filter with regex: (FirebaseCrashlytics|TransportRuntime.SQLiteEventStore|TransportRuntime.JobInfoScheduler|TransportRuntime.CctTransportBackend|TransportRuntime.DefaultScheduler) UPDATE: |
|
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 All, In (project-level) build.gradle:- repositories { } In your app-level build.Gradle Added Manifest - Application Class - Logs:- |
|
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 |
|
Crashes not Showing in Firebase console : I have tried many ways
Issue no 1: In 2 sample app I can see few report but when i purposily crash same app then I can't see report. Any Solution Please :) |
|
I am tired of trying to fix problems with this so reaching out. This occurred when I am trying to move to Gradle6.7.
When I start the application up Notice - Some more digging, going down to 17.1.0 -- the fatals are being logged but no crashes so far. |
|
Hallo all,
All of the crashes will be reported later with all correct data if the app on the same device starts to works well or if another crash is being triggered later in some of the activities of the application. @mrwillis21 Executing Executing It looks like that the jobscheduler times out for 100% of the cases when the crash is happening in the early start of the app. Please let me know if more detailed information is needed. |
|
Thanks very much @smiljkov-pero! This is really helpful. We're looking into this now. Anyone else that's seeing this issue, please post output of your |
|
Thank you @AllwinJohnson , you got it ! |
|
Hello @mrwillis21, do you have any updates on this issue? Thank you |
|
@smiljkov-pero We're currently investigating this issue and trying to determine potential solutions; however, it's quite difficult to reproduce. Can you describe exactly how/when you're crashing your app such that this reproduces 100% of the time? |
|
Also, to be clear, this issue should not result in losing crashes, @smiljkov-pero, it's only the upload that's getting stuck. Crash reports are still cached, and should be uploaded later, if the app opens successfully. Is this the case for your app? |
|
Hello @mrwillis21 I think I managed to reproduce the issue of crash not being reported on the early stage of the application like in the Application class Here is example project: https://github.com/smiljkov-pero/CrashExampleApp
when the crash later is moved later in the app journey then I was able to see both crashes with correct number of occurences. Please let me know if any additional information is needed. |
|
Using KTS |
|
Same issue here :
|
|
@mrwillis21
gradle - project
|
|
Hello @mrwillis21 Thank you |
|
@mrwillis21 Looking for some progress... 4 months later. Push notifications AND firebase crash analytics aren't working for me currently |
|
Dear all bro, this way working for me: create new app on firebase and add to my project. |
|
I had the same issue, i fixed it by adding this line of code FirebaseCrashlytics.getInstance().recordException(new Exception()); now it sends reports to my firebase dashboard. I hope it also works for you guys! |
|
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 |
|
@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. 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:50.594 9848 9848 D FirebaseCrashlytics: Crashlytics is handling uncaught exception "java.lang.RuntimeException: Test Crash" from thread main 08-12 20:27:53.051 10019 10019 D FirebaseCrashlytics: Crashlytics automatic data collection ENABLED by API. ` |
|
@mrwillis21 Hi, Im having the same problem. Crashes are not showing up on dashboard. I tried so many thing from upgrading to downgrading the version. Currently im on '17.1.0' and crashlytics gradle '2.2.0'.
I added these on the Application.class. When I insert Im trying to solve this for long. Below ill add the logs 09-20 21:06:40.875 18853 18853 D FirebaseCrashlytics: Firebase Analytics is available. |
|
crashlytics 18.2.3 is out: along with analytics 19.0.2 If you want to give it a shot. Still not a lot of luck from my end, but wanted to share just in case the update fixes the issue for someone else |
|
I am getting the: the "Persisting non-fatal event for session" occurrence, on android, creates an event file in: So after you restart the application, a report is created based on that event and then that report is sent to the firebase console. However, When I run my test crash function in the same place, but instead with a fatal crash: I'm using FYI, to get the verbose logs, run the command: to see the file system, run Can anyone confirm that an event is created with a test crash? ( |
|
Hi all, The Application crash race condition was fixed in Crashlytics 18.2.3, released in early October. Crashlytics crash reporting from Instant apps has never been officially supported. Crashes will be reported for full apps that have been upgraded from Instant apps, but we do not report crashes from Instant apps. Better Instant app support is a known feature request, but it is unprioritized at this time. I'm going to close this issue because I believe those two points cover the vast majority of the customer cases mentioned here. @petenathan42 If the problem you described a few weeks ago is persisting, can you open a new issue? I suspect your problem is unrelated to other customer problems in this ticket. |
and others
[REQUIRED] Step 2: Describe your environment
[REQUIRED] Step 3:
I have seen this message in my Firebase Crashlytics:
"Please upgrade to the generally available Firebase Crashlytics SDK to continue receiving crash reports in the Firebase console after 15 November 2020."
so I understand that I should remove fabric SDK as soon as possible from my app and publish it.
I saw in my code that I am still using this line :
Fabric.with(this, Crashlytics())for reporting my crashes.
I completely removed fabric SDK, and checked the documentation for setting up firebase and all is Done.
after creating crash in my app I didn't see any crashes in my firebase console.(have checked on several devices and nothing reported)
but the strange thing is that when I run the app on an emulator 'Pixel 2 API 29', crashes are reporting immediately to firebase console, but no report on crashes on real devices.
What could be the problem?
I have debug the crashes that are not being reported and here is the log :
here when I start the app:
and here when a crash happens:
The text was updated successfully, but these errors were encountered: