Develop Reference

App doesn't start when deployed on the market

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.

Fabric doesn't report fatal crashes on android

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.

How can I know whether user installed my .apk failed or successed?

Android will send a broadcast if the .apk install successful ,such as replaced,removed and added, but How can I get an message about .apk install failed?

This might help..
ACRA is a library enabling Android Application to automatically post their crash reports to a report server. It is targeted to android applications developers to help them get data from their applications when they crash or behave erroneously.Check this link for more...
https://github.com/ACRA/acra

Why dont you try integrating Google new Analytics feature "Firebase Analytics" into your app. Its simple and provides lots of information and Statistics about your App after user installation.
Its Firebase crashing reports Fatal and Non-Fatal crashes and also provides detailed information such as the device on which the crash occurred, the version of your app, the line number in which the crash happened and also the reason for the crash.
For more reference https://firebase.google.com/docs/analytics/ refer this documentation.

1 use the adb method install the apk
2 do the "adb install ..." in your code
3 return the status result if faile this is return like INSTALL_FAILED_OLDER_SDK INSTALL_FAILED_ALREADY_EXISTS INSTALL_FAILED_INVALID_APK
hope this is useful

Flurry Analytics causing App Not Responding on Android App

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.

Crashlytics on Android - can't capture logcat

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.