blocks|key|1045272|text|我认为要在uncaughtException()方法中禁用该功能，请不要调用previousHandler.uncaughtException()，因为previousHandler是由|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1045273|previousHandler+=+Thread.getDefaultUncaughtExceptionHandler();|code-block|syntax|javascript|1045274|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

I think to disable that in your uncaughtException() method do not call previousHandler.uncaughtException() where previousHandler is set by

<pre><code>previousHandler = Thread.getDefaultUncaughtExceptionHandler();
</code></pre>

blocks|key|1260221|text|这应该就是您需要做的全部工作。(确保之后导致进程停止--事情可能处于不确定的状态。)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1260222|首先要检查的是Android处理程序是否仍在被调用。有可能您的版本正在被调用，但却致命地失败了，当system_server看到进程崩溃时，它会显示一个通用对话框。|1260223|在您的处理程序的顶部添加一些日志消息，以查看它是否到达那里。打印来自getDefaultUncaughtExceptionHandler的结果，然后抛出一个未捕获的异常以导致崩溃。密切关注logcat输出，看看发生了什么。|1260224|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

That should be all you need to do. (Make sure you cause the process to halt afterward -- things could be in an uncertain state.)

The first thing to check is whether the Android handler is still getting called. It's possible that your version is being called but failing fatally and the system_server is showing a generic dialog when it sees the process crash.

Add some log messages at the top of your handler to see if it's getting there. Print the result from getDefaultUncaughtExceptionHandler and then throw an uncaught exception to cause a crash. Keep an eye on the logcat output to see what's going on.

blocks|key|1260252|text|它不会工作，直到你调用|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1260253|android.os.Process.killProcess(android.os.Process.myPid());|code-block|syntax|javascript|1260254|在你的UncaughtExceptionHandler的末尾。|1260255|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

It doesn't work until you call

<pre><code>android.os.Process.killProcess(android.os.Process.myPid());
</code></pre>

at the very end of your UncaughtExceptionHandler.

blocks|key|1045410|text|我很久以前就发布了用于自定义处理安卓崩溃的简单solution。这有点老生常谈，但它适用于所有Android版本(包括棒棒糖)。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1045411|首先是一个小小的理论。在Android中使用未捕获的异常处理程序时，主要问题是主线程(也称为UI)中抛出的异常。这就是为什么。当应用程序启动时，系统调用准备并启动应用程序Main+looper的ActivityThread.main方法：|1045412|public+static+void+main(String[]+args)+{
++…
++…
++++Looper.prepareMainLooper();
++…
++++Looper.loop();
++++throw+new+RuntimeException("Main+thread+loop+unexpectedly+exited");
}|code-block|syntax|javascript|1045413|主循环负责处理发布在UI线程中的消息(包括与UI呈现和交互相关的所有消息)。如果在UI线程中抛出异常，它将被您的异常处理程序捕获，但是由于您的loop()方法已用完，您将无法向用户显示任何对话框或活动，因为没有人为您处理UI消息。|style|CODE|1045414|建议的解决方案非常简单。我们自己运行Looper.loop方法，并用try-catch代码块包围它。当捕获到异常时，我们会根据需要对其进行处理(例如，启动我们的自定义报告活动)，然后再次调用Looper.loop方法。|1045415|下面的方法演示了这种技术(应该从Application.onCreate侦听器中调用)：|1045416|private+void+startCatcher()+{
++++UncaughtExceptionHandler+systemUncaughtHandler+=+Thread.getDefaultUncaughtExceptionHandler();

++++//+the+following+handler+is+used+to+catch+exceptions+thrown+in+background+threads
++++Thread.setDefaultUncaughtExceptionHandler(new+UncaughtHandler(new+Handler()));

++++while+(true)+{
++++++++try+{
++++++++++++Looper.loop();
++++++++++++Thread.setDefaultUncaughtExceptionHandler(systemUncaughtHandler);
++++++++++++throw+new+RuntimeException("Main+thread+loop+unexpectedly+exited");
++++++++}+catch+(Throwable+e)+{
++++++++++++showCrashDisplayActivity(e);
++++++++}
++++}
}|1045417|如您所见，未捕获的异常处理程序仅用于后台线程中抛出的异常。下面的处理程序捕获这些异常并将它们传播到UI线程：|1045418|static+class+UncaughtHandler+implements+UncaughtExceptionHandler+{

++++private+final+Handler+mHandler;

++++UncaughtHandler(Handler+handler)+{
++++++++mHandler+=+handler;
++++}

++++public+void+uncaughtException(Thread+thread,+final+Throwable+e)+{
++++++++mHandler.post(new+Runnable()+{
++++++++++++public+void+run()+{
++++++++++++++++throw+new+BackgroundException(e);
++++++++++++}
++++++++});
++++}
}|1045419|在我的GitHub存储库中提供了一个使用此技术的示例项目：https://github.com/idolon-github/android-crash-catcher|1045420|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/7639113/648313|1|http://developer.android.com/reference/android/os/Looper.html#getMainLooper()|2|http://grepcode.com/file/repository.grepcode.com/java/ext/com.google.android/android/4.2_r1/android/app/ActivityThread.java#ActivityThread.main%2528java.lang.String%255B%255D%2529|3|https://github.com/idolon-github/android-crash-catcher^0|N|8|0|0|2D|B|1|2P|J|2|0|0|1Z|6|0|I|B|2N|B|0|G|K|0|0|0|0|T|1I|3|0^^$0|@$1|2|3|4|5|6|7|1E|8|@]|9|@$A|1F|B|1G|1|1H]]|C|$]]|$1|D|3|E|5|6|7|1I|8|@]|9|@$A|1J|B|1K|1|1L]|$A|1M|B|1N|1|1O]]|C|$]]|$1|F|3|G|5|H|7|1P|8|@]|9|@]|C|$I|J]]|$1|K|3|L|5|6|7|1Q|8|@$A|1R|B|1S|M|N]]|9|@]|C|$]]|$1|O|3|P|5|6|7|1T|8|@$A|1U|B|1V|M|N]|$A|1W|B|1X|M|N]]|9|@]|C|$]]|$1|Q|3|R|5|6|7|1Y|8|@$A|1Z|B|20|M|N]]|9|@]|C|$]]|$1|S|3|T|5|H|7|21|8|@]|9|@]|C|$I|J]]|$1|U|3|V|5|6|7|22|8|@]|9|@]|C|$]]|$1|W|3|X|5|H|7|23|8|@]|9|@]|C|$I|J]]|$1|Y|3|Z|5|6|7|24|8|@]|9|@$A|25|B|26|1|27]]|C|$]]|$1|10|3|-4|5|6|7|28|8|@]|9|@]|C|$]]]|11|$12|$5|13|14|15|C|$16|17]]|18|$5|13|14|15|C|$16|19]]|1A|$5|13|14|15|C|$16|1B]]|1C|$5|13|14|15|C|$16|1D]]]]

I posted the simple <a href="https://stackoverflow.com/a/7639113/648313">solution</a> for custom handling of Android crashes a long ago. It's a little hacky however it works on all Android versions (including the Lollipop).

First a little bit of theory. The main issues when you use uncaught exception handler in Android come with the exceptions thrown in the main (aka UI) thread. And here is why. When the app starts system calls <a href="http://grepcode.com/file/repository.grepcode.com/java/ext/com.google.android/android/4.2_r1/android/app/ActivityThread.java#ActivityThread.main%28java.lang.String%5B%5D%29" rel="noreferrer">ActivityThread.main</a> method which prepares and starts the <a href="http://developer.android.com/reference/android/os/Looper.html#getMainLooper()" rel="noreferrer">Main looper</a> of your app:

<pre><code>public static void main(String[] args) {
 …
 …
 Looper.prepareMainLooper();
 …
 Looper.loop();
 throw new RuntimeException("Main thread loop unexpectedly exited");
}
</code></pre>

Main looper is responsible for processing messages posted in the UI thread (including all messages related to UI rendering and interaction). If an exception is thrown in the UI thread it will be caught by your exception handler, but since you're out of <code>loop()</code> method you won't be able to show any dialog or activity to the user as there's no one left to process UI messages for you.

The proposed solution is quite simple. We run <code>Looper.loop</code> method by our own and surround it with try-catch block. When an exception is caught we process it as we want (for example start our custom report activity) and call <code>Looper.loop</code> method again. 

The following method demonstrates this technique (it should be called from the <code>Application.onCreate</code> listener): 

<pre><code>private void startCatcher() {
 UncaughtExceptionHandler systemUncaughtHandler = Thread.getDefaultUncaughtExceptionHandler();

 // the following handler is used to catch exceptions thrown in background threads
 Thread.setDefaultUncaughtExceptionHandler(new UncaughtHandler(new Handler()));

 while (true) {
 try {
 Looper.loop();
 Thread.setDefaultUncaughtExceptionHandler(systemUncaughtHandler);
 throw new RuntimeException("Main thread loop unexpectedly exited");
 } catch (Throwable e) {
 showCrashDisplayActivity(e);
 }
 }
}
</code></pre>

As you can see the uncaught exception handler is used only for the exceptions thrown in background threads. The following handler catches those exceptions and propagates them to the UI thread:

<pre><code>static class UncaughtHandler implements UncaughtExceptionHandler {

 private final Handler mHandler;

 UncaughtHandler(Handler handler) {
 mHandler = handler;
 }

 public void uncaughtException(Thread thread, final Throwable e) {
 mHandler.post(new Runnable() {
 public void run() {
 throw new BackgroundException(e);
 }
 });
 }
}
</code></pre>

An example project which uses this technique is available on my GitHub repo: <a href="https://github.com/idolon-github/android-crash-catcher" rel="noreferrer">https://github.com/idolon-github/android-crash-catcher</a>

I want to set a global uncaught exception handler for all the threads in my Android application. So, in my <code>Application</code> subclass I set an implementation of <code>Thread.UncaughtExceptionHandler</code> as default handler for uncaught exceptions.

<pre><code>Thread.setDefaultUncaughtExceptionHandler(
 new DefaultExceptionHandler(this));
</code></pre>

In my implementation, I am trying to display an <code>AlertDialog</code> displaying appropriate exception message.

However, this doesn't seem to work. Whenever, an exception is thrown for any thread which goes un-handled, I get the stock, OS-default dialog ("Sorry!-Application-has-stopped-unexpectedly dialog").

What is the correct and ideal way to set a default handler for uncaught exceptions?

Ideal way to set global uncaught exception Handler in Android

Android

GitHub

我想为我的Android应用程序中的所有线程设置一个全局未捕获的异常处理程序。因此，在我的Application子类中，我将Thread.UncaughtExceptionHandler的一个实现设置为未捕获异常的默认处理程序。Thread.setDefaultUncaughtExceptionHandler(    ...

问在Android中设置全局未捕获异常处理器的理想方式
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在Android中设置全局未捕获异常处理器的理想方式EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在Android中设置全局未捕获异常处理器的理想方式
EN