In regards to Android, is targetSdkVersion with my control as the app creator? Or is this something that is dependent upon which build of Corona I am using?
Thank you!
No. Not for Corona Simulator builds. That is something we control. And this is not something we’ll ever introduce into the Corona Simulator because it has severe repercussions on how the compiled app is treated by the Android OS. Upping the target API Level causes default Android feature behaviors to typically change and we may be forced to call out to new Android Java APIs dynamically (but only for new Android OS versions, not old versions) to maintain the expected feature behavior.
If you want to control it, then you’ll have to use Corona Enterprise. But then it’s on you to re-test your app to make sure it works as expected. Usually we recommend that you target the same API Level Corona does for Corona Simulator builds, which is currently API Level 21 (Android 5.0) at the time of this posting.
Hi @Joshua Quick,
Thank you for your response. Do you guys have a timeline for when you’ll be moving onto the latest version (22)?
Our company has an opportunity for one of our apps to be featured by Google. One of the requirements is that the targetSdkVersion must be set to the latest version (22).
Jeff
Is Google Play blocking your app from being featured because of this?
Are you unable to negotiate with them about this?
Because we’re currently targeting API Level 21, which should be good enough.
Changing the target API Level on our end is not something we can do on a whim. It’s expensive and takes a lot of time on our side.
We usually only update the target API level about once a year, because it typically introduces a lot of ugly breaking changes and new bugs. While we try our best to re-test and debug the hell out of Corona before making it available in a daily build, almost every time some unexpected issue leaks through. Bottom line, it’s a high risk change and Google has to make it worth the upgrade. We made the upgrade to API Level 21 because it came with new Android L/5.0 features and Android TV support.
Hi Josh -
This is Andrew, I work with Jeff. Google’s editorial team has indicated this as a “Must Do.” So, they feel pretty strongly about it. We can go back and push on them to see if there is any give. But here is part of a message we got from them when they reviewed our app for featuring:
[Must Do]The app’s targetSdkVersion must be set to the latest version (currently 22) in order to ensure that newer platform behaviors such as hardware acceleration and the correct default visual theme are applied. For more info: http://developer.android.com/guide/topics/manifest/uses-sdk-element.html#target https://developer.android.com/about/versions/android-5.1.html
Thanks!
Andrew
Jeff, Andrew,
We’re currently running some tests to see if it’s possible for you guys to compile for API Level 22 via Corona Enterprise. So far, our core Corona features appear to run fine, but we suspect that some ad plugins/libraries may crash on startup due to their usage of Android networking APIs that were deprecated in API Level 22. If you two are willing to use Corona Enterprise, then this may be the more immediate solution.
Hi @Josh,
Thank you for running the test and the lead! We’ll check it out further.
Also, we have been pushed Google as well on the requirement, and they may be willing to give us a pass on it.
Thanks again for the help!!
Thanks!
Andrew
We have the exact same issue, Google have asked us to use sdk 22 in order to be considered for promotion. Is there any news on using sdk22 in the sim?
akao, did you have any luck asking Google to waive the issue?
I just received the same notice for our game to be considered for featuring through Google. Is there a resolution to this and if so can someone post how to resolve this?
K
Yeah. We basically told them we are using Corona SDK and that Corona can only support up to API 21, and that we will support API 22 as soon as Corona supports it. They seem to be satisfied with that as an answer.
No. Not for Corona Simulator builds. That is something we control. And this is not something we’ll ever introduce into the Corona Simulator because it has severe repercussions on how the compiled app is treated by the Android OS. Upping the target API Level causes default Android feature behaviors to typically change and we may be forced to call out to new Android Java APIs dynamically (but only for new Android OS versions, not old versions) to maintain the expected feature behavior.
If you want to control it, then you’ll have to use Corona Enterprise. But then it’s on you to re-test your app to make sure it works as expected. Usually we recommend that you target the same API Level Corona does for Corona Simulator builds, which is currently API Level 21 (Android 5.0) at the time of this posting.
Hi @Joshua Quick,
Thank you for your response. Do you guys have a timeline for when you’ll be moving onto the latest version (22)?
Our company has an opportunity for one of our apps to be featured by Google. One of the requirements is that the targetSdkVersion must be set to the latest version (22).
Jeff
Is Google Play blocking your app from being featured because of this?
Are you unable to negotiate with them about this?
Because we’re currently targeting API Level 21, which should be good enough.
Changing the target API Level on our end is not something we can do on a whim. It’s expensive and takes a lot of time on our side.
We usually only update the target API level about once a year, because it typically introduces a lot of ugly breaking changes and new bugs. While we try our best to re-test and debug the hell out of Corona before making it available in a daily build, almost every time some unexpected issue leaks through. Bottom line, it’s a high risk change and Google has to make it worth the upgrade. We made the upgrade to API Level 21 because it came with new Android L/5.0 features and Android TV support.
Hi Josh -
This is Andrew, I work with Jeff. Google’s editorial team has indicated this as a “Must Do.” So, they feel pretty strongly about it. We can go back and push on them to see if there is any give. But here is part of a message we got from them when they reviewed our app for featuring:
[Must Do]The app’s targetSdkVersion must be set to the latest version (currently 22) in order to ensure that newer platform behaviors such as hardware acceleration and the correct default visual theme are applied. For more info: http://developer.android.com/guide/topics/manifest/uses-sdk-element.html#target https://developer.android.com/about/versions/android-5.1.html
Thanks!
Andrew
Jeff, Andrew,
We’re currently running some tests to see if it’s possible for you guys to compile for API Level 22 via Corona Enterprise. So far, our core Corona features appear to run fine, but we suspect that some ad plugins/libraries may crash on startup due to their usage of Android networking APIs that were deprecated in API Level 22. If you two are willing to use Corona Enterprise, then this may be the more immediate solution.
Hi @Josh,
Thank you for running the test and the lead! We’ll check it out further.
Also, we have been pushed Google as well on the requirement, and they may be willing to give us a pass on it.
Thanks again for the help!!
Thanks!
Andrew
We have the exact same issue, Google have asked us to use sdk 22 in order to be considered for promotion. Is there any news on using sdk22 in the sim?
akao, did you have any luck asking Google to waive the issue?
I just received the same notice for our game to be considered for featuring through Google. Is there a resolution to this and if so can someone post how to resolve this?
K
Yeah. We basically told them we are using Corona SDK and that Corona can only support up to API 21, and that we will support API 22 as soon as Corona supports it. They seem to be satisfied with that as an answer.
@josh We are working with Google guys on another promo opportunity and this issue came up again. We’ll tell them the same thing as last time to see if they are still OK with it. But, want to make sure you guys are aware that this continues to be a real issue for folks like us.
Thanks!
Andrew