[FIXED] Android build failures `No matching variant of com.facebook.react:react-native:0.71.0-rc.0 was found.`
Problem
Description Hey all, I'd like to share an update on a series of build failures React Native & Expo users have been experiencing when building Android apps starting from November 4th 2022. We'd like to apologize for the disruption this caused to your developer workflows. The React team is fully committed to delivering a smooth developer experience, and we take this type of issues extremely seriously. 📢 Patches for >= 0.63 We have prepared releases for all the main versions of react-native with an hotfix: 🛳 0.70.5: https://github.com/facebook/react-native/releases/tag/v0.70.5 🛳️ 0.69.7: https://github.com/facebook/react-native/releases/tag/v0.69.7 🛳 0.68.5: https://github.com/facebook/react-native/releases/tag/v0.68.5 🛳️ 0.67.5: https://github.com/facebook/react-native/releases/tag/v0.67.5 🛳️ 0.66.5: https://github.com/facebook/react-native/releases/tag/v0.66.5 🛳️ 0.65.3: https://github.com/facebook/react-native/releases/tag/v0.65.3 🛳️ 0.64.4: https://github.com/facebook/react-native/releases/tag/v0.64.4 🛳️ 0.63.5: https://github.com/facebook/react-native/releases/tag/v0.63.5 By updating to these patch versions, your Android build should start working again. To do so, in your `package.json` change `react-native`'s version to the relevant new patch (ex. if you are on 0.64.3, change to 0.64.4) and run `yarn install`. No other changes should be necessary, but you might want to clean your android artifacts with a `cd android && ./gradlew clean` before trying to re-r
Error Output
error looks something like this:
Unverified for your environment
Select your OS to check compatibility.
1 Fix
Solution: [FIXED] Android build failures `No matching variant of com.facebook.react:react-native:0.71.0-rc.0 was found.`
@JodiRaina that likely indicates your gradle plugin or gradle is too old to use this advice - it appears gradle 6.1 and older does not have the exclusiveContent / include filter in the preferred solution. If you cannot upgrade gradle (and react-native...), you might try one of the fallback workarounds for old react-native using very old gradle plugin / gradle, specifically this one, which was the
Trust Score
9 verifications
- 1
@JodiRaina that likely indicates your gradle plugin or gradle is too old to use
@JodiRaina that likely indicates your gradle plugin or gradle is too old to use this advice - it appears gradle 6.1 and older does not have the exclusiveContent / include filter in the preferred solution.
- 2
If you cannot upgrade gradle (and react-native...), you might try one of the fal
If you cannot upgrade gradle (and react-native...), you might try one of the fallback workarounds for old react-native using very old gradle plugin / gradle, specifically this one, which was the best-known solution if exclusiveContent is not available / until the exclusiveContent idea occurred
- 3
https://github.com/facebook/react-native/issues/35204#issuecomment-1304281740
https://github.com/facebook/react-native/issues/35204#issuecomment-1304281740
- 4
@brentvatne @ Expo proposes this as a refinement to avoid the hard coded version
@brentvatne @ Expo proposes this as a refinement to avoid the hard coded version, it is the same as the previous best-known solution but now with dynamic version powers, otherwise same idea - you put this in the allprojects area of your `android/buld.gradle` file
Validation
Resolved in facebook/react-native GitHub issue #35210. Community reactions: 103 upvotes.
Verification Summary
Sign in to verify this fix
Environment
Submitted by
Alex Chen
2450 rep