Android Force Close Uncatchable Unreportable

Question

This week I released my second game project on the Android Market and immediately received several reports of 1 star due to the closure of power. I tested it on many phones and many emulators with zero problems. I absolutely do not understand how to act and seek advice.

I use Thread.setDefaultUncaughtExceptionHandler to catch and report exceptions and then gracefully close. The forces telling people do not reach this point, although this is the first thing that is indicated in the main application task designer, and everything is wrapped in try / catch throughout. They also report that there is no “Send Report” option in the forced close pop-up window (providing error reports for the developer console), so I absolutely don’t know what the problem is.

Uses Android 2.0 with Android: minSdkVersion = "5". Only permission is required - INTERNET.

(on the Android market “Fortunes of War FREE” if you want to test)

Answer 1

I am a little surprised by the missing "Send Report" button. What level of API did you build the game with? I usually create a level with a minimum API level to make sure that you are not using any API calls outside of this, but then go to the highest API level to use features such as "install on SD".

I am sure that there is at least one user who wrote you an email. Can you ask them to install LogCollector and send you a log?

Btw, , Thread.setDefaultUncaughtExceptionHandler, . ( , .)

Btw btw, . OpenGL, , GL?

Answer 2

, , , Android , UncaughtExceptionHandler .

:
UncaughtExceptionHander Thread.getDefaultUncaughtExceptionHandler ( Handler). Handler uncaughtException() , , defaultHandler.uncaughtException() .

, - :
, uncaughtException(). , ..

, try/catch, , , ?: P

Answer 3

, , . . , , , , .

Answer 4

, , , ( ), GSM-.

If you are transferring data in a user interface thread, this one is blocked and the system detects a block - but then it should end with "Do not respond", but then I saw one user report an error in the market in my application, which was such a slow reason.