npm run android stuck at "Evaluating settings..." — Gradle Daemon hangs during build on first run #50814
Labels
Needs: Attention
Issues where the author has responded to feedback.
Needs: Repro
This issue could be improved with a clear list of steps to reproduce the issue.
First of all, thank you for all the amazing work you're doing on React Native.
I ran into an issue while trying to launch the project using npm run android:
react-native info
info Fetching system and libraries information...
System:
OS: Windows 11 10.0.22631
CPU: (8) x64 Intel(R) Core(TM) i5-8265U CPU @ 1.60GHz
Memory: 1001.46 MB / 7.75 GB
Binaries:
Node:
version: 20.17.0
path: C:\Program Files\nodejs\node.EXE
Yarn: Not Found
npm:
version: 10.8.2
path: C:\Program Files\nodejs\npm.CMD
Watchman:
version: 20240603.014635.0
path: C:\Users\USER\AppData\Local\watchman-v2024.06.03.00-windows\bin\watchman.EXE
SDKs:
Android SDK:
API Levels:
- "33"
- "34"
- "35"
- "36"
Build Tools:
- 35.0.0
System Images:
- android-33 | Google Play Intel x86_64 Atom
- android-35 | Google Play Intel x86_64 Atom
Android NDK: 27.0.12077973
Windows SDK: Not Found
IDEs:
Android Studio: AI-231.9392.1.2311.11076708
Visual Studio: Not Found
Languages:
Java:
version: 17.0.9
path: /c/Program Files/Common Files/Oracle/Java/javapath/javac
Ruby: Not Found
npmPackages:
"@react-native-community/cli":
installed: 15.0.1
wanted: 15.0.1
react:
installed: 19.0.0
wanted: 19.0.0
react-native:
installed: 0.78.2
wanted: 0.78.2
react-native-windows: Not Found
npmGlobalPackages:
"react-native": Not Found
Android:
hermesEnabled: true
newArchEnabled: false
iOS:
hermesEnabled: Not found
newArchEnabled: Not found
info React Native v0.79.1 is now available (your project is running on v0.78.2).
info Changelog: https://github.com/facebook/react-native/releases/tag/v0.79.1
info Diff: https://react-native-community.github.io/upgrade-helper/?from=0.78.2&to=0.79.1
info For more info, check out "https://reactnative.dev/docs/upgrading?os=windows".
I've tried cleaning the build and restarting the Metro server, but the issue persists. Please let me know if there's any other information I can provide to help debug this.
The text was updated successfully, but these errors were encountered: