-
Notifications
You must be signed in to change notification settings - Fork 24.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Setting react-native run-android to use a custom adb.exe #13397
Comments
+1 |
Hi there! This issue is being closed because it has been inactive for a while. Maybe the issue has been fixed in a recent release, or perhaps it is not affecting a lot of people. Either way, we're automatically closing issues after a period of inactivity. Please do not take it personally! If you think this issue should definitely remain open, please let us know. The following information is helpful when it comes to determining if the issue should be re-opened:
If you would like to work on a patch to fix the issue, contributions are very welcome! Read through the contribution guide, and feel free to hop into #react-native if you need help planning your contribution. |
I had the same problem I solved, then react-native run-android |
Can anyone help me to fix same issue on Windows machine? |
I am in the same case as @jackyef . |
I have same problem, Im using NOX,too. When create app using |
Somehow I managed to solve this issue. Let me share it on this thread for future references. This solution has three parts Mobile Emulator (NOX)
Connectivity:
then just go to the react native project folder and write Ps. For me this solution works with a smalllllllll exception, sometimes I get that the nox_adb.exe (check step 2 in connectivity) has stopped working but just close that window cause the emulator is working perfectly for me. |
@ShooterArk I got this In your Connectivity step 2 you said rename the adb.exe to nox_adb.exe inside the sdk/platform-tools folder what did I do wrong? |
@makiabuan did you make a copy in the NOX folder and then renamed it to nox_adb.exe ? |
@ShooterArk Thanks bro. Your solution works perfectly. |
@makiabuan I have same problem in my mac, but I already solved.
export ANDROID_HOME=$HOME/Library/Android/sdk
export PATH=$PATH:$ANDROID_HOME/tools
export PATH=$PATH:$ANDROID_HOME/tools/bin
export PATH=$PATH:$ANDROID_HOME/platform-tools WARNING: PLEASE make sure Windows can Refer to this configure-the-android-home-environment-variable. Don't forget to choose the If the above still doesn't work, Do the second step:
|
I have been trying to deploy a react-native app to the Nox emulator.
Apparently, the emulator comes with its own adb.exe. More info about this: https://www.bignox.com/blog/how-to-connect-android-studio-with-nox-app-player-for-android-development-and-debug/
The problem is, everytime I run
react-native run-android
, the cli will fail to find a device, eventhough the custom adb.exe clearly found a device before. My guess isreact-native
doesn't call the right adb.exe, because everytime I runreact-native run-android
, a new adb.exe process will be started. So I add a PATH to the custom adb.exe, and remove the PATH adb.exe that comes with the Android SDK. It still fails. The same thing still happens.react-native run-android
:react-native run-android
:The reason that I want to use nox emulator is because the other emulators are simply too slow on my machine. I tried AVD and genymotion, both are really slow on my machine, for whatever reason. Nox though, runs very smoothly on my machine, I have even played some games on it for several months.
Can anyone help me with this? It will be really appreciated! Thanks!
The text was updated successfully, but these errors were encountered: