-
Notifications
You must be signed in to change notification settings - Fork 24.5k
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
CreateProcess error=2, The system cannot find the file specified #25488
Comments
me too!!! |
Same problem with: |
Same problem here .... this is probably with the new version of react-native-0.60.0 info Starting JS server...
FAILURE: Build failed with an exception. |
Same problem. Even after using version 0.59.9 the "ERROR: Build failed with an exception" is being displayed.
FAILURE: Build failed with an exception.
Deprecated Gradle features were used in this build, making it incompatible with Gradle 6.0. BUILD FAILED in 5s |
👋 there, can you check that you are using the cli version 2.0.2? There was an issue with windows that was related to that -> react-native-community/cli#464 to make sure you will install it, you should check in your yarn.lock which version got installed - it should say something like
if instead the version is 2.0.1, you should remove that portion from the yarn lock and your yarn again. If it still happens, please open a dedicated issue in that repo -> https://github.com/react-native-community/cli |
still not working |
Why this issue has been closed? The error still persists. |
As I mentioned, this is an issue with the CLI and since it's in a dedicated repo now, the issue should be opened there. |
Still the same probleme |
this is so disheartening. I still have the same problem.. |
React Native version:
Steps To Reproduce
Describe what you expected to happen:
Build successful apps in android emulator or real device
!!! I have searched for more than half a day for this problem but I have not resolved it, I tried to go back to version 0.59.9 to install and use, no problem occurred.
The text was updated successfully, but these errors were encountered: