Hi, I'm not sure about the removal of the signature attribute, but here are a few points to check:
- the sharedUserId value you specify seems too generic to me. In order to be sure the uid name is unique to your apps, it should probably be something like com.frogdesign.shareduid. Dianne can confirm. - the install error seem to indicate that the signature of your application does not match the signature of something that is already installed with the specified shared user uid. This might be due to the error above (ie this is the shared uid of something in the system and you should not attempt to use it, create your own instead). Since this is the first SDK where applications are signed, You may have had the problem in earlier SDK, but the system just didn't check/complain about it. One important part of the signing process is to understand how the debug signature works. Whenever you compile in Eclipse or in ant (using the default "debug" target), the build system uses a debug signature located in ~/.android/debug.keystore (somewhere inside Local app data on windows). If you have multiple computers (or developers) and build some of your apks on some computer, and other apks on another computer, the signatures will *not* match (they are created automatically on the first build), and you will not be able to use the sharedUserId feature. A solution to that, is to make sure everyone use the same debug.keystore (just copy it from one computer to all the other computer), or build on just one machine. Xav On Tue, Aug 19, 2008 at 3:43 PM, Cheryl Sedota <[EMAIL PROTECTED]>wrote: > > Hi, > > In the past Diane showed me how to use two attributes of the Android > manifest in order to get ActivityGroups working properly (i.e. all the > apps whose activities will be combined using the ActivityGroup will be > accessible) - those attributes are 'sharedUserId' and 'signature'. > > > http://groups.google.com/group/android-developers/browse_thread/thread/4dec6c72fabf101/b61e179023762556?lnk=gst&q=ActivityGroup > > This is what I had working in the past: > > <manifest xmlns:android="http://schemas.android.com/apk/res/android"; > package="com.frogdesign.desktop" > android:sharedUserId="android.uid.system" > android:signature="android.signature.system"> > ... > > With the beta SDK that was just released, this mechanism is broken, as > the 'signature' attribute is no longer valid. Please advise on how to > implement ActivityGroups where Activities are in different apps with > the new SDK. > > The docs still indicate that the signature is still required for > userid match to occur: > > http://code.google.com/android/reference/android/R.styleable.html#AndroidManifest > > ... and in the logs I see: > > From the console: > [2008-08-19 17:26:52 - FrogDesktop] Installation error: > INSTALL_FAILED_SHARED_USER_INCOMPATIBLE > > From logcat: > DEBUG/PackageManager(56): Scanning package com.frogdesign.desktop > DEBUG/PackageManager(56): Shared UserID android.uid.system (uid=1000): > packages=[PackageSetting{433aa490 com.frogdesign.desktop/1000}, > PackageSetting{43540b50 com.frogdesign.desktop/1000}, > PackageSetting{434275a0 com.android.providers.settings/1000}, > PackageSetting{434eeea0 android/1000}] > ERROR/PackageManager(56): Package com.frogdesign.desktop has no > signatures that match those in shared user android.uid.system; > ignoring! > WARN/PackageManager(56): Package couldn't be installed in /data/app/ > com.frogdesign.desktop.apk > > Thanks!! > Cheryl > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] Announcing the new Android 0.9 SDK beta! http://android-developers.blogspot.com/2008/08/announcing-beta-release-of-android-sdk.html For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
