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.
Related
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 have an app on Google Play Store using Fabric Crashlytics and
Fabric SDK is not currently accepted and will continue to report your application problem until November 15, 2020. On this date, the Fabric SDK and old versions of the Firebase Crashlytics SDK will stop sending crashes for your app.(https://firebase.google.com/docs/crashlytics/get-started)
I do not want to upgrade to Firebase because I do not use this function and keep current app version available on Google Play Store.
If so, does my application have a problem when Fabric shuts down all services, does it crash due to a failure to connect to the Fabric server?
After November 15th, any apps still using the Fabric SDK will stop reporting crashes/non fatals. Any apps still using the Fabric SDK will continue to work, the Fabric SDK will just fail silently in the background, and not report any crash data.
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.
What I want?
I have an Android App that I want to upload to Fabric Beta.
How do I want it ?
I want to upload my Android App to Fabric Beta using Fastlane.
What goes wrong ?
After running my fastlane fastlane beta command, I get a nice report that everything is fine and I should see my app on Fabric dashboard:
[16:06:57]: Uploading the build to Crashlytics Beta. Time for some ☕️.
[[16:07:03]: Build successfully uploaded to Crashlytics Beta 🌷
[[16:07:03]: Visit https://fabric.io/_/beta to add release notes and notify testers.
But when I go https://fabric.io/_/beta, my app DOES NOT appear there !
What else did I try?
Tried the official integration doc. Installed the Fabric plugin on Android Studio.Logged in with my credentials,selected my app bundle identifier and always get throwed to credentials screen from the "All Kits" screen.Looks like a bug to me.Didn't find solution for that anywhere.
Did I try to integrate Fabrik SDK by hand and run the app ?
Yes I did, and the app still didn't appear in the Fabric dashboard.Didn't see any related errors in the logcat.
What about uploading using Gradle Plugin?
That one was tricky because I had to fix numerous errors and provide fabric.properties file with my credentials, but eventually got a promising message :
Task :application:crashlyticsUploadDistributionGoogleProdStagingAlpha
Uploading /Users/yanbraslavsky/booking-app/application/build/outputs/apk/googleProd/stagingAlpha/application-google-prod-stagingAlpha.apk to Crashlytics...
BUILD SUCCESSFUL in 6s
And still no app in the Fabric dashboard.
What do I want now?
I have an Android App that I want to upload to Fabric Beta...
Fabric/Firebaser here -
This issue was solved over the Fabric support channel! When attempting to upload a Beta distribution to Fabric, first make sure that the app is onboarded properly (visible on your dashboard at fabric.io). If it isn't, the above can happen where you still get a successful upload result without being able to view the distribution.
If you've included all the Fabric dependencies and are still having trouble seeing the app on your dashboard, try running a clean of the project, then building, waiting some time, and running the app. If you still can't see the app after a few minutes, reach out to the Fabric support address with your package name/bundle ID.
Also make sure that your build.gradle is properly configured if you have multiple build configurations. In this particular app, the issue was in the applicationIdSuffix of one of the build configurations. Finally, check that you've used the correct API key and build secret from the Fabric organization settings - this ensures that you have permission to upload the Beta distribution and puts it in the right place.
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.