Skip to content

Update Android SDK from 28 to 29 in new plugins and project templates #54382

Description

@boskokg

Currently compileSdkVersion and targetSdkVersion are 28.
Plugins and a new project should use 29.

Activity

  1. changed the title [-]Android | Update compileSdkVersion and targetSdkVersion[/-] [+][android] Update compileSdkVersion and targetSdkVersion[/+] on Apr 13, 2020
  2. added
    platform-androidAndroid applications specifically
    c: proposalA detailed proposal for a change to Flutter
    toolAffects the "flutter" command-line tool. See also t: labels.
    on Apr 13, 2020
  3. 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
  4. jmagman commented on Aug 3, 2020

    @jmagman
    Member

    From duplicate #62295:

    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.

  5. jmagman commented on Aug 3, 2020

    @jmagman
    Member

    \cc @xster @jonahwilliams @blasten I guess we should do this sooner rather than later? Not sure what the testing matrix would look like.

  6. blasten commented on Aug 3, 2020

    @blasten

    +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.

  7. xster commented on Aug 3, 2020

    @xster
    Member

    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

    Screen Shot 2020-08-03 at 11 14 01 AM

    Though most users should already be on 29 if they installed Android Studio this year.

  8. xster commented on Aug 3, 2020

    @xster
    Member

    @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.

  9. reopened this on Aug 4, 2020
  10. self-assigned this
    on Aug 4, 2020
  11. xster commented on Aug 4, 2020

    @xster
    Member

    gradle doesn't always cleanly install 29 automatically. Reopening

  12. xster commented on Aug 4, 2020

    @xster
    Member
  13. added
    P3Issues that are less important to the Flutter project
    on Aug 18, 2020
  14. boskokg commented on Aug 22, 2020

    @boskokg
    Author

    @xster I see that my ticket is closed, but I also see that flutter plugins still have "compileSdkVersion 28".
    Should we reopen the ticket?

  15. xster commented on Aug 22, 2020

    @xster
    Member

    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?

  16. boskokg commented on Aug 22, 2020

    @boskokg
    Author

    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"

  17. xster commented on Aug 22, 2020

    @xster
    Member

    This bug is for updating the new plugin template right? We can create a new bug to update Flutter's existing first party plugins.

  18. boskokg commented on Aug 22, 2020

    @boskokg
    Author

    Actually, this issue is edited by @jmagman and lost full description what I reported...

    Should I write a new issue?

  19. xster commented on Aug 22, 2020

    @xster
    Member

    ya, go ahead. Thanks

  20. github-actions commented on Aug 13, 2021

    @github-actions

    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.

  21. locked as resolved and limited conversation to collaborators on Aug 13, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

P3Issues that are less important to the Flutter projectc: proposalA detailed proposal for a change to Flutterdependency: androidAndroid team may need to help usplatform-androidAndroid applications specificallytoolAffects the "flutter" command-line tool. See also t: labels.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions