You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Update Android SDK from 28 to 29 in new plugins and project templates #54382
changed the title [-]Android | Update compileSdkVersion and targetSdkVersion[/-][+][android] Update compileSdkVersion and targetSdkVersion[/+]on Apr 13, 2020
changed the title [-][android] Update compileSdkVersion and targetSdkVersion[/-][+]Update Android SDK from 28 to 29 in new plugins and project templates[/+]on Aug 3, 2020
Your app currently targets API level 28 and must target at least API level 29 to ensure it is built on the latest APIs optimized for security and performance.
+1. Let's bump the version. The net effect is that plugins would be able to use Android 10 features. (note they can do this manually already). For apps, it isn't much of a gain since Flutter app developers usually don't write Java/Kotlin code in the app itself.
@redbrogdon@filiph actually disregard please. Gradle 2.2+ actually automatically downloads and installs new Android SDKs when not installed manually on the machine via the SDK manager when the compileSdkVersion exceeds the installed versions.
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.
Activity
[-]Android | Update compileSdkVersion and targetSdkVersion[/-][+][android] Update compileSdkVersion and targetSdkVersion[/+][-][android] Update compileSdkVersion and targetSdkVersion[/-][+]Update Android SDK from 28 to 29 in new plugins and project templates[/+]jmagman commentedon Aug 3, 2020
From duplicate #62295:
jmagman commentedon Aug 3, 2020
\cc @xster @jonahwilliams @blasten I guess we should do this sooner rather than later? Not sure what the testing matrix would look like.
blasten commentedon Aug 3, 2020
+1. Let's bump the version. The net effect is that plugins would be able to use Android 10 features. (note they can do this manually already). For apps, it isn't much of a gain since Flutter app developers usually don't write Java/Kotlin code in the app itself.
xster commentedon Aug 3, 2020
Yes we missed the timeline and should do it now.
@redbrogdon @filiph I think we should also broadcast that API 29 (or higher) is needed to build Flutter
Though most users should already be on 29 if they installed Android Studio this year.
xster commentedon Aug 3, 2020
@redbrogdon @filiph actually disregard please. Gradle 2.2+ actually automatically downloads and installs new Android SDKs when not installed manually on the machine via the SDK manager when the compileSdkVersion exceeds the installed versions.
xster commentedon Aug 4, 2020
gradle doesn't always cleanly install 29 automatically. Reopening
xster commentedon Aug 4, 2020
Good callout from @blasten
We should also change https://github.com/flutter/flutter/blob/master/packages/flutter_tools/lib/src/android/android_workflow.dart#L28 for a catch either way.
boskokg commentedon Aug 22, 2020
@xster I see that my ticket is closed, but I also see that flutter plugins still have "compileSdkVersion 28".
Should we reopen the ticket?
xster commentedon Aug 22, 2020
Did you mean you created a new plugin on master channel and still have sdk 28 or were you on stable or were looking at an existing plugin?
boskokg commentedon Aug 22, 2020
I am talking about flutter packages.
example: https://github.com/flutter/plugins/blob/master/packages/connectivity/connectivity/android/build.gradle
There is still written "compileSdkVersion 28"
xster commentedon Aug 22, 2020
This bug is for updating the new plugin template right? We can create a new bug to update Flutter's existing first party plugins.
boskokg commentedon Aug 22, 2020
Actually, this issue is edited by @jmagman and lost full description what I reported...
Should I write a new issue?
xster commentedon Aug 22, 2020
ya, go ahead. Thanks
github-actions commentedon Aug 13, 2021
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.