I am trying to integrate flurry analytics in my Android App. I followed all the steps mentioned here.
However FlurryAgent.init is converting all App crashes into "App Not responding". For e.g. if any of the child activity has bug such as null pointer exception , as soon as I uncomment "FlurryAgent.init" instead of app crashing, app stops responding.
My flurry init code is in extended Application class and is properly setup in manifest file as well.
Any suggestions on how to avoid this?
Contacted flurry support. Seems flurry 6.3 has bug about ANR and Flurry team is working on it. Used 6.2 and issue was resolved. Issue for 6.3 is for both compile dependency as well as jcenter jar files.
Related
I have already tried crashlytics but it is not supported.
this is the reply i got from their team
Thanks for reaching out on this and Crashlytics, or any part of Fabric, cannot be included in any SDK that is distributed to external apps. As you mentioned, this will cause conflicts for both the SDK and app. With that said, we do hope to support this in the future and if you'd like, I can keep you updated on that.
I have tried to set my own UncaughtExceptionHandler for this but the problem with that is my library also starts to catch error of the client's application module.
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.
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 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 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.