4.23 release notes #403
4.23 release notes #403
Conversation
erincbailey
left a comment
erincbailey
left a comment
There was a problem hiding this comment.
Apologies - when I read through it again - I came up with some additional changes. Can you please make these changes and publish. Or if you need my approval again - we can do that during our meeting. Thanks.
|
|
||
| == New OS support | ||
|
|
||
| NOTE: Before upgrading Mac mini hosts to a new OS version, ensure that the connected iOS/iPadOS devices are running a supported OS version and has a compatible version of Xcode installed. For details on which macOS and Xcode versions are required, see Apple’s https://developer.apple.com/support/xcode/[compatibility information,window=read-later]. |
There was a problem hiding this comment.
Realized the verbs don't match in first sentence - please replace first sentence with:
Before upgrading Mac mini hosts to a new OS version, ensure that all connected iOS and iPadOS devices are running supported OS versions and that a compatible version of Xcode is installed.
|
|
||
| All sessions running on devices connected to the same host count toward the parallel test limit. This includes both user-visible sessions and hidden system-managed sessions, such as sessions in cleanup, API-triggered sessions, and retained sessions. Retained sessions are counted to ensure continued access to retained devices. | ||
|
|
||
| When the limit is reached, no new sessions can start on the host until one or more active sessions end, and the session count drops below the limit. The limit applies only to new sessions. If the limit is lowered below the current number of active sessions, existing sessions continue running and are not terminated. |
There was a problem hiding this comment.
Is the last sentence talking about an admin changing the limit? If so, let's be more specific.
If an admin lowers the limit below the current number of active sessions, those existing sessions continue running and are not terminated.
|
|
||
| Remote passcode unlock using a Bluetooth keyboard is now available for iOS devices during testing sessions. | ||
|
|
||
| While this feature supports other iOS versions, it is primarily designed for device labs managing iOS 26 devices that require a passcode. iOS 26 introduced stricter security controls that prevent traditional remote unlock methods when devices are offline. Remote passcode unlock enables secure passcode entry, so these devices remain accessible for testing, including passcode-protected devices that cannot use Kobiton’s managed passcode functionality. |
There was a problem hiding this comment.
-
Please remove word "stricter"
I know I added it - but reading it now - it's not quite accurate. They really introduced a bug :) -
Remove phrase "when devices are offline"
|
|
||
| === Requirements | ||
|
|
||
| To use remote passcode unlock, you must have: |
There was a problem hiding this comment.
Please change remote passcode unlock to "Bluetooth passcode unlock" here and in the next bullet
|
|
||
| A user guide for iOS VoiceOver support will be available soon. | ||
|
|
||
| == Bluetooth passcode unlock on iOS |
There was a problem hiding this comment.
We need to remove this section - there are issues with the solution. So, we'll leave it out.
|
|
||
| == Automation improvements & fixes | ||
|
|
||
| * *Improved error handling:* Display correct error message when invalid kobiton store ID (format: `kobiton-store:v<app_id>`) is used in either API call or automation scripts. |
There was a problem hiding this comment.
call should be plural "calls"
| * *Improved error handling:* Display correct error message when invalid kobiton store ID (format: `kobiton-store:v<app_id>`) is used in either API call or automation scripts. | ||
| * *Enhanced device selection*: | ||
| ** Added capabilities to select devices with specific tags in automation: `kobiton:deviceTags` and `kobiton:deviceTagType` | ||
| ** Deprecated `kobiton:tagName`. This capability provided similar functionality but supported only a single tag. |
There was a problem hiding this comment.
Hmm - reading this again. If someone uses kobiton:tagName in existing scripts - will it break and they will have to figure out why? Or do we allow it - we just don't advertise ti. Where do we document this? Is it here: https://docs.kobiton.com/automation-testing/capabilities/available-capabilities
Do we have a ticket to update that
|
|
||
| == Kobiton CLI improvements & fixes | ||
|
|
||
| * *CLI download from Portal:* Users can now download the Kobiton CLI directly from the Portal. |
There was a problem hiding this comment.
Add another sentence: Kobiton CLI can be used with private and local devices.
| == General improvements & fixes | ||
|
|
||
| * *Upgrade behavior:* Preserved GigaCap user configuration during `dpkg` installs instead of overwriting existing settings. | ||
| * *Logging improvements:* Updated the Portal logging console to display logs in a single-line format (normal console) instead of object format. |
There was a problem hiding this comment.
Is above an internal enhancement for Kobiton troubleshooting? If so - please remove it.
|
|
||
| * *Upgrade behavior:* Preserved GigaCap user configuration during `dpkg` installs instead of overwriting existing settings. | ||
| * *Logging improvements:* Updated the Portal logging console to display logs in a single-line format (normal console) instead of object format. | ||
| * *Org Management:* Added new permission that allows non-account owners to modify subscriptions in self-serve plans. This permission is not included in the Admin role by default and must be explicitly assigned by the Org Owner or an Admin. |
There was a problem hiding this comment.
Please move this to its own section before the Scriptless enhancements and use the below:
New Subscription Management Permission
A new permission, subscription.modify_subscription, allows Admins to manage subscriptions on self-serve plans. Previously, this capability was limited to Org Owners. This permission is not included in the Admin role by default. To enable it, create a custom role, add the permission, and assign the role to an Admin.
Summary
Related PRs, issues, or features (optional)
Metadata
PR contributor checklist
My PR follows the Kobiton Docs contributor guidelines, meaning:
nav.adocfile.en-us) from my URLs.