Android Permissions

Solar2D Native builds
#1

I’d like to not have “System tools” and “Development tools” in the permissions list on published apps.

System tools has to do with the RECEIVE_BOOT_COMPLETED and BOOT_COMPLETED stuff in the manifest. What does Corona do that need those in there?
I can see in the manifest generated that the intent for the BOOT_COMPLETED has something to do with com.ansca.corona.SystemStartupBroadcastReceiver, but what’s it for?

I have no clue why “Development tools” is in there!? I’ve removed any and all debug stuff I could find.
It’s sub-texted with “test access to protected storage”
Is it possible to get rid of that? [import]uid: 63706 topic_id: 35289 reply_id: 335289[/import]

#2

Are you a Corona Enterprise user?
If so, then the “com.ansca.corona.SystemStartupBroadcastReceiver” is clearly explained in the AndroidManifest.xml file in all of the sample projects.

What that broadcast receiver does is start up a Corona app in the background when the Android device finishes booting up. This should be used by apps that support local/push notifications, because the app’s notifications will only be shown on the Android status bar if the app is running in the background. That is, if you force quit the app, then all of its notifications in the status bar will disappear. This is standard Android behavior. Starting up an app in the background on boot-up is normal for apps that display notifications, such as the standard Gmail app.

Now, a Corona app will not be started in the background on boot-up by default. You have to opt in to it by adding Android permission “android.permission.RECEIVE_BOOT_COMPLETED” to your AndroidManifest.xml file… or to your “build.settings” if you are a Corona Simulator user. Otherwise, this broadcast receiver will be ignored by the Android OS.

Regarding “System tools” and “Development tools”, I don’t know what you are talking about. Nor am I familiar with the message “test access to protected storage”. This doesn’t sound like something Corona Labs has written. Perhaps you are looking at a Corona app built by a 3rd party?
[import]uid: 32256 topic_id: 35289 reply_id: 140290[/import]

#3

Are you a Corona Enterprise user?
If so, then the “com.ansca.corona.SystemStartupBroadcastReceiver” is clearly explained in the AndroidManifest.xml file in all of the sample projects.

What that broadcast receiver does is start up a Corona app in the background when the Android device finishes booting up. This should be used by apps that support local/push notifications, because the app’s notifications will only be shown on the Android status bar if the app is running in the background. That is, if you force quit the app, then all of its notifications in the status bar will disappear. This is standard Android behavior. Starting up an app in the background on boot-up is normal for apps that display notifications, such as the standard Gmail app.

Now, a Corona app will not be started in the background on boot-up by default. You have to opt in to it by adding Android permission “android.permission.RECEIVE_BOOT_COMPLETED” to your AndroidManifest.xml file… or to your “build.settings” if you are a Corona Simulator user. Otherwise, this broadcast receiver will be ignored by the Android OS.

Regarding “System tools” and “Development tools”, I don’t know what you are talking about. Nor am I familiar with the message “test access to protected storage”. This doesn’t sound like something Corona Labs has written. Perhaps you are looking at a Corona app built by a 3rd party?
[import]uid: 32256 topic_id: 35289 reply_id: 140290[/import]