Kobiton 4.4 release notes

Kobiton 4.4 supports the following:

Users can now retain a Private or Local device without having to launch a Manual session. Just open the Device Details of an available device in the Device List, and select a retain period from the drop-down list to retain the device.

NOTE:

Kobiton 4 utilizes Xium to run your Appium tests 2-3x faster than Appium. Similar to the download Appium logs feature in Legacy Kobiton, testers running Appium automated sessions can now download automation logs. Look for the Xium button in the Logs area of Session Overview. Note that the structure of the Appium logs from Xium is a little different from standard Appium logs.

We introduced several enhancements to the UI/UX below:

If a user stops utilizing a device in the virtualUSB app but forgets to close virtualUSB properly, the device is retained and not available to other users for 24 hours. To prevent this issue, we introduced a mechanism to automatically release the device if virtualUSB app is inactive for a certain amount of time. The virtualUSB is set as inactive under any of the conditions below:

After the device is released, the status of the device changes from Retained to Online and other users can now utilize the device.

NOTE:

Before this release, the Save Logs button in virtualUSB was only accessible after the user logged in. Now, this option is under Help in the menu bar for both macOS and Windows so users can download logs even if they cannot log in.

NOTE:

We introduced Touch Target Size validations for hybrid apps in Release 4.2 with limited support for Ionic Framework. We now leverage the Shadow DOM Inspector feature in Release 4.3 to bring better support for the Touch Target Size validation for Ionic Framework.

NOTE:

When performing some tasks such as enrolling devices to an MDM or testing Apple Pay, users are required to input the passcode during a manual session. For organizations with passcode mode 1 or 2 enabled, where a random passcode is generated for each device, these tasks can be difficult as users have to contact Support to retrieve the device passcode.

To make the process easier, we now display the device passcode in the session information area of a Manual session.

NOTE:

Prior to this release, users of organizations with passcode mode 3 enabled can choose to keep or remove the device passcode when they exit a session. To prevent cases where users forget to remove the device passcode and make the device unavailable for others, we removed this option and applied the following rules instead:

NOTE:

To increase the security of devices with passcode, devices in organizations with passcode mode 3 enabled are required to have 8 to 10 digits for PIN instead of 6 to 10 digits as before.

This new rule only applies for PIN that are set after the release. PINs with less than 8 digits set before this release will be kept until they are removed.

NOTE:

Administrators of customer-hosted Local devices and Kobiton-hosted Private devices need to restart the services on the deviceConnect machine to fix device issues and apply software updates. This action can now be done from the Kobiton Portal instead of logging into the deviceConnect machine.

To restart services, Admins navigate to Settings>Device Management and click Restart Services button next to a specific deviceConnect host Mac mini.

Restarting services will interrupt all running sessions on the affected devices so make sure there are no running sessions on the machine or inform the affected users before restarting.

NOTES:

In addition to the above, this release includes a number of minor bug fixes and enhancements to improve your day-to-day testing.