Skip to content
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

[Android] Could not get unknown property 'javaCompileProvider' for object of type #124

Closed
lorenzo-crowd opened this issue Jul 9, 2019 · 10 comments

Comments

@lorenzo-crowd
Copy link

Hi,

I followed all Installation steps but when I try to build the app for Android I get the following error.

React native version 0.58.4
React Navigation Version ^3.1.5

  • Where:
    Build file '/Library/WebServer/Documents/offf-app/node_modules/react-native-screens/android/build.gradle' line: 103

  • What went wrong:
    A problem occurred configuring project ':react-native-screens'.

Could not get unknown property 'javaCompileProvider' for object of type com.android.build.gradle.internal.api.LibraryVariantImpl.

@lorenzo-crowd lorenzo-crowd changed the title [Android] [Android] Could not get unknown property 'javaCompileProvider' for object of type Jul 9, 2019
@JustinKasad
Copy link

I'm having the same issue. I temporarily fixed it with this:
software-mansion/react-native-reanimated#315 (comment)

JustinKasad added a commit to JustinKasad/react-native-screens that referenced this issue Jul 10, 2019
@se-bastiaan
Copy link

What version of gradle and the android build plugin are you using?

@lorenzo-crowd
Copy link
Author

From my build.gradle file:

buildToolsVersion = "28.0.2"

classpath 'com.android.tools.build:gradle:3.2.1'

gradleVersion = '4.7'

@se-bastiaan
Copy link

se-bastiaan commented Jul 11, 2019

According to the PR that created this change you need Gradle 4.10+. So if you update it should work again. You need to update the version of the gradle plugin to 3.3.2 as well. I'm not sure but I do think you could even update to Gradle 5.x and build plugin 3.4+.

@WoLewicki
Copy link
Member

It looks like the issue is outdated, so I am closing it then. Feel free to comment if I am wrong.

@imamarham10
Copy link

you are wrong,any issue can never be outdated, there are unnumerable beginners coming to dev world

@1-aminadab
Copy link

I got this error all the time I start my react-native app. I'm about to lose my job. pleace help
A problem occurred configuring project ':react-native-screens'.

Could not determine the dependencies of null.
Could not resolve all dependencies for configuration ':react-native-screens:classpath'.

@tboba
Copy link
Member

tboba commented Dec 18, 2023

Hi @1-aminadab, I'm sorry that's happening for you. Could you provide us more information about your project? What's your Java/Kotlin, Gradle and React Native version and which version of react-native-screens are you trying to install? Also if it's possible for you, could you provide any steps to reproduce and more logs from the build phase, so we could also test that? If not, could you at least send us your configuration (what dependencies are you using, how does your gradle configuration look like, etc.)?

@easyecom-manu
Copy link

same problem with "react-native-screens": "^3.31.1",

BUILD FAILED in 6s error Failed to install the app. Command failed with exit code 1: gradlew.bat app:installDebug -PreactNativeDevServerPort=8081 FAILURE: Build failed with an exception. * What went wrong: A problem occurred configuring project ':react-native-screens'. > com.android.builder.errors.EvalIssueException: [CXX1101] NDK at C:\Users\manu\AppData\Local\Android\Sdk\ndk\26.1.10909125 d id not have a source.properties file * 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. BUILD FAILED in 6s. info Run CLI with --verbose flag for more details.

why this happening even it is recommended in react native official page
https://reactnative.dev/docs/navigation

@tboba
Copy link
Member

tboba commented May 6, 2024

Hi @easyecom-manu, I believe this has been already reported before. Please check out if solution from this comment resolves your issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants