Mark, I figured this was the case but wasn't sure if there was a nice workaround for it. I'll probably end up just specifying the install order for now and try some of your suggestions later.
Thanks again for the response, Jason Prenger On Tuesday, March 6, 2012 11:26:27 AM UTC-7, Mark Murphy (a Commons Guy) wrote: > > On Tue, Mar 6, 2012 at 1:20 PM, Jason Prenger <jasonmpren...@gmail.com> > wrote: > > I have two apps, one contains an exported provider that the second app > > uses to look up values. I recently decided it'd be a good idea to add > > read and write permissions to the provider, but now I've run into an > > issue. If I install the app reading from the provider first it'll > > crash with a permission denial. If I install the provider first, > > everything works fine. > > Yup, this is a known limitation of custom preferences. > > > While > > specifying and order for install isn't the worst thing ever I'm > > wondering if there is a workaround for this > > Somebody recently mentioned having the same <permission> element in > both apps, though I haven't tried it and I forget if that was a > solution or a failed solution. :-) > > If that works, to keep things a teensy bit more DRY, you could have an > Android library project for your string resources for the permission. > While I haven't created a resource-only library project, in principle > it should work. > > -- > Mark Murphy (a Commons Guy) > http://commonsware.com | http://github.com/commonsguy > http://commonsware.com/blog | http://twitter.com/commonsguy > > Android Training in NYC: http://marakana.com/training/android/ > > On Tuesday, March 6, 2012 11:26:27 AM UTC-7, Mark Murphy (a Commons Guy) wrote: > > On Tue, Mar 6, 2012 at 1:20 PM, Jason Prenger <jasonmpren...@gmail.com> > wrote: > > I have two apps, one contains an exported provider that the second app > > uses to look up values. I recently decided it'd be a good idea to add > > read and write permissions to the provider, but now I've run into an > > issue. If I install the app reading from the provider first it'll > > crash with a permission denial. If I install the provider first, > > everything works fine. > > Yup, this is a known limitation of custom preferences. > > > While > > specifying and order for install isn't the worst thing ever I'm > > wondering if there is a workaround for this > > Somebody recently mentioned having the same <permission> element in > both apps, though I haven't tried it and I forget if that was a > solution or a failed solution. :-) > > If that works, to keep things a teensy bit more DRY, you could have an > Android library project for your string resources for the permission. > While I haven't created a resource-only library project, in principle > it should work. > > -- > Mark Murphy (a Commons Guy) > http://commonsware.com | http://github.com/commonsguy > http://commonsware.com/blog | http://twitter.com/commonsguy > > Android Training in NYC: http://marakana.com/training/android/ > > On Tuesday, March 6, 2012 11:26:27 AM UTC-7, Mark Murphy (a Commons Guy) wrote: > > On Tue, Mar 6, 2012 at 1:20 PM, Jason Prenger <jasonmpren...@gmail.com> > wrote: > > I have two apps, one contains an exported provider that the second app > > uses to look up values. I recently decided it'd be a good idea to add > > read and write permissions to the provider, but now I've run into an > > issue. If I install the app reading from the provider first it'll > > crash with a permission denial. If I install the provider first, > > everything works fine. > > Yup, this is a known limitation of custom preferences. > > > While > > specifying and order for install isn't the worst thing ever I'm > > wondering if there is a workaround for this > > Somebody recently mentioned having the same <permission> element in > both apps, though I haven't tried it and I forget if that was a > solution or a failed solution. :-) > > If that works, to keep things a teensy bit more DRY, you could have an > Android library project for your string resources for the permission. > While I haven't created a resource-only library project, in principle > it should work. > > -- > Mark Murphy (a Commons Guy) > http://commonsware.com | http://github.com/commonsguy > http://commonsware.com/blog | http://twitter.com/commonsguy > > Android Training in NYC: http://marakana.com/training/android/ > > On Tuesday, March 6, 2012 11:26:27 AM UTC-7, Mark Murphy (a Commons Guy) wrote: > > On Tue, Mar 6, 2012 at 1:20 PM, Jason Prenger <jasonmpren...@gmail.com> > wrote: > > I have two apps, one contains an exported provider that the second app > > uses to look up values. I recently decided it'd be a good idea to add > > read and write permissions to the provider, but now I've run into an > > issue. If I install the app reading from the provider first it'll > > crash with a permission denial. If I install the provider first, > > everything works fine. > > Yup, this is a known limitation of custom preferences. > > > While > > specifying and order for install isn't the worst thing ever I'm > > wondering if there is a workaround for this > > Somebody recently mentioned having the same <permission> element in > both apps, though I haven't tried it and I forget if that was a > solution or a failed solution. :-) > > If that works, to keep things a teensy bit more DRY, you could have an > Android library project for your string resources for the permission. > While I haven't created a resource-only library project, in principle > it should work. > > -- > Mark Murphy (a Commons Guy) > http://commonsware.com | http://github.com/commonsguy > http://commonsware.com/blog | http://twitter.com/commonsguy > > Android Training in NYC: http://marakana.com/training/android/ > > On Tuesday, March 6, 2012 11:26:27 AM UTC-7, Mark Murphy (a Commons Guy) wrote: > > On Tue, Mar 6, 2012 at 1:20 PM, Jason Prenger <jasonmpren...@gmail.com> > wrote: > > I have two apps, one contains an exported provider that the second app > > uses to look up values. I recently decided it'd be a good idea to add > > read and write permissions to the provider, but now I've run into an > > issue. If I install the app reading from the provider first it'll > > crash with a permission denial. If I install the provider first, > > everything works fine. > > Yup, this is a known limitation of custom preferences. > > > While > > specifying and order for install isn't the worst thing ever I'm > > wondering if there is a workaround for this > > Somebody recently mentioned having the same <permission> element in > both apps, though I haven't tried it and I forget if that was a > solution or a failed solution. :-) > > If that works, to keep things a teensy bit more DRY, you could have an > Android library project for your string resources for the permission. > While I haven't created a resource-only library project, in principle > it should work. > > -- > Mark Murphy (a Commons Guy) > http://commonsware.com | http://github.com/commonsguy > http://commonsware.com/blog | http://twitter.com/commonsguy > > Android Training in NYC: http://marakana.com/training/android/ > > -- 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
