Troubleshooting automated mobile testing

• Connect your device to Xcode.
• Go to Settings -> Developer > turn ON UIAutomation.

• Check if your device is recognized using the following commands on Terminal.

  cd /Applications/Katalon\ Studio.app/Contents/Eclipse/configuration/resources/tools/imobiledevice 
  idevice_id -l

  If your iOS version is iOS 11, make sure Katalon Studio's version is 5.3+.

• Developer option is turned on.
• A trusted connection is established by tapping on 'Trust this computer' whenever this dialog is displayed on your device.
• Check if the device is listed using adb command:
  • On Windows command line/ MacOS terminal: Navigate to platform-tools folder in <Android SDK folder>\platform-tools.
  • Type in "adb devices" and observe devices listed there. Make sure that your corrected device is listed there with online status. 

Your .ipa application and/or WebDriverAgent is not signed correctly.

• Sign and rebuild the WebDriverAgent XCode project with your developer certificate.
• Uncheck 'Automatically Signing' option from WebDriverAgentRunner and select valid provisioning profile (profile displayed as Eligible from the list).

This necessitates manually changing the bundle id for the target by going into the "Build Settings" tab, and changing the "Product Bundle Identifier" from com.facebook.WebDriverAgentRunner to something that Xcode will accept.

• Fail to start the Appium server in 60 seconds.
• Original error: 'x.x.SplashActivity' never started.

Set your Appium Log Level to "Debug" which you can find this option in Windows > Katalon Studio Preferences > Katalon > Mobile to generate debug logs of Appium.

After this change is applied, retry your record/spy session and then open generated .appium file in the project folder. 
Somewhere in this file you are likely will see these lines: 

[debug] [ADB] Running '..\adb.exe' with args: [...] 
[debug] [ADB] Found package: 'com.abc.def.xyz' and fully qualified activity name : 'com.egh.jik' 
[debug] [ADB] Incorrect package and activity. Retrying.

The root cause is Katalon Studio can't start application due to incorrect package and activity by default, so you need to add additional settings to desired capabilities: 

 - Navigate to Mobile settings (Project > Settings > Execution > Default > Mobile > Android). 
 - Add the following key.
   Name: appWaitActivity. 
   Value: com.* (based on the prefix of 'Found package' log).

Katalon Studio cannot locate the provided Appium directory. Please double check your Appium directory to make sure it should be as shown below:

Windows: (Window → Katalon Studio Preferences → Mobile → Appium Directory).

C:\Users\<Username>\AppData\Roaming\npm\node_modules\appium

MacOS/Linux: (Katalon Studio → Preferences → Mobile → Appium Directory).

/usr/local/lib/node_modules/appium

First, upgrade to the latest version of Appium.

In Katalon Studio, go to Project Settings > Desired Capabilities > Mobile > Android and add this desired capabilities:

• Name: appWaitActivity
• Type: String
• Value: *

Click Apply to save, then run the test again.

When running tests with Katalon Runtime Engine, by default Katalon checks the Appium directory at:

• APPIUM_HOME environment variable (*).
• Windows: C:\Users\AppData\Roaming\npm\node_modules\appium.
• macOS and Linux: /usr/local/lib/node_modules/appium.

(*) To set Appium location by using APPIUM_HOME environment variable:

Windows:

export APPIUM_HOME=/usr/local/lib/node_modules/appium

Solution:

1. Install Webdriveragent.
2. Kill the running appium proccesses with the following command:

   killall -9 node

3. Start the AUT again.

Solution:

1. Create a SetText Custom keyword.
2. Run the test again in script mode.

This happens when:

• Missing one or more dependencies
• Outdated or incompatible dependencies
• Wrong dependencies installation order
• Broken WebDriverAgent build package

Solution:

• Reinstall dependencies.
• Rebuild WebDriverAgent. Learn how to rebuild WebDriverAgent at Install WebDriverAgent.