Digital.ai Testing 25.10 Release Notes

Support for WebDriver BiDi Protocol in Appium Tests

Digital.ai Testing now supports the WebDriver BiDi protocol, enabling real-time, two-way communication between browsers and automation frameworks.

Traditionally, the WebDriver protocol only allowed commands and responses in a strict sequence. With BiDi (bidirectional), browsers can now send live events directly to the controlling software—allowing for faster, more synchronized, and event-driven automation.

For details on how to enable BiDi in your tests, see Appium documentation

Bug Fixes and Improvements

• Android Support 

  • Resolved an issue that caused applications to fail installation when instrumented with supported libraries.

• iOS Support 

  • 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.

• Shared Devices

  • Fixed an issue where launching Chrome URLs during native app tests caused the browser to get stuck on the first-run screen.

• Cloud 

  • 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 the reports were not accessible after the project was renamed.

Notes and Known Issues

• iOS 26 and later: Due to a change in third-party behavior, the Clear Passcode operation for supervised devices now requires additional configuration to complete successfully. For more info please visit here.

• 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 now return a digitalai: prefix for Digital.ai Testing capabilities, to maintain W3C compliance.

Cloud Management and On-Premises Deployment

info

This section is only relevant for Cloud Administrators.

• For documentation around installation deployment and management processes, head to the Cloud Management Documentation, space.

• Installers for on-prem deployments can be found here.

• If you do not have credentials to access the relevant links, reach out to our Support Team.

Important Notes and Known Issues

• 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.

• For large Reporter databases with more than 1m records: We recommend updating the following PostgreSQL configurations:

  • random_page_cost = 2.0
  • default_statistics_target = 1000
  • shared_buffers = 25% of RAM on the machine

• The URL used to download the certificates for HAR recording changed in the 25.9 release.

  • The new URL is: MITMProxy Status
  • The rest of the process remains unchanged.

warning

Windows and CentOS are no longer supported for cloud components (learn more here). No Builds for these platforms are available.

• To improve the stability of mobile devices connectivity, we recommend enabling "PortAlwaysOn" on the USB hub UI, as described in System Requirements.

Official	15.8.X - 26.1 18.7.2	7 – 16	141	143	140	18	122
Beta	26.2 beta	16 developer QPR2 Beta 1	142	144	141	—	123

Limitations on Android 12 - 16 devices are mentioned here and iOS limitations can be found here. For browser testing limitations, read more [here]

Next Release

Due date:  December 10th, 2025 (or prior)

The due date and highlights of the next release are as anticipated by Digital.ai Testing on the date of release of the current version, and are forward-looking statements. Actual due dates and highlights may vary.