I have made three education apps for kids and when they were installed on android devices there are three warnings raised:
=“android.permission.INTERNET”
=“android.permission.ACCESS_NETWORK_STATE”
=“android.permission.READ_PHONE_STATE”
Now, the apps do not require either one of these permissions. We scanned the forum, the net and got bits an pieces but no real solution to the issue on hand.The solution: “Decompile, edit the APK and remove the permissions, recompile” is a quite elaborate workaround, but really helpful?
I must agree with Bohumil; we really, really need a solution to this issue (Also mentioned by Naomi in #10)
Well, these 3 warnings do stop sales. Especially, for educational apps for kids and games not requiring the internet. We have installed 3 kiddies apps together with parents, apps which I have made with CORONA, and we have asked if they would buy them. Most anwers were: NO. Why? Mostly because of the warnings. All got quide suspicious because they did not expect such warnings(permissions) in a small number adding puzzle game. The other anwers; well, you can`t get everything right
The “workaround” to remove these three “unwanted” adroid permissions can be a quick help, if CORODA will help. But, to me, as developer, it is most cruicial to have control of the android manifest!!
It looks like a “default” android manifest is included in the apps build by CORONA. What are all the permissions in this “default” android manifest? Why are there permissions, that the developer did not confirm in the android manifest? What happens if this “default” android manifest is changed", or deleted altogether, or whatnot?
To me, the developer and only the deleloper, following the Android Guidelines, should have control of the android manifest. I cannot responsibly publish an app, which android manifest contains entries which I don`t know, which were made by “who knows” and which could be changed by “who knows”. (I appreciate and am aware of the Android 3 to 4.2 releases involved).
But to change the APK manually is not an alternative, in my opinion.
Permit me to make the following suggestion:
As we are putting “additonal” permissions to the android manifest via build.lua, we could put ALL required permissions in the build.lua. It should then be possible for CORONA to create the android manifest based exclusively on the enties in build.lua. After all, it`t just an XML which needs to be included in the app building, which CORONA might be doing anyway.
Benefits: The developer has control and resposibility of the android manifest as only the permissions in build.lua would be in the android manifest. No workaround, no dodgeing. Nice for CORONA 
Can we please, please have from CORONA a workaround to get rid of the unwanted permissions quickly?
And can CORONA please provide the anwers to my questions above and hopefully take up my suggestion, or find a better alternative.
CORONA is quite exiting. Please solve the problem the we, the developers know and control what is in the android manifest.
Thank you very much for your help - we really need it here.
Dieter
[import]uid: 185880 topic_id: 33398 reply_id: 333398[/import]