Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

new project with RN 0.60.3 returns ENOENT

See original GitHub issue

Clean install with react-native init AwesomeApp results with ENONET error on react-native run-android

React Native version: 0.60.3 IDE: Visual Studio Code

System: OS: Windows 10 CPU: (8) x64 Intel® Core™ i7-7700HQ CPU @ 2.80GHz Memory: 2.47 GB / 7.95 GB Binaries: Node: 10.3.0 - C:\Program Files\nodejs\node.EXE npm: 6.1.0 - C:\Program Files\nodejs\npm.CMD IDEs: Android Studio: Version 3.4.0.0 AI-183.6156.11.34.5692245

Steps To Reproduce

run react-native init AwesomeApp
run react-native run-android

Describe what you expected to happen:

Command to execute successfully.

Error:

error Failed to run jetifier. Error: spawnSync E:\DEV\AwesomeApp\node_modules\jetifier\bin\jetify ENOENT at Object.spawnSync (internal/child_process.js:981:20) at spawnSync (child_process.js:588:24) at execFileSync (child_process.js:616:13) at Object.runAndroid [as func] (E:\DEV\AwesomeApp\node_modules\@react-native-community\cli-platform-android\build\commands\runAndroid\index.js:101:41) at Command.handleAction (E:\DEV\AwesomeApp\node_modules\react-native\node_modules\@react-native-community\cli\build\cliEntry.js:160:21) at Command.listener (E:\DEV\AwesomeApp\node_modules\commander\index.js:315:8) at Command.emit (events.js:182:13) at Command.parseArgs (E:\DEV\AwesomeApp\node_modules\commander\index.js:651:12) at Command.parse (E:\DEV\AwesomeApp\node_modules\commander\index.js:474:21) at setupAndRun (E:\DEV\AwesomeApp\node_modules\react-native\node_modules\@react-native-community\cli\build\cliEntry.js:210:24)

Issue Analytics

State:
Created 4 years ago
Reactions:2
Comments:14 (3 by maintainers)

Top GitHub Comments

1reaction

sambestsolutionscommented, Jul 16, 2019

It’s closed because cli published a fix, so next time you init a fresh project or regenerate the lock file (to use cli v2.6.2 or newer), jetifier should be executed properly.

Thanks Got it to work…

1reaction

thymikeecommented, Jul 16, 2019

It’s closed because cli published a fix, so next time you init a fresh project or regenerate the lock file (to use cli v2.6.2 or newer), jetifier should be executed properly.

Top Results From Across the Web

Upgrading to new React Native versions

Upgrading to new versions of React Native will give you access to more APIs, views, developer tools and other goodies.

Failed to start application in for latest React-native

My React-native version is 0.60.3. ... I opened up a new terminal window within the project and ran react-native ... RN is never...

Troubleshooting | React Navigation

Troubleshooting. This section attempts to outline issues that users frequently encounter when first getting accustomed to using React Navigation.

task :react-native-reanimated:buildcmakedebug failed - You.com

I created a new project with "create-react-native-app" and then ejected it to plain react native project. When i try to run "react-native run-android"...

Installation | React Native Navigation - Open Source

If autolinking is not available in your project (RN version < 0.60), you can always try and install the hardcore way: In Xcode,...