(My WSL is Ubuntu 18.04, this is untested on other flavors.) There's a bit more to setting up this side of things, so bear with me. This is pretty straightforward so I'm not gonna walk you through that. The only thing required on the Windows side is to install Android Studio and setup the emulator / virtual device. Here is what you need to do to get it working. The benefits of doing it this way over way is that this way supports autolinking. It is possible to set it up so that the emulator runs in Windows while running react-native run-android in WSL.

Note: For this to work your project needs to be located in the native Windows file system i.e.

I've tested this out with some fairly complex projects using multiple native Android components. Once the APK has been assembled and uploaded to your device or emulator, run the debug server from within WSL using the command react-native start. From the /android directory inside your project, execute the gradle wrapper gradlew.bat installDebug, or with the Creator's Update, you can do this from inside the WSL bash shell /mnt/c/Windows/System32/cmd.exe /C gradlew.bat installDebug. No need for a duplicate windows binary node/npm stack.ĭon't use react-native run-android, instead compile and deploy from cmd. react-native-cli installed globally in WSL.

The trick is to separate out the Gradle based Android compile.Īll project setup and package management performed in WSL with npm/yarn.

Realistically, you'll want to install the native Windows Android Studio/SDK to use the Intellij IDE and the emulator anyway. However, I've found a workaround that combines a native windows android build with a npm stack in WSL.

AFAIK it is not possible to use react-native in WSL due to a number of issues.

Android emulator mac os x 10.4