On May 26, 1:57 am, Dave Johnston 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 speci
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 wrote:
> I've seen problems like this. There appears to be no discernable
> rhyme and reason as to when a VerifyError will be thrown.
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 wrote:
>
Aha, appears to be the optimisation step of ProGuard!
-dave
On May 26, 8:05 am, Dave Johnston 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, ref
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
On May 18, 11:56 am, Mark Murphy wrote:
> On Wed, May 18, 2011 at 5:03 AM, Dave Johnston 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 det
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 "Andr
On Wed, May 18, 2011 at 5:03 AM, Dave Johnston 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, t
On May 17, 10:02 pm, fadden wrote:
> On May 16, 11:44 pm, Dave Johnston wrote:
> > java.lang.VerifyError: android.support.v4.app.FragmentManagerImpl
> > at android.support.v4.app.FragmentActivity.(SourceFile:87)
> > (...)
>
> The exception message is a bit lacking. There's more detail in the
> l
On May 16, 11:44 pm, Dave Johnston wrote:
> java.lang.VerifyError: android.support.v4.app.FragmentManagerImpl
> at android.support.v4.app.FragmentActivity.(SourceFile:87)
> (...)
The exception message is a bit lacking. There's more detail in the
logcat output.
--
You received this message beca
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 wrote:
> Aye I couldn't see anything odd either, glad I was on the right track!
>
> I'm trying to contact the user involved
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 wrote:
> Eyeballing th
12 matches
Mail list logo
