NoClassDefFoundError的:android.app.ANRManagerProxy [英] NoClassDefFoundError: android.app.ANRManagerProxy

查看:1612
本文介绍了NoClassDefFoundError的:android.app.ANRManagerProxy的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

有谁知道为什么会这样?我看到这个崩溃报告我的应用程序,但我不知道它是什么。

  java.lang.NoClassDefFoundError的:android.app.ANRManagerProxy

主题:Binder_3,异常:java.lang.NoClassDefFoundError的:android.app.ANRManagerProxy
在android.app.ANRManagerNative.asInterface(ANRManagerNative.java:30)
在android.app.ANRManagerNative $ 1。创建(ANRManagerNative.java:94)
在android.app.ANRManagerNative $ 1。创建(ANRManagerNative.java:88)
在android.util.Singleton.get(Singleton.java:34)在android.app.ANRManagerNative.getDefault(ANRManagerNative.java:37)
在android.os.MessageLogger.dump(MessageLogger.java:253)
在android.app.ANRAppManager.dumpMessageHistory(的SourceFile:38)
在android.app.ActivityThread $ ApplicationThread.dumpMessageHistory(ActivityThread.java:1176)
在android.app.ApplicationThreadNative.onTransact(ApplicationThreadNative.java:609)
在android.os.Binder.execTransact(Binder.java:351)
在dalvik.system.NativeStart.run(本机方法)
 

解决方案

此错误就可以看到一小群设备(我没有一个名单,但他们往往是杂牌品牌)的固件开发,不知什么原因,删除了 ANRManagerProxy 从设备框架(我证实了这一点被追捕固件和反编译它自己)。

你能做的最好的就是尽力追捕任何可能的code这可能是锁定了线程并导致设备变得无响应,并尝试使用的AsyncTask 或类似的异步运行code和避免ANR。有问题的设备始终低端,所以你的code将需要更长的时间来运行,并有导致这种情况发生的几率较大。

我建议雨果作为调试方法的执行时间一个伟大的图书馆,以缩小重点关注其中大部分时间都是花在。这将有助于提高你的code为所有用户,以及减少有关崩溃的危险。

Does anyone know why this happens? I see this crash reported by my app but I have no idea what it is.

java.lang.NoClassDefFoundError: android.app.ANRManagerProxy

Thread: Binder_3, Exception: java.lang.NoClassDefFoundError: android.app.ANRManagerProxy 
at android.app.ANRManagerNative.asInterface(ANRManagerNative.java:30) 
at android.app.ANRManagerNative$1.create(ANRManagerNative.java:94) 
at android.app.ANRManagerNative$1.create(ANRManagerNative.java:88)
at android.util.Singleton.get(Singleton.java:34) at android.app.ANRManagerNative.getDefault(ANRManagerNative.java:37) 
at android.os.MessageLogger.dump(MessageLogger.java:253) 
at android.app.ANRAppManager.dumpMessageHistory(SourceFile:38) 
at android.app.ActivityThread$ApplicationThread.dumpMessageHistory(ActivityThread.java:1176) 
at android.app.ApplicationThreadNative.onTransact(ApplicationThreadNative.java:609) 
at android.os.Binder.execTransact(Binder.java:351) 
at dalvik.system.NativeStart.run(Native Method)

解决方案

This error can be seen on a small group of devices (I don't have a list, but they tend to be no-name brands) whose firmware developers, for unknown reasons, removed the ANRManagerProxy from the device framework (I confirmed this by hunting down a firmware and decompiling it myself).

The best you can do is try to hunt down any possible code which could be locking up the thread and causing the device to become nonresponsive, and try to use an AsyncTask or similar to run the code asynchronously and avoid the ANR. The devices in question are always low end, and so your code will take longer to run and have a greater chance of causing this to happen.

I'd suggest Hugo as a great library for debugging method execution times, in order to narrow your focus on where the most time is being spent. This will help improve your code for all users, as well as reducing the risk of the crash in question.

这篇关于NoClassDefFoundError的:android.app.ANRManagerProxy的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆