-
Notifications
You must be signed in to change notification settings - Fork 29.2k
Closed
Labels
P1High-priority issues at the top of the work listHigh-priority issues at the top of the work listpackageflutter/packages repository. See also p: labels.flutter/packages repository. See also p: labels.platform-androidAndroid applications specificallyAndroid applications specificallyt: gradle"flutter build" and "flutter run" on Android"flutter build" and "flutter run" on Android
Description
I just tried bumping the compileSdkVersion
in a plugin to be able to use an API available in Android S,
and none of the new symbols are defined when an app depends on this plugin.
It turns out this never worked in Flutter, and people have run into this issue without noticing that the app must
also bump the compileSdkVersion
in order for this work.
This isn't a problem in native android because Android dependencies are distributed as AARs binaries with
metadata that specify the compileSdkVersion
that the Android Gradle plugin must enforce.
The only option is left is to have the Flutter Gradle plugin enforcing the right compileSdkVersion.
Related issues:
Metadata
Metadata
Assignees
Labels
P1High-priority issues at the top of the work listHigh-priority issues at the top of the work listpackageflutter/packages repository. See also p: labels.flutter/packages repository. See also p: labels.platform-androidAndroid applications specificallyAndroid applications specificallyt: gradle"flutter build" and "flutter run" on Android"flutter build" and "flutter run" on Android