It’s clearly not a good predicament: a choice between Samsung build approval and Google featuring approval.
Would a solution be to have a special build command for Samsung like you have for NOOK and Kindle? It would be good to keep the Android build as ‘pure’ as possible.
We really need a solution urgently though, any chance of a daily build for Google Play?
Thanks a lot for the support.
Ian
[import]uid: 29093 topic_id: 35634 reply_id: 141960[/import]
Can I just get some confirmation regarding the removal of default permissions?
Although they won’t be included by default any more, is there any reason we would still need to have READ_PHONE_STATE in order for a Corona app to work. We use Flurry for our analytics, and as far as I can tell that only requires the INTERNET permission - which is fine because we need that for our leaderboards etc.
There shouldn’t be anything in our app that requires any of the info returned by the READ_PHONE_STATE permission, so would it be safe for us to leave it out entirely once the daily build has removed them? [import]uid: 84115 topic_id: 35634 reply_id: 142072[/import]
Regarding a quick solution to the ringer mode issue, I’ll talk to the rest of the team this coming Monday on what the best course of action should be on our end. It’s not a small decision and the rest of the team here at Corona Labs needs to be sold on it. Sorry about the delay. [import]uid: 32256 topic_id: 35634 reply_id: 142119[/import]
Alan,
We’ve updated our API documentation to indicate which APIs require the INTERNET, READ_PHONE_STATE, and ACCESS_NETWORK_STATE permissions. You can download the newest API documentation from our daily build page here…
http://developer.coronalabs.com/downloads/daily-builds
Flurry only requires the INTERNET permission and it optionally supports the ACCESS_FINE_LOCATION and ACCESS_COARSE_LOCATION permissions.
Only ads (inneractive and InMobi) require the 3 permissions that you’ve mentioned.
OpenFeint used to require those 3 permissions as well, not that it matters anymore.
The function [lua]system.getInfo(“deviceID”)[/lua] will return the phone ID that was assigned by the cellular service if the READ_PHONE_STATE permission is set. If not set, then it returns the ID assigned by the operating system upon installation, which is the same ID returned by tablets (ie: devices that are not phones). We’ve documented this in our newest API documentation as well.
I hope this helps! [import]uid: 32256 topic_id: 35634 reply_id: 142120[/import]
Brilliant. Thanks Joshua for the thorough responses. We await the team’s decision with bated breath. [import]uid: 29093 topic_id: 35634 reply_id: 142141[/import]
So is it the case that now I can build my app so that users can install it without having to grant phone and internet privileges? I’m one of those who felt that my users would be significantly discouraged by this, and have been holding off purchasing the SDK until this was addressed… [import]uid: 157797 topic_id: 35634 reply_id: 142980[/import]
@capellf
The short answer would be Yes, but you’d need to use build 2013.1030 or later for this to take effect. You also need to verify that you’re not using any API’s in your app that require any of the privileges you don’t want. [import]uid: 70847 topic_id: 35634 reply_id: 143003[/import]
Everyone,
Sorry for not getting back to you on this topic.
We’ve temporarily removed our silent/vibrate mode handling as of daily build #1031.
http://developer.coronalabs.com/release/2013/1031/
This means that audio will be played when the device is in silent/vibrate mode, which will allow your app to pass the Google Play featured app review process.
If you intend to publish your app to the Samsung App Store, then I recommend that you build with daily build #1030.
Also note that we’ve “removed” the default Android permissions that Corona used to include in all Android builds as of daily build #1030. This way you can take advantage of this change for both Google Play and Samsung releases. Please see the following blog post about our Android permission changes for more details.
http://www.coronalabs.com/blog/2013/02/18/say-goodbye-to-default-android-permissions/
Anyways, I hope this helps! [import]uid: 32256 topic_id: 35634 reply_id: 143390[/import]
Thanks again Joshua for your help with this. We spotted the changes in the daily build notes and resubmitted to Google on Monday! Fingers-crossed we’ll get that feature now. [import]uid: 29093 topic_id: 35634 reply_id: 143443[/import]
So is it the case that now I can build my app so that users can install it without having to grant phone and internet privileges? I’m one of those who felt that my users would be significantly discouraged by this, and have been holding off purchasing the SDK until this was addressed… [import]uid: 157797 topic_id: 35634 reply_id: 142980[/import]
@capellf
The short answer would be Yes, but you’d need to use build 2013.1030 or later for this to take effect. You also need to verify that you’re not using any API’s in your app that require any of the privileges you don’t want. [import]uid: 70847 topic_id: 35634 reply_id: 143003[/import]
Everyone,
Sorry for not getting back to you on this topic.
We’ve temporarily removed our silent/vibrate mode handling as of daily build #1031.
http://developer.coronalabs.com/release/2013/1031/
This means that audio will be played when the device is in silent/vibrate mode, which will allow your app to pass the Google Play featured app review process.
If you intend to publish your app to the Samsung App Store, then I recommend that you build with daily build #1030.
Also note that we’ve “removed” the default Android permissions that Corona used to include in all Android builds as of daily build #1030. This way you can take advantage of this change for both Google Play and Samsung releases. Please see the following blog post about our Android permission changes for more details.
http://www.coronalabs.com/blog/2013/02/18/say-goodbye-to-default-android-permissions/
Anyways, I hope this helps! [import]uid: 32256 topic_id: 35634 reply_id: 143390[/import]
Thanks again Joshua for your help with this. We spotted the changes in the daily build notes and resubmitted to Google on Monday! Fingers-crossed we’ll get that feature now. [import]uid: 29093 topic_id: 35634 reply_id: 143443[/import]
So is it the case that now I can build my app so that users can install it without having to grant phone and internet privileges? I’m one of those who felt that my users would be significantly discouraged by this, and have been holding off purchasing the SDK until this was addressed… [import]uid: 157797 topic_id: 35634 reply_id: 142980[/import]
@capellf
The short answer would be Yes, but you’d need to use build 2013.1030 or later for this to take effect. You also need to verify that you’re not using any API’s in your app that require any of the privileges you don’t want. [import]uid: 70847 topic_id: 35634 reply_id: 143003[/import]
Everyone,
Sorry for not getting back to you on this topic.
We’ve temporarily removed our silent/vibrate mode handling as of daily build #1031.
http://developer.coronalabs.com/release/2013/1031/
This means that audio will be played when the device is in silent/vibrate mode, which will allow your app to pass the Google Play featured app review process.
If you intend to publish your app to the Samsung App Store, then I recommend that you build with daily build #1030.
Also note that we’ve “removed” the default Android permissions that Corona used to include in all Android builds as of daily build #1030. This way you can take advantage of this change for both Google Play and Samsung releases. Please see the following blog post about our Android permission changes for more details.
http://www.coronalabs.com/blog/2013/02/18/say-goodbye-to-default-android-permissions/
Anyways, I hope this helps! [import]uid: 32256 topic_id: 35634 reply_id: 143390[/import]
Thanks again Joshua for your help with this. We spotted the changes in the daily build notes and resubmitted to Google on Monday! Fingers-crossed we’ll get that feature now. [import]uid: 29093 topic_id: 35634 reply_id: 143443[/import]
So is it the case that now I can build my app so that users can install it without having to grant phone and internet privileges? I’m one of those who felt that my users would be significantly discouraged by this, and have been holding off purchasing the SDK until this was addressed… [import]uid: 157797 topic_id: 35634 reply_id: 142980[/import]
@capellf
The short answer would be Yes, but you’d need to use build 2013.1030 or later for this to take effect. You also need to verify that you’re not using any API’s in your app that require any of the privileges you don’t want. [import]uid: 70847 topic_id: 35634 reply_id: 143003[/import]
Everyone,
Sorry for not getting back to you on this topic.
We’ve temporarily removed our silent/vibrate mode handling as of daily build #1031.
http://developer.coronalabs.com/release/2013/1031/
This means that audio will be played when the device is in silent/vibrate mode, which will allow your app to pass the Google Play featured app review process.
If you intend to publish your app to the Samsung App Store, then I recommend that you build with daily build #1030.
Also note that we’ve “removed” the default Android permissions that Corona used to include in all Android builds as of daily build #1030. This way you can take advantage of this change for both Google Play and Samsung releases. Please see the following blog post about our Android permission changes for more details.
http://www.coronalabs.com/blog/2013/02/18/say-goodbye-to-default-android-permissions/
Anyways, I hope this helps! [import]uid: 32256 topic_id: 35634 reply_id: 143390[/import]