Cloud November 13, 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.

New Individual Sessions report

The Individual Sessions report lists every session started within a selected date range, one row per session, with session timing, user, team, device details, session minutes, type, and state.

  • Available under Analytics Reports in the Portal to organization ADMINs only, in the Usage group.

  • The date range defaults to the last 7 days.

  • Filter by Date Range, Team, or User Email. User Email accepts multiple addresses and searches the full user list as you type.

  • The table displays up to 100,000 rows. For larger result sets, narrow the filters or export the report to CSV.

Private mode pauses recording in automation sessions

Turn on private mode in a Xium or basic Appium 2 automation session to pause recording while your script handles private data.

  • Turn on private mode with the kobiton:privateMode capability at session start, or turn it on and off during the session with the Update Settings Appium command.

  • While private mode is on, screenshots, Appium and Xium logs, device logs, WebDriver traffic, view trees, system metrics, and network capture are not recorded. Commands run during this time are hidden in Session Explorer, and the session video skips the private part.

  • Errors are still returned to the script, and crash logs are still collected.

  • Recording resumes when private mode is turned off. Sessions that never turn on private mode are recorded as before.

For details and limitations, see Use private mode in Appium scripts.

App uploads no longer stay in Parsing

Each app upload now finishes parsing or ends in a parsing failure. In the Kobiton API, the app version state moves from PARSING to OK or FAILURE_PARSING.

  • If the uploaded file can’t be read, the app version shows a parsing failure.

  • If parsing can’t start after the upload, the app version is marked as a parsing failure.

  • An app or app version that is waiting to be parsed can be deleted from the Portal.

  • The option to delete an app in Parsing now appears after 1 hour instead of 15 minutes.

Accurate install errors for iOS apps built with an App Store distribution profile

Installing an iOS app built with an App Store distribution profile no longer returns an incorrect AD-403 error asking you to re-upload a development build.

  • When the install fails, the error reported by the device is shown instead, such as a code signature verification failure.

  • When App signing using Kobiton Certificate (iOS) is turned off, these apps are no longer rejected before installation.

Improved screen updates in Android manual sessions

Addressed an issue where the live view could lag behind session actions when Lightning Mode is turned off during a manual session.

Standard W3C errors for Selenium Java clients in Xium sessions

Xium automation sessions started with Selenium 3 or Selenium 4 Java clients, including Appium Java client 10, now return standard W3C WebDriver errors. For example, a missing element raises NoSuchElementException instead of a general WebDriverException, and client logs no longer show incorrect JSON status mapping. Sessions that use only desiredCapabilities and basic Appium 2 sessions are unchanged.

Text entry into covered fields in iOS Xium sessions

In iOS Xium sessions, tapping, clearing, or typing into an element now succeeds when iOS can’t scroll the element into view. For example, the on-screen keyboard can cover a password or PIN field on an iPad in landscape orientation, in an app whose form uses its own scrolling instead of the standard iOS scrolling.

  • The session scrolls the element’s nearest scrollable container until the element can be reached, then completes the action.

  • If the element still can’t be reached after three scroll attempts, the session returns the kAXErrorCannotComplete error.

  • Elements that are already visible, or that iOS can scroll into view, are not affected.

More accurate messages when no devices are available

Addressed an issue where sessions requested by device tags could report that matching devices were in use when none matched the requested tags. Error messages now reflect only devices with the requested tags. This applies to Appium sessions using kobiton:deviceTags and Turbo Test sessions started by device tags.

More reliable WEBVIEW discovery in Android mixed sessions

On Android devices, each Appium session that runs during the same mixed session now lists the WEBVIEW context for a web page open in Chrome, including pages in a Chrome Custom Tab such as Auth0 sign-in pages. Previously, only the first Appium session listed the WEBVIEW context. Later Appium sessions in the same mixed session returned only NATIVE_APP, without an error.

Mixed sessions that include only one Appium session behave as before. iOS sessions are unaffected.

Reliable screen reads on iOS 15 devices

Screen reads now complete reliably on iOS 15 devices, including the XML hierarchy captured around each action in a manual session, Appium element searches and page source requests, and Network Payload Capture setup.

Kobiton CLI prevents commands from acting on the wrong session

Kobiton CLI commands that pass -s <SESSION_ID> with a session token for a different session now fail with an error that identifies the token to pass, instead of acting on the wrong session.

Previously, with more than one CLI session open, parts of a command that passed -s without a matching token could apply to the most recently created session instead of the one named.

  • Each open session needs its own session token, passed with -a <SESSION_TOKEN> or the KOBITON_SESSION_TOKEN environment variable.

  • Help for -a, -s, kobiton session create, and --hide now describes this requirement.

  • With a single session open, commands run without -a or -s work as before.

deviceConnect Console device list loads with provisioning profiles from more than one team

The device list in deviceConnect Console now loads, and other Console pages and API requests respond, when an iOS device is covered by provisioning profiles from more than one Apple Developer team.

  • When a newer provisioning profile from a different team covers the device, the agent apps are re-signed with that profile once, and the signed copy is reused after that.

  • Re-signing of your iOS apps can also use a newer provisioning profile from a different team than the one the app was last signed with. Profiles that lack a capability your app requires are still not used.

New Android devices appear right away while USB debugging is unauthorized

A new Android device connected to a deviceConnect host now appears in the device list right away, even before USB debugging is allowed on the device. Until you allow USB debugging, the device shows an error status, such as Device inaccessible: Unauthorized or Device inaccessible: Authorizing. Previously, the device could take up to 10 minutes to appear.

deviceConnect Console connection status

deviceConnect Console now shows in its header whether deviceConnect is connected to Kobiton and to gigacap. Connection problems can be identified at a glance without reading deviceConnect logs.

  • A status dot and label for Kobiton and gigacap appear next to the user menu for users with System Configuration access. Hover over a status to see its state and the reason for it.

  • Each service shows one of these states: Online, Offline, Error, or Not Configured.

  • Kobiton shows Error when the tenant API key in dc.ini is rejected, for example a wrong key or a key that belongs to another account. The hover text shows the reason, such as Invalid username or apikey/password.

  • Kobiton shows Not Configured when ApiBaseUrl or a linked tenant is not set. gigacap shows Not Configured when no GEM redirect is configured.

  • Status changes appear automatically, without reloading the page.

  • The status dots turn gray while the console is disconnected from deviceConnect, such as during a service restart, and show the current state again when the connection returns.

  • In windows narrower than 1200 pixels, only the status dots appear.

Component versions

  • Portal 2611.13

  • deviceConnect 2611.12

  • Kobiton CLI 2611.9