WDB(WeTest Debug Bridge) is a tool that let your local Mac or PC to connect to the remote WeTest cloud device for conveniently debugging the device locally. Please follow the instructions below to start remote debugging.
Connecting a WeTest device to your local machine
MacOS
- Go to WeTest Console and open a real device in Live Testing
- [Optional] Run the following command to backup the current usbmuxd domain socket.
sudo mv /var/run/usbmuxd /var/run/usbmuxd_bak
- Download the wdb tool and Run the command to connect to the WeTest iOS device. If you encounter the problem “command not found”, you should run
chmod +x wdb
in your local terminal,

- If the port is already in use, you can use
wdb -p <port> start-server
to change the port.

- Use
./wdb devices
to see the devices you have connected.
- After finishing your remote debugging, use
./wdb disconnect
to disconnect with devices.
Linux
Steps to Start Remote Debugging
- Go to WeTest Console and open a real device in Live Testing
- [Optional] If /var/run/usbmuxd exists, Run the following command to backup the current usbmuxd domain socket
sudo mv /var/run/usbmuxd /var/run/usbmuxd_bak
- Download the wdb tool and Run the command to connect to the WeTest iOS device

- You can use tools on Linux to debug the iOS remote device now.
- Use
./wdb devices
to see the devices you have connected.
- After finishing your remote debugging, use
./wdb disconnect
to disconnect with devices
Windows
Steps to Start Remote Debugging
- Go to WeTest Console and open a real device in Live Testing.
- If iTunes is installed, then Run the following command to stop the “Apple Mobile Device Service” service.
net stop "Apple Mobile Device Service"
- Download wdb.exe and Run the command to connect to the WeTest iOS device

- You can use tools on Windows to debug the iOS remote device now.
- Use
./wdb devices
to see the devices you have connected.
- After finishing your remote debugging, use
./wdb disconnect
to disconnect with devices
FAQs
1. command not found?
- In your local terminal, run
chmod +x wdb
2. Run wdb but showing a popup “developer cannot be verified” ?