Is anyone else seeing a system crash and reboot when attempting to install an update for (aka re-install) an application in Android 1.6? I have an application that is triggering just that symptom and, according to the following exception trace recorded just before the crash, it seems related to the fact that I use the sharedUserId attribute in my manifest file...
10-07 13:47:30.567: ERROR/AndroidRuntime(619): Uncaught handler: thread PackageManager exiting due to uncaught exception 10-07 13:47:30.567: ERROR/AndroidRuntime(619): *** EXCEPTION IN SYSTEM PROCESS. System will crash. 10-07 13:47:30.637: ERROR/AndroidRuntime(619): java.lang.NullPointerException 10-07 13:47:30.637: ERROR/AndroidRuntime(619): at com.android.server.PackageManagerService $Settings.updateSharedUserPermsLP(PackageManagerService.java:6051) 10-07 13:47:30.637: ERROR/AndroidRuntime(619): at com.android.server.PackageManagerService$Settings.access$1700 (PackageManagerService.java:5651) 10-07 13:47:30.637: ERROR/AndroidRuntime(619): at com.android.server.PackageManagerService.removePackageDataLI (PackageManagerService.java:4223) 10-07 13:47:30.637: ERROR/AndroidRuntime(619): at com.android.server.PackageManagerService.deleteInstalledPackageLI (PackageManagerService.java:4327) 10-07 13:47:30.637: ERROR/AndroidRuntime(619): at com.android.server.PackageManagerService.deletePackageLI (PackageManagerService.java:4383) 10-07 13:47:30.637: ERROR/AndroidRuntime(619): at com.android.server.PackageManagerService.replaceNonSystemPackageLI (PackageManagerService.java:3591) 10-07 13:47:30.637: ERROR/AndroidRuntime(619): at com.android.server.PackageManagerService.replacePackageLI (PackageManagerService.java:3568) 10-07 13:47:30.637: ERROR/AndroidRuntime(619): at com.android.server.PackageManagerService.installPackageLI (PackageManagerService.java:3941) 10-07 13:47:30.637: ERROR/AndroidRuntime(619): at com.android.server.PackageManagerService.access$1500 (PackageManagerService.java:104) 10-07 13:47:30.637: ERROR/AndroidRuntime(619): at com.android.server.PackageManagerService$5.run (PackageManagerService.java:3444) 10-07 13:47:30.637: ERROR/AndroidRuntime(619): at android.os.Handler.handleCallback(Handler.java:587) 10-07 13:47:30.637: ERROR/AndroidRuntime(619): at android.os.Handler.dispatchMessage(Handler.java:92) 10-07 13:47:30.637: ERROR/AndroidRuntime(619): at android.os.Looper.loop(Looper.java:123) 10-07 13:47:30.637: ERROR/AndroidRuntime(619): at android.os.HandlerThread.run(HandlerThread.java:60) The only workaround that I've found is to uninstall the old version and install the new one, but that isn't acceptable as it wipes out app settings and data (it's a database app, so that's kind of important, and it breaks usability of the Android Market upgrade system). For the record, I'm testing with an ADP1, flashed with HTC's 1.6 recovery image. The app is currently targeting the 1.1 SDK, but I plan to move it soon to either 1.5 or 1.6. There don't seem to be any 1.6 compatibility issues when the app actually runs. I've submitted it as issue #4165 in the bug tracker, but at this point I'm starting to wonder if I'm the only one seeing this, and if I've somehow missed something in my use of the shared user/process name attributes. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
