How to fix command node issue while building android app with react-native?

Question

I am using react-native and updated android studio to 3.0. After updating while trying to debug on a device I am getting a build error.

Error:Execution failed for task ':app:recordFilesBeforeBundleCommandDebug'.
> A problem occurred starting process 'command 'node''

I have stopped and rerun the gradle but I'm getting the same error.

The solution written here might help you fix it: github.com/expo/expo/issues/28309#issuecomment-2405560702 — ashuvssut
– ashuvssut, Commented Aug 27 at 23:41

Mohssine Oussama · Accepted Answer · 2024-10-22 19:08:31Z

88

for me i had to open Android Studio from terminal using this command for Mac users open -a "Android Studio"

answered Oct 22, 2024 at 19:08

Mohssine Oussama

1,0798 silver badges12 bronze badges

Sign up to request clarification or add additional context in comments.

5 Comments

Armando Marques da S Sobrinho Nov 20, 2024 at 14:09

for me fixed also, but I don't understand why, this happened after an update I did on my mac, note, the android studio app is on an external hard drive, could that be why?

Jacob Sherwood Mar 25 at 15:57

This also fixed my issues. I'd also like to understand why. The only difference I noticed was Android studio downloading a new gradle when opened via cmd line

jose920405 Apr 4 at 15:50

It Worked. My theory is that this command is telling Android Studio what node version is set in the terminal. But if someone is clear about what is internally happening, please share it.

jvp May 27 at 22:37

Worked for me as well. I suspect this is because an environment variable isn't set correctly in the app, but is in the shell. Anyway, similarly, if Android Studio is installed for all users, this command should also work: /Applications/Android\ Studio.app/Contents/MacOS/studio

Akshay I Jun 3 at 10:57

Is there any proper solution, open android studio using command is not proper solution.

Abhishek · Accepted Answer · 2020-11-07 23:31:03Z

51

./gradlew --stop and then start the build your project again.

answered Nov 7, 2020 at 23:31

Abhishek

1,43013 silver badges22 bronze badges

3 Comments

Justice Mba Over a year ago

Thanks! Any explanation why this worked?

Abhinandan Kushwaha May 1 at 0:00

Mysteriously works! After wasting multiple hours banging my head across different solutions, this seemingly minusucle command worked like a charm!!

Nhan Jul 21 at 11:43

Wonderful! It’s the bundle command in my case ./gradlew bundleRelease.

Rajesh Vyas · Accepted Answer · 2025-02-20 16:27:23Z

14

You just need to fix the Gradle JDK version in settings. Go to Android Studio Settings->Build Execution, Deployment -> Build Tools -> Gradle and update the Gradle JDK version.

I wiped out my ~/.gradle folder that's why it had reset the Gradle JDK version and I have to set it again to correct version going to the Settings.

This solved for me https://github.com/expo/expo/issues/28309

edited Feb 20 at 16:27

answered Feb 14 at 22:24

Rajesh Vyas

3011 gold badge4 silver badges11 bronze badges

1 Comment

starball Feb 14 at 23:52

please expand. meta.stackexchange.com/a/8259/997587

Igor Vanian · Accepted Answer · 2018-01-08 23:33:32Z

5

Just got this error myself. Actually, just close Android Studio when doing ./gradlew assembleDebug in your cmd. It just blocks gradle node execution somehow.

answered Jan 8, 2018 at 23:33

Igor Vanian

4105 silver badges15 bronze badges

1 Comment

Frexuz Over a year ago

Wow, who could have guessed this :O

AverageProgrammer · Accepted Answer · 2025-08-27 10:52:29Z

This happens each time for me when installing Android Studio on a new mac, I have to change the Gradle JDK location to JAVA_Home instead of what the default value of Android Studio is. Change it by going to Android Studio Settings -> Build Execution, Deployment -> Build Tools -> Gradle JDK

For example, my JAVA_HOME is java 17 but Android Studio defaults to Jetbrains Runtime 21, which causes the

A problem occurred starting process 'command 'node'

error for me.

Check that Android Studio uses the actual Java version you want it to use. Using SDKMan in terminal doesn't mean that Android Studio also defaults to that Java Version.

Celso Wellington · Accepted Answer · 2025-09-30 14:27:57Z

This error may happen when there is a mismatch between the versions of the Java running in your environment and the required Java version of your project.

I ofter run with this problem between projects since I maintain multiple project (most of them are legacy) and usually fix the issue by selecting the correct Java version.

If you're running on MacOS, you can solve this issue by changing the java your terminal is using: You can just run

export JAVA_HOME="/Users/YOUR_USERNAME/Library/Java/JavaVirtualMachines/{JAVA_INSTALATION_FOLDER}/Contents/Home"

just replace JAVA_INSTALATION_FOLDER for your desired Java version and YOUR_USERNAME to your username folder. This works for Sequoia 15 or later

You can also do this on Android Studio by opening Settings > Build, Execution, Deployment > Build Tools > Gradle and changing the Gradle JDK version (you can install multiple java versions using Android Studio)

Collectives™ on Stack Overflow

How to fix command node issue while building android app with react-native?

6 Answers 6

5 Comments

3 Comments

1 Comment

1 Comment

Comments

Comments

Linked

Hot Network Questions

Collectives™ on Stack Overflow

6 Answers 6

5 Comments

3 Comments

1 Comment

1 Comment

Comments

Comments

Linked

Related