I have been using ACRA for reporting my crashes with my Android app but have noticed something odd recently where analytics reported crashes, but ACRA was not reporting anything.
I decided to try Crashlytics and was able to get it going with Eclipse with no problems and then forced a crash to confirm the integration was working. When I looked at the crash report on the Crashlytics site I could not find any reference to the logcat output.
Does Crashlytics have the ability to capture logcat? I could not find any reference to this capability on their website.
Related
I have an app that works on my device while debugging on Android Studio. It works too when I generate the apk copy it to my phone and install it from there. But it doesn't work anymore if i install it from the market.
I just have an error message "Unfortunately, xxxxx has stopped". I checked the crash report in Google Play Console but I have 0 crash, at least for now... Is there a way to get some crash log or some clue to debug this ?
Install crashlytics or firebase crash dependencies and you'll be able to see the crash logs on their consoles. If you don't want that, you yourself can override the Thread.UncaughtexceptionHandler and set your custom handler as the default handler. Just Google how to do that as it's a lengthy thing to explain here.
Also if you are using proguard, firebase crash will need other configurations apart from just adding the dependency. Crashlytics handles this on its own.
Does Firebase Crash reporting support NDK / C++ in the latest version?
Has anybody tested it and how are the results?
Firebase Crash Reporting currently does not support NDK/native code. The team recommends use of Crashlyics (acquired by Google) for NDK crash reporting.
Firebase Crash Reporting automatically generates reports for fatal errors (or uncaught exceptions). However, you can also generate reports in instances where you catch an exception but still want to report the occurrence. To report such an error, you can follow the steps listed on official Doc :
Some time You got an email from google Firebase to your registered email address to solve out bug
only supports collecting Java crashes (on Android).
For more information look this blog
We build Android-based game Apps on the Cocos2d platform using C++ and JavaScript. App uses no internet.I can able to see the crash report when we use the android studio to debug. but how to catch the log/report when the app crashes on the mobile device when it's not connected to Computer.
Use crash reporter, which allows your to view crash-related information on the web when a crash occurs. It's easy to integrated into your project by reference each document.
You can use Crashlytics by Fabric (recommended)
The most powerful, yet lightest weight crash reporting solution. You can easily integrate with your app through gradle and get crash report.
Enable NDK crash reporting in your project, for more information check this thread.
BugSense
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.
i added crashlytics feature to my app but i got the following NullPointerException at:
com.crashlytics.android.answers.Answers.doInBackground(Answers.java:102)
The app does not crash so at least the app is safe... just wondering if anybody had the same issue
Thanks