Update the minimum supported android version from 21 to 24

Bump the template build.gradle minSdkVersion number.
Add auto-migration for existing projects with 21-23
Update minSdkVersion in the engine AndroidManifest.xml (and tests)
Update all code examples/tests to Android version 24
Create a breaking change notice and migration guide on https://docs.flutter.dev/release/breaking-changes
Update minimum supported Android version to 24 in flutter/website
Update all existing Flutter maintained plugins to Android 24 (after a stable has min sdk 24)
Audit native android code in any plugins that needed to be update to 24 as a min sdk version for pre 24 codepaths and delete those codepaths.
Document the steps required to deprecate an android version in docs/platforms/android/
Close all github issues against the deprecated platform
Migrate all g3 apps internal tracking issue b/450579100

Past prs that may help:
flutter-team-archive/engine#43822
flutter/packages#4459

Update all existing Flutter maintained plugins to Android 24

I would recommend a separate bullet point to track scrubbing all the native code and plugin READMEs for anything specific to pre-24 support. In the past we've sometimes done the mechanical steps of changing the min deployment version but forgotten the step of cleaning up unnecessary code.

done

@stuartmorgan-g

@stuartmorgan-g I forget the preferred order. Would you like me to update the engine/framework then update the plugins once there is a new version published to stable or would you like me to update the plugins to have a higher min first.

Would you like me to update the engine/framework then update the plugins once there is a new version published to stable

This one; the other versions can break people's compilation because we don't have a way to feed OS version requirements into the resolver. By changing Flutter first to require 24 first, and then updating the plugin's min Flutter SDK version to that Flutter version, we can use existing resolver information (the Flutter constraint) to prevent anyone building for 21-23 from getting a version that requires 24 and thus breaking their build.

Android min sdk 24 part 1 (#170882)

Android min sdk 24 part 1 (flutter#170882)

[3.35] Update supported platforms (#12230)

http://goto.google.com/rfc-flutter-android-m-deprecation is not accessible to the general public. may we get the reason behind this decision.

[url_launcher] Re-remove Android API<24 support (#9987)

@khaled-0

@khaled-0 Here is the summary of the summary.

The tools we use and the services we depend on to test and run flutter are dropping support for those versions of android.

From the top of the doc with internal information redacted.

Marshmallow represents a very small portion of Android users globally (<1.4%).
Google 3 has dropped support for api 21-22
Flutter predicts that PlayServices will drop support for android m aka api 23 in 2025 (turns out that prediction was incorrect)
OmniLab (firebase test lab) has dropped android 21-23 support

Website updated https://github.com/flutter/website/blob/4c36e78bbb91c5736c1ccb1847b4d51d3c468df1/src/_data/platforms.yml#L4

This is currently blocked on migrating all google 3 apps.

[url_launcher] Re-remove Android API<24 support (flutter#9987)

Android min sdk 24 part 1 (flutter#170882)

Last task to close this issue is to land #175508

Add documentation for what to do when bumping the minimum sdk version…

Unify Surface code between Skwasm and CanvasKit

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.

Navigation Menu

Repository navigation

Update the minimum supported android version from 21 to 24 #170807

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Update the minimum supported android version from 21 to 24 #170807

Description

Activity

stuartmorgan-g commented on Jun 18, 2025

reidbaker commented on Jun 18, 2025

reidbaker commented on Jun 19, 2025

stuartmorgan-g commented on Jun 19, 2025

khaled-0 commented on Sep 7, 2025

reidbaker commented on Sep 15, 2025

reidbaker commented on Sep 30, 2025

reidbaker commented on Oct 7, 2025

reidbaker commented on Dec 11, 2025

github-actions commented on Dec 26, 2025

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions