Hi Mark,
I've implemented it and I got the crash report from the end user. See
details below.
The error report is VerifyError when the broadcastReceiver tries to
start the WakefulIntentService.
It happens on Cupcake/Samsumg. I've tested under emulator with 1.5
(minSDK=3) and it works perfect.
It seems that a WakefulIntentService field or class is not valid. What
could be the problem ?
The service was working before without extending WakefulIntentService
under the same device.
Device:
======
Package: my.application
Phone model: SPH-M900
Android Version: 1.5
Board: SPH-M900
Brand: Samsung
Device: SPH-M900
Display: CUPCAKE.CJ05
FingerPrint: Samsung/SPH-M900/SPH-M900/SPH-M900:1.5/CUPCAKE/CJ05:user/
ota-rel-keys,release-keys
ID: CUPCAKE
Model: SPH-M900
Product: Samsung
Total internal memory : 292724736
Available internal memory : 172212224
Stack:
=====
java.lang.VerifyError:
my.application.widget.UpdateServiceExtendingWakefulIntentService
at java.lang.Class.newInstanceImpl(Native Method)
at java.lang.Class.newInstance(Class.java:1472)
at android.app.ActivityThread.handleCreateService(ActivityThread.java:
2446)
at android.app.ActivityThread.access$2800(ActivityThread.java:112)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:
1744)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:123)
at android.app.ActivityThread.main(ActivityThread.java:3948)
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)
Thread:
======
Thread[main,5,main]
Any idea ?
Thanks.
On Mar 19, 5:52 pm, Mark Murphy <mmur...@commonsware.com> wrote:
> Derek wrote:
> > I'm also using your WakefulIntentService sample. It works fine in
> > emulator (all releases of Android). It seems to work fine on many
> > devices (HTC Magic, Nexus One ...). However, I get "Force Close"
> > complains from some users everytime the Alarm goes off. Some are under
> > 1.5 and other are under 2.1. Did you experiment such issue ? I don't
> > understand how it can generate a Force Close because I've used a try
> > {} catch (Throwable) in the handleIntent method.
>
> > Users are not able to tell me more about the issue. All they can say
> > is that the phone displays "Force Close" dialog evertime the Alarm
> > goes off. Using single Alarm (and set it after service run) instead
> > of repeating Alarm seems to fix the issue for these users.
>
> > Thanks for any help or advice.
>
> Use Flurry, DroidDrop, or similar tools to register a top-level
> exception handler via Thread.setDefaultUncaughtExceptionHandler(). You
> should be able to collect more information about what is going wrong.
>
> http://www.androidguys.com/2009/11/16/diagnosing-sporadic-errors/
>
> --
> Mark Murphy (a Commons
> Guy)http://commonsware.com|http://twitter.com/commonsguy
>
> _The Busy Coder's Guide to Android Development_ Version 3.0
> 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
To unsubscribe from this group, send email to
android-developers+unsubscribegooglegroups.com or reply to this email with the
words "REMOVE ME" as the subject.
