I have Craslytics integrated in an app for long time. I'm using Proguard to obfuscate the code. Everything was working fine, I was getting my crash reports deobfuscated without problems.
Last week, I enabled the integration of Craslytics in Firebase and since then the crash reports are not being deobfuscated, neither in Crashlytics nor Firebase (I do get the crash reports in both places).
I'm using crashlytics:2.8.0 in production (I'll update to crashlytics:2.9.1 in next week's release). And I have all Proguard rules indicated in the docs (Configure ProGuard and DexGuard).
I've noticed that the release notes from crashlytics:2.9.0 say:
App teams who use both Fabric and Firebase can now link their apps and use Crashlytics within the Firebase console (requires Firebase Core, version 11.4.2+ recommended).
Does that means that I shouldn't have linked Crashlytics with Firebase before updating to crashlytics:2.9.1? Can that be the source of the problem?
Thanks for your help.
After updating Crashlytics from 2.8.0 to 2.9.1 I started to get deobfuscated crash reports again in both Crashlytics and Firebase.
Related
I have followed the steps on this firebase crashlytics upgrade guide and I have replaced all the code for recording crashes in my app. But I am still getting a warning in the firebase console that says "Please upgrade to the generally available Firebase Crashlytics SDK to continue receiving crash reports in the Firebase console after 15 November 2020".
Is there another step that I should do to upgrade.
I am also still receiving crashes from older versions of my app that are not upgraded to the newest SDK. Could this be why the warning is popping up on firebase?
After upgrade firebase libraries:
Test your Crashlytics implementation
Force a crash to test your implementation
val crashButton = Button(this)
crashButton.text = "Crash!"
crashButton.setOnClickListener {
throw RuntimeException("Test Crash") // Force a crash
}
addContentView(crashButton, ViewGroup.LayoutParams(
ViewGroup.LayoutParams.MATCH_PARENT,
ViewGroup.LayoutParams.WRAP_CONTENT))
Enable Crashlytics debug logging
adb shell setprop log.tag.FirebaseCrashlytics DEBUG
instead of enabling debug logging you can build a release version and Force a crash in the release apk to test your Crashlytics implementation
crash
After your Forced crash in release version, this message should be displayed in the firebase console
It may take up to five minutes for the report to appear in the
Firebase console
My application was using fabric. I was getting continuous message to upgrade to sdk before 15Nov 2020.
I followed same link
https://firebase.google.com/docs/crashlytics/upgrade-sdk?platform=android.
After 4-5 hours releasing it to my testing team. Firebase console updated to notify me that application is using latest sdk.
Step 1: Go to firebase console.
Step 2: select your project.
Step 3: Go to Crashlytics option from left menu.
STep4: you will get below page.
I am developing an android app in a company.
This app has used the Fabric library.
I can find the dependencies in the 'build.gradle' files.
And we could see the crash report in our Firebase Crashlytics console.
Recently, I changed the dependencies from the Fabric to Firebase Crashlytics.
// Remove the Fabric Crashlytics SDK.
implementation 'com.crashlytics.sdk.android:crashlytics:2.10.1'
// Add the Firebase Crashlytics SDK.
implementation 'com.google.firebase:firebase-crashlytics:17.1.1'
And I followed the migration guide documents.
Building the signing Apk success.
And I upload the APK into the PlayStore yesterday.
Today morning, when I check the Firebase Crashlytics console.
There were no crash reports related to the new version of APK.
(I couldn't find only old version's crash reports.)
But when I check it on PlayStore console, I can find some crash reports.
What should I do now?
When I run it on debug mode, I can find below logs.
2020-08-13 12:35:31.568 709-709/co.spoonme I/FirebaseCrashlytics: Initializing Crashlytics 17.1.1
And when I check the "Firebase > Latest Release" tab, I can find the new version.
This means that the new version is tracked by Firebase.
But only crash reports are not tracked... why......
Firebaser here -
Make sure that you've followed all the instructions in the migration guide, in case there are any old dependencies or things that you've accidentally left behind.
If you're still not able to get crash reports after creating and forcing a test crash, try enabling debug mode and forcing another test crash. After you relaunch, there should be some more logging in your logcat that tells you more about the state of Firebase initialization, and if the crash report has been successfully uploaded. If you're okay with sharing the logs, it would be a good idea to update your post with those logs for visibility.
I think it would also be helpful to see your build.gradle files and where you're initializing Firebase in your main app code.
I added firebase crashlytics to my app before two days ago .
Our app yesterday 10 times crashed this report i saw today in my play
console. But my firebase console not showing this data. what is the reason?
Firebase console now showing me progress bar continues, but is not showing any report.
At the time of adding firebase crashlytics to project i followed steps from official documentation from https://firebase.google.com/docs/crashlytics/get-started?authuser=0&platform=android
Crash reports are uploaded almost in real-time after your app crashes and relaunches. If you are still unable to see your crash reports, then likely your Crashlytics integration is off.
If you followed all of the documentation correctly that you linked, then you would need to contact Firebase support so they could take a look at your gradle files, and how you're calling Crashlytics in your app.
I have an app that was using fabric crashlytics. New version of this app will be using firebase service for crash logging, but I would like to have some visibility of current users (that are still on fabric sdk).
According to https://firebase.google.com/docs/crashlytics/get-started?platform=android :
The Fabric SDK is now deprecated and will continue reporting your app's crashes until November 15, 2020.
Where can I find these reports? I can't sign in to fabric dashboard anymore and they are not showing in firebase console.
firebaser here
Since the Fabric dashboard has been shut down, the crash reports from apps using the legacy SDKs are only visible in the Firebase console.
If you are having a hard time getting this to work, reach out to Firebase support for personalized help in troubleshooting.
I've an IOS app which is using Fabric Crashlytics. As you know:
The Fabric iOS and Android mobile apps will be sunset on November 30, 2018.
So I'm trying to migrate all existing data from Fabric's Crashlytics to Firebase. But I've seen this topic Migrate Fabric's Crashlystic data to Firebase, and Mike from Fabric recommended that we should not yet migrate now.
Here is the question:
At this moment, I'm linking Fabric with Firebase, and the data shows up in both place. What happens if one day Fabric shut down its Crashlytics service, will my crash report continues to show up on Firebase with current configuration?
Could someone give me a solution/answer for this case?
Thanks.
Mike from Firebase & Fabric here. I updated my other answer. That notice is only for the Fabric mobile apps available on the Play and App Stores. It does not affect the Fabric dashboard, Beta, or any other products. Your Crashlytics data in Fabric will continue to be processed until mid-2019 when Fabric is retired.
Once you link between Fabric and Firebase, data will flow into both dashboards. In early 2019, we plan on releasing a new SDK that is streamlined. Once you update to that future SDK, it will have the Fabric parts of the SDK removed which will make it smaller, but will then only send data to Firebase.