Cloud October 16, 2026

Manual sessions on supported foldable Android devices now include controls for folding and unfolding the device. Session Explorer also records these actions, making it easier to review how an app behaves across different screen configurations.

You can now enter device passcodes during iOS manual sessions, including passcode prompts for Apple Pay, Wallet, and the hidden apps folder.

Users with the ADMIN role or the org_setting.modify permission can now configure Appium AI for the organization in Kobiton Portal, under Settings > AI Settings. New Appium sessions use the organization’s LLM provider and locator settings without extra capabilities in test scripts.

With organization settings, you can:

Changes apply to new sessions. Running sessions keep their existing settings. Organizations without saved settings continue to use the host defaults.

Appium AI is in Beta and is available on Private and Local devices only.

For details, see Configure Appium AI settings for your organization.

Android Appium sessions now support the waitForIdleTimeout setting, which controls how long UiAutomator waits for an app to become idle before searching for elements.

Set appium:waitForIdleTimeout when starting a session, or change the setting during a session using the Appium Settings API.

Setting the timeout to 0 skips the idle wait, helping prevent element searches from failing in apps that continuously update their interface.

The default remains 10 seconds when no value is specified.

For details, see waitForIdleTimeout.

The Kobiton MCP server now provides more information about validation progress and search results, along with improvements to interactive automation.

For details, see Kobiton AI plugin and tools reference.

Organization administrators can now use the POST /v2/execute-admin-tasks API to reset devices that remain in an incorrect state, such as a device that appears in use after its session has ended.

The new RESET_DEVICE_STATE task resets the recorded state of one or more devices and returns the result for each device.

The reset does not end active sessions or cancel reservations. Devices become available for new sessions when their host machine next reports their state.

The new GET /v2/devices/{deviceId}/installed-apps and GET /v2/devices/udid/{udid}/installed-apps APIs return applications installed on a private device, including apps installed manually or through mobile device management (MDM).

Results include each application’s bundle ID, name, version, and build version. An optional parameter also returns the Kobiton app repository version ID when a matching version exists.

Several fixes improve how Appium sessions identify and interact with elements:

Several fixes improve device connections, cleanup, and health checks on iOS and iPadOS devices.

Session Explorer now displays app crashes and their crash logs for sessions on Android and iOS devices, including manual, Appium, and API sessions. Previously, crashes that occurred during these sessions were not captured, leaving no crash logs available for review.

Sessions without recorded steps now open on Session Overview instead of an empty Session Explorer. The Explorer tab displays "Explorer is not available for this session."

This also fixes an issue where XCUITest sessions displayed steps labeled null with no screenshots.

When an app installation fails during a manual session, Kobiton Portal now displays the error reported by the device instead of replacing it with a potentially misleading explanation.

For example, iOS signature verification failures now display ApplicationVerificationFailed instead of an AS-500 error about Kobiton certificate signing. Installation errors that include a Kobiton error code continue to display that code.

The GET /v1/sessions/{id} and GET /v2/sessions/{id} APIs now return session details while XCUITest native framework sessions are running. Previously, these requests returned an HTTP 500 error before the session’s test report and video became available.