Debug common SDK errors

Learn how to identify and fix frequent SDK integration and runtime errors on BrowserStack Automate with actionable troubleshooting steps.

This page describes common error codes you might encounter when using the BrowserStack SDK and provides troubleshooting steps to resolve them. Each error code includes specific actions you can take to fix the issue.

SDK-TRA-001

1. Integrate a supported test framework if you intend to use features such as Test Reporting & Analytics (TRA), Accessibility, App Accessibility, or Percy.
2. If a test framework is already in use, specify it explicitly under the framework key in your browserstack.yml file.
3. If the issue persists, contact BrowserStack support

SDK-TRA-002

1. Review the error message for this error code to confirm the list of currently supported test frameworks.
2. If your intended framework is supported as per documentation, verify that the framework key in your browserstack.yml file is correctly spelled and matches the supported value.
3. If your framework is unsupported or not listed in documentation, contact BrowserStack support for clarification or feature requests.

SDK-TRA-003

Check for the process signal code you received in the table below:

SDK-TRA-004

1. Ensure you have installed the cucumber-core dependency with your test project.
2. Another way to check if the dependency is installed is by running this command: mvn dependency:tree
3. If the dependency is installed and you continue to see this error code alongside missing tests on the BrowserStack dashboard, contact BrowserStack support.

SDK-TRA-005

1. Review the error message for this code to check the list of supported Cucumber versions.
2. If you’re using an unsupported version, upgrade or downgrade to a supported one.
3. If you’re already running a supported version or the migration is not feasible, contact BrowserStack support.

SDK-TRA-006

1. Check if your test framework recently updated, try reverting to an earlier version to confirm if a breaking change caused the issue.
2. Verify that your test library is correctly installed by running this command: mvn dependency:tree
3. Compare your project’s dependencies with BrowserStack’s public sample projects.
4. Re-verify that the correct framework value is defined in your browserstack.yml.
5. If there have been no recent dependency changes and the issue persists, contact BrowserStack support.