-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
[feature-request] change the default target sdk to (API Level 30) #1006
Comments
This is considered a breaking change so it won't be in the If you want to target SDK 30 in your app however, you can do so by using the |
SDK 30 is not even released yet, is at beta stage. Won’t be released until some point of Q3 |
I am not sure if it still in beta or not, because I can see it added recently to the latest version of Android Studio as API LEVEL 30 (Android 10+ R) |
It's misleading, it's still a beta release. You can view their release timeline here: https://developer.android.com/preview/overview The expected final release is sometime in Q3. |
Thanks for clarification |
@breautek you shared a link to the android 11 version "Android 11 Developer Preview" (the title on the page). SDK 30 is not exclusively for Android 11 but also for Android 10.0, I would assume this is because of the changes Google are making to the Bluetooth API because of COVID19 track & trace app problems. so it appears they have rushed out SDK 30 to work with Android 10.0+ and if they need more or exclusive to 11 SDK features, it will come out as 31. as the image above shows, it is for Android 10.0+ also as the AVD Manager shows it. |
That what i mentioned before We can see it in Androod Studio SDK manager |
Nevertheless a default target SDK bump needs to happen in a major version (i.e., cordova-android@10) and given that we've just release v9 this is not likely to happen any time soon and rather around the general release of Android 11. But yes, we are aware of this new SDK version and Android 11 being in development. |
@mosabab yeah, I agree with you and think the claim below is wrong
I was just pointing out, that SDK 30 is not a Beta, and what's more likely Google accidentally released something that was beta and changed it to 10.0+ to mislead people, or it was a deliberate action by Google for a reason and I speculated on what that reason could be. @timbru31 are versions, not branches? would it not be possible to fork/branch from v9 and create a v10 alpha with just the SDK support update in? |
It's not misleading at all, it's clearly described in the timeline. Just saying the Android Studio UI is misleading. The API is in a "final preview" state. It's still a beta release. Things can still change from now and the final release targeting Q3 then (although should not be breaking). Changes at this current time will be mainly for incompatibility fixes. You see the update in Android Studio because as of Beta 1 (Which was June), apps can now be published targeting API 30, but the API is still in a beta state. Beta 3 (August) will be release candidate, and an undisclosed date (sometime in Q3) for the final release of SDKs as well as the Android 11 platform. Cordova doesn't support beta packages.
I personally don't see the need for that unless if there are many changes required to support API 30, which may or may not be the case. I'd personally just start off by using the |
any update on this? I use cordova and have below issue when target==30. |
Ooof, that sounds bad. If Google is actually going to require using WebViewAssetsLoader then we have no choice but to move Cordova to AndroidX, which will break a tonne of plugins 😞 |
as an alternative you can use Anyway, next cordova major should move to AndroidX, some plugins will break, but a lot of other plugins are holding back because they don't want to update to use AndroidX until it's the default on Cordova and that makes the plugin use out of date support libraries. Or some plugin authors are maintaining two versions of the same plugin, one for AndroidX and another for the old support libraries. |
Hi all, Any updates on this issue ? "If you want to target SDK 30 in your app however, you can do so by using the android-targetSdkVersion preference for the time being." It does not work if I changed the config.xml or even any build-extras.gradle
or/and (build-extras.gradle)
When adding platform android@9.0.0, the following is still displayed
Thanks |
@breautek any plans to update target to 30? Please confirm.. We have blocker when target 30 is made.. https://bugs.chromium.org/p/chromium/issues/detail?id=1101250 |
(to track it here) |
I have a brand new Pixel 4a 5G and I can't install my API level 29 cordova app. Not compatible. When will we be able to target API 30? |
FYI: By specifying |
@breautek Thanks for the tip! :) 👍 |
I have a strange problem around targeting SDK 30. I'm using cordov-android@9 and setting the Adndroid SDK via preferences:
The app builds, is successfully signed and zip aligned. However the APK will not install on any Android 11 device I have (Galaxy S10 with developer mode and emulator). I've tried sideloading and also using adb install. When sideloading there's no useful feedback, just "App not installed", but using adb it reports that the APK isn't signed. Despite the fact that it most certainly is. If I drop the targetSdkVersion back down to 29 then all is sweetness and light again. |
@lunedam-git you are likely signing with the signature scheme v1, as of api 30 you must sign with signature scheme v2 |
@gjsalot Thankyou! |
The preference
As workaround you can modify your build-extra.gradle as follows:
When building your project there is still displayed Android target: android-29 (which is not true). |
See this Android Blog:
|
Merged to master: #1182 |
Since Google is enforcing API 30, we should publish a corresponding Cordova version as soon as possible.
This message appears on Play Store Console. Also see the Google News. |
|
Feature Request
Motivation Behind Feature
The latest version of Android Studio allow you to set the latest API level available which is API LEVEL 30.
Feature Description
It is good idea to increase the default target sdk to 30.
Alternatives or Workarounds
The text was updated successfully, but these errors were encountered: