Plugin with id ‘maven’ not found.
See original GitHub issueSummary
I Just upgraded react-native from 0.62.0 to 0.63.0 and all was working fine. But after I integrated expo unimodules in my bare expo project when I try to make the build for android then expo dependencies give me the below error.
Managed or bare workflow? If you have ios/
or android/
directories in your project, the answer is bare!
bare
What platform(s) does this occur on?
Android
SDK Version (managed workflow only)
No response
Environment
React-native : 0.63.0 Expo Unimodules : 0.13.3 Gradle version : 7.0 Project : Typescript
buildToolsVersion = “30.0.0” minSdkVersion = 21 compileSdkVersion = 30 targetSdkVersion = 30
Reproducible demo or steps to reproduce from a blank project
- Integrate it for the bare project after upgrading to 0.63.0 from 0.62.0 .
Error
Deprecated Gradle features were used in this build, making it incompatible with Gradle 8.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See https://docs.gradle.org/7.0/userguide/command_line_interface.html#sec:command_line_warnings
FAILURE: Build completed with 2 failures.
1: Task failed with an exception.
-----------
* Where:
Build file '/Users/ios/Desktop/Old MacMini Data/Desktop/React Live Projects/afridom/node_modules/expo-constants/android/build.gradle' line: 2
* What went wrong:
A problem occurred evaluating project ':expo-constants'.
> Plugin with id 'maven' not found.
* 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.
==============================================================================
2: Task failed with an exception.
-----------
* What went wrong:
A problem occurred configuring project ':expo-constants'.
> compileSdkVersion is not specified. Please add it to build.gradle
* 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 12s
error Failed to install the app. Make sure you have the Android development environment set up: https://reactnative.dev/docs/environment-setup. Run CLI with --verbose flag for more details.
Error: Command failed: ./gradlew app:installDebug -PreactNativeDevServerPort=8081
Issue Analytics
- State:
- Created 2 years ago
- Reactions:22
- Comments:33 (12 by maintainers)
Top Results From Across the Web
Plugin with id 'maven' not found - Stack Overflow
I got this error in IDEA that uses with 7.1, that is strange as maven is built-in plugin, and should be distributed with...
Read more >Plugin with id 'maven' not found - Help/Discuss - Gradle Forums
Plugin with id 'maven' not found. Try: Run with --info or --debug option to get more log output. Run with --scan to get...
Read more >Plugin with id 'maven' not found. react native - CodeSolution
Plugin with id 'maven' not found. * Try: Run with --stacktrace option to get the stack trace. Run with --info or --debug option...
Read more >Plugin with id 'maven' not found - CSDN博客
Caused by: org.gradle.api.plugins.UnknownPluginException: Plugin with id 'maven' not found.原因分析:这是关于该问题的讨论文章。
Read more >Plugin with id 'maven' not found. - Expo Development Tools
Plugin with id 'maven' not found. ... I Just upgraded react-native from 0.62.0 to 0.63.0 and all was working fine. After I integrated...
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
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
android studio 4.2 with gradle 7.0.1 gives below error
downgraded gradle-6.8.1-all.zip in gradle-wrapper.properties … working good
Temporary workaround:
For any expo package, go to its
android/build.gradle
and modify to usemaven-publish
plugin: