Support for iOS 12.2

[Dan-Maor]

It appears as if there was a change in the way Web Inspector works with iOS 12.2; when I try to check the inspectable pages none are retrieved (using the latest version from brew, 1.8.3).

It should be noted that as of the latest Mojave release the official Safari inspector is not working as well, however I am not able to test it with the latest Mojave beta since I can't upgrade my machine.

Your assistance will be highly appreciated.

Thanks,
Dan.

[3Spiders]

i have the same problem. https://www.zhihu.com/question/313614095

[artygus]

hi @Dan-Maor is it still an issue? and does it happen for both simulator and ios devices?

[oberhamsi]

i'm testing with an ios device and with the latest master from a few min ago i can now see the pages and open the inspector but nothing shows up. not even the URL in the address bar. i tried the default safari inspector and the chrome dev tools.

[artygus]

@oberhamsi check out readme https://github.com/google/ios-webkit-debug-proxy#using-with-devtools

[oberhamsi]

thanks, i'm trying this now. chrome used to work before 12.2 with a few glitches.

[artygus]

oh then it could be something else

[oberhamsi]

same effect with remotedebug_ios_webkit_adapter. i can now see the ios safari pages in chrome://inspect/#devices, i can open the inspector but it's just as empty as with "raw" ios-webkit-debug-proxy

i get a ton of errors in the --debug log. i don't want to put it all online b/c not sure what i'm leaking with it. some snippets are:

{"erro
 .r":{"code":-32601,"
 .message":"'Runtime'
 . domain was not fou
 .nd","data":[{"code"
 .:-32601,"message":"
 .'Runtime' domain wa
 .s not found"}]}
 
{"erro
 .r":{"code":-32601,"
 .message":"'Emulatio
 .n' domain was not f
 .ound","data":[{"cod
 .e":-32601,"message"
 .:"'Emulation' domai
 .n was not found"}]}

[artygus]

the messages look good, meaning iwdp actually proxies messages. seems like some changes must be done in compatibility layer

if I have some free time anytime soon I'll take a look and ping you back

[imurchie]

On iOS 12.2 everything is wrapped in Target messages and events, and the rest of the protocol is not exposed.

• iOS sends Target.targetCreated and Target.targetDestroyed messages to indicate that things are connected/disconnected (this is in addition to apps).
• All messages get wrapped in a Target.sendMessageToTarget to a particular target.
• iOS returns, for a particular message, an empty event (which I take as a read receipt) and then a Target.dispatchMessageFromTarget event which has the return data (often wrapped in multiple nested results properties).

For some sort of reference, Appium's implementation for handling data messages can be found here: https://github.com/appium/appium-remote-debugger/blob/master/lib/remote-debugger-message-handler.js#L174-L248

[auchenberg]

Interesting set of changes. This is essentially Apple adopting the Target domains in DevTools Protocol.

Work for mapping this to Chrome DevTools should probably land in https://github.com/RemoteDebug/remotedebug-ios-webkit-adapter/

[auchenberg]

Tracking in RemoteDebug/remotedebug-ios-webkit-adapter#138

[benmalka]

Why is this a closed issue? It seems that it's proxying the messages but there's still a problem with the protocol like @imurchie said