显示在`Thread.setDefaultUncaughtExceptionHandler`对话(S

当我的Android应用程序抛出一个异常，我想说明一个自定义对话框，告诉用户有什么不对的事，所以我用Thread.setDefaultUncaughtExceptionHandler设置一个全球性的异常处理程序：

public class MyApplication extends Application {

    @Override
    public void onCreate() {
        super.onCreate();

        Thread.setDefaultUncaughtExceptionHandler(new Thread.UncaughtExceptionHandler() {
            @Override
            public void uncaughtException(Thread thread, final Throwable ex) {
                AlertDialog.Builder builder = new AlertDialog.Builder(getApplicationContext());
                builder.setTitle("There is something wrong")
                        .setMessage("Application will exit：" + ex.toString())
                        .setPositiveButton("OK", new DialogInterface.OnClickListener() {

                            @Override
                            public void onClick(DialogInterface dialog, int which) {
                                // throw it again
                                throw (RuntimeException) ex;
                            }
                        })
                        .show();
            }
        });
    }

}

但我发现它有抛出的任何异常， AlertDialog不会出现，取而代之的是，应用程序块，一段时间后，它会显示一个系统对话框：

X app is not responding. Would you like to close it?
Wait  |  OK

我现在应该怎么做？

UPDATE

日志：

11-16 12:54:16.017: WARN/WindowManager(90): Attempted to add window with non-application token WindowToken{b38bb6a8 token=null}.  Aborting.

这似乎错误是来自new AlertDialog.Builder(getApplicationContext());

但是，这是一个异常处理Application子类，我怎么可以设置一个活动实例呢？

Answer 1:

你不能从这里做任何UI操作。刚开始另一个活动/闪屏。通过额外的意图表示崩溃，并在该活动显示对话框。

    /*
     * (non-Javadoc)
     * 
     * @see
     * java.lang.Thread.UncaughtExceptionHandler#uncaughtException(java.
     * lang.Thread, java.lang.Throwable)
     */
    @Override
    public void uncaughtException(Thread t, final Throwable e) {
        StackTraceElement[] arr = e.getStackTrace();
        final StringBuffer report = new StringBuffer(e.toString());
        final String lineSeperator = "-------------------------------\n\n";
        report.append(DOUBLE_LINE_SEP);
        report.append("--------- Stack trace ---------\n\n");
        for (int i = 0; i < arr.length; i++) {
            report.append( "    ");
            report.append(arr[i].toString());
            report.append(SINGLE_LINE_SEP);
        }
        report.append(lineSeperator);
        // If the exception was thrown in a background thread inside
        // AsyncTask, then the actual exception can be found with getCause
        report.append("--------- Cause ---------\n\n");
        Throwable cause = e.getCause();
        if (cause != null) {
            report.append(cause.toString());
            report.append(DOUBLE_LINE_SEP);
            arr = cause.getStackTrace();
            for (int i = 0; i < arr.length; i++) {
                report.append("    ");
                report.append(arr[i].toString());
                report.append(SINGLE_LINE_SEP);
            }
        }
        // Getting the Device brand,model and sdk verion details.
        report.append(lineSeperator);
        report.append("--------- Device ---------\n\n");
        report.append("Brand: ");
        report.append(Build.BRAND);
        report.append(SINGLE_LINE_SEP);
        report.append("Device: ");
        report.append(Build.DEVICE);
        report.append(SINGLE_LINE_SEP);
        report.append("Model: ");
        report.append(Build.MODEL);
        report.append(SINGLE_LINE_SEP);
        report.append("Id: ");
        report.append(Build.ID);
        report.append(SINGLE_LINE_SEP);
        report.append("Product: ");
        report.append(Build.PRODUCT);
        report.append(SINGLE_LINE_SEP);
        report.append(lineSeperator);
        report.append("--------- Firmware ---------\n\n");
        report.append("SDK: ");
        report.append(Build.VERSION.SDK);
        report.append(SINGLE_LINE_SEP);
        report.append("Release: ");
        report.append(Build.VERSION.RELEASE);
        report.append(SINGLE_LINE_SEP);
        report.append("Incremental: ");
        report.append(Build.VERSION.INCREMENTAL);
        report.append(SINGLE_LINE_SEP);
        report.append(lineSeperator);

        Log.e("Report ::", report.toString());
        Intent crashedIntent = new Intent(BaseActivity.this, SplashActivity.class);
        crashedIntent.putExtra(EXTRA_CRASHED_FLAG,  "Unexpected Error occurred.");
        crashedIntent.addFlags(Intent.FLAG_ACTIVITY_CLEAR_WHEN_TASK_RESET);
        crashedIntent.addFlags(Intent.FLAG_ACTIVITY_CLEAR_TOP);
        startActivity(crashedIntent);

        System.exit(0);
        // If you don't kill the VM here the app goes into limbo

    }

另请参阅：

Android的UncaughtExceptionHandler的实例化一个AlertDialog休息

敬酒不显示的UncaughtExceptionHandler了

如何，如果这是主线程崩溃开始从UncaughtExceptionHandler的活动？

我如何做到这一点：

我有延伸活性的BaseActivity，并在活动的的onCreate我设置的UncaughtExceptionHandler。我所有的活动，而不是延长活动的BaseActivity。

按键

你不能设置异常处理程序中Application.onCreate ，相反，你应该创建一个BaseActivity并设置它的onCreate的方法就可以了。
启动SplashActivity之后，我们应该调用System.exit(0)
我们不能抱错误实例分享给SplashActivity ，因为它会被破坏，取而代之的是，我们可以通过一些错误消息或坚持它在文件中。

Answer 2:

看来，所提供的解决方案不会（至少在Android 4.0及以上）工作。对于任何人谁可能会感兴趣，打开一个Activity或涉及某种形式的UI元素，如Dialogs是不可能的。经过一番研究，我意识到，可以提供最大是Toast消息通知日志传送到服务器。可选一个SharedPreferences可以用来指示应用程序崩溃，并且在应用程序重新启动，一个Dialog可以根据显示SharedPreferences属性值，并从那里提供先前捕获的异常（显然阿克拉使用相同的方法）：

public class FirstAc extends Activity{
    @Override
    protected void onCreate(Bundle savedInstanceState) {

        super.onCreate(savedInstanceState);
        setContentView();

        sharedPrefValue = pref.getBoolean("DID_APP_CRASH", false);
        if(sharedPrefValue)
           dialog.show();
    }
}

异常可以保存为一个字符串时，应用程序会与下面的代码片段崩溃：

StringWriter sw = new StringWriter();
PrintWriter pw  = new PrintWriter(sw);
exception.printStackTrace(pw);
String stStr = sw.toString();
prefEditor.putString("EXCEPTION_CAUGHT", stStr);

综上所述，为了实现未捕获的异常到远程服务器创建一个自定义UncaughtExceptionHandler ，最重要的保持为默认的参考UncaughtExceptionHandler 。而不是通过调用突然关闭VM System.exit()更合理，让Android的处理异常进行自定义操作之后。我喜欢上设置异常处理程序Application方面：

public class CustomApp extends Application {

    @Override
    public void onCreate() {

        super.onCreate();
        Thread.setDefaultUncaughtExceptionHandler(new CustomExceptionHandler(this));
    }
}

内CustomExceptionHandler执行自定义行为后，让Android为处理在默认方式除外：

public class CustomExceptionHandler implements UncaughtExceptionHandler {

    private CustomApp                _app;
    private UncaughtExceptionHandler _defaultEH; 

    public YolbilExceptionHandler(YolbilApp ac){

        _defaultEH = Thread.getDefaultUncaughtExceptionHandler();
        _app = ac;
    }

    @Override
    public void uncaughtException(Thread thread, final Throwable ex) {

        Toast.makeText(_app, "Delivering log...", Toast.LENGTH_LONG).show();
        // obtain the Exception info as a String
        StringWriter sw = new StringWriter();
        PrintWriter pw  = new PrintWriter(sw);
        ex.printStackTrace(pw);
        String exStr    = sw.toString();
        ExceptionServer.getInstance().deliverMessageAsync(exStr, _app);
        _defaultEH.uncaughtException(thread, ex);
    }

}

这里是一个样本如何异步邮件传递到服务器：

public void deliverMessageAsync(final String msg, final YolbilApp app){

    new Thread(new Runnable() {

        @Override
        public void run() {

            HttpClient httpclient = new DefaultHttpClient();
            HttpPost httppost = new HttpPost(SERVER_ADDR); 
            try {
                Looper.prepare();
                Toast.makeText(app, R.string.msg_delivering_log, Toast.LENGTH_LONG).show();
                httppost.setHeader("Content-Type","application/x-www-form-urlencoded;charset=UTF-8");                   
                httpclient.execute(httppost); 
                Toast.makeText(app, "Log delivered ...", Toast.LENGTH_SHORT).show();
                Looper.loop();
            } catch (ClientProtocolException e) {
                e.printStackTrace();
            } catch (IOException e) {
                e.printStackTrace();
            }
        }
    }).start();
}

文章来源: Show a dialog in `Thread.setDefaultUncaughtExceptionHandler`