[TIMOB-7950] TIAPI: allow user to disable automated permissions configuration with a new setting in tiapp.xml
| GitHub Issue | n/a |
|---|
| Type | New Feature |
|---|
| Priority | Low |
|---|
| Status | Closed |
|---|
| Resolution | Won't Fix |
|---|
| Resolution Date | 2016-08-24T05:20:54.000+0000 |
|---|
| Affected Version/s | Release 1.8.2 |
|---|
| Fix Version/s | n/a |
|---|
| Components | TiAPI |
|---|
| Labels | n/a |
|---|
| Reporter | Paul Dowsett |
|---|
| Assignee | Eric Merriman |
|---|
| Created | 2012-03-09T12:16:39.000+0000 |
|---|
| Updated | 2017-03-24T19:02:03.000+0000 |
|---|
Description
Request
Currently, permissions are automatically configured during the build process. While this is convenient, applications in the marketplaces may be perceived as more of a risk to install if they have WRITE access to a resource on the device when they only need READ access.
Hence, add a new setting in tiapp.xml that allows developers to enable/disable auto permissions (for example, auto-permissions:true/false) at their discretion.
Comments
JSON Source
I believe this ticket refers to Android. Titanium doesn't seem to require permissions for any of the APIs to work. When building an app, the Android build parses the JavaScript code into an AST where we look for Titanium APIs that are used. From there, it can determine the minimum permissions needed for the Titanium APIs to work. This can be overwritten by using a custom AndroidManifest.xml. Simply build the app, then copy
build/android/AndroidManifest.xmltoplatform/android/AndroidManifest.xml, then edit and remove the permissions. This is how to get rid of theWRITE_EXTERNAL_STORAGEpermission which was needed back in the day when apps were installed on an SD card and not the main storage.Closing ticket with reference to the previous comments.