You just flew a few hours and are now safely ensconced onsite with your customer’s team, ready to help them troubleshoot the awesome app they built with OutSystems. Then, you realize they want you to test it on iOS phones. All you have is your beloved state-of-the-art laptop running Windows.

What to do now? First, don’t panic. Here's what you need to know to troubleshoot iOS on Windows.

What You Need

Like every good mechanic (which will be kind of your job here) knows, the best way to repair anything starts with the right set of tools. To troubleshoot iOS on Windows, your toolbox must include a few things.


Scoop is a command line installer that you will be using to install other tools. To install it make sure you have PowerShell 3 or later, installed in your machine and .NET Framework 4.5 or later. To verify your PowerShell version, go on your PowerShell console and run the following command, to get information about your PowerShell version:


After you have verified that you are in version 3 or later, install scoop by running the following command in the PowerShell console:

iex (new-object net.webclient).downloadstring('')

In some cases, you can get errors in the installation, due to some policy issues. If that’s the case, run the following command and then repeat the installation command:

Set-ExecutionPolicy RemoteSigned -scope CurrentUser

Scoop Extras

Scoop Extras is an extra bucket that will allow you to install the remaining dependencies. To do it, go on the PowerShell console and run:

scoop bucket add extras


Install Git so you can access the WebKit debugger Proxy and the Adapter. In the PowerShell console, run the following command:

scoop install git

troubleshoot ios on windows


You’ll need the latest iTunes on your computer. If you are installing it, make sure that you have your PC updated, you are at least on Windows 7, and you use the Microsoft Store version of iTunes. This allows you to establish the connection to the iOS device to test and to get its Unique Device Identifier—the UDID—as well.


The Node.js JavaScript runtime includes npm, a package manager for JavaScript that enables the installation of WebKit Adapter and the libimobile. Follow the instructions for installation and then reboot your computer.

iOS WebKit Debug Proxy

iOS WebKit Debug Proxy allows debugging in iOS by managing the requests from the Adapter. To install it, run the following command in the PowerShell:

scoop install ios-webkit-debug-proxy

libimobiledevice Library

The libimobiledevice library. This is the tool that will help you communicate with any iOS device that you are using in your debug. To install it, just go on the PowerShell console and run:

npm install -g vs-libimobile

Remote Debug iOS WebKit Adapter

And finally, there’s the Remote Debug iOS WebKit Adapter. This is a tool that enables iOS/Safari debugging by using the Google Chrome Debugging Protocol.

troubleshoot ios on windows

To install it, open the PowerShell console and install the package for the WebKit Adapter by running the following command:

npm install remotedebug-ios-webkit-adapter -g

Now that you have your toolbox ready, it’s time to get the hands dirty.

Let’s Get Hands-On!

First of all, enable the remote debugging on the iOS device used for testing. Go to the device Settings, tap the Safari icon, and open the Advanced menu. Turn the Web Inspector switch on.

troubleshoot ios on windows

Troubleshooting a Mobile App

If you are troubleshooting a mobile app, you need to to have an Apple Developer account and get an iOS App Development certificate. Find more information about this subject here.

Also, your app should be generated in Development mode. To learn what you have to do to ensure this, check this article.

If you are troubleshooting a UI problem (JS or CSS related), I recommend troubleshooting them by replicating the issue on Safari. To do this, copy the app webview link to the iOS device browser. This way, we don’t need the certificates mentioned.

If you need to debug further than the UI, you must, on your computer, open iTunes and keep it running. This guarantees the connection between your PC and the iOS phone during the whole operation.

Connect the iPhone and choose to trust your computer, if prompted. Click on the phone icon that just appeared in the top-left corner of the iTunes window to show all the information about the connected device.

troubleshoot ios on windows

Then click on the Serial Number field until it changes to the UDID code of the phone connected:

 troubleshoot ios on windows

Right-click the UDID string and select Copy to keep the device identifier:

troubleshoot ios on windows

The iPhone UDID you copied needs to be attached to a Provisioning profile. Learn how here.

Troubleshooting a Web App

And what about web apps? Well, they are way simpler. You just have to open the app link in the device’s Safari browser and start debugging as described in the next section. Easy peasy.

3, 2, 1, Debug!

Now that we have everything in place, it’s time to start the remote debugging. First, execute this line in your PowerShell console:

remotedebug_ios_webkit_adapter --port=9000

Note that in some cases, you might have to try a different port number instead of the default 9000 value. For example, try 9221 or 9222.

We now have open communication between our PC and our Device, is time to:

  1. Open the web app URL in the device’s Safari browser or open the mobile app on the device.
  2. Open Google Chrome, on your PC and, in the address bar, type:
  3. The Device menu for Chrome DevTools is displayed. In it, click on Configure... and add the port used for debugging:

How to Troubleshoot iOS on Windows

In the Remote Target list, select the app/link you want to troubleshoot and click the Inspect link:

troubleshoot ios on windows

A new window will open, and in it, you should be able to see your app in the Chrome DevTools window:

troubleshoot ios on windows

You now have access to the app that you are debugging; it’s time to have fun!

In Case It Goes South

If Inspect is not working correctly and not refreshing the elements and the applied CSS, my one recommendation is the biggest IT cliché. Just try to turn it off and on again. Unplug the iPhone cable, plug it back in again, go back to Chrome, and see if you can finally inspect your app.

The Power and the Glory at Last!

You can finally dive deeply into the iOS app and start hunting for those miserable and annoying bugs. You're back on track, go get yourself some bugs, and show your customer who’s the best! May the glory be with you!