[android-developers] Re: v4 Fragments library VerifyError crash
On May 26, 1:57 am, Dave Johnston john...@gmail.com wrote: Aye, I'm going to try enabling/disabling certain optimisation passes and see if I can isolate the one causing this issue. Methods that are only referenced via reflection may be dropped as dead. If that's what's happening here, there's a way to specify them as not dead in the makefile. (See the proguard docs.) -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: v4 Fragments library VerifyError crash
I managed to extract a crash log. This crash also happens on the emulator: 05-26 06:57:08.516: ERROR/dalvikvm(339): Could not find method android.app.Activity.invalidateOptionsMenu, referenced from method android.support.v4.app.FragmentActivity.supportInvalidateOptionsMenu 05-26 06:57:08.516: WARN/dalvikvm(339): VFY: unable to resolve virtual method 124: Landroid/app/Activity;.invalidateOptionsMenu ()V 05-26 06:57:08.516: WARN/dalvikvm(339): VFY: rejecting opcode 0x6e at 0x0006 05-26 06:57:08.516: WARN/dalvikvm(339): VFY: rejected Landroid/ support/v4/app/FragmentActivity;.supportInvalidateOptionsMenu ()V 05-26 06:57:08.516: WARN/dalvikvm(339): Verifier rejected class Landroid/support/v4/app/FragmentActivity; 05-26 06:57:08.516: WARN/dalvikvm(339): Class init failed in newInstance call (Luk/co/johnsto/android/alf/activities/HomeActivity;) 05-26 06:57:08.526: DEBUG/AndroidRuntime(339): Shutting down VM 05-26 06:57:08.526: WARN/dalvikvm(339): threadid=3: thread exiting with uncaught exception (group=0x4001aa28) Only appears to occur in release builds. Any ideas? -dave On May 17, 7:44 am, Dave Johnston john...@gmail.com wrote: A user of mine is encountering a crash every time they start my application: java.lang.VerifyError: android.support.v4.app.FragmentManagerImpl at android.support.v4.app.FragmentActivity.init(SourceFile:87) (...) Their phone is a Sony Ericsson U20i (Xperia X10 Mini Pro) running Android 1.6. I understand the Fragments compatibility library supports Android 1.6, and thatVerifyErrorexceptions typically occur on outdated or unsupported systems, so would this error suggest the U20i isn't entirely compatible? Regards, Dave -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: v4 Fragments library VerifyError crash
Aha, appears to be the optimisation step of ProGuard! -dave On May 26, 8:05 am, Dave Johnston john...@gmail.com wrote: I managed to extract a crash log. This crash also happens on the emulator: 05-26 06:57:08.516: ERROR/dalvikvm(339): Could not find method android.app.Activity.invalidateOptionsMenu, referenced from method android.support.v4.app.FragmentActivity.supportInvalidateOptionsMenu 05-26 06:57:08.516: WARN/dalvikvm(339): VFY: unable to resolve virtual method 124: Landroid/app/Activity;.invalidateOptionsMenu ()V 05-26 06:57:08.516: WARN/dalvikvm(339): VFY: rejecting opcode 0x6e at 0x0006 05-26 06:57:08.516: WARN/dalvikvm(339): VFY: rejected Landroid/ support/v4/app/FragmentActivity;.supportInvalidateOptionsMenu ()V 05-26 06:57:08.516: WARN/dalvikvm(339): Verifier rejected class Landroid/support/v4/app/FragmentActivity; 05-26 06:57:08.516: WARN/dalvikvm(339): Class init failed in newInstance call (Luk/co/johnsto/android/alf/activities/HomeActivity;) 05-26 06:57:08.526: DEBUG/AndroidRuntime(339): Shutting down VM 05-26 06:57:08.526: WARN/dalvikvm(339): threadid=3: thread exiting with uncaught exception (group=0x4001aa28) Only appears to occur in release builds. Any ideas? -dave On May 17, 7:44 am, Dave Johnston john...@gmail.com wrote: A user of mine is encountering a crash every time they start my application: java.lang.VerifyError: android.support.v4.app.FragmentManagerImpl at android.support.v4.app.FragmentActivity.init(SourceFile:87) (...) Their phone is a Sony Ericsson U20i (Xperia X10 Mini Pro) running Android 1.6. I understand the Fragments compatibility library supports Android 1.6, and thatVerifyErrorexceptions typically occur on outdated or unsupported systems, so would this error suggest the U20i isn't entirely compatible? Regards, Dave -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: v4 Fragments library VerifyError crash
I've seen problems like this. There appears to be no discernable rhyme and reason as to when a VerifyError will be thrown. The only way to know is to run your code. If it only happens with the release build, I suspect a ProGuard optimization issue. On May 26, 3:05 pm, Dave Johnston john...@gmail.com wrote: I managed to extract a crash log. This crash also happens on the emulator: 05-26 06:57:08.516: ERROR/dalvikvm(339): Could not find method android.app.Activity.invalidateOptionsMenu, referenced from method android.support.v4.app.FragmentActivity.supportInvalidateOptionsMenu 05-26 06:57:08.516: WARN/dalvikvm(339): VFY: unable to resolve virtual method 124: Landroid/app/Activity;.invalidateOptionsMenu ()V 05-26 06:57:08.516: WARN/dalvikvm(339): VFY: rejecting opcode 0x6e at 0x0006 05-26 06:57:08.516: WARN/dalvikvm(339): VFY: rejected Landroid/ support/v4/app/FragmentActivity;.supportInvalidateOptionsMenu ()V 05-26 06:57:08.516: WARN/dalvikvm(339): Verifier rejected class Landroid/support/v4/app/FragmentActivity; 05-26 06:57:08.516: WARN/dalvikvm(339): Class init failed in newInstance call (Luk/co/johnsto/android/alf/activities/HomeActivity;) 05-26 06:57:08.526: DEBUG/AndroidRuntime(339): Shutting down VM 05-26 06:57:08.526: WARN/dalvikvm(339): threadid=3: thread exiting with uncaught exception (group=0x4001aa28) Only appears to occur in release builds. Any ideas? -dave On May 17, 7:44 am, Dave Johnston john...@gmail.com wrote: A user of mine is encountering a crash every time they start my application: java.lang.VerifyError: android.support.v4.app.FragmentManagerImpl at android.support.v4.app.FragmentActivity.init(SourceFile:87) (...) Their phone is a Sony Ericsson U20i (Xperia X10 Mini Pro) running Android 1.6. I understand the Fragments compatibility library supports Android 1.6, and thatVerifyErrorexceptions typically occur on outdated or unsupported systems, so would this error suggest the U20i isn't entirely compatible? Regards, Dave- Hide quoted text - - Show quoted text - -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: v4 Fragments library VerifyError crash
Aye, I'm going to try enabling/disabling certain optimisation passes and see if I can isolate the one causing this issue. -dave On May 26, 8:10 am, Zsolt Vasvari zvasv...@gmail.com wrote: I've seen problems like this. There appears to be no discernable rhyme and reason as to when a VerifyError will be thrown. The only way to know is to run your code. If it only happens with the release build, I suspect a ProGuard optimization issue. On May 26, 3:05 pm, Dave Johnston john...@gmail.com wrote: I managed to extract a crash log. This crash also happens on the emulator: 05-26 06:57:08.516: ERROR/dalvikvm(339): Could not find method android.app.Activity.invalidateOptionsMenu, referenced from method android.support.v4.app.FragmentActivity.supportInvalidateOptionsMenu 05-26 06:57:08.516: WARN/dalvikvm(339): VFY: unable to resolve virtual method 124: Landroid/app/Activity;.invalidateOptionsMenu ()V 05-26 06:57:08.516: WARN/dalvikvm(339): VFY: rejecting opcode 0x6e at 0x0006 05-26 06:57:08.516: WARN/dalvikvm(339): VFY: rejected Landroid/ support/v4/app/FragmentActivity;.supportInvalidateOptionsMenu ()V 05-26 06:57:08.516: WARN/dalvikvm(339): Verifier rejected class Landroid/support/v4/app/FragmentActivity; 05-26 06:57:08.516: WARN/dalvikvm(339): Class init failed in newInstance call (Luk/co/johnsto/android/alf/activities/HomeActivity;) 05-26 06:57:08.526: DEBUG/AndroidRuntime(339): Shutting down VM 05-26 06:57:08.526: WARN/dalvikvm(339): threadid=3: thread exiting with uncaught exception (group=0x4001aa28) Only appears to occur in release builds. Any ideas? -dave On May 17, 7:44 am, Dave Johnston john...@gmail.com wrote: A user of mine is encountering a crash every time they start my application: java.lang.VerifyError: android.support.v4.app.FragmentManagerImpl at android.support.v4.app.FragmentActivity.init(SourceFile:87) (...) Their phone is a Sony Ericsson U20i (Xperia X10 Mini Pro) running Android 1.6. I understand the Fragments compatibility library supports Android 1.6, and thatVerifyErrorexceptions typically occur on outdated or unsupported systems, so would this error suggest the U20i isn't entirely compatible? Regards, Dave- Hide quoted text - - Show quoted text - -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: v4 Fragments library VerifyError crash
On May 17, 10:02 pm, fadden fad...@android.com wrote: On May 16, 11:44 pm, Dave Johnston john...@gmail.com wrote: java.lang.VerifyError: android.support.v4.app.FragmentManagerImpl at android.support.v4.app.FragmentActivity.init(SourceFile:87) (...) The exception message is a bit lacking. There's more detail in the logcat output. Unfortunately, all automated crash reports are anonymous so that's all I've got! -dave -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
Re: [android-developers] Re: v4 Fragments library VerifyError crash
On Wed, May 18, 2011 at 5:03 AM, Dave Johnston john...@gmail.com wrote: Unfortunately, all automated crash reports are anonymous so that's all I've got! Hmmm... you might see if a third-party crash logger like ACRA has more smarts here. Since the additional details fadden is seeking are not in the exception, that information would have to be read out of LogCat, which is a pain and requires an extra permission, IIRC. But, if you can find a third-party solution that will grab all the VFY log messages as well, you might try switching to that. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy _The Busy Coder's Guide to Android Development_ Version 3.6 Available! -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
Re: [android-developers] Re: v4 Fragments library VerifyError crash
I've got a Mini Pro here (or will later today - it's out of the office at the moment). I'd be glad to take a look and give you more details from a dev perspective if it'd help. Contact me off-forum if so. String -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: v4 Fragments library VerifyError crash
On May 18, 11:56 am, Mark Murphy mmur...@commonsware.com wrote: On Wed, May 18, 2011 at 5:03 AM, Dave Johnston john...@gmail.com wrote: Unfortunately, all automated crash reports are anonymous so that's all I've got! Hmmm... you might see if a third-party crash logger like ACRA has more smarts here. Since the additional details fadden is seeking are not in the exception, that information would have to be read out of LogCat, which is a pain and requires an extra permission, IIRC. But, if you can find a third-party solution that will grab all the VFY log messages as well, you might try switching to that. Sorry, I should have said that I'm already using ACRA. I'll investigate a bit and see if I can squeeze it into providing more details in future. -dave -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: v4 Fragments library VerifyError crash
Aye I couldn't see anything odd either, glad I was on the right track! I'm trying to contact the user involved in the hoping of extracting more information and determine the root cause. Hopefully there's at least a simple workaround. -dave On May 17, 11:31 am, Mark Murphy mmur...@commonsware.com wrote: Eyeballing the source code, everything in the initializers for FragmentManagerImpl seems kosher. My best guess is that it is referring to some method that exists on real 1.6 and does not exist on the X10 Mini Pro. Unfortunately, those VerifyError reports are not terribly specific. On Tue, May 17, 2011 at 2:44 AM, Dave Johnston john...@gmail.com wrote: A user of mine is encountering a crash every time they start my application: java.lang.VerifyError: android.support.v4.app.FragmentManagerImpl at android.support.v4.app.FragmentActivity.init(SourceFile:87) (...) Their phone is a Sony Ericsson U20i (Xperia X10 Mini Pro) running Android 1.6. I understand the Fragments compatibility library supports Android 1.6, and that VerifyError exceptions typically occur on outdated or unsupported systems, so would this error suggest the U20i isn't entirely compatible? Regards, Dave -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -- Mark Murphy (a Commons Guy)http://commonsware.com|http://github.com/commonsguyhttp://commonsware.com/blog|http://twitter.com/commonsguy _Android Programming Tutorials_ Version 3.4 Available! -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: v4 Fragments library VerifyError crash
There was a guy here today from Sony Ericsson: http://groups.google.com/group/android-developers/browse_thread/thread/f5abf823a7ccfeef# On May 17, 8:15 pm, Dave Johnston john...@gmail.com wrote: Aye I couldn't see anything odd either, glad I was on the right track! I'm trying to contact the user involved in the hoping of extracting more information and determine the root cause. Hopefully there's at least a simple workaround. -dave On May 17, 11:31 am, Mark Murphy mmur...@commonsware.com wrote: Eyeballing the source code, everything in the initializers for FragmentManagerImpl seems kosher. My best guess is that it is referring to some method that exists on real 1.6 and does not exist on the X10 Mini Pro. Unfortunately, those VerifyError reports are not terribly specific. On Tue, May 17, 2011 at 2:44 AM, Dave Johnston john...@gmail.com wrote: A user of mine is encountering a crash every time they start my application: java.lang.VerifyError: android.support.v4.app.FragmentManagerImpl at android.support.v4.app.FragmentActivity.init(SourceFile:87) (...) Their phone is a Sony Ericsson U20i (Xperia X10 Mini Pro) running Android 1.6. I understand the Fragments compatibility library supports Android 1.6, and that VerifyError exceptions typically occur on outdated or unsupported systems, so would this error suggest the U20i isn't entirely compatible? Regards, Dave -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -- Mark Murphy (a Commons Guy)http://commonsware.com|http://github.com/commonsguyhttp://commonsware.com/blog|http://twitter.com/commonsguy _Android Programming Tutorials_ Version 3.4 Available!- Hide quoted text - - Show quoted text - -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: v4 Fragments library VerifyError crash
On May 16, 11:44 pm, Dave Johnston john...@gmail.com wrote: java.lang.VerifyError: android.support.v4.app.FragmentManagerImpl at android.support.v4.app.FragmentActivity.init(SourceFile:87) (...) The exception message is a bit lacking. There's more detail in the logcat output. -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
