BrowserStack Maestro FAQs

BrowserStack prioritizes unblocking users quickly, regardless of the Maestro version they use. While the bundled version may be older, we provide compatibility support to ensure newer Maestro versions work seamlessly.

Due to our custom implementation for Maestro on iOS real devices, each upgrade requires additional validation to maintain a stable, reliable, and high-quality iOS real-device testing experience. If a newer version is required due to specific errors, please reach out to us with specific details and we will ensure you are unblocked as soon as possible.

Maestro supports React Native, Flutter, and Webview-based applications.

On Maestro iOS, the clearKeychain command isn’t supported. When a flow includes it, the command runs but has no effect, so the app’s keychain entries aren’t purged and any credentials stored in the secure keychain persist across app launches.

To reset keychain state on iOS, set the ios_keychain_support=true parameter at the app upload stage. BrowserStack then instruments your app to clear its keychain data at the end of each test session. Clearing the keychain mid-session, between flows within a single session, isn’t currently supported. For more information, refer to the iOS keychain cleanup and access groups support page.

Cause: Your .zip file was not structured correctly with a single parent folder.

Solution: Re-zip your files inside one main folder and upload the new suite.

Cause: The app_url or test_suite_url in your cURL command is incorrect or has expired.

Solution: Verify you have copied the correct and most recent URLs from your uploads. Re-upload if necessary.

Cause: You did not use the execute parameter, and there are no flow files at the root of your parent folder.

Solution: Either move your primary flow files to the root or use the execute parameter to specify their paths.