

The protocol is compatible with the Chrome Debugging Protocol for the script debugging APIs, and this means our debugger works without additional mapping logic. To make the connection from our debugging library to the iOS device, we are leveraging two open-source projects, ios-webkit-debug-proxy and ios-webkit-debug-proxy-win32, that enables communication with the iOS devices over USB through the WebKit Remote Debugging Protocol. Under the hood, it’s the same debugger running inside VS Code, which is powered by our open-source vscode-chrome-debug-core library. Our new iOS Web Debugger works quite similar to our Chrome debugger which we introduced back in February. This debug extension works on both Mac and Windows. Today, we’re enabling mobile web developers to debug JavaScript running on their iOS devices directly from their editor with a new iOS Web Debugger for Visual Studio Code. For example, using the Safari Web Inspector (Safari DevTools) requires an instance of desktop Safari which only is available for macOS users. Introductionĭebugging websites running on iOS devices is accessible only to a subset of developers. To learn more, see this introductory guide to the RemoteDebug iOS WebKit Adapter.

The iOS Web debugger has been deprecated and we now recommend that you use the RemoteDebug iOS WebKit Adapter together with Visual Studio Code.
#Os x simulator attach debugger to app code
Node.js Development with Visual Studio Code and Azure.

Moving from Local to Remote Development.
