New Features
Now Supporting Apple CarPlay Projection Testing

You can now validate in-car infotainment experiences with Apple CarPlay using Automation Testing. Combined with our existing Android Auto support, this enhancement provides complete coverage across iOS and Android-based in-car systems, helping teams deliver safer, more consistent connected-car experiences.
Support for Appium 3 Official Release
Appium 3.0 introduces key enhancements such as integrated Inspector hosting, masking of sensitive request data, and the deprecation of legacy server endpoints. Mobile Device Cloud i Testing now fully supports Appium 3.0, enabling teams to take advantage of the latest framework improvements. To add the latest Appium images to your environment, reach out to our Support Team. For migration details, refer to the Appium Migration Guide
Support for WebDriver BiDi Protocol in Appium Tests
Mobile Device Cloud now supports the WebDriver BiDi (Bidirectional) protocol, enabling real-time, two-way communication between automation frameworks and connected mobile devices.
The traditional WebDriver protocol operates in a strictly command–response sequence, limiting real-time interaction. The WebDriver BiDi protocol overcomes this limitation by allowing mobile devices to send live, event-driven updates directly to the controlling automation software.
For details on enabling BiDi in your tests, see the Appium Documentation
For more information on device-specific BiDi support, see the following resources:
Bug Fixes and Improvements
- Mobile Studio
- Fixed an issue that caused audio recordings to play in fast-forward.
- Android Support
- Mock Authentication can now be used in scenarios where authentication is required to open an application.
- Resolved an issue that caused applications to fail installation when instrumented with supported libraries.
- iOS Support
- iPhone 16 series specific - Resolved an issue where enabling a passcode on a device would fail when audio streaming was active.
- Resolved an issue where developer mode was not enabled automatically when connecting new devices with iOS 16 and later.
- Optimized iOS configuration cleanup by automatically trusting the certificate during installation.
- Fixed an issue where devices occasionally went offline during automation when using the SetPasscode command
- Resolved a server-related issue that caused certain Appium tests to fail.
- Appium Server
- Fixed an issue where Bluetooth adapters disconnected from a mobile device when an automation session started.
- Cloud
- Fixed an issue that caused devices to go offline when multiple files were open simultaneously.
- Fixed an issue that caused dates to be missing from support data file names.
- Fixed an issue that caused device host machines to go offline randomly during operations.
- Fixed an issue where reports were not accessible after the project was renamed.
- Fixed an issue where the Spring license was revoked after upgrade via Ansible.
- Resolved a pairing error that caused certain cloud components to remain offline after an upgrade.
- Redesigned all existing card components in the Cloud UI to meet Web Content Accessibility Guidelines(WCAG) 2.1 Level AA accessibility standards, improving usability for all users.
- Reporter
- Fixed an issue where video recordings were unavailable for certain reports.
- Fixed an issue where the reports were not accessible after the project was renamed.
Notes and Known Issues
- iOS 26 and later: Due to a third-party bug, the clear passcode operation is not working for supervised devices.
- Android 15 and later: An additional step is required when connecting a new device to your cloud. For more information please visit here
- As of 25.9, Device reservations, test requests, and session data older than two years will be deleted from the cloud database.
- As of 25.5, Samsung devices running Android 14+ with a PIN code must have the PIN specified in the device information. See our documentation for configuration details. See our documentation for configuration details.
- As of 25.4, mobile automation tests will return a
digitalai: prefix for Digital.ai Testing capabilities, to maintain W3C compliance. - Android web testing: Chrome driver is not automatically downloaded when using Appium 3 with a Docker configuration. To resolve the issue, follow this guide. Alternatively, run the same test with an Appium Server version < 3.
| 
| 
| 
| 
| 
| 
| 
|
|---|
| Official | 15.8.x — 26.1 | 7 — 16 | 141 | 143 | 140 | 18 | 122 |
| Beta | 26.2 beta | 16 developer 15 QPR2 Beta 1 | 142 | 144 | 141 | | 123 |