Troubleshooting Errors on the Local Device

As per initial setup and configuration, familiarity with the command line is assumed. Additionally, some steps may require assistance from a colleague with an Apple Developer account.

If the troubleshooting steps below do not resolve the issue that you are facing, refer to this article and contact us with the relevant log files and test result URL (if available).

1. Setup

Q1-1. “No devices are currently connected.” appears in NoCode Mobile even after connecting the device

Run autify mobile link doctor in a new Terminal (If you are using Windows, use Command Prompt or PowerShell) and check whether the connected device name appears.

• If the device does not appear, stop autify mobile link start, unplug the device from the computer, then reconnect it and rerun the command.
• If the device appear
  • Confirm that the autify mobile link start command is running, then reload NoCode Mobile page
  • Confirm that you are using the same user account on NoCode Mobile application that created the access token set with autify mobile auth login

Q1-2. When using a local iOS device, a “Profile not found” message is displayed

Verify that the Apple Developer account you are using has Access to Certificates, Identifiers & Profiles privileges. This privilege is enabled by default for the Admin role, but must be manually enabled for App Manager or Developer roles.

Q1-3. I want to use the latest versions of Autify CLI and Autify Mobile link. How do I update them?

If a warning such as "Warning: @autifyhq/autify-cli update available from 0.61.0 to 0.62.0." appears in your command line, update the apps by running the commands below in your terminal app:

autify update
autify mobile link install

Q1-4.After running the autify mobile link doctor command, the message "API connectivity check failed: Failed to access the server" is displayed on the CLI.

If you run the autify mobile link doctor command and see the error "API connectivity check failed: Failed to access the server" on your command line interface (CLI), it may indicate that your environment is unable to connect to the Autify API.

To determine if you can access the Autify API directly (bypassing the Mobile Link mechanism), please follow the steps below to run a manual connectivity test.

Direct API Connectivity Test

1. Create a new Personal Access Token (API Authentication) from the Autify settings page.
2. Replace <ACCESS_TOKEN> in the code below with your generated token.
3. Replace <PROJECT_ID> in the code below with your workspace ID.
4. Copy and paste the modified command into your CLI and execute it.

curl -H "Content-Type: application/json" \
-H "Authorization: Bearer <ACCESS_TOKEN>" \
"https://mobile-app.autify.com/api/v1/projects/<PROJECT_ID>/results"

If you do not receive a successful response: Please contact your internal IT or network team and request permission to access the Autify API endpoint: https://mobile-app.autify.com/api/v1/projects/<PROJECT_ID>/results

If you can connect to the API via the curl command above but still encounter the "Failed to access the server" error, your network's SSL/TLS configuration might be the cause.

To test if the issue is related to SSL certificate verification, you can temporarily disable it and check the connectivity.

Note: The following commands are for troubleshooting and diagnostic purposes only. We do not recommend using them for regular operations due to security risks.

Try running the following commands:

NODE_TLS_REJECT_UNAUTHORIZED=0 autify mobile link doctor
NODE_TLS_REJECT_UNAUTHORIZED=0 autify mobile link start

2.Recording

Q2-1. When using a local iOS device, "The application is already running. Multiple launches are not allowed." is displayed when trying to run "autify mobile link start", but the Autify NoCode Mobile screen shows "No devices are currently connected"

If you see "Application is already running. Multiple instances cannot be started" when trying to run autify mobile link start, but the Autify NoCode Mobile screen shows "No devices are currently connected", it is possible that there is a dangling process that needs to be manually stopped.

To resolve the issue, try the following troubleshooting steps:

1. In Terminal, press "Ctrl + C" to stop the CLI.
2. In Terminal, run the following command to find any dangling processes.
   ps aux | grep 'mobile link start
3. The command above will return a list of processes similar to the following:

autify             69112   0.0  0.0 410200128   1248 s101  S+    4:56PM   0:00.00 grep mobile link start
autify             68641   0.0  0.1 411668048  66032 s070  S+    4:55PM   0:00.22 /opt/homebrew/Cellar/autify-cli/0.62.0/libexec/bin/node /opt/homebrew/Cellar/autify-cli/0.62.0/libexec/bin/run mobile link start nYmF1n
autify             68628   0.0  0.0 410210544   3312 s070  S+    4:55PM   0:00.01 bash /opt/homebrew/bin/autify mobile link start nYmF1n

The first result relates to the command you just ran, so this can be ignored. Make a note of the other two process IDs that are shown in the second column from the left (68641 and 68628 in this example).

4. Execute the following command twice to kill the processes, replacing <PID> each time with one of the process IDs that you noted in step 3.
   kill <PID>
5. After performing the steps above, run ps aux | grep 'mobile link start again to confirm that only a single process is returned this time (grep mobile link start)
6. Run autify mobile link start again.

Q2-2. When trying to start the recording with a local iOS device, a "Profile not found" message is shown and recording cannot proceed.

If you see the message "Profile not found. To install WebDriverAgent, you need to set the appropriate provisioning profile. Please set the profile." after starting a recording, check whether the Certificates, Identifiers & Profile setting is enabled on the App Store Connect screen for an account enrolled in the paid Apple Developer Program.

You should also check the "Apple Developer Account" section under What will you need.

Q2-3. When using an Android device, an error occurs before launching the Step 1 application, and I cannot start recording.

If your recording log (e.g., recording-1234XXX-appium.log) contains the error "info: java.lang.SecurityException: Permission denial: writing to settings requires:android.permission.WRITE_SECURE_SETTINGS", the issue may be due to permission settings on your Android device.

Try changing your device's settings as follows to resolve the problem and try the recording again:

1. Refer to this guide (external site) to enable Developer Options.
2. In the "Developer Options" or "Security" settings, both switch "Disable Permission Monitoring" to ON and switch "App Permission Monitor" to OFF.

Note: If you encounter the error "Test execution was interrupted due to an internal error or exceeding the maximum test execution time" when running a scenario recorded on a different device, the setting above may also resolve the issue.

3.Test execution

Q3-1. When using a local iOS device, during test execution the error message "Aborted due to an internal error or the test execution timeout." is shown at step 0.

There isn't a single cause for this error, but the following troubleshooting steps may resolve the issue:

1. Confirm that your XCode account is properly configured. If you don't have the necessary permissions, it will result in an error.
2. Ensure that the local device's screen is unlocked before running the test. If the screen is locked during test execution, an error will occur.

Q3-2. When using an Android device, during test execution the error message "Aborted due to an internal error or the test execution timeout." is shown at step 0.

If your test result log (e.g., recording-1234XXX-appium.log) contains the error "info: java.lang.SecurityException: Permission denial: writing to settings requires:android.permission.WRITE_SECURE_SETTINGS", the issue may be due to permission settings on your Android device.

Try changing your device's settings as follows to resolve the problem and try rerun it:

1. Refer to this guide (external site) to enable Developer Options.
2. In the "Developer Options" or "Security" settings, both switch "Disable Permission Monitoring" to ON and switch "App Permission Monitor" to OFF.

If the steps above do not resolve the issue, refer to this article and contact us with the relevant log files and test result URL (if available)