Couldn't adb reverse: closed

[wrightmk]

I'm trying to get up and running with my recently detached app. First I run the app in Android Studio and then I try to connect my external device to Expo XDE (via usb debugging), but Expo is returning “Tunnel connected, Couldn’t adb reverse: closed”. The external device has the error message “Could not load exp://j3-iqd.. Are you sure XDE or exp is running?” I've checked some of the stack overflow posts on the matter and my adb version is the same in android studio and on my local machine. Any Idea on why this isn’t working?

[jimmylee]

Assigning @fson to have a look at it and see if he can help.

[fson]

The latest release of exp (v47.1.1) includes a fix to adb reverse. Can you try upgrading and then run exp start to see if that fixes the problem for you?

[wrightmk]

I upgraded from v45 to v47.1.1, however, the problem is still persisting

[exp] Using project at /Users/whosbuddy/Desktop/test
[exp] Warning: Not using the Expo fork of react-native. See https://docs.expo.io/.
[exp] Starting React Native packager...
[exp] Scanning folders for symlinks in /Users/whosbuddy/Desktop/test/node_modules (55ms)
[exp] Loading dependency graph.
[exp] Couldn't adb reverse: closed
[exp] Tunnel connected.
[exp] Expo is ready.
[exp] Your URL is: exp01d3c6d99348422ca4aab5539bd88105://5q-bhf.wrightmk.test.exp.direct:80
[exp] Logs for your project will appear below. Press Ctrl+C to exit.
[exp] Dependency graph loaded.
[exp] Warning: Not using the Expo fork of react-native. See https://docs.expo.io/.

[fson]

Thanks for upgrading.

Just a few things to check come to mind:

• Can you double check that USB debugging is enabled on your phone?
• Does running adb devices list your phone?
• If not, run adb usb to make sure adb is in USB mode and then check adb devices. If that doesn’t help you can also restart adb server with adb kill-server; adb start-server

[wrightmk]

• USB debugging is enabled on the device
• The device isn't a phone, it's a pos machine running Android 4.4.4
• I've run adb kill-server and fired it up again and still no luck.

Btw I've managed to build a test create-react-native-app using expo and then run the program on my pos machine through android studio using adb install . Since this works, I know the machine is capable of running react native, the issue only seems to rise when interacting with XDE.

[haydencarlson]

I’m having this issue to

[SytzeAndr]

I'm getting the following log on genymotion+xde

17:33:09 Couldn't adb reverse: closed 17:33:09 Downloading latest version of Expo 17:33:10 Installing Expo on device 17:33:11 Opening on Android device 17:33:12 Couldn't start project on Android: Error running adb: Error running app. Error: Activity not started, unable to resolve Intent { act=android.intent.action.VIEW dat=exp://c2-5cj. ... .exp.direct:80 flg=0x10000000 }

Same issue here when trying to run on genymotion+xde. It seems to fail on genymotion android versions with 4.x.x when opened with xde.

It fails on 4.1.1, 4.2.2 but works on 7.1.0, 6.0.0 and 5.1.0

I tried testing it on a real phone (both using xde and using the terminal), which runs 4.4.2, and this doesn't raise the issue.

[soulawaker]

In my case, on a real android 4.1.2 device with expo 50.0.1

21:03:53 [exp] Couldn't adb reverse: closed
21:03:54 [exp] Downloading latest version of Expo
21:03:55 [exp] Installing Expo on device
21:04:02 [exp] Opening on Android device
21:04:03 [exp] Couldn't start project on Android: Error running adb: Error running app. Error: Activity not started, unable to resolve Intent { act=android.intent.action.VIEW dat=exp://192.168.0.111:19000 flg=0x10000000 }

(node:17798) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'length' of null
    at /xdl/src/Android.js:88:18
    at Generator.next (<anonymous>)
    at step (<user>/.nvm/versions/node/v8.10.0/lib/node_modules/exp/node_modules/xdl/build/Android.js:473:191)
    at <user>/.nvm/versions/node/v8.10.0/lib/node_modules/exp/node_modules/xdl/build/Android.js:473:361
    at <anonymous>
    at process._tickCallback (internal/process/next_tick.js:188:7)
(node:17798) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:17798) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Ah, expo doesn't support 4.1. I find it lately

[siran12]

[19:54:29] Starting Metro Bundler on port 19001.
[19:54:29] Metro Bundler ready.
[19:54:30] Couldn't adb reverse: closed
[19:54:30] Expo DevTools is running at http://localhost:19002
[19:54:31] Opening DevTools in the browser... (press shift-d to disable)
Error: spawn cmd ENOENT
at Process.ChildProcess._handle.onexit (internal/child_process.js:232:19)
at onErrorNT (internal/child_process.js:407:16)
at process._tickCallback (internal/process/next_tick.js:63:19)

[siran12]

pls reply this problem

[mauld-tech]

I same this issues on genymotion android 5.1.0

[fson]

I’m closing this issue because it has been open for a long time and some of the information in this thread might not be relevant to the latest Expo CLI versions anymore.

If you're still having this issue, please open a new issue and make sure to provide as much information as possible (see the issue template).