I have a little problem that I was hoping someone could give me some insight.
Sometimes, when a user updates my application from the market (from one version to another), they receive a VerifyError when the application starts. This happens to a random class; you can use part of the application, and then move on to another action in the application that causes it to explode. This happens only once; as soon as Dalvik pulls him out of his system, he will never happen again.
Since this happens only once per update (and most of the time, and not at all), this is admittedly a minor issue, but I think it reflects badly on my application, so if anyone has any ideas , it would be great.
Stack traces don't seem so useful as they always happen elsewhere (which confuses me even more). Here is an example of one of them:
java.lang.VerifyError: com.mypackage.myapp.package.SomeClass at java.lang.Class.newInstanceImpl(Native Method) at java.lang.Class.newInstance(Class.java:1472) at android.app.Instrumentation.newActivity(Instrumentation.java:1097) at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2255) at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2371) at android.app.ActivityThread.access$1800(ActivityThread.java:118) at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1759) at android.os.Handler.dispatchMessage(Handler.java:99) at android.os.Looper.loop(Looper.java:123) at android.app.ActivityThread.main(ActivityThread.java:4077) at java.lang.reflect.Method.invokeNative(Native Method) at java.lang.reflect.Method.invoke(Method.java:521) at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:782) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:540) at dalvik.system.NativeStart.main(Native Method)
source share