-
-
Notifications
You must be signed in to change notification settings - Fork 21.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Minimum Android target sdk level 18 (version 4.3) required even for 3.1 with GLES2 #21735
Comments
https://developer.android.com/about/dashboards/ |
See #18627 - basically if we supported SDK below 18, we couldn't ship applications on the Play Store.
|
I have an Android 4.4 device for testing purpose, but not below 4.4 according to the link from @akien-mga, Android OS distribution and difficulty of maintenance, |
@akien-mga do you have a reference link saying that SHA1 signed APKs can't be submitted to the play store? I couldn't find such an announcement. I had a look at this since my personal device was on SDK 16. My export got as far as the loading screen but encountered some issue compiling the fragment shader (possibly an issue specific to my device?). It could be a useful starting point if someone else wants to try: |
@stewbasic See #18626 and #18627. Since April 2017, JAR files signed with MD5 (and SHA-1) are treated as unsigned, so they produce invalid APKs for Android. We now need to use SHA-256, which is not supported on API level < 18 as per #18626 (comment) And anyway the hardware and graphics drivers of such < 18 devices is way too old for us to be able to support, so it's a good change that the minimum is now 18. |
You still need a device that is atleast at version 4.3 (The one that has GLES3 support) even with the GLES2 backend. May be related #21710
The text was updated successfully, but these errors were encountered: