Autolinking fails on Windows

[thecodrr]

Environment

System:
    OS: Windows 10
    CPU: (8) x64 Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz
    Memory: 9.61 GB / 15.89 GB
  Binaries:
    Node: 10.16.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.16.0 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
    npm: 6.9.0 - C:\Program Files\nodejs\npm.CMD
  SDKs:
    Android SDK:
      Android NDK: 18.1.5063045
  IDEs:
    Android Studio: Version  3.3.0.0 AI-182.5107.16.33.5264788

Output of react-native --version:

react-native-cli: 2.0.1
react-native: 0.60.0

Description

This is the error I am getting while running react-native run-android or .\gradlew app:installDebug:

:ReactNative:Cannot run program "./node_modules/.bin/react-native" (in directory "C:\Users\thecodrr\Source\Repos\Mysue\android\.."): CreateProcess error=2, The system cannot find the file specified
:ReactNative:Automatic import of native modules failed.

> Configure project :app
:ReactNative:Cannot run program "./node_modules/.bin/react-native" (in directory "C:\Users\thecodrr\Source\Repos\Mysue\android\.."): CreateProcess error=2, The system cannot find the file specified
:ReactNative:Automatic import of native modules failed.

I tried running the gradlew app:installDebug command on Git Bash but still got the same error.

Reproducible Demo

1. Create a new project using react-native init
2. Run yarn add react-native-track-player@latest
3. Run yarn react-native run-android

[thymikee]

Hey! Thanks for filing this issue. Unfortunately we don't have Windows machines to test on. We used to do node ./node_modules/.bin/react-native config, but we got a report that it doesn't work on Windows, but ./node_modules/.bin/react-native config works. So could you share some more information about that?

[victorwpbastos]

I confirm that ./node_modules/.bin/react-native config works on Windows 10 and node ./node_modules/.bin/react-native config doesn't.

[thymikee]

It's already resolved and fixed in @react-native-community/cli@2.0.2, make sure you have it installed (check the lock file)

[victorwpbastos]

I already have the version 2.0.2 installed:

"@react-native-community/cli@^2.0.1":
  version "2.0.2"
  resolved "https://registry.yarnpkg.com/@react-native-community/cli/-/cli-2.0.2.tgz#a157722d2a506e7e9a7d1079e3032b18ef6b0378"
  integrity sha512-U0v8QuFYnX9AvUOew9LfJS9FgnDtYsz7HhbsRyvXtaFu4kUnq2g7MgkC4zG0y3oqQzlOxhcO7Hoyv80XDsBQoQ==

[thymikee]

Then you have a caching issue :) check your node modules, the updated code is there

[victorwpbastos]

I deleted the node_modules folder and run yarn again. I confirm that @react-native-community/cli@2.0.2 was installed correctly, but the error still persists:

> Configure project :app:ReactNative:Cannot run program "./node_modules/.bin/react-native" (in directory "C:\Users\vbastos\Desktop\chundaApp\android\.."): 
CreateProcess error=2, O sistema nÒo pode encontrar o arquivo especificado
:ReactNative:Automatic import of native modules failed.

[thecodrr]

Okay so doing node ./node_modules/.bin/react-native config gives this:

* Where:
Script 'C:\Users\thecodrr\Source\Repos\Mysue\node_modules\@react-native-community\cli-platform-android\native_modules.gradle' line: 182

* What went wrong:
A problem occurred evaluating settings 'Mysue'.
> Text must not be null or empty

And doing node ./node_modules/react-native/cli.js config stops the gradle from proceeding, stucking on this:

<-------------> 0% INITIALIZING [7s]
> Evaluating settings 

In the second case, the node process never exits so cmdProcess.waitFor() keeps waiting and waiting. In the first case, the command only inits the node without executing the command.

Adding a delay of, let's say 5 seconds, with cmdProcess.waitFor(5000, java.util.concurrent.TimeUnit.MILLISECONDS) and command node ./node_modules/react-native/cli.js config executes without a hitch albeit after waiting 5 seconds to get config.

[thecodrr]

@thymikee I upgraded to 2.0.2 but the error still persists. I have this command ./node_modules/.bin/react-native config in my native_modules.gradle file.

[thecodrr]

@thymikee after deleting node_modules folder, doing yarn cache clean the problem is still there. I tried on Git Bash, Powershell and CMD. And version is 2.0.2. So can we please reopen this?

[thymikee]

Sure. But you'll need to help us make it work with your environment. We got signals that it works on some Windows, but looks like not all of them. Help appreciated :)

[thymikee]

Also check if running this command alone, run from terminal, produces a json output. Maybe it takes too long