-
Notifications
You must be signed in to change notification settings - Fork 24.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0 #29829
Comments
|
Recent react native version having huge issues with android gradle. still i am finding its solution |
Hi @wontone18, I looks like the Flipper version is causing issues. We have an open PR for it here: #29787 Could you apply the diff to your project and see if it helps? |
I will check the above point. But in my thinking its some where else is the issue. It making all the package components invalid and deprecated. Some of those packages we are regularly using
etc. gradle is somewhere making all these issues. I can see several users are facing this issue but nobody getting a better result. |
Same issue by using your flipper github version.
|
Hi at last issue is resolve. There are few things to be check.
|
@wontone18 glad you found a solution. Currently React Native is not supporting Gradle 7.0, we are using v6.6. Is there any specific reason you need v7 support at this time? |
nah i am not using gradle 7 at all. React native already having a gradle plugin package in gradle wrapper. which is 6 but based on jdk version. |
Has anyone managed to solve this problem? I tried everything I found in this post and others, but without success. |
I solved the error creating a new 'react-native init' with the same name of the app, in another folder. Then I deleted the android folder of my app, and pasted the android folder of the new app. Now everything is working again. |
I solved the error creating a new 'react-native init' with the same name of the app, in another folder. Then I deleted the android folder of my app, and pasted the android folder of the new app. Now everything is working again. |
Based on the fact that original issue filer seems unblocked, closing this issue. |
I ran into the same error while debugging from the phone. The cause was I had manually uploaded and installed my app apk. After deleting the app from the phone, and all was fine after |
Do we have a boiler plate code to fix these incompatible issues for RN setup? |
for me the |
I had the same error and fixed it by deleting the \android\app\build\generated\not_namespaced_r_class_sources\debug\r\androidx folder. It was empty and saw something about not being able to delete this folder in the error text. |
I recently encountered this with an error related to Firebase:
And this solution worked for me. (adding firebaseMessagingVersion = "21.1.0" to ext {...}) |
I got this error as well today: "Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0." It looks like it complains about bunch of libraries such as: react-native-async-storage_async-storage, react-native-gesture-handler, react-native-webview, react-native-screens, react-native-firebase_app. Any updates about this issue? |
I have the same problem too |
its not working |
Reopening since RN still doesn’t work with Gradle 7 it seems. A workaround to downgrade to Gradle 6 is helpful but not long term feasible. |
Most of the issues I see reported in this thread seem unrelated to Gradle 7 upgrade. The actual warning (from the issue title) is from Gradle 6, notifying that some things WILL break with the upgrade. |
Even after downgrading Gradle on my system, I still have the same issue. Anyone else? |
I still have the issue, and it's caused by
And my react native is 0.63.4, "react-native-unimodules" is "~0.13.3", and my @unimodules/core is 7.1.0. My project is ejected from Expo. |
Same here. react native cli builds good without uni module android confuguration. Once I apply the changes from https://docs.expo.io/bare/installing-unimodules/. Build break with message Task :app:processDebugResources FAILED Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0. FAILURE: Build failed with an exception.
|
An update on my issue, I added |
Experienced the same issue, while migrating RN from 0.62.2 to 0.63.4 Used Gradle setup: Initial Steps: Next Steps : Moreover, after taking the stacktrace for Then, cleanup of junks at all levels of cache (Project, User/username/.gradle, /var/root/.gradle) is done Then, now able to generate the release mode build. Issue is fixed Note - Weird thing here is no issue on debug mode build Thanks |
After a long time dealing with this, I got it by trying all Gradle distributions from top to bottom until one of them works. In my case it has been 6.9. After changing the following line:
I ran the following command: I hope this helps! |
|
@RickameCua ya its working this tips for my project |
Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may also label this issue as a "Discussion" or add it to the "Backlog" and I will leave it open. Thank you for your contributions. |
I believe we can close this as the upcoming version of RN will run on Gradle 7.3.3. Is there anything else to be done here? |
Agreed, closing as RN has been migrated to support Gradle 7+ |
Try this solution worked for me. |
I am still having this issue - not a signle solution worked for me. :( Deprecated Gradle features were used in this build, making it incompatible with Gradle 8.0. You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.` |
Awesome! It works well on my end. Thank you so much. |
Unfortunately, it was a good experience using react native to develop mobile apps but I found my self wasting a lot of time just solving issue after issue, it's been more than 1 week now of headaches with those errors. I hope RN team work on this side and try to solve those problems |
Hi
i dont know whats wrong but i am getting this error continuously. Even i tried all with the fresh version also.
i tried all my procedures like for instance
info Fetching system and libraries information...
System:
OS: Windows 10 10.0.18363
CPU: (4) x64 Intel(R) Core(TM) i5-3320M CPU @ 2.60GHz
Memory: 1.43 GB / 5.59 GB
Binaries:
Node: 13.9.0 - C:\Program Files\nodejs\node.EXE
Yarn: 1.22.0 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
npm: 6.14.4 - C:\Program Files\nodejs\npm.CMD
Watchman: Not Found
SDKs:
Android SDK: Not Found
Windows SDK: Not Found
IDEs:
Android Studio: Version 4.0.0.0 AI-193.6911.18.40.6626763
Visual Studio: Not Found
Languages:
Java: 1.8.0_161
Python: 2.7.17
npmPackages:
@react-native-community/cli: Not Found
react: 16.13.1 => 16.13.1
react-native: 0.63.2 => 0.63.2
npmGlobalPackages:
react-native: Not Found
The text was updated successfully, but these errors were encountered: