+1 Same issue.

+1 here, using iPhone with iOS version 13.3.

+1 Same

+1

See #180 (comment)

@auchenberg Just going to keep posting here as #180 seems to be unrelated and #138 which seems more related has already been closed as fixed with commit #177

Running npm i -g remotedebug-ios-webkit-adapter@next as described in the comment you referenced on #180 and then running the remotedebug_ios_webkit_adapter --port=9000 still does not work in Windows 10 running in PowerShell and Chrome.

Running remotedebug_ios_webkit_adapter --port=9000 results in the following console error:

remotedebug-ios-webkit-adapter is listening on port 9000
undefined:1

SyntaxError: Unexpected end of JSON input
at JSON.parse ()
at Request.request [as _callback] (C:\Users\joe\AppData\Roaming\npm\node_modules\remotedebug-ios-webkit-adapter\out\adapters\iosAdapter.js:45:38)
at Request.self.callback (C:\Users\joe\AppData\Roaming\npm\node_modules\remotedebug-ios-webkit-adapter\node_modules\request\request.js:185:22)
at emitTwo (events.js:126:13)
at Request.emit (events.js:214:7)
at Request. (C:\Users\joe\AppData\Roaming\npm\node_modules\remotedebug-ios-webkit-adapter\node_modules\request\request.js:1161:10)
at emitOne (events.js:116:13)
at Request.emit (events.js:211:7)
at IncomingMessage. (C:\Users\joe\AppData\Roaming\npm\node_modules\remotedebug-ios-webkit-adapter\node_modules\request\request.js:1083:12)
at Object.onceWrapper (events.js:313:30)

and the Devices page shows shows any open chrome tabs and installed chrome extensions under RemoteDebug iOS Webkit Adapter as shown here:

Running remotedebug_ios_webkit_adapter --port=9222 starts with no error, but the devices tab shows nothing under localhost as the original issue described:

Both ports localhost:9000 and localhost:9222 are specified in the Target discovery settings

@imjoeco Fantastic, thanks for the debugging and instructions to reproduce! I hope someone has time to jump into and help debug this further.

+1 (also for iPhone)

+1

Also having this issue with both iPhone 6s and iPad Pro with iOS version 13.3 when trying to inspect on Mac OS. I see the devices listed on chrome://inspect under Remote Target, but when clicking Inspect, just a white blank window opens.

+1

need to use weinre for now ? They've broken alot of things in IOS 13

Same here apparently, blank windows.

everyone seems to be having the same issue :(

facing same issue on iOS 13.3.1 iPhone 6s

Blank window
remotedebug-ios-webkit-adapter@next
Chrome dev 82.0.4068.4
Fedora 31
node v13.9.0
ProductType: iPhone6,2, iOS 12.4.5

+1 same issue, I've this error: remotedebug_ios_webkit_adapter : The term 'remotedebug_ios_webkit_adapter' is not recognized as the name of a cmdlet

+1
iOS 13.3.1 iPhone XR
remotedebug-ios-webkit-adapter@next
Chrome 80.0.3987.149
latest Win 10

Ok, looks like its not fixed yet +1

I updated to the most recent version of the adapter with:

npm update remotedebug-ios-webkit-adapter -g

After doing that, I was able to see the screen. @next did not work for me.

I updated to the most recent version of the adapter with:
npm update remotedebug-ios-webkit-adapter -g
After doing that, I was able to see the screen. @next did not work for me.

This helped!

I updated to the most recent version of the adapter with:

npm update remotedebug-ios-webkit-adapter -g

After doing that, I was able to see the screen. @next did not work for me.

This worked for me too

Also having this issue with both iPhone 6s and iPad Pro with iOS version 13.3 when trying to inspect on Mac OS. I see the devices listed on chrome://inspect under Remote Target, but when clicking Inspect, just a white blank window opens.

The same for me.

The debug proxy has a supposed fix but there is no release binary. Only the broken one is released. There is no documentation how to build yourself.

Same problem, @next did not work for me either

The debug proxy binary fix has never been released, I have mentioned it 3 times and nobody has bothered. Once they release a new tag version it should work. There is no instructions how to compile yourself. I had to struggle with weinre and ngrok hacks to debug over ssl, barely worked and slow.

@Kibukita, @danrossi

This helped me

I updated to the most recent version of the adapter with:

npm update remotedebug-ios-webkit-adapter -g

After doing that, I was able to see the screen. @next did not work for me.

Thanks @burnot,

I tried update but problem remains, I can see remote target in Chrome but after click on "inspect" only a blank window appears

@danrossi, dou you know if weinre or ngrok can be used to debug a phonegap app? I haven´t found an alternative tool to debug proxy for debugging an ios phonegap app from Windows, does anyone know one? I am a bit frustated.

I recovered an old iPad with 10.3.3 and debug proxy works perfectly but the new one with 12.4.6 only shows the blank window.

Potential lead - having had what looks to be the same issues (though currently running iOS 13.5, connected to Windows 10 1909 and Chrome 83), I was able to inspect pages if I'm running iTunes at the same time.

Same here - it works openning iTunes :)
@BernieMK thanks for the tip

Finally got it to work after my iOS update, this is what worked for me: (iOS 13.5.1, Win10)

• Update iOS Webkit Debug Proxy: scoop update ios-webkit-debug-proxy
• Update Remotedebug iOS Webkit Adapter : npm update remotedebug_ios_webkit_adapter
• Keep iTunes open

@Nyota Thanks

Finally Works on iphone 7 13.5.1 & iphone 6 12.4.7
Windows 10

Best I can get is for it to show up in Chrome's devtools (multiple times, oddly), click inspect, and white screen. Have tried all I've seen on this issue.

Windows 10 version 1909 (18363.900)
iOS 13.4.1, iPhone 11 Pro
npm 6.14.5
node v12.18.2

It used to work for iOS 13 previously for my iPhone XR on Windows 10

Now I have iOS 13.5.1 and console on the Chrome DevTools does not log any message.
Sometimes it logs messages but without variable values.

var temp_var = "test variable";
console.log("value is: ", temp_var);

this just logs this on console:

value is:

and now since it has stopped logging to the console it's pretty much impossible to debug

@manmohanbishnoi That's not how you concatenate in Javascript. console.log("value is: " . temp_var not a comma.

@manmohanbishnoi That's not how you concatenate in Javascript. console.log("value is: " . temp_var not a comma.

@eristic it was just an example
for debugging Javascript Objects this comma syntax will dump object on the console; otherwise you will get [Object] in the console output.

anyways the output is empty when I try to debug such things

Finally got it to work after my iOS update, this is what worked for me: (iOS 13.5.1, Win10)

• Update iOS Webkit Debug Proxy: scoop update ios-webkit-debug-proxy
• Update Remotedebug iOS Webkit Adapter : npm update remotedebug_ios_webkit_adapter
• Keep iTunes open

Not working on iOS 13.6.1 . Blank console, no network data. It does show the DOM elements though.

Same blank page as everyone else is getting. It seems like every time I try to pick up this library I have to work for 3 hours just to get it to work :'D

Same blank page as everyone else is getting. It seems like every time I try to pick up this library I have to work for 3 hours just to get it to work :'D

Well did you manage to get it to work? Because I wasted my time installing this debugger only to find out it doesn't work. Had to get myself a cheap Mac.

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.