Not working when tethering is on #23241
Labels
Ran Commands
One of our bots successfully processed a command.
Resolution: Locked
This issue was locked by the bot.
When I run the app on my device, It worked fine. After that, I have turned the USB tethering mode ON for getting my laptop connected in order to access internet. After that "react-native run-android" stopped working .Even though I turned the tethering mode OFF, It is not working.
This is the error log:
react-native run-android
JS server already running.
Building and installing the app on the device (cd android && ./gradlew installDebug)...
FAILURE: Build failed with an exception.
Execution failed for task ':app:installDebug'.
Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.
Get more help at https://help.gradle.org
BUILD FAILED in 1s
28 actionable tasks: 1 executed, 27 up-to-date
Could not install the app on the device, read the error above for details.
Make sure you have an Android emulator running or a device connected and have
set up your Android development environment:
https://facebook.github.io/react-native/docs/getting-started.html
Command failed: ./gradlew installDebug
Error: Command failed: ./gradlew installDebug
at checkExecSyncError (child_process.js:625:11)
at Object.execFileSync (child_process.js:643:13)
at runOnAllDevices (/home/charanrajh/ToDo/node_modules/react-native/local-cli/runAndroid/runAndroid.js:299:19)
at buildAndRun (/home/charanrajh/ToDo/node_modules/react-native/local-cli/runAndroid/runAndroid.js:135:12)
at isPackagerRunning.then.result (/home/charanrajh/ToDo/node_modules/react-native/local-cli/runAndroid/runAndroid.js:65:12)
at processTicksAndRejections (internal/process/next_tick.js:81:5)
Also when I tried the command "adb devices", this is the log:
List of devices attached
MCCDU17905002875 no permissions (user in plugdev group; are your udev rules wrong?); see [http://developer.android.com/tools/device.html]
The text was updated successfully, but these errors were encountered: