React native 0.69.0 support
See original GitHub issueI can’t sync Project with Graddle in React native 0.69.0
Repro step
npx react-native init diff
yarn add react-native-auth0
- Open with Android Studio
Output
Build file '/Users/bardiamist/Documents/files/diff/node_modules/react-native-auth0/android/build.gradle' line: 95
A problem occurred configuring project ':react-native-auth0'.
> Could not resolve all files for configuration ':react-native-auth0:implementation'.
> Could not resolve com.facebook.react:react-native:+.
Required by:
project :react-native-auth0
> Cannot choose between the following variants of com.facebook.react:react-native:0.69.0:
- debugVariantDefaultRuntimePublication
- releaseVariantDefaultRuntimePublication
All of them match the consumer attributes:
- Variant 'debugVariantDefaultRuntimePublication' capability com.facebook.react:react-native:0.69.0:
- Unmatched attributes:
- Provides com.android.build.api.attributes.BuildTypeAttr 'debug' but the consumer didn't ask for it
- Provides org.gradle.category 'library' but the consumer didn't ask for it
- Provides org.gradle.dependency.bundling 'external' but the consumer didn't ask for it
- Provides org.gradle.libraryelements 'aar' but the consumer didn't ask for it
- Provides org.gradle.status 'release' but the consumer didn't ask for it
- Provides org.gradle.usage 'java-runtime' but the consumer didn't ask for it
- Variant 'releaseVariantDefaultRuntimePublication' capability com.facebook.react:react-native:0.69.0:
- Unmatched attributes:
- Provides com.android.build.api.attributes.BuildTypeAttr 'release' but the consumer didn't ask for it
- Provides org.gradle.category 'library' but the consumer didn't ask for it
- Provides org.gradle.dependency.bundling 'external' but the consumer didn't ask for it
- Provides org.gradle.libraryelements 'aar' but the consumer didn't ask for it
- Provides org.gradle.status 'release' but the consumer didn't ask for it
- Provides org.gradle.usage 'java-runtime' but the consumer didn't ask for it
* Try:
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
...
Issue Analytics
- State:
- Created a year ago
- Reactions:4
- Comments:9 (5 by maintainers)
Top Results From Across the Web
Announcing React Native 0.69
We are delighted to share with you that React Native 0.69 is the first release to support React 18. React 18 has brought...
Read more >Road to 0.69.0 · Discussion #21 · reactwg/react-native-releases
React Native 0.69.0 contains changes to how Hermes is distributed to you. The change will improve the general stability of the Engine and ......
Read more >What's New in React Native 0.69 - Medium
React Native 0.69 is the first release to support React 18. React Native enhances performance, flexibility, and memory usage. What's React 18 support?...
Read more >What's New in React Native 0.69 — How to Upgrade and Why ...
React Native 0.69 brings a ton of important improvements & updates to the table, with performance & memory usage being a major theme....
Read more >React Native 0.69 is Out! Check Out the Exciting Features
Feature Upgrades/Updates · With this new version, developers can build apps for iOS/tvOS. · It offers better support to M1 users in Android...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hey @Bardiamist, we have released a new version here - https://github.com/auth0/react-native-auth0/pull/489 to fix this issue. Please check this out and let us know. We are closing this issue for now but please feel free to reopen it for further doubts
Looks like commenting out line 95 seems to make it work. Still exploring what change in the new React version is causing this. You can check this fix locally and let us know your feedback. We will explore more details before rolling out the fix.