Spiritual successor?

[HimbeersaftLP]

Hey! I found your project was genius, so I took inspiration from it and decided to make an automated script that works with the latest version of WebKit. You can find it here: https://github.com/HimbeersaftLP/ios-safari-remote-debug-kit

It'd be cool if you could link it in your README (and maybe also the README of https://github.com/artygus/devtools-compat-proxy) or something, as it looks like you abandoned the project and there is no other free option for remote debugging iOS Safari on non-Macs.

[p0358]

Shameless plug, I developed my fork and it works pretty well: https://github.com/p0358/webkit-webinspector

As described in readme, it requires the use of a WebKit-based browser on the computer to work properly. It does not include or touch ios-webkit-debug-proxy as that thing does not need any modification as it's used only to expose the websocket to the computer.

[HimbeersaftLP]

@p0358 My project doesn't change anything about ios-webkit-debug-proxy either, the only changes I make are to the Webkit-Webinspector to make it compatible with Chromium-based browsers.

[artygus]

hey guys, I've abandoned that repo for a while, happy to see the idea lives!

I've just updated WebInspectorUI to latest version available for local debugging experiments, only to find out that @p0358 had done the same 😅 @HimbeersaftLP I like the all-in-one approach of https://github.com/HimbeersaftLP/ios-safari-remote-debug-kit 💪🏾 Let me see if I can figure out the iOS 16 compatibility issues.

[HimbeersaftLP]

@artygus if you mean the problem with ios-webkit-debug-proxy failing to connect, I don't think it's down to the iOS version as people have had the issue with 15 already and 16 works fine for a lot of other people. It's probably something with the host setup, but I can't really attempt to debug it because I can't reproduce the issue.