Welcome to OStack Knowledge Sharing Community for programmer and developer-Open, Learning and Share
Welcome To Ask or Share your Answers For Others

Categories

0 votes
537 views
in Technique[技术] by (71.8m points)

exception - Android UncaughtExceptionHandler that instantiates an AlertDialog breaks

As the title says, I have an UncaughtExceptionHandler set in my custom application class that gets set as the default when my application starts.

However, while not in the documentation I have read that you cannot instantiate a Dialog using MyApplication.this or getApplicationContext(). When I try to do it, I get a

WindowManager$BadTokenException...

I need an alternative. I have thought of making a new activity to compensate for this but would rather have it be an AlertDialog.

Is there a way I can get a valid context to my UncaughtExceptionHandler from inside MyApplication class?

See Question&Answers more detail:os

与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…
Welcome To Ask or Share your Answers For Others

1 Answer

0 votes
by (71.8m points)

I have read that you cannot instantiate a Dialog using MyApplication.this or getApplicationContext

Correct. The Application context is not especially useful for constructing UIs.

I have thought of making a new activity to compensate for this but would rather have it be an AlertDialog.

An AlertDialog is impossible in this case. For starters, only an activity can open a dialog, and none of your activities may be running (e.g., crash in a background service) and valid (e.g., you had one, but it's the one that crashed).

EDIT: Fixed previous paragraph to clear up confusion


与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…
Welcome to OStack Knowledge Sharing Community for programmer and developer-Open, Learning and Share
Click Here to Ask a Question

2.1m questions

2.1m answers

60 comments

57.0k users

...