Skip to main content

Troubleshooting

This guide provides solutions for common issues you might encounter after following the getting started instructions.

Connection issues

Cable problems

Try these solutions if your device isn't connecting properly:

  • Check cable connection: Ensure your cable is firmly plugged into both your phone and laptop.
  • Direct connection: If using a hub, try connecting your device directly to your computer. Some hubs require permission pop-ups that may have been missed.
  • Use compatible cables: Not all cables support data transfer. If using a non-official cable, try switching to the manufacturer's cable.

Network configuration

The Abra test suite requires internet access to communicate with our backend:

  • Check app permissions: On your mobile device, go to the app-specific settings for the Abra test suite and verify that both mobile data and Wi-Fi data permissions are enabled.

Power management

Low battery can affect device functionality:

  • Check battery status: Operating systems may limit functionality when in low power mode.
  • Recommended action: Charge your device and disable low power mode, then try again.

Software conflicts

Other applications may interfere with the connection:

  • Close conflicting apps: Programs like iTunes (for iOS) or Android file transfer utilities can interrupt the connection.
  • Restart after closing: After closing potentially conflicting apps, try reconnecting.

Setup troubleshooting

Our tools require developer-oriented configurations that are usually set up automatically. First-time users may encounter initial hurdles:

  • First-time setup: If using a device for testing for the first time, the operating system may need to complete background configurations.
  • Recommendation: If you encounter errors on first use, wait a few minutes, restart Abra Desktop, and try again.

Platform-specific solutions

iOS issues

Unable to run tests

Verify Xcode configuration:

  1. Open Xcode
  2. Navigate to Xcode > Settings > Locations (or use shortcut Cmd ⌘ + ,)
  3. Check if command line tools are properly selected
    • The dropdown should show command line tools for your current Xcode version
    • Verify the gray text below matches: Command Line Tools (Xcode XX.X)
Xcode settings opened on the location tab with a default valid setupXcode settings opened on the location tab with a default valid setup

If you see "No Xcode selected" instead, follow these steps:

  1. Open Terminal
  2. Run: sudo xcode-select -s /Applications/Xcode.app/Contents/Developer/
  3. Enter your password when prompted
  4. Verify the fix by running: xcrun --find simctl (should output a valid path)
Developer Mode

When this is the first time you use Abra Desktop and haven't used your phone in combination with Xcode before it might show a validation error when scanning your app for the first time. See the image below for an example of the error you might encouter.

Luckily we can resolve this issue with a few simple steps:

  1. Disconnect your phone
  2. Open up Xcode
  3. Reconnect your device
  4. Xcode should automatically show a prompt to put your phone in developer mode.
  5. Restart Abra Desktop and try again.

Are you still facing issues? Check our documentation about resigning to ensure you followed all required stepts to make your device available for use.

Android issues

Failed to load Android device(s)

This typically occurs when the connected Android device isn't authorized for debugging:

  1. Check for authorization pop-up: When connecting for the first time, look for a permission dialog on your phone
  2. Grant permission: Tap "Allow" (we recommend selecting "Always allow" for convenience)

If no pop-up appears:

  1. Go to Settings on your Android device
  2. Navigate to "Developer options"
  3. Toggle "Revoke USB debugging authorizations" on and off
  4. Reconnect your device if necessary

ADB command not found

If you encounter this error:

  1. Open Terminal
  2. Run: echo "$SHELL" to verify it outputs /bin/zsh
  3. Run: nano ~/.zprofile
  4. Add this line: export PATH=$PATH:<ADB_PATH_COPIED_FROM_ABOVE>
  5. Save with Ctrl + X, then press Y and Enter
  6. Run: ~/.zprofile
  7. Verify by running: adb --version (should show version information)

App not installed on device

Samsung's Secure Folder can conflict with Abra Desktop:

Resigning

Invalid UDID

Ensure that the UDID is correctly copied. Double-check the length and format.

Device Limit Exceeded

Apple limits the number of devices you can register per membership year. If you reach this limit, you may need to remove old devices to add new ones.

Extended processing time

In some cases Apple might take an extended period of time (up to 72 hours) to process the device registration. For more information, follow Apple’s Reference article.

Permission issues

You might receive a pop-up: Abra Desktop would like to access data from other apps. This pop-up is when one of the command-line tools used by Abra Desktop is trying to access files on your system.

Please press 'Yes' to grant permission.

To persistenly enable permission, follow these steps:

  1. Open System Settings on your Mac.
  2. Select Privacy & Security in the sidebar.
  3. Select Full Disk Access.
  4. Press the + button in the bottom-left corner of the right pane.
  5. Select the Applications folder.
  6. Select the Abra Desktop application.
  7. Press Open to grant permission.