Is targetSdkVersion within my control? Or is it chosen by my build of Corona?

Solar2D Android
#21

We’re aware.  The plan is to skip API Level 22 in favor of supporting API Level 23 (Android M) in the near future.

#22

Just fyi for others. We told Google that API 22 will be skipped for API 23 support. And they are willing to give us a one-time exemption from the API 22 requirement.

#23

is version 23 currently supported?

#24

Not yet.  Google has introduced several breaking changes in API Level 23 (aka: Android 6.0) that need to be resolved on our end and in several plugins before we can target it via Corona Simulator builds.  You’ve probably seen several Android 6.0 related changes in our daily build release notes recently.  We’re definitely on the road to getting there, but because we keep finding new 6.0 related issues, we can’t really provide an accurate ETA yet.

#25

Hi Joshua,

On a slightly related note, on API 21+ Android has by default disabled third party cookies in webViews. As explained here:

https://developer.android.com/about/versions/android-5.0-changes.html#BehaviorWebView

This is causing all kinds of issues for one of our clients apps that uses webViews and logins for certain features. Is it possible to have “setAcceptThirdPartyCookies()” added to Corona webViews? 

​I stumbled across this thread in the hope that I could target a lower API level to test with, but adding this feature to webViews sounds like the better option! 

Thanks. 

#26

TandG, good find.  Yeah, we’ll need to solve that.  Can you write up a bug report on that please?  That way we can notify you when it gets resolved.  You can do so by clicking the “Report a Bug” a the top of this webpage.  Thanks.

#27

Thanks Joshua. Bug submitted with Case 43664. 

I just made a very basic example with a webView/iFrame pointing to Coronas account page. When you try to login it just redirects to the login page again on 5.0+… Hopefully thats good enough an example! 

#28

TandG, the issue you’ve mentioned will be resolved in daily build #2766.

Thanks for taking the time to report it and giving us a reproducible test case.  :)

#29

Thanks a lot Joshua, really appreciate the quick turnaround! 

#30

Related to API 23 support - will you add the ability to request permissions at runtime?

https://developer.android.com/training/permissions/requesting.html

#31

We are working on permissioning changes. I’m not exactly sure how it will work, but this is one of the major things that Android 6 brings.

Rob

#32

@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 

#33

We’re aware.  The plan is to skip API Level 22 in favor of supporting API Level 23 (Android M) in the near future.

#34

Just fyi for others. We told Google that API 22 will be skipped for API 23 support. And they are willing to give us a one-time exemption from the API 22 requirement.

#35

is version 23 currently supported?

#36

Not yet.  Google has introduced several breaking changes in API Level 23 (aka: Android 6.0) that need to be resolved on our end and in several plugins before we can target it via Corona Simulator builds.  You’ve probably seen several Android 6.0 related changes in our daily build release notes recently.  We’re definitely on the road to getting there, but because we keep finding new 6.0 related issues, we can’t really provide an accurate ETA yet.

#37

Hi Joshua,

On a slightly related note, on API 21+ Android has by default disabled third party cookies in webViews. As explained here:

https://developer.android.com/about/versions/android-5.0-changes.html#BehaviorWebView

This is causing all kinds of issues for one of our clients apps that uses webViews and logins for certain features. Is it possible to have “setAcceptThirdPartyCookies()” added to Corona webViews? 

​I stumbled across this thread in the hope that I could target a lower API level to test with, but adding this feature to webViews sounds like the better option! 

Thanks. 

#38

TandG, good find.  Yeah, we’ll need to solve that.  Can you write up a bug report on that please?  That way we can notify you when it gets resolved.  You can do so by clicking the “Report a Bug” a the top of this webpage.  Thanks.

#39

Thanks Joshua. Bug submitted with Case 43664. 

I just made a very basic example with a webView/iFrame pointing to Coronas account page. When you try to login it just redirects to the login page again on 5.0+… Hopefully thats good enough an example! 

#40

TandG, the issue you’ve mentioned will be resolved in daily build #2766.

Thanks for taking the time to report it and giving us a reproducible test case.  :)