We have released Android client 2.10.0, which now fully supports Android 14. We have widened the enrollment option portfolio for Fully managed with work profile devices, fixed several Android-related bugs, and modified our Free plan.
New features
We have added the following new features:
- We have released Android client 2.10.0, which now fully supports Android 14.
Note: Installing applications that target SDK23 (Android 6), or lower versions, is not supported on Android 14 devices.
- On Fully managed Android devices, administrators can block ultra-wideband communication by adding it to the configuration profile restrictions.
- For Fully managed with work profile (COPE) devices, we have added the Zero-touch and Knox Mobile Enrollment (KME) enrollment options.
- We support setting different wallpapers on Android device home and lock screens.
Updated features
We have modified our Free plan.
Fixes
We have fixed the following Android-related bugs:
- Enrolling Work profile management for Android devices was possible only if 'All the time' location access was selected.
- Android system applications that were installed on a device before the device was enrolled could not be managed and the managed configurations did not apply to them.
- If the undeploy operation was started for an app that was embedded in Android firmware, the undeployment did not finish and the status remained 'in progress'.
- The Android client's 'Disable kiosk mode' only worked with Samsung kiosk mode, now it works for generic kiosk mode as well.
- The deployment of an APK the application ID of which contained both upper and lower case letters got stuck in 'in progress' state.
- Previously, when using Zero Touch or KME enrollments, the Android client always enrolled devices in Fully managed mode, even if the Fully managed with work profile mode was selected.
- If font scaling was used on the client user interface, in some cases, the layout was incorrect.
- For COPE devices, deploying a passcode configuration profile for the lock screen with the default passcode failed when both 'Force unlock passcode' and 'Lock screen message' were enabled.
- Some conditions caused Android retirements fail.