> If you want to find out about an application, use > Context.createPackageContext() to create a Context configured for another > application. >
This seems to be what I am looking for, however, when I call it with the package name of the other app, it returns null (I get nothing from logCat either). I can use the PackageManager and retrieve the info for that same package, so I am pretty sure I have the name correct and the app is installed. Do you have any ideas about what might be wrong? > And if you are using sharedUserId for this... please do reconsider, this > locks you into that forever and has pretty deep repercussions on the apps > since they are now one unified entity whose permissions must be the union of > both apps etc.) I am using a sharedUserId, however, the two apps are unified. In fact, I would much rather have just a SINGLE app. However, I want the user to be able to install the app to the SD card, but it includes a AppWidget component (which is optionally used) which cannot reside on the SC card. This seems to be forcing me to create two apps, may main app, and a separate app to handle the AppWidget. If there is a better way to do this, I am all ears. Thanks On Jan 16, 2:54 pm, Dianne Hackborn <hack...@android.com> wrote: > That can break, there is no guarantee the apps are installed the same place, > for example if one is on the SD card and one isn't. > > If you want to find out about an application, use > Context.createPackageContext() to create a Context configured for another > application. > > (I assume you are doing tricks like creating the files world read/write to > allow access between them. If so, note this can open up security holes. I > would strongly recommend using one of the standard facilities for > interacting between them, such as a receiver, service, or content provider. > And if you are using sharedUserId for this... please do reconsider, this > locks you into that forever and has pretty deep repercussions on the apps > since they are now one unified entity whose permissions must be the union of > both apps etc.) > > > > On Sun, Jan 16, 2011 at 2:27 PM, John Gaby <jg...@gabysoft.com> wrote: > > I have two applications which can access each others files. To get a > > path to a file in the other app, I am using the context.getDir(...) > > function to get a path to the file for the running app, and then > > changing the package name component of that path to the package name > > of the other app. This seems to work, but I am wondering if this is a > > reliable way of doing this, or if there is another more appropriate > > way. > > > Thanks. > > > -- > > 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<android-developers%2bunsubscr...@googlegroups.com> > > For more options, visit this group at > >http://groups.google.com/group/android-developers?hl=en > > -- > Dianne Hackborn > Android framework engineer > hack...@android.com > > Note: please don't send private questions to me, as I don't have time to > provide private support, and so won't reply to such e-mails. All such > questions should be posted on public forums, where I and others can see and > answer them. -- 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
