React Native on Android: Cannot run program "node": error=2, No such file or directory
Asked Answered
B

32

163

EDIT: I am uncertain which steps I took to resolve this problem, and am no longer seeing this error message so I cannot test the solutions below. Please try them individually as different answers seem to be working for different people.

The iOS version works fine, but running Android Studio on my Mac I get the following Gradle Build error (paraphrased):

:ReactNative:Running ‘[node, -e, console.log(require(‘react-native/cli’).bin);]’ command failed.

- Where:
Script ‘/Users/…/Desktop/…/node_modules/@react-native-community/cli-platform-android/native_modules.gradle’ line: 154

- What went wrong:
A problem occurred evaluating script.
> Cannot run program “node”: error=2, No such file or directory

Caused by: java.io.IOException: Cannot run program “node”: error=2, No such file or directory

I've tried so many things:

I used to be able to still run yarn android in Terminal, but even that has stopped working.

Billet answered 20/5, 2020 at 20:17 Comment(1)
JetBrains issue was created for this: youtrack.jetbrains.com/issue/TBX-7313Entopic
F
394

It's because Android Studio couldn't find node and should be run from a terminal window.

If you are using Mac you can run Android Studio using this command in terminal. Note that if Android Studio is already running, it will need to be shut down completely before running the command.

1. Run this open -a /Applications/Android\ Studio.app

If you installed Android Studio through Jetbrains Toolbox version 1.x, run

open -a ~/Applications/JetBrains\ Toolbox/Android\ Studio.app

If you installed Android Studio through Jetbrains Toolbox version 2.x, run

open "Applications/Android Studio.app"

2. Then sync Gradle

And this will solve the problem.

Note: If you are using Node through nvm, you should run nvm use [version] in the same terminal window before running the above command to open Android Studio.

Fourierism answered 5/9, 2021 at 18:22 Comment(8)
Worked for me on Apple Silicon @TimurGaitov for whatever reason Android Studio is not using .zshrc PATH vars so opening it from terminal ensures that it willGlanville
I guess, this is a bug in Android Studio Bumblebee 2021.1.1. Same for me on Intel Mac. Related bug report, I found: youtrack.jetbrains.com/issue/TBX-7313Bibliophile
Fixed in Android Studio Bumblebee | 2021.1.1 Patch 1 (February 2022): androidstudio.googleblog.com/2022/02/…Bibliophile
This worked but you may better upgrade to the latest Android Studio which also solved the problem. For me it's from 2021.x.x to 2022.3.1Subak
@PabloMiranda Doesn't work for me. Any other workaround?Vitus
Using Android Studio Iguana | 2023.2.1 and it is still the same node error, so it is definitely not fixed in later Android Studio versions.Loadstone
Unfortunately it's not working. I encountered this issue previously and it has been solved. But suddenly got this again. Damn RN!Vitus
it's 2024 and this doesn't work. I can open up Android Studio and in it's terminal, it can find node. But whatever is running the cli thing that VSC is triggering, can't find node. Perhaps react native has found some new clever way to run whatever script is causing this problem because Android Studio's ability to find node seems unrelated, but I am not sure.Billon
P
105

In my case with this setup:

  • Apple chip M1
  • Android Studio arctic fox 2020.3.1 Patch 2

I previously ran the command mentioned above, but I kept getting the same error:

sudo ln -s "$(which node)" /usr/local/bin/node

I had to update the gradle version in the project (android/gradle/wrapper/gradle-wrapper.properties)

from:

distributionUrl=https\://services.gradle.org/distributions/gradle-6.7-all.zip

to:

distributionUrl=https\://services.gradle.org/distributions/gradle-6.9-all.zip

and execute this command in the project:

cd android && ./gradlew clean

or just delete this folder instead of the executing the previous command: android/.gradle

And after doing these steps I no longer have any problem.

Projector answered 2/10, 2021 at 19:35 Comment(2)
I am already on Gradle 6.9 and I still have this issue.Haaf
Its not working for me in M1 Macbook ProTouraine
A
98

Simply linking node (installed previously by nvm) to /usr/local/bin/node.

sudo ln -s "$(which node)" /usr/local/bin/node

Ubuntu 20.4, Node 14.15.0

Analogical answered 19/11, 2020 at 10:34 Comment(3)
this doesn't resolve the issue for some reason, I'm on macOS catalina, do u have an idea what else I could try ?Humo
This resolved my issue. The reason why this worked is because I used to run Android Studio from terminal which had the .bashrc loaded and thus knew where to find node executable. The problem occurred when I ran Android Studio outside the terminal and my .bashrc did not load. If node is installed using nvm, then it won't have an executable on the PATH, unless you explicitly add it to the PATH. The command above will add a symlink to /usr/local/bin/ which is on the PATH and it will point to the location of node executable.Hurff
Worked for me on Ubuntu latest. Android terminal was somehow able to run node, but build command always gave error about node.Feltie
K
55

Solution

Running chmod +x /Applications/Android\ Studio.app/Contents/bin/printenv in the terminal and restarting Android Studio will make the gradle sync work again.

Detail

I am using the latest Android Studio and I did a patch update of the application. My system is running macOS 12.1 on a M1 Pro Apple CPU.

After the restart I could not run my react native application and the gradle sync failed. Any fixes above did not help for me. So I read the gradle log file idea.log in detail. In the very beginning in the log I see the application printenv has some issues.

loading shell env: /bin/zsh -l -i -c '/Applications/Android Studio.app/Contents/bin/printenv' '/var/folders/7y/gz2kx4917yl_804mbfrnkqxc0000gn/T/intellij-shell-env.9046002349811239017.tmp' 
...
.intellij.util.EnvironmentUtil - can't get shell environment 
java.io.IOException: command [/bin/zsh, -l, -i, -c, '/Applications/Android Studio.app/Contents/bin/printenv' '/var/folders/7y/gz2kx4917yl_804mbfrnkqxc0000gn/T/intellij-shell-env.9046002349811239017.tmp']
exit code:126 text:0 out:zsh:1: permission denied: /Applications/Android Studio.app/Contents/bin/printenv

After that I go to folder /Applications/Android Studio.app/Contents/bin/ and list printenv in my terminal and saw that printenv did not have the execute rights:

-rw-r--r--@ 1 user admin 152080 Jan 28 09:12 printenv

Android Studio

Android Studio Bumblebee | 2021.1.1 Build #AI-211.7628.21.2111.8092744, built on January 19, 2022 Runtime version: 11.0.11+0-b60-7772763 aarch64 VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o. macOS 12.1 GC: G1 Young Generation, G1 Old Generation Memory: 2048M Cores: 10 Registry: external.system.auto.import.disabled=true

Kilah answered 28/1, 2022 at 9:36 Comment(2)
This was the issue for me also, same setup. Though the command had to be entered as follows to escape the space in the directory: chmod +x /Applications/Android\ Studio.app/Contents/bin/printenvWarrant
This fixed the issue for me as well after upgrading to Android Studio Bumblebee. For anyone who installs Android Studio through Jetbrains Toolbox, the fix is the same, just with a different path, i.e. chmod +x ~/Library/Application\ Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/211.7628.21.2111.8092744/Android\ Studio.app/Contents/bin/printenvUnasked
S
39

For M1 Mac, I downloaded Android Studio (Mac with Apple Chip) version and faced this issue.

It got fixed for me by changing the gradle version to 6.9-rc-1.

This can be done from File -> Project Structure -> Project -> Gradle Version -> Type or select "6.9-rc-1" and click OK button.

You can find similar and more solutions here as well.

Gradle sync failed: Cause: error=2, No such file or directory

Spada answered 22/10, 2021 at 17:40 Comment(0)
D
24

Android Studio uses PATH environment variable that is available when the Android Studio process is started up, and your Node binary directory should be in that PATH.

I got this same error in Linux when I had Node installed via n (Node version management tool) which sets the Node path at Bash startup.

The problem in my case was that I started the Android Studio from the desktop and because the Bash startup file was not executed, also the Node path was not set.

The solution was to run Android Studio from the command line.

You could also try to pass the PATH environment variable directly to Android Studio while starting it from the command line:

PATH=$PATH:/path/to/node/bin/ /path/to/android/studio/bin/studio.sh
Doak answered 22/5, 2020 at 13:24 Comment(2)
Since my node is already in /usr/local/bin/node, the answer from @Analogical doesn't help. However, open Android Studio from terminal as suggested here resolves the issue. I don't have to specify the PATH.Crofoot
@FanchenBao you can add the path in the file bin/studio.sh then you don't have to run android studio from command lineCartier
C
18

I'm on my Mac, and i solve this by close the android studio completely(close the process), and restart it.

Coster answered 7/4, 2021 at 3:17 Comment(2)
Thanks, seems to happen after MacOS updates for some reason, but a restart fixes.Typhus
that fixed it for me. on Mac, you can press command + q to close an app entirelySummertime
S
17

Had the same issue in m1 mac and opening the android studio via terminal worked for me
open -a /Applications/Android\ Studio.app

So answered 9/11, 2022 at 5:26 Comment(2)
There is already an accepted answer with the same solution. It would be better to keep @Aly's answer as primary choice.Woolsack
Doesn't work for my m2 Mac.Vitus
I
9

On a Mac with M1, upgrading Android Studio fixed the issue for me. I upgraded from Arctic Fox to Bumblebee.

Also used this version of Gradle (android/gradle/wrapper/gradle-wrapper.properties):

distributionUrl=https\://services.gradle.org/distributions/gradle-6.9-bin.zip
If answered 24/3, 2022 at 13:35 Comment(0)
D
6

Invalidate Caches & Restart on File Tab in Android Studio.

Doggoned answered 27/5, 2022 at 9:20 Comment(0)
S
6

I just ran into this issue as well, and for me the solution was to stop the running Gradle daemon:

./gradlew --stop
Styria answered 13/10, 2022 at 0:45 Comment(0)
G
5

How I solved the same issue.

  1. Open Android studio via terminal
  2. Build Project Like before

Note: I installed node via nvm (I believe that's why I had the issue)

If you installed android studio via snap then its pretty simple to launch it via command line.

Open project folder in terminal and run:

android-studio .

Graybill answered 9/3, 2021 at 10:16 Comment(0)
U
5

I struggled with this a long time on my M1 mac mini. I was getting this error after opening RN android project in Intellij IDEA during gradle sync and also while trying to run ./gradlew commands from command line.

What seems to be a solution for me:

  • rm -rf .gradle (in the RN_PROJECT/android folder)
  • killall java (to stop running gradle daemon)
  • updated node to v16.8.0

I think the real solution is the first step. Now the project opens in IDEA without errors and I can run ./gradlew commands.

Ushijima answered 31/8, 2021 at 6:59 Comment(0)
R
5

In android Studio, I solved this problem when it happened to me as follows:

1 - Go to File - Invalidate Caches / Restart; 2 - Choose the option "Invalidate and Restart".

Ratha answered 4/10, 2021 at 11:11 Comment(0)
T
3

I have tried most of the answers posted here but the only solution worked was to upgrading the gradle to 6.9 or later.

File -> Project Structure -> Project -> Gradle Version = 6.9(Select version 6.9 or later from dropdown).

Wait for it to download all modules and it should load your project.

Torietorii answered 25/4, 2022 at 14:56 Comment(0)
A
2

I was able to make it work in android studio bumblebee by running this command in terminal on mac,

sudo chmod +x /Applications/Android\ Studio.app/Contents/bin/printenv

and then restart the android studio.

Albanese answered 3/2, 2022 at 8:35 Comment(0)
A
2

you can use: open your project -> run:

npx react-native bundle --platform android --dev false --entry-file index.js --bundle-output android/app/src/main/assets/index.android.bundle

Acetometer answered 14/2, 2022 at 9:35 Comment(1)
run: open -a /Applications/Android\ Studio.appAcetometer
I
2

Adding what worked for me on MacOs Monterey.

I updated the graddle version using one of the solutions here. This can be done from File -> Project Structure -> Project -> Gradle Version -> Type or select "6.9-rc-1" and click OK button.

Double-check if node is installed with node --version, if it is open -a /Applications/Android\ Studio.app Open the project and the error should disappear.

Inescutcheon answered 30/5, 2022 at 19:31 Comment(0)
R
1

You can kill gradle daemon, or just restart your machine if you made some changes, and it will work.

Ricotta answered 8/9, 2021 at 8:24 Comment(0)
W
1

Many of these answers are half-right but you must do both of these things:

  1. Make sure that the $PATH variable includes wherever your node is installed. You will will probably set this in .bashrc.

  2. Start Android Studio from the command-line.

Waac answered 28/10, 2021 at 20:25 Comment(0)
V
1

Change the default JDK version from Android studio embeded JDK11 to JDK zulu version. That works for me on Apple M2. This changed the gradle scripts running env PATH, after which node can be found. But I don't know why this change affect env.

Vesture answered 13/9, 2023 at 8:57 Comment(0)
G
0

I had this issue on M1 mac, found a solution after 3 days, it was because of nvm and .zsh having issues. If you used brew to install it like i did, it's going to cause a lot of issues.

Solution:

I had to uninstall nvm

rm -rf ~/.nvm
rm -rf ~/.npm
rm -rf ~/.bower

Then install nvm via instructions on readme on its github page

curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.0/install.sh | bash

Other than that, there is a section about troubleshooting M1 macs, that might help futher if needed. But other than that, Android Studio works fine now without having to open it via terminal or any other work-arounds. (You might have to agree to the sdk license agreement if your build fails, view the build tab for the issue, to agree to the license, just go to Tools > Sdk Manager and uninstall the sdk, click apply and retick it and Apply to reinstall it and it will ask you about the license agreement also.

Garage answered 25/10, 2021 at 8:41 Comment(0)
O
0

This is not a specific answer to the question, but as some of the comments here helped me resolve my issue, maybe this answer will help someone else.

I was struggling to run a Gradle project using Intellij IDEA on Ubuntu 22.04. It was giving me the same error: Cannot run program "X": error=2, No such file or directory.

Here is what I did to overcome that:

echo 'export PATH=$PATH:/path/to/X' >> ~/.bashrc

echo 'export PATH=$PATH:/path/to/X' >> ~/.profile

sudo echo 'export PATH=$PATH:/path/to/X' >> /etc/environment

I also added the path variable to Intellij IDEA: click File -> Settings -> Path Variables and then add the variable in question (name of the program: X).

As @Jari-Jokinen mentioned above, for the IDE to use program 'X' from /path/to/X you need to restart your computer. Both Intellij IDEA and Android Studio are similar and developed by Jetbrains, so I hope this can be useful to someone.

Ogive answered 10/5, 2022 at 14:55 Comment(0)
K
0

For me.

I'm using a Mac Pro 2019 with Intel Processor.

when I executed yarn Android I got that same error the author said.

The only thing that really works.

Looks like that, in my case, some Android Studio config was wrong.

Kimi answered 7/7, 2022 at 21:28 Comment(0)
K
0

There are a lot of solutions about this issue and most are talking about updating the gradle plugin. I have tested a lot of solutions and running the latest Android Studio version (Chipmunk 2021.2.1 Patch 1).

The main issue is still that AndroidStudio, with gradle version lower than 6.9.x, can not lookup properly the PATH environment, which is set by /bin/printenv tool from Android Studio application package itself. If you see in the Android Studio logfile that it can not execute the printenv command, please update to latest Android Studio version.

In 'Project Structure' select 'Gradle Version' 6.9 or higher and you can build your project properly.

In 'Project Structure' select 'Gradle Version' 6.9 or higher

Kilah answered 13/7, 2022 at 9:49 Comment(0)
B
0

You should update Android Studio to latest version. It does work for me.

Ban answered 7/9, 2022 at 3:26 Comment(0)
W
0

You can upgrade your Android studio to 2021.3.1. Its working for us.

Wauters answered 20/10, 2022 at 11:26 Comment(0)
O
0
  1. close android studio
  2. end any android task from the task manager
  3. use terminal to build the app using
cd android && ./gradlew build
  1. launch android studio
  2. you should be able to run your app on a simulator
Operation answered 16/11, 2022 at 16:22 Comment(0)
C
0

I was also facing issue on Mac(Monterey 12.6.1).I don't know what was the exact reason but I've just upgraded my Android studio artic fox to Android Studio Dolphin | 2021.3.1 Patch 1. And surprisingly my issue is resolved.

Calyptra answered 18/11, 2022 at 19:3 Comment(0)
K
0

Nothing helped me, just when I changed Gradle JDk it started working

Klos answered 20/6, 2023 at 14:52 Comment(1)
In my case running one project with "react-native": "0.61.2", worked after install azul-11 - Azul Zulu 11.0.20, just using the gui to install.Lopeared
O
0

If you're using nvm, this can work: https://mcmap.net/q/94654/-react-native-on-android-cannot-run-program-quot-node-quot-error-2-no-such-file-or-directory

But you need to run nvm use [version] (or just nvm use if you have an .nvmrc configured) in the terminal before launching android studio.

Otiliaotina answered 24/7, 2023 at 22:1 Comment(0)
V
-2

If you have a M1 Mac and are using Android Studio:

Venterea answered 9/9, 2021 at 10:7 Comment(1)
This is good advice for M1, I found that same JDK as one of the few native options for JDK. But I guess it's not directly relevant to this question.Haaf

© 2022 - 2024 — McMap. All rights reserved.