Page tree
Skip to end of metadata
Go to start of metadata

Remote Debug Bridge CLI is a command-line tool that allows you to use a remote device as a local device.

This allows you to develop and debug on several devices that are managed in the Cloud Server.


  1. Install the SeeTest Remote Debugging tool.
  2. The Device must be reserved for the current user.
  3. iOS:
    1. Works only on Mac machine with one device (client side).
    2. Requires good network conditions between the cloud machine and the local machine.
    3. iTunes and Xcode must be closed before starting the remote debugging.
  4. Android - Works with Mac and Windows machines, and can work with up to 4 devices in parallel.

Commands and Descriptions

helpnonePrints help message to the console

versionnonePrints the product version

Connects to device from cloud server and starts remote debugging

[-udid <device udid>]The UDID of the device (mandatory if the 'store' command is not used)

[-ip <ip>]Cloud server IP (mandatory if the 'store' command is not used)

[-port <port>]Cloud server port (mandatory if the 'store' command is not used)

[-project <project_name>]

Project name (if not mentioned will use the default project)


For secured cloud

trustStorePath <Path>Truststore path, if the cloud is secured

-agentPath <agentPath>

For single port cloud, to get agent path:

  1. Open device from the Cloud UI
  2. Look on the tab URL: for example
  3. Agent path is: 'agent-25'


Verbose (print log to console)

[-timeout <timeout>]

Set timeout (in seconds) for the remote session


Connect to the device using the access key

Gets all the projects for the current user

[ip <ip>]Cloud server ip

[-port <port>]Port

[-v]Verbose (print log to console)

Fixes connection issues with iOS devices (requires admin permissions)

[-v]Verbose (print log to console)

Receives the path to the Remote Debug Bridge tool log file


Stores the username and password for connecting to the cloud server (data encrypt)


Stores the Cloud Server information

-ip <ip_adress>Cloud server ip

-port <port>Port

[-project <project name>]Project name

Remove all stored data (user credentials and server information)

[-v]Verbose (print log to console)

Usage Examples 

 This example will demonstrate how to work with a remote Android device.

  1. Open a command line in the SeeTest Remote Debugging folder and run rdb credentials to store the cloud username and password.

    usage: rdb store -ip <ip> -port <port>
    C:\Program Files (x86)\Experitest\SeeTestRemoteDebugging>rdb credentials:


  2. Run rdb store to store the cloud IP and port, for example:

    usage: rdb store -ip <ip> -port <port>
    C:\Program Files (x86)\Experitest\SeeTestRemoteDebugging>rdb store -ip -port 80

  3. Open the Cloud UI to reserve the remote device and to get it a device ID.

  4. Run rdb connect to connect to the remote device.

    usage: rdb store -ip <ip> -port <port>
    C:\Program Files (x86)\Experitest\SeeTestRemoteDebugging>rdb connect -udid ce05160545dc6d3702

    The device is now attached as local to the client machine.


    You must keep the console alive during the remote session, closing the console will disconnect the remote device.

    The device must be reserved, releasing the device or session timeout will disconnect the remote device.

  5. You can now open Android Studio to work with the connected device.



  1. Android - ADB version mismatch

    The ADB version in the SeeTest Remote debugging installation folder <Installation_Folder>\bin\adb\ must be the same version as in your Android SDK folder.
    To check the version, open the command line and run the command ADB version from the ADB folder.
  2. iOS - Local devices do not return after using Remote Debugging feature
    Please try the following:
    1. Close iTunes and Xcode and then reopen them again
    2. Run the command rdb repair

  3.  iOS & Android - Failed to connect to the RDB daemon 
    In order to establish a connection with the remote device, we need to restart the RDB daemon

Mac machine

 Open a terminal and run the following commands (required admin password):

Kill rdb daemon

sudo launchctl unload -w /Library/LaunchDaemons/com.experitest.remotedebuggingdaemon.plist


Start rdb daemon

sudo launchctl load /Library/LaunchDaemons/com.experitest.remotedebuggingdaemon.plist

Windows Machine
Open the task manager and go to the services tab, restart the 'RemoteDebuggingDaemon' service.



  • No labels