Replies: 1 comment
-
Historically we have often used a different version than the AIR SDK (particularly when Adobe was(n't) maintaining AIR). It really depends on the build tools and sdk that you have installed and the gradle options that you have in your app descriptor. I would say that most of distriqt's extensions are only tested to 34 / 35 currently so pushing to 36 would likely introduce some issues. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello, we've always stuck to the suggested TargetSDK mentioned in the release notes of the Flex+AIR version we compile with.
Of course, each August Google starts notifying us about apps needing updates, requiring us to comply by August 31st for future upgrades. If we don't update by then, new app updates are blocked, and after a year of non-compliance, the app's visibility is significantly reduced or the listing may be removed.
What prevents me today from listing TargetSDK="36" in the Android manifest, obviously after checking that all the ANEs we use are working correctly with older and newer Android devices?
0 votes ·
Beta Was this translation helpful? Give feedback.
All reactions