-
Notifications
You must be signed in to change notification settings - Fork 90
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
Socket hang up #98
Comments
Are you able at point 3 to run:
If not, there's some TCP connection issue with your phone. |
Nope, I am not able to. Any help on how to proceed about it? |
I did packet capture and could see a few ports connected to 9222 constantly. (exchanging keep-alive messages) I guess forwarding should have worked fine. are you saying that I should capture packets on the mobile device interface? |
So the reason is this:
I have no idea why this fails on Chrome for Android, in any case this issue concerns |
Environment
| Component | Version
| Node.js | v12.22.9
| Client (Chrome/Chromium/...) | Google Chrome 123.0.6312.58
| OS running Node.js | Ubuntu 22.04
| OS running the client | Ubuntu 22.04
| chrome-remote-interface | 0.31.3
Is the client running in a container? NO
Description
I was trying to run the following the set of commands (basically to capture HAR file from android) chrome
(1) adb shell am start -n com.android.chrome/com.google.android.apps.chrome.Main
(2) adb forward tcp:9222 localabstract:chrome_devtools_remote
(3) chrome-har-capturer --force --port 9222 -o my.har http://www.example.com
Issue received: Socket hang up
How to solve this?
The text was updated successfully, but these errors were encountered: