Console mode

After downloading and installing Mobitru Connect, you can run it in the Console mode. For macOS and Linux, the Console and UI applications are one file, while there are two separate files for Windows.

There are two ways to start the application from a console application:

  • .env file.
  • parameters typing directly in the console.

Start with .env file

You should follow the steps to start Mobitru Connect in the Console mode with the help of the .env file:

  1. Prepare the .env file with these parameters:
  • HOST: URL of the platform where you use the Remote debugging feature.
  • DEVICE_UDID: Serial number or UDID of a device that will be used.
  • API_KEY: your access key.
  • ADB_PORT: the parameter is optional. 5038 is the default port.
  • LT_PROXY: the parameter is optional and needed for Proxy. If the feature is needed, use “”. Leave empty and do not type in the .env file, if not needed.
  • LOG_LEVEL: the parameter is optional. To see debug logs, you should type “debug”.

Example of the file:

Parameters in the .env file for Mobitru Connect.
  1. Place the .env file in the same folder where the Mobitru Connect application is kept.
  1. Open the folder with .env and application in a Console/Terminal application.
Opening an application in Terminal on Windows
  1. On the platform, start the device from the DEVICE_UDID field.
  2. In the Terminal, run a command of the feature you need:
Remote debugging: name_of_the_app --no-ui --remote-debug
Local tunneling: name_of_the_app --no-ui --local-tunnel
Proxy: name_of_the_app --no-ui --local-tunnel 

Example for Windows: mobitru-connect-console.exe --no-ui --local-tunnel
Example for macOS: mobitru-connect --no-ui --remote-debug
  1. Open your IDE.
  2. Check the device in the device list.

Start from a Terminal app

  1. Open the folder with the Mobitru Connect tool in a CMD/Terminal application.
  2. Paste the command to the CMD/Terminal:
Remote debugging: name_of_the_app --no-ui --remote-debug --device-udid UDID_value --api-key YOUR_API_KEY --host HOST_WHERE_DEVICE_IS --adb-port 5038
Local tunneling: name_of_the_app --no-ui --local-tunnel --device-udid UDID_value --api-key YOUR_API_KEY --host HOST_WHERE_DEVICE_IS --adb-port 5038
Proxy: name_of_the_app --no-ui --local-tunnel --lt-proxy --device-udid UDID_value --api-key YOUR_API_KEY --host HOST_WHERE_DEVICE_IS --adb-port 5038

Example for Windows: mobitru-connect-console.exe --no-ui --remote-debug --device-udid BHtest1072 --api-key mobitru_ak_SpbolNwmkteste6QsUIZTC_test60w2AgtestBgvNXntmZFtsF1test5IbsHfjHGKjiWI78Ianz9auiTT6P --host --adb-port 5038
  1. Start the device on the platform.
  2. Run the command from Step 2.
  3. Open your IDE.
  4. Check the device in the device list.

Notes for Xcode

For macOS, take into account the following moments:

  • Debug symbols will be downloaded for every iOS device you use for the first time for Remote debugging. If you have downloaded the symbols for a device, this step will not appear.
  • Open Xcode in the very end after running the Remote debugging command. If you have opened XCode earlier, you will need to reopen it. Otherwise, you will not see the device in the list.
Scroll to Top