rive-app / rive-app/rive-react-native
Android builds fails using react-native-rive 6.2.x against RN 0.72.7.
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 783
- Forks
- 81
- Avg merge
- 3d 6h
- Merged PRs (30d)
- 3
Description
Description
Since release 6.2.x (which bumps Android to SDK version 34), building on Android fails with the following error:
Provide a Repro
n/a
Source .riv/.rev file
n/a
Expected behavior
Android app builds without errors.
Output
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':app:checkClientreleaseAarMetadata'.
> A failure occurred while executing com.android.build.gradle.internal.tasks.CheckAarMetadataWorkAction
> 2 issues were found when checking AAR metadata:
1. Dependency 'androidx.core:core-ktx:1.12.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.core:core:1.12.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).
Device & Versions (please complete the following information)
- Device: n/a
- OS: Android
- NPM Version: 10.2.3
Additional context
I would expect bumping the Android SDK to 34 to be a breaking change (e.g. major version bump) since it implies upgrading to React Native 0.73.x. And it is also not explicitly mentioned in the changelog. E.g. we have automated dependency updates (for patch/minor updates) set up via Renovate, so this effectively broke our pipeline.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file or test is named. Start by reproducing the Android build with react-native-rive 6.2.x against React Native 0.72.7, then inspect the Android SDK and Gradle requirements behind androidx.core 1.12.0 and compile SDK 34. Done means the app builds successfully or the compatibility and breaking-change requirements are documented clearly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, react-native
- Domain
- build-system, mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100