Remote debugging allows testers and developers to connect to remote devices, directly to their local PC/MAC machines. This tutorial guides you on how to get started with remote debugging on iOS and Windows.
This table details the remote debugging capabilities based on the mobile/desktop OS.
|Desktop OS||Mobile OS|
|MAC OS||iOS \ Android|
- Remote debugging on iOS is enabled only when connecting from a macOS machine. Make sure the SeeTest Remote Debugging CLI and Xcode is installed.
- When working from macOS machines, Xcode must be closed when initiating the Remote Debugging session. Otherwise Xcode will not identify the device.
- It is not recommended to use remote debugging on devices connected to DHM's with latency greater than ~50ms (round trip).
To enable remote debugging:
- Open a device. To learn how to open a device, see Mobile Devices.
- Click Tools → Remote Debugging. The Remote Debugging dialog appears. The dialog contains all the information to get started with CLI tool.
- Click Download.
- Install the tool.
For the Mac OS, double-click the downloaded file, then click OK.
Warning for MAC OS
If you get a malicious software warning, click System Preferences → Security & Privacy -> General, then click Open Anyway.
For Windows, open the zip file, then open command line session.
Note: If your network is behind a proxy, see Configure Proxy for Remote Debugging.
- In a command line, run
- Copy the text to the clipboard from the Remote Debugging window.
Paste it into the terminal and enter to start the debugging session. Once the session is up, the Debugging icon turns red ().
You can now start debugging.
To debug using Xcode:
- Make sure Xcode is closed.
- Start a debugging session.
Click Window -> Devices and Simulators.
Wait for Xcode to finish making the device ready for development.
To debug using Android Studio:
- Open Android Studio.
Wait a few seconds for Android Studio to fully load.
Choose your device as a target.
Run your application.