(node:50307) UnhandledPromiseRejectionWarning: #<Object>

[tomayac]

• Device: iPhone 6s
• OS: iOS 13.3
• Browser: Edge Canary v81

I have tried this with a first time clean install following the (great!) instructions from the README. After running the tool, I can see the device show up in Edge DevTools (since Chrome Beta v80 has disabled Custom Elements v0 that the DevTools inspector code relies on) and can open a DevTools window, but then the remotedebug-ios-webkit-adapter console logs the following error:

(node:50307) UnhandledPromiseRejectionWarning: #<Object>

Full logs:

New websocket connection to /ios_4dcba3dc5102f3d8f829044e420e54e74c7b3b7c/ws://127.0.0.1:9101/devtools/page/1
Connection established to ws://127.0.0.1:9101/devtools/page/1
iosAdapter.getTargets
iosAdapter.getTargets
iosAdapter.getTargets
(node:50307) UnhandledPromiseRejectionWarning: #<Object>
(node:50307) 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:50307) [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.
(node:50307) UnhandledPromiseRejectionWarning: #<Object>
(node:50307) 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: 2)
(node:50307) UnhandledPromiseRejectionWarning: #<Object>
(node:50307) 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: 3)
(node:50307) UnhandledPromiseRejectionWarning: #<Object>
(node:50307) 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: 4)
(node:50307) UnhandledPromiseRejectionWarning: #<Object>
(node:50307) 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: 5)
(node:50307) UnhandledPromiseRejectionWarning: #<Object>
(node:50307) 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: 6)

[unstablereality]

I am experiencing this same issue
iOS 13
iPhone 11 Pro
Chrome 79
Mac OS 10.14.6

Same behavior for me. I have installed everything from head and it fails to show any information within the debugger window. I was able to verify that everything works as expected with another phone running iOS 11, leading me to believe this is an iOS 13 related issue.

[aappddeevv]

I'm on iOS 12.4.5, ipad air 1 and am experiencing it. I reinstalled the software with brew using --HEAD.

I also do not receive any console messages.

[auchenberg]

This project is now super-seeded by https://inspect.dev/ – a new developer tool for macOS and Windows to inspect and debug your web apps and websites in Safari and WebViews on iOS devices.

RemoteDebug iOS WebKit Adapter is not proactively maintained or extended.