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.
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 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 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.
I register on firebase and i followed the steps from Android studio everything looks fine, i found my app in firebase console and some stats for my app.
But the most important is to see when my app crash and i also want to get some info from variables before the crash, so from Android Studio again i add the the crash report but nothing happened, then i follow the steps on the site...still nothing.
When my app runs the test crash lines examples from firebase site it crashes also at firebase console at the crash section nothigh is appeared except the install in fabric & install in firebase options
I just needed to Update everything on Android Studio and make use of latest vesions.
I use fabric with crashlytics plugin
I have following code in the onCreate:
if (!BuildConfig.DEBUG)
Fabric.with(this, new Crashlytics());
I receive daily reports from fabric.What's strange is in the reports crash-free users is less than 100% but I don't see opened issues in the fabric dashboard.Moreover some crashes fabric does report with emails like:
A fatal issue was closed, but it popped up again in version 1.0.1
Does it normal behaviour?If not how can I receive reports for all crashes?
Mike from Fabric here. We don't notify on each crash as that would be overwhelming for many developers. We will notify you when an issue is new, regressed or in the stability digest. If you close an issue and then we detect that the crash happened in a different version where we haven't seen the crash before, then we will re-open it and mark it is a regression which is the notification you received.
On your Fabric dashboard, we default to open issues in the past 7 days with your app's top builds based on daily active users. If you don't see the issue in your dashboard, I'd recommend adjusting the filters to select all issues and all versions.