Skip to content

fix(android): bump compileSdkVersion 33 -> 37 - #76

Open
omaraalqarni wants to merge 1 commit into
moyasar:mainfrom
Khales-ha:khalesaha/compilesdk-37
Open

omaraalqarni wants to merge 1 commit into
moyasar:mainfrom
Khales-ha:khalesaha/compilesdk-37

Conversation

@omaraalqarni

Copy link
Copy Markdown

Several transitive AndroidX dependencies (androidx.fragment:1.7.1, androidx.lifecycle:*:2.7.0, androidx.core:*:1.13.1) now require the consuming module to compile against API 34+. With compileSdkVersion 33, AGP 9's :moyasar:checkDebugAarMetadata check fails for any app consuming this plugin, regardless of the app's own compileSdk.

This raises it to 37 (current stable). compileSdk is compile-time only — no change to runtime behavior, minSdk, or targetSdk.

Verified with flutter build apk --debug against a real app; build fails without this change, succeeds with it.

Several transitive androidx dependencies (androidx.fragment:1.7.1,
androidx.lifecycle:*:2.7.0, androidx.core:*:1.13.1) declare an AAR-metadata
floor requiring the consuming module to compile against API 34+. moyasar's
compileSdkVersion 33 fails AGP 9's :moyasar:checkDebugAarMetadata check
against that floor regardless of the consuming app's own compileSdk.

compileSdk is compile-time only and does not change runtime behaviour;
minSdk/targetSdk are untouched. Verified end to end: flutter build apk
--debug succeeds with this change alone.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant