App Automate Error Codes
This topic lists BrowserStack App Automate error codes their resolutions.
BrowserStack App Automate enables instant Appium testing on a real Android and iOS devices. You can run hundreds of parallel tests concurrently and debug using text logs, console logs, network logs, screenshots, and video recordings.
While executing the App Automate Tests you may encounter some errors exhibited in the form of error codes, these errors can be resolved using the steps provided in the document mentioned below:
| Error code | Error details |
|---|---|
BROWSERSTACK_INVALID_APP_CAP |
The app_url or custom_id or shareable_id specified in the app capability in your test script is invalid. Learn more about this error and its resolution. |
Issues with local connection |
The local testing configurations have issues. Learn more about this error and its resolution. |
BROWSERSTACK_APP_DELETED |
Your test script’s app capability specifies a deleted app build that cannot be accessed. BrowserStack deletes uploaded apps after 30 days from upload. Re-upload the app using the REST API or BrowserStack CLI and try again. For steps to upload apps, see Upload apps from filesystem. |
BROWSERSTACK_DEPRECATED_DEVICE_ERROR |
BrowserStack no longer supports the device you are trying to run a test on. For more information, see the device deprecation policy. To resolve this error, update your test script to remove deprecated devices from your capabilities. For the current list of supported devices on BrowserStack, see Real Mobile & Tablet Devices for App Automate Testing. |
BROWSERSTACK_INVALID_APP_URL |
The app_url or custom_id or shareable_id specified in the app capability in your test script is invalid. Update the app capability with a valid value and try again. A valid app_url is one returned in response to an upload app API request. To reset the app capabilities, see Specify application under test. |
BROWSERSTACK_ALL_PARALLELS_IN_USE |
In addition to the queued tests, all parallels based on your purchase plan are currently in use. Learn more about this error and its resolution. |
BROWSERSTACK_FEATURE_NOT_AVAILABLE_IN_CURRENT_PLAN |
One or more of the features you are using are not part of your current plan. Check out our pricing page and subscribe to the plan with the required features. |
BROWSERSTACK_APP_UNZIP_FAILED |
There was a problem extracting or unzipping the uploaded app. Check if the uploaded app is valid and re-upload a valid version. For steps to upload apps, see Upload apps from filesystem. |
BROWSERSTACK_APP_PROFILE_EXPIRED |
Provisioning profile on enterprise signed app is expired. Learn more about this error and its resolution. |
BROWSERSTACK_INVALID_LANGUAGE |
Language capability has been passed incorrectly. Update the language capability with a valid format. To view acceptable formats, refer to Set localization options |
BROWSERSTACK_INVALID_APP_PACKAGE |
App package currently used to start the app does not exist. Correct the App package being used. Check the logs on a terminal or console for suggestions on the supported app package for the uploaded app. |
BROWSERSTACK_INVALID_OS_VERSION or BROWSERSTACK_INCOMPATIBLE_OS_VERSION
|
BrowserStack does not support the selected device’s OS version. For more information about supported devices and OS versions, refer to the device field in our capability builder. |
BROWSERSTACK_NO_DEVICE_SPECIFIED |
BrowserStack does not support the device, version, and operating system you entered for your tests. Learn more about this error and its resolution. |
BROWSERSTACK_INVALID_DEVICE |
The device capability field contains incorrect device name. Change the device name in the device capability. For more information about supported devices and OS versions, refer to the device field in our capability builder. |
Dashboard not loading |
The Dashboard not loading: Something went wrong. Please go back to the dashboard error is displayed when certain network calls get dropped because the required IP’s are not whitelisted. Learn more about this error and its resolution. |
BROWSERSTACK_IDLE_TIMEOUT |
The session timed out due to inactivity for the configured time limit. If no time limit is explicitly set, 90 minutes is the default. Extend the timeout value and retry the session. |
BROWSERSTACK_UI_STOPPED |
The session was manually stopped from the dashboard. Let the session run completely until the end of execution. |
BROWSERSTACK_COULD_NOT_LAUNCH_APP |
An error occurred or you were disconnected before the device could be found, preventing the app from being launched. Retry the session and allow it to run until the end of execution. |
BROWSERSTACK_SESSION_LIMIT_REACHED |
The session was timed out. The session default timeout of 2 hours or the reserved terminal timeout of 1 hour has been exceeded. Rerun the session. |
BROWSERSTACK_SO_TIMEOUT |
The code timed out since no response was received from an Appium command used within it. Rerun the session. |
BROWSERSTACK_QUEUE_SIZE_EXCEEDED |
All parallel tests based on your purchase plan are currently in use, and the number of sessions exceeds the queue limit. Wait for the currently queued tests to finish or upgrade your plan to add more sessions. |
BROWSERSTACK_QUEUE_TIME_LIMIT_EXCEEDED |
The queue time limit was exceeded due to multiple failed retries. To resolve this error, wait for the currently queued tests to finish or upgrade your plan to add more sessions. |
BROWSERSTACK_MULTIPLE_ADB_COMMANDS_ERROR |
You tried to run multiple Android Debug Bridge (adb) commands in parallel. BrowserStack Android devices do not currently support running multiple adb commands simultaneously. For more information, see adb equivalent functionalities in App Automate. |
We're sorry to hear that. Please share your feedback so we can do better
Contact our Support team for immediate help while we work on improving our docs.
We're continuously improving our docs. We'd love to know what you liked
We're sorry to hear that. Please share your feedback so we can do better
Contact our Support team for immediate help while we work on improving our docs.
We're continuously improving our docs. We'd love to know what you liked
Thank you for your valuable feedback!