I know what you mean by the paranoid users out there. I’ve seen negative comments on apps calling OpenFeint spyware simply for their READ_PHONE_STATE usage. It’s a very vocal minority who unfairly spread FUD (fear-uncertainty-doubt) about an app being spyware when it’s not, causing bad PR for the app and its developers. So, we definitely understand the unfairness of the situation which is why removing this permission (and the other default ones) is on our to-do list. The unfortunate truth is that a lot of 3rd party libraries, like OpenFeint, require this permission… and that is what we have to work-around on our end to prevent a Corona app from crashing. We’ll get to it. [import]uid: 32256 topic_id: 16687 reply_id: 121388[/import]
Joshua, just rehashing our conversation from the other thread, as a preliminary measure, you could just make a *preliminary* fix that would allow those of us who want to, to remove those permissions completely. TRUST us not to use the features that require those permissions and would crash without them. [import]uid: 160496 topic_id: 16687 reply_id: 121409[/import]
Joshua - about the “we’ll get to it” - is it a matter of weeks or months? I need to release the app I have to Android markets, and if it’s weeks, I will wait. If it’s months, I’d have to release now and take my lumps and 1-star reviews…
Or, alternatively, maybe you could tell me what exactly changed in the latest builds that doesn’t allow the apktool to work with Corona APKs anymore? [import]uid: 160496 topic_id: 16687 reply_id: 121787[/import]
I would like to know the answer to this too. I know this came up nearly a year ago when I first started to put apps up on the Android Market. I create children’s apps and most parents do not want to see permissions that appear to be collecting information on their children in kids apps. My apps do not use 3rd party software and have launch pad turned off. I’m not sure why I couldn’t have the option to remove this permission in this case.
@mike470 - there used to be some postings in the forums on how to remove these states, but it is a lot of work. [import]uid: 79834 topic_id: 16687 reply_id: 121795[/import]
@scottadelman - yes, I am quite aware of those postings, but the apktool stopped working with latest (after 840) builds. You go through exactly the same process as before, decompile, recompile, sign, zipalign - and the result fails to run (where the .840 does run). Unfortunately, since I use newTextField, I need the later builds’ fix for it, otherwise I’d switch back to 840.
If you can still use 840, leave me your email and I will walk you through the apktool process to remove those permissions. [import]uid: 160496 topic_id: 16687 reply_id: 121801[/import]
That would be awesome. I am actually still using 704 so hopefully that is not a problem. My email is orionsmason at gmail.com [import]uid: 79834 topic_id: 16687 reply_id: 121802[/import]
Removing these permissions has not been scheduled yet. So, I can’t commit to a date. We have to meet our current commitments first, as you can see on our roadmap here…
http://www.coronalabs.com/resources/roadmap
This change is definitely not going to happen within the next month. There is a huge demand for local/push-notifications on Android, so that has to be next on our to-do list. [import]uid: 32256 topic_id: 16687 reply_id: 121893[/import]