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
Related
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.
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 have tried to find out from the documentation whether Google is supporting NDK C++ crashes in the newly released Firebase Crash Reporting. So far I have seen only Java crashes support.
Does any one know if Google is planning to add support in the near future.
In the initial beta version, Firebase Crash Reporting only supports collecting Java crashes (on Android).
Can't make any comments on future support, but its certainly an important area to consider for us.
After google's acquisition of fabric and their claim that crashlytics will become the main crash reporting tool for firebase; I would say that crashlytics is the way to go. Crashlytics also has good ndk support
I have an Android app which has a C++ library (via JNI).
Whenever the library crashes, it makes the app also crash, but I don't receive the crash on crashlytics.
Is this a limitation of Crashlytics. Does it only catches the uncaught Java exceptions?
Note: Any Java exception on main thread that makes the app crash is caught by Crashlytics, so I know it is working.
Now it's official, Crashlytics supports NDK!
If you read their blog:
http://www.crashlytics.com/blog/crashlytics-february-2015-update/
They say:
Latest Toys from Crashlytics Labs : Many of you who are building awesome apps with the NDK on Android have
requested support from Crashlytics. Since opening access to our beta
program in October, our Labs team has continued building this out and
enhancing its functionalities every day. We’re now working with top
companies who have already shipped their apps with our beta — so if
you haven’t test out our NDK beta yet, request early access here
You can get the beta access here:
http://try.crashlytics.com/secret/
Edit:
We been using the beta for some time now and it does the trick nicely. It's now out to the general public and you can read their blog post about it.
You're right that the Android SDK only catches Java exceptions at the moment. Twitter announced that Crashlytics has NDK support coming soon, though.
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.