Introducing VMware AirWatch® Launcher 3.3 for Android

The VMware AirWatch® team is excited to announce that AirWatch Launcher 3.3 for Android is publicly available.

What’s New in this App Version

  • ALAU-169666: Added restrictions for power off, safe mode, and restart options when using Launcher.
  • ALAU-169952: Created restriction to disable editing or renaming folder name in Launcher.
  • ALAU-169901: Enhanced Hot-swap functionality to a limit the number of profiles cached during Check-in/Check-out.
  • ALAU-170047: Added Send Debug Logs command to upload application logs to the AirWatch Console.
  • ALAU-169986: Added ability to display lock screen information to show what user the device is checked out to.
  • ALAU-169963: Added ability to clear cache for selected applications on Check-in/Check-out.
  • ALAU-169899: Added Sync and Reload option when device is stuck in “Waiting for Profile” state due to connectivity issues. 

Bugs Fixed in this App Version

  • ALAU-169897: Fixed an issue where Launcher 3.2 is not configured on Android O devices due to SDK.
  • ALAU-169999: Fixed an issue where Launcher stuck in waiting for profile state intermittently on profile delete and re-push.
  • ALAU-170052: Fixed an issue where Launcher crashed after browsers are disabled.
  • ALAU-170043: Fixed an issue where Custom XML for preventing Safe Reboot does not work after a device reboot.
  • ALAU-169799: Fixed an issue where user is prompted to set passcode after the passcode already set.
  • ALAU-170016: Fixed an issue where Max profile cache deleted all cached profiles when value is set to 0.
  • ALAU-170014: Fixed an issue where Launcher failed to check out, when using Auto fill or Enter buttons.
  • ALAU-170012: Fixed an issue where Launcher hangs when large block of text is pasted into an editable field.
  • ALAU-170011: Fixed an issue where Launcher force stopped Google Play Store and Android settings.
  • ALAU-170041: Fixed an issue where Sync and Reload buttons were present but deactivated on the change orientation screen in Launcher.
  • ALAU-170040: Fixed an issue with incorrect timestamp for Boxer event notification in Launcher notification panel.
  • ALAU-170044: Fixed an issue where AirWatch Launcher conflicted with DeX launcher.
  • ALAU-170008: Fixed an issue where Lock screen message not displayed after restart.
  • ALAU-170009: Fixed an issue with 'Language and Input' access is blocked on Android O device.
  • ALAU-170010: Fixed an issue where Launcher crashed when the Launcher profile was removed from the AirWatch Agent and the back button is pressed.

Customer Impact

Take advantage of these updates by meeting the minimum requirements and downloading AirWatch Launcher 3.3 for Android. 

Minimum Requirements

  • Android 4.0 (Ice Cream Sandwich)+
  • AirWatch Console 9.1.2+
  • AirWatch Agent 7.3+ for Android (Highly recommended in order to utilize new features and other useful fixes)

How to Download AirWatch Launcher 3.3 for Android

Prior Version is Installed - The admin can decide when to push the app once it is available on the AirWatch Console as a seeded application.

  • For devices that support silent install of applications, the Launcher application seamlessly updates over the existing application version without disrupting device enterprise functionality. For devices that do not support silent install of applications, the users will be prompted to install the new version.
  • For Android Marshmallow and above, the user will be prompted to grant permission for the Launcher to have access to the Usage Data, if they have not already granted the permissions.
  • For Android Lollipop, the users will be prompted to grant permissions for Launcher to have access to Usage Data only if the admin has pushed a profile requiring the user to do so (more details present in previous technical bulletins).

Prior Version is Not Installed - Once the admin decides to push the AirWatch Launcher to the devices, the Launcher gets downloaded to the device as a seeded application.

  • For Samsung SAFE devices, the Launcher will be setup without any end user interaction and the native launcher will be replaced by AirWatch Launcher. For non-SAFE devices, the user will be directed through a two-step process to set the AirWatch Launcher as the default Launcher.
  • For Android Marshmallow and above, the user will be prompted to grant permission for the Launcher to have access to the Usage Data, if they have not already granted the permissions.
  • For Android Lollipop, the users will be prompted to grant permissions for Launcher to have access to Usage Data only if the admin has pushed a profile requiring the user to do so (more details present in previous technical bulletins).

Support Contact Information

To open a Support Request, please call your local AirWatch support line or submit a Support Request via myAirWatch.

 

Best Regards,

The AirWatch Team

Have more questions? Submit a request

0 Comments

Article is closed for comments.