BB 4.2: Remove permission check on app startup

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Build CN1 app for BB 4.2
2. Start it on device. See permission check prompt on app startup
3. This is special system screen with options to change permissions (long 
list). It will be shown on each app startup and there is no way to disable it, 
at least for average user (like me). No other apps do this.

What is the expected output? What do you see instead?
prompt only for required permissions. if app does not need any - no prompt.

What version of the product are you using? On what operating system?
BB Curve 8310 OS 4.5

Please provide any additional information below.
Please provide API to disable that prompt, or something like that 
(configuration in CN1 project). In current conditions CN1 apps generated for BB 
4.2 are not usable at all - nobody will release it with such bad UX.

Original issue reported on code.google.com by gmi...@gmail.com on 19 Apr 2012 at 11:37

[GoogleCodeExporter]

This issue is also an Android/J2ME issue where permissions need to be refined 
by the build server.

Original comment by shai.almog on 19 Apr 2012 at 12:31

• Changed state: Accepted

[GoogleCodeExporter]

Oh well, I just generated Android build for my next project, tried it on device 
and see it also asks for all possible permissions. I do not believe that the 
app may be accepted by customer with such fault - asking user for permissions 
it never use. 
This is a major showstopper, because if an user when installing the app sees 
bunch of permissions (reading phone contacts, GPS location, and so on, which 
are outside the scope the app states for in app description in store), he may 
reject such app, and he will be right, at least I would do so.
In my opinion, it's a high priority issue, I do not understand how CN1 apps may 
be distributed in Android stores at all with it.
What to do now? Build Android port locally on my PC, the same as I did with BB 
port? 8-/
Or is there an option to sign the debug build with proper permissions?

Original comment by gmi...@gmail.com on 19 May 2012 at 2:11

[GoogleCodeExporter]

I agree with Mike in that this really should be a high priority.  I personally 
wouldn't release an app with the broad range of permissions it's asking for.  
I'd feel more comfortable having some control of the permissions the app 
requires rather than letting the build server guess it (a developer override 
perhaps?).

Original comment by 1815...@coolman.ca on 19 May 2012 at 4:26

[GoogleCodeExporter]

I agree that its an important issue. I can't give you an exact ETA but I can 
guarantee there will be no 1.0 version with this issue open.

Original comment by shai.almog on 19 May 2012 at 7:21

• Added labels: Priority-Critical
• Removed labels: Priority-Medium

[GoogleCodeExporter]

This is now fixed in the server. Android permissions are detected automatically 
and we now have a build argument in the latest plugin that allows you to 
disable that permission in RIM.

Original comment by shai.almog on 2 Jul 2012 at 10:27

• Changed state: Fixed