Closed
Description
Not a bug, but a warning. Perhaps re-numbering to 6.1-beta is appropriate.
Upgrading from 6.0.0-beta24+1 to -beta25 updates dependencies, according to the changelog:
Updated androidx.webkit:webkit dependency to 1.8.0
Updated androidx.browser:browser dependency to 1.6.0
The androidx updates require Android 34, which in turn requires Android Gradle Plugin 8+, which is often going to require an upgrade (most existing projects are probably on AGP 7). Additionally, upgrading Gradle plugin from 7 to 8 sometimes introduces a namespace
error, here's a SO issue describing the problem.
Typical error when trying to build with 6.0.0-beta25:
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':app:checkDebugAarMetadata'.
> A failure occurred while executing com.android.build.gradle.internal.tasks.CheckAarMetadataWorkAction
> 2 issues were found when checking AAR metadata:
1. Dependency 'androidx.browser:browser:1.6.0' requires libraries and applications that
depend on it to compile against version 34 or later of the
Android APIs.
:app is currently compiled against android-33.
Also, the maximum recommended compile SDK version for Android Gradle
plugin 7.4.2 is 33.
Recommended action: Update this project's version of the Android Gradle
plugin to one that supports 34, then update this project to use
compileSdkVerion of at least 34.
Note that updating a library or application's compileSdkVersion (which
allows newer APIs to be used) can be done separately from updating
targetSdkVersion (which opts the app in to new runtime behavior) and
minSdkVersion (which determines which devices the app can be installed
on).
2. Dependency 'androidx.webkit:webkit:1.8.0' requires libraries and applications that
depend on it to compile against version 34 or later of the
Android APIs.
:app is currently compiled against android-33.
Also, the maximum recommended compile SDK version for Android Gradle
plugin 7.4.2 is 33.
Recommended action: Update this project's version of the Android Gradle
plugin to one that supports 34, then update this project to use
compileSdkVerion of at least 34.
Note that updating a library or application's compileSdkVersion (which
allows newer APIs to be used) can be done separately from updating
targetSdkVersion (which opts the app in to new runtime behavior) and
minSdkVersion (which determines which devices the app can be installed
on).
* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
> Get more help at https://help.gradle.org.
Metadata
Metadata
Assignees
Labels
No labels