Hi, Elliot
Sorry for the late response.
Can I please clarify: do these permissions have an effect on Tizen? I thought
that the permissions field in the manifest was ignored on Tizen.
Shiliu: After asking the engineers working on Tizen, you are right, the
permissions are not having effect on Tizen either.
If the permissions are only used to create Android <uses-permission> elements,
is there any reason to have permissions which don't create those elements? In
the mapping table, there are several permissions with empty lists, which
presumably won't have an effect on the resulting AndroidManifest.xml, i.e.
'devicecapabilities': [],
'fullscreen': [],
'presentation': [],
'rawsockets': [],
'screenorientation': []
So do these have any effect at all?
Shiliu: I think the permissions’ list is from the manifest spec definition.
Although it won’t affect the app created by make_apk.py, it tells that the
permission is not requiring any Android system permission instead of we are
ignoring it.
Thanks,
Shiliu.
From: Smith, Elliot [mailto:[email protected]]
Sent: Wednesday, June 11, 2014 5:05 PM
To: Wang, Shiliu
Cc: [email protected]
Subject: Re: [Crosswalk-help] Do manifest.json permissions have any runtime
effects on Android?
Thanks, this is a great answer, and just what I needed. It raises a few more
questions, inline below.
On 11 June 2014 03:35, Wang, Shiliu
<[email protected]<mailto:[email protected]>> wrote:
From: Crosswalk-help
[mailto:[email protected]<mailto:[email protected]>]
On Behalf Of Smith, Elliot
Sent: Tuesday, June 10, 2014 9:21 PM
To:
[email protected]<mailto:[email protected]>
Shiliu:
Crosswalk doesn’t do extra permission check for Android. For two reasons:
1. On Android, permissions are only granted at installation time. No such
mechanism to dynamically/temporally grant one permission to some app.
2. For Crosswalk on android, unlike Tizen. Each App is running completely
separated. Crosswalk doesn’t need to manage multiple app’s permissions.
For detail, you can refer XWALK-555.
Can I please clarify: do these permissions have an effect on Tizen? I thought
that the permissions field in the manifest was ignored on Tizen.
Shiliu:
No, currently if a feature doesn’t request any Android system permission,
crosswalk will not disable even it’s not specified in manifest. The thought is
on android, each Crosswalk app is an independent native app from OS
perspective. If Android system doesn’t think such operation need extra
permission, crosswalk won’t block it as well. The manifest is only for package
tool to easily declare <uses-permission> elements so far.
If the permissions are only used to create Android <uses-permission> elements,
is there any reason to have permissions which don't create those elements? In
the mapping table, there are several permissions with empty lists, which
presumably won't have an effect on the resulting AndroidManifest.xml, i.e.
'devicecapabilities': [],
'fullscreen': [],
'presentation': [],
'rawsockets': [],
'screenorientation': []
So do these have any effect at all?
Finally, is there a mechanism in the embedding API to set a permission without
specifying it in a manifest.json file? (I can't see one.)
Shiliu:
There is not, and not needed. However, to help set <uses-permission> for
Android.manifest is a problem for Embedding API. In embedding API’s usage, we
can’t cover the apk packaging part for developer, so that we can’t do what we
do in make_apk.py to help developers add the permissions in manifest
automatically. We do need some tool to at least warn developer the permissions
needed.
That makes sense. I notice you have commented on the related bug
(https://crosswalk-project.org/jira/browse/XWALK-1867), so that's all good.
Elliot
--
Elliot Smith
Senior Software Engineer
Intel Open Source Technology Centre
_______________________________________________
Crosswalk-help mailing list
[email protected]
https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-help
