-
Notifications
You must be signed in to change notification settings - Fork 29.2k
Closed
flutter/packages
#4005Closed
Copy link
Labels
P1High-priority issues at the top of the work listHigh-priority issues at the top of the work listc: contributor-productivityTeam-specific productivity, code health, technical debt.Team-specific productivity, code health, technical debt.packageflutter/packages repository. See also p: labels.flutter/packages repository. See also p: labels.platform-androidAndroid applications specificallyAndroid applications specifically
Description
In general we want to keep our example apps updated to recent versions of AGP and Gradle:
- Ensures compatibility with recent versions of AGP/Gradle that many users will be using
- Ensures compatibility with recent related toolchains (e.g., the latest version of Android Studio doesn't easily work with AGP 4.1)
- In some cases, avoids hard-to-understand errors when updating dependencies
However, the downside is that we aren't testing with old versions of AGP; #125621 and #125482 are examples of recent cases where we broke people using old versions of AGP with changes that were fine on current versions. Ideally we should have testing in CI that builds all of our Android plugins in a project that uses the oldest version of AGP that flutter
supports.
Metadata
Metadata
Assignees
Labels
P1High-priority issues at the top of the work listHigh-priority issues at the top of the work listc: contributor-productivityTeam-specific productivity, code health, technical debt.Team-specific productivity, code health, technical debt.packageflutter/packages repository. See also p: labels.flutter/packages repository. See also p: labels.platform-androidAndroid applications specificallyAndroid applications specifically