I have been informaed by Google that I cannot submit a build (APK) to the marketplace unless it conforms to security functionality rm26 for Android. 1) What the heck are they talking about? 2) How can I set my build or gradle file to get approved? Is there a plugin or does the lastest version of Corona already handle that?
What is the exact message they gave you?
When I look up ‘rm 26 android’ I get results that seem to indicate this is a Bluetooth watch communications thing.
That makes no sense, so the exact message may help narrow this down.
Also did they link or reference any docs or guidelines in the message?
Hmmm… the more I look at this the more it seems to be about Bluetooth device mating with watches and or cameras.
So, my guess here is, either you’re doing something with Bluetooth and didn’t set the right permissions request or you set the wrong permissions request and are not doing something with Bluetooth.
Also, you could be using a library that has Bluetooth features in it and thus need to request the permission.
All guesses.
Why post here asking if the latest Corona build fixes the problem?
I mean, come on man…
Corona’s latest public build, 2018.3326 has support for Android SDK API level 26 and later, so if you’re using 3326 or later, you should be able to submit builds to Google Play.
If you’re getting some other error (and I don’t recognize the message you entered), you need to provide more details about what you’re doing. Like are you using simulator builds or are you doing native builds with Android Studio.
What are you doing with regards to keysigning? Are you using an old keystore? a new one? Have you told Google to manage your keystores for you?
Rob
Rob,
Thanks for the information. These are builds from the simulator I am in the middle of making modifications to my game and just downloaded the latest version so had not had an opportunity to re-submit. I simply wanted to know if there was anything special I needed to do. As this is my first game the information from Google surprised me as I am doing nothing at all with Bluetooth.
So this matter is resolved and thanks again.
What is the exact message they gave you?
When I look up ‘rm 26 android’ I get results that seem to indicate this is a Bluetooth watch communications thing.
That makes no sense, so the exact message may help narrow this down.
Also did they link or reference any docs or guidelines in the message?
Hmmm… the more I look at this the more it seems to be about Bluetooth device mating with watches and or cameras.
So, my guess here is, either you’re doing something with Bluetooth and didn’t set the right permissions request or you set the wrong permissions request and are not doing something with Bluetooth.
Also, you could be using a library that has Bluetooth features in it and thus need to request the permission.
All guesses.
Why post here asking if the latest Corona build fixes the problem?
I mean, come on man…
Corona’s latest public build, 2018.3326 has support for Android SDK API level 26 and later, so if you’re using 3326 or later, you should be able to submit builds to Google Play.
If you’re getting some other error (and I don’t recognize the message you entered), you need to provide more details about what you’re doing. Like are you using simulator builds or are you doing native builds with Android Studio.
What are you doing with regards to keysigning? Are you using an old keystore? a new one? Have you told Google to manage your keystores for you?
Rob
Rob,
Thanks for the information. These are builds from the simulator I am in the middle of making modifications to my game and just downloaded the latest version so had not had an opportunity to re-submit. I simply wanted to know if there was anything special I needed to do. As this is my first game the information from Google surprised me as I am doing nothing at all with Bluetooth.
So this matter is resolved and thanks again.