[Mono-bugs] [Bug 645234] New: Deploying widget causes Settings application to crash
bugzilla_noreply at novell.com
bugzilla_noreply at novell.com
Sun Oct 10 11:32:35 EDT 2010
https://bugzilla.novell.com/show_bug.cgi?id=645234
https://bugzilla.novell.com/show_bug.cgi?id=645234#c0
Summary: Deploying widget causes Settings application to crash
Classification: Mono
Product: MonoDroid
Version: unspecified
Platform: Other
OS/Version: Other
Status: NEW
Severity: Major
Priority: P5 - None
Component: Runtime
AssignedTo: mkestner at novell.com
ReportedBy: gshackles at gmail.com
QAContact: mono-bugs at lists.ximian.com
Found By: ---
Blocker: ---
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US)
AppleWebKit/534.7 (KHTML, like Gecko) Chrome/7.0.517.24 Safari/534.7
I created a very basic widget and deployed it to my emulator. After deploying,
I try to pull up the list of Widgets so I can add it, and it results in the
Settings application crashing:
E/AndroidRuntime( 267): java.lang.RuntimeException: Unable to start activity
ComponentInfo{com.android.settings/com.android.settings.AppWidgetPickActivity}:
java.lang.NullPointerException
E/AndroidRuntime( 267): at
android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2496)
E/AndroidRuntime( 267): at
android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2512)
E/AndroidRuntime( 267): at
android.app.ActivityThread.access$2200(ActivityThread.java:119)
E/AndroidRuntime( 267): at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:1863)
E/AndroidRuntime( 267): at
android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 267): at android.os.Looper.loop(Looper.java:123)
E/AndroidRuntime( 267): at
android.app.ActivityThread.main(ActivityThread.java:4363)
E/AndroidRuntime( 267): at java.lang.reflect.Method.invokeNative(Native
Method)
E/AndroidRuntime( 267): at
java.lang.reflect.Method.invoke(Method.java:521)
E/AndroidRuntime( 267): at
com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:860)
E/AndroidRuntime( 267): at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:618)
E/AndroidRuntime( 267): at dalvik.system.NativeStart.main(Native
Method)
E/AndroidRuntime( 267): Caused by: java.lang.NullPointerException
E/AndroidRuntime( 267): at
com.android.settings.ActivityPicker$IconResizer.createIconThumbnail(ActivityPicker.java:364)
E/AndroidRuntime( 267): at
com.android.settings.ActivityPicker$PickAdapter$Item.<init>(ActivityPicker.java:226)
E/AndroidRuntime( 267): at
com.android.settings.AppWidgetPickActivity.putAppWidgetItems(AppWidgetPickActivity.java:185)
E/AndroidRuntime( 267): at
com.android.settings.AppWidgetPickActivity.putInstalledAppWidgets(AppWidgetPickActivity.java:226)
E/AndroidRuntime( 267): at
com.android.settings.AppWidgetPickActivity.getItems(AppWidgetPickActivity.java:207)
E/AndroidRuntime( 267): at
com.android.settings.ActivityPicker.onCreate(ActivityPicker.java:98)
E/AndroidRuntime( 267): at
com.android.settings.AppWidgetPickActivity.onCreate(AppWidgetPickActivity.java:63)
E/AndroidRuntime( 267): at
android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1047)
E/AndroidRuntime( 267): at
android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2459)
E/AndroidRuntime( 267): ... 11 more
---
I'm attaching a sample project for reproducing the problem. Basically, it's
just a widget that does nothing but display some text when it loads up. As a
test, I implemented the same widget in Java and it worked correctly. There is
a dummy activity in there so that the project will build (see
https://bugzilla.novell.com/show_bug.cgi?id=645213).
Reproducible: Always
Steps to Reproduce:
1. Build/deploy the attached project to the emulator
2. Try to open the list of widgets you can add to a home screen
Actual Results:
Settings application crashes
Expected Results:
The Settings application should load, display the new widget, and allow you to
add it to the home screen.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
More information about the mono-bugs
mailing list