Cloud October 16, 2026

Cloud release notes are typically published weekly and summarize changes since the previous publication. Kobiton uses date-based release versioning, with releases identified by the build date in YYMM.DD format. Version information for individual software components is available in the Component versions section.

Session Explorer support for Kobiton CLI sessions

Kobiton CLI sessions now support capturing and reviewing session activity in Session Explorer. Captured data provides a more detailed view of commands, device logs, and screenshots throughout a session.

Capture session data from the Kobiton CLI

Use the new --capture option with kobiton session create to specify which session data to capture, including screenshots, view trees, device logs, metrics, and video.

Session capture is optional. CLI sessions created without --capture continue to open on Session Overview, with Session Explorer unavailable.

Review CLI session activity in Session Explorer

Session Explorer now provides a more accurate view of captured CLI session activity:

  • Session timeline: The timeline shows session creation once, followed by a step for each kobiton webdriver call, without duplicate session creation steps.

  • Device logs: Each step displays the device logs recorded since the previous step, making it easier to associate log entries with the corresponding activity.

  • Screenshots: Steps without their own screenshot display the screenshot from the previous step instead of showing "Screenshot Not Available". This behavior also applies to session command APIs.

  • Appium Inspector: Screenshots and XML hierarchies follow the same display behavior, while remaining associated with the appropriate session steps.

For sessions without captured device logs, View Device Logs and Download all are unavailable rather than displaying an error.

Passcode entry support for iOS manual sessions

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

Enter device passcodes during a manual session

When an iOS passcode screen appears, Kobiton Portal displays an interactive keypad overlay. Enter the passcode using the overlay or select Auto-fill passcode to use the device’s configured passcode.

The Passcode helper menu on the session toolbar provides controls for showing or hiding the keypad and auto-filling the passcode.

Find devices that support passcode entry

The Devices page now includes a Passcode filter with Supported and Not Supported options.

Supported devices also display a passcode icon in card and list views, making them easier to identify before starting a session.

Passcode entry is supported when your organization has passcode (PIN) mode turned on and the device has a passcode configured.

For Apple Pay instructions, see Use Apple Pay on iOS devices.

Configure Appium AI settings across your organization

Administrators can now configure Appium AI settings for their organization in Kobiton Portal. New Appium sessions use the organization’s configured LLM provider and locator settings without requiring additional capabilities in test scripts.

Organization settings include:

  • Turn Appium AI on or off for the organization.

  • Configure the LLM endpoint, API key, models, and locator settings.

  • Apply saved settings to new sessions across device hosts.

  • Override organization settings for individual sessions using kobiton:* desired capabilities.

Changes to organization settings apply to new sessions. Running sessions retain their existing settings.

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

Configure UiAutomator idle wait in Android automation sessions

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.

Fold and unfold Android devices during manual sessions

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.

Fold or unfold a device during a manual session

Use the Fold device or Unfold device control on the session toolbar to change the device’s posture. The session stream and Inspector adjust to the active screen.

Review fold and unfold actions in Session Explorer

Session Explorer records each fold or unfold action as a timeline step, including a screenshot of the device in its corresponding posture.

Screenshots retain the screen dimensions of the active posture, and touch and swipe markers remain aligned with the captured screen.

This functionality supports book-style foldable devices, such as Galaxy Z Fold and Pixel Fold. Flip-style devices, such as Galaxy Z Flip, are not supported.

Improved results and session visibility in the Kobiton MCP server

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

  • Validation progress: AI assistants can distinguish between scans that are still processing and completed results, including accessibility, crash, response time, and network payload validations.

  • Search results: Device searches now report the total number of matching devices. Pagination limits also help manage results for test cases, test suites, test runs, and user input events.

  • UI inspection: The automate plugin 1.15.0 now uses a compact UI tree by default during interactive automation, with full page source available on request.

For details, see Kobiton AI plugin and tools reference.

Reset stuck device states with the Kobiton API

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.

List installed apps on devices with the Kobiton API

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.

Improved element inspection and interaction in Appium sessions

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

  • iOS 26 location permissions: Automation scripts can now locate and interact with buttons on location permission alerts, including Allow Once, Allow While Using App, and Don’t Allow.

  • iPad web sessions: Appium Inspector now displays the correct XML hierarchy for each step of an iPad automation session started without an app, such as a Safari session.

  • Android web views: Fixed an issue on Android 13 and later where screens containing web views did not display their complete XML hierarchy, preventing element searches and interactions.

  • Element attributes: The WebDriver Get Element Attribute command now returns null when an element does not have the requested attribute, instead of returning an error.

  • Set element text: Appium automation sessions now support the mobile: setText command on Android and iOS. Previously, using this command returned a "not implemented" error.

Improved reliability for iOS and iPadOS devices

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

  • Device connections: Fixed intermittent Developer Disk Image (DDI) mounting failures on newer iOS devices, including iPhone 18 models running iOS 26.4 and later. This also resolves failures when a DDI is already mounted.

  • Device cleanup: Device cleanup now correctly resets settings such as time zone, language, and HTTP proxy on devices with newer iOS and iPadOS Settings layouts.

  • Device health checks: When an XCTest runner fails to start, the device health check now reports the underlying runner error instead of an unrelated passcode error. The device also retains its passcode when the failure is unrelated to passcode configuration.

Restored crash reporting in Session Explorer

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.

Session Explorer: Improved handling of sessions without recorded steps

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.

Improved app installation error messages in manual sessions

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.

Improved access to running XCUITest session details

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.

Component versions

  • Portal 2610.15

  • deviceConnect 2610.15

  • gigacap 2610.14

  • Kobiton CLI 2610.6