Ok you can scream at me now ... everything is explained in http://developer.android.com/guide/publishing/app-signing.html#setup
So I am assuming that my original question of how I will be able to sign both apps with the same key is answered by doing so manually for each of the unsigned apks. I never signed these apks before but yet they are running fine on the emulator and the real device so I assumed that the plug in does it automatically in which case I will need to intervene to sign them with the same key before I can used the SharedId. Thanks and again apologies for the multiple postings On Oct 13, 12:17 pm, Mark Murphy <[email protected]> wrote: > On Wed, Oct 13, 2010 at 12:07 PM, kypriakos <[email protected]> wrote: > > Well these are two separate projects that eventually co-operate with > > each other > > using that "shared space". So yes if I could give specific access to a > > particular > > app to access that space that would be fine. Else, I will need to find > > another > > way to approach it. Generating such a shared space on the sdcard is a > > better > > idea? > > If these are two projects of yours, then you can use the > android:sharedUserId attribute in your manifest. Give both apps the > same user ID and sign both with the same signing key. Then they will > run as the same Linux user, and they can access each other's files > without further modification. And, the files will still be protected > from other apps. > > -- > Mark Murphy (a Commons > Guy)http://commonsware.com|http://github.com/commonsguyhttp://commonsware.com/blog|http://twitter.com/commonsguy > > _The Busy Coder's Guide to Android Development_ Version 3.1 Available! -- 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] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
