incubator-callback-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Brooks <mich...@michaelbrooks.ca>
Subject Re: Platform permissions and documentation
Date Mon, 14 May 2012 17:26:03 GMT
Good suggestion Fil. The documentation should document the access /
permission name for each API. I'll create the appropriate JIRA issues for
the documentation.

On Mon, May 14, 2012 at 9:57 AM, Jesse MacFadyen <purplecabbage@gmail.com>wrote:

> +1 to doing both.
> This applies to WP7 as well.
>
> Cheers,
>  Jesse
>
> Sent from my iPhone5
>
> On 2012-05-14, at 9:46 AM, Filip Maj <fil@adobe.com> wrote:
>
> > Hey all,
> >
> > This was brought to my attention via this thread:
> >
> > https://issues.apache.org/jira/browse/CB-756
> >
> > Tl;dr: knowing which core plugins map to which necessary permissions as
> > defined in the AndroidManifest. The same would apply to BlackBerry. Some
> > people trim their permissions list in their app's manifest (as they
> > should) based on which plugins they are using.
> >
> > Presumably, this problem should be solved by constraining users via the
> > CLI tools.
> >
> > That said, I believe it would be good to either:
> > - document the mapping of core plugins to required platform permissions,
> or
> > - tweak the implementations on Android + BlackBerry to check which
> > permissions exist in the app's manifest and return a meaningful error
> > message to the user (should be doable on Android [1])
> >
> > (or both ;) )
> >
> > Thoughts?
> >
> > [1] http://stackoverflow.com/a/4409222 /via Joe
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message