Unfortunately, MyApp has stopped - no error logs in logcat

Question

Every once in a while I get:

Unfortunately, MyApp has stopped.

Problem is easy to solve if you have some logs, but in my case logcat has absolutely no message of error (it has normal messages published by my app and other exceptions are shown there but not this one which causes this app has stopped).

Is there any chance I can solve this problem?

The good thing is I can quite easily reproduce it, thus I'm trying to put as many information I can to logcat and then investigate what happened.

I have ACRA up and running (other exceptions are caught by it but not this app has stopped).

When it happens my app is not visible and there are some things happendnig in IntentService. My app is tracking geofences and the app has stopped happens only on HTC M8 when I switch on and off Location in phone Settings. I've tested on different phones and it does not happen on LG G3, Nexus 5, Moto G, LG Swift L9.

Answer 1

• Did you try to run LogCat in command-line? You might be able to see the error. Android LogCat in command-line
• If your using Eclipse as IDE, try checking your filters for LogCat. You may accidently not displaying errors in LogCat.
• Try finding the error via the Debugger. Place breakpoints to places where you suggest the error to be.

Answer 2

In my case logcat was filtered. You can change filter in Android Monitor -> logcat -> Bottom right corner, change filter to No Filters. It will show all errors.