If your execution has not started and is still showing the Queued Status, please check the below guide for more details:
How to fix permanently 'Queued' executions for Local executions in my Testsigma Account?

 

Otherwise, if your execution failed or did not execute and gave an error message, please check the below list to see if the error is listed here. If not, please contact Support.


1.  java.net.ConnectException: Connection refused


Complete Error message:

Exception in initiating a browser session in path: java.net.ConnectException: Connection refused (Connection refused)


Solution:

This is mostly caused when there is a connection issue between the Appium Server and Testsigma. Please perform the following steps:

  1. Confirm that you have started the Appium Server on the local machine using Command line or Appium Desktop App. A running Appium-server is needed for Android/iOS Hybrid Executions.
  2. If the Appium server is indeed started, next check if the Appium listener IP:Port is the same as the Appium URL in the Execution Configuration.


Note: If it still doesn't work, please contact Testsigma Support on Instant Chat or mail to support@testsigma.com and provide the Appium logs.


2. Unable to start WebDriverAgent session because of xcodebuild failure


Complete Error message:

[MJSONWP] Encountered internal error running command: Error: Unable to start WebDriverAgent session because of xcodebuild failure: "Could not proxy command to remote server. Original error: Error: socket hang up". Make sure you follow the tutorial at https://github.com/appium/appium-xcuitest-driver/blob/master/docs/real-device-config.md. Try to remove the WebDriverAgentRunner application from the device if it is installed and reboot the device.


Solution:

This is most probably a temporary issue. Please perform the following steps:

  1. Uninstall WebDriverAgentRunner app on iOS device if already installed.
  2. Reboot the iOS device and the Mac PC.
  3. Try again.


Note: If it still doesn't work, please contact Testsigma Support on Instant Chat or mail to support@testsigma.com and provide the Appium logs.

3. Cannot start the <app_package_name> application. Original error: Error executing adbExec.


Complete Error message:

Exception in initiating a browser session in path:, An unknown server-side error occurred while processing the command. Original error: Cannot start the 'com.jillstuart.beauty.app.stg' application. Original error: Error executing adbExec. Original error: 'Command 'C\:\\Users\\huy.nvt\\AppData\\Local\\Android\\Sdk\\platform-tools\\adb.exe -P 5037 -s 3100dc566118a2a5 shell am start -W -n com.jillstuart.beauty.app.stg/com.jillstuart.beauty.app.activity.MainActivity -S' exited with code 1'; Stderr: 'java.lang.SecurityException: Permission Denial: starting Intent { flg=0x10000000 cmp=com.jillstuart.beauty.app.stg/com.jillstuart.beauty.app.activity.MainActivity launchParam=MultiScreenLaunchParams { mDisplayId=0 mBaseDisplayId=0 mFlags=0 } } from null (pid=30564, uid=2000) not exported from uid 10717


Reason for Error:

The permission to start <activity_name> activity has been denied. Make sure activity/package names are correct.The package name or activity name is not correct

OR
A user doesn't have permission to start the Activity due to missing permissions in the manifest.Double check the Activity and package name or try another activity name.


Solution:

  • Double check the Application Package Name and Activity Name for spelling mistakes.
  • Make sure the user has permission set in the manifest to start the Activity or use another activity that has the permission. Usually, the Splash or Main Activity will be permitted to start from. Please check the following article - Permission to start activity denied while launching the app


Note: If it still doesn't work, please contact Testsigma Support on Instant Chat or mail to support@testsigma.com and provide the Appium logs.

4. Unrecognized SSL message, plaintext connection?


Complete Error message: 

Exception in initiating a browser session in path:, javax.net.ssl.SSLException: Unrecognized SSL message, plaintext connection?


Solution:

Please check the Appium URL given in Execution Configuration(Create Run) page and make sure it starts with http and not https.

i.e the Appium URL should be similar to http://0.0.0.0:4723/wd/hub ( Not https://0.0.0.0:4723/wd/hub)


Note: If that's not the case, please try again or contact Testsigma Support on Instant Chat or mail to support@testsigma.com and provide the Appium logs.