Dharmesh wrote: > You must specify the permission in androidMenifest.xml file for the > application you want to access.
Permissions (i.e., <uses-permission> elements in the manifest) have nothing to do with this issue, AFAIK. > On May 25, 6:52 am, mongd <[email protected]> wrote: >> Hello, I'm trying to find a way to access private files created by >> other packages. >> >> According to the dev site (plz see the following), I can read/write >> files of other packages if some flags are set on the create of those >> files, but I don't know how. >> Can I just open those files with Context.openFileInput(or >> Context.openFileOutput)? Do I need a different way for those three >> cases? You would definitely need to use ordinary file I/O and fully-qualified paths: /data/data/the.other.package.here/... >> By three cases, I mean getSharedPreferences(String, int), >> openFileOutput(String, int), openOrCreateDatabase(String, int, >> SQLiteDatabase.CursorFactory). The downside of MODE_WORLD_WRITEABLE is that it is "world writeable". Another approach is for you to arrange for both applications to run as the same user ID: http://developer.android.com/guide/topics/manifest/manifest-element.html And have both applications signed by the same key (debug or production). Then, both applications should be able to read/write each other's files without issue, because they are both running as the same user. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://twitter.com/commonsguy Android App Developer Training: http://commonsware.com/training.html --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
