Introducing AirWatch Launcher 4.1 for Android

The VMware Workspace ONE team is excited to announce that AirWatch Launcher 4.1 for Android is publicly available.

 

What’s New in this App Version

  • ALAU-170177: Support for skip usage access in COSU (Corporate-owned, single use) CICO
  • ALAU-170065: AirWatch Launcher and Chrome "Add to Homescreen" support
  • ALAU-170111: Add SSID configuration to multi-user Staging login screen
  • ALAU-170143: Badging for notifications on Floating Home Button

Bugs Fixed in this App Version

  • ALAU-169727: [Motorola LEX L10ig]: AirWatch Launcher terminates before selecting it as default launcher in device
  • ALAU-169726: AirWatch Launcher 3.0 crashes on Android 4.4 devices
  • ALAU-169712: AirWatch Launcher crashes observed on LG G2 device
  • ALAU-170172: AirWatch Launcher does not exit gracefully in Samsung DeX
  • ALAU-169902: [Huawei Holly2]: User needs to select 'Always' multiple times when setting AirWatch Launcher as the default launcher
  • ALAU-169887: [Lenovo TB3-850M]: Application name is not displayed clearly in AirWatch Launcher
  • ALAU-169862: Profile lands on the device only after home press during CICO intermittently
  • ALAU-169709: CICO times out if EULA is expected to come up for the check-out user
  • ALAU-169780: AirWatch Launcher not handling package manager crash and crashes
  • ALAU-169997: Badge for number of notifications gets removed on device orientation change
  • ALAU-169970: [Lenovo TB3-730X]: Application icons are not visible in Template Mode in AirWatch Launcher
  • ALAU-169971: AirWatch Launcher crashes after tapping Launcher settings options.
  • ALAU-169979: After enterprise reset AirWatch Launcher is not set as default
  • ALAU-170197: Notifications bar disabled after device reboot
  • ALAU-170190: Device settings that are restricted can be accessed from AirWatch Launcher intermittently only on three models of Samsung Galaxy devices.
  • ALAU-170146: Floating home button is not shown on restarting an Android 8.0 device
  • ALAU-170050: Application icons are not removed from AirWatch Launcher after sending Whitelist profile
  • ALAU-170125: Logout fails intermittently with Agent SDK service error
  • ALAU-169943: [PENTA K706]:Application name is not displayed clearly in AirWatch Launcher
  • ALAU-170090: [i18n-level2] Date format in Device Details Widget is not correct in non-English locales

Customer Impact

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

Minimum Requirements

  • Android 4.0+
  • Workspace ONE UEM 9.4+
  • AirWatch Agent 8.1+ for Android

How to Download AirWatch Launcher 4.1 for Android

  • Prior Version is Installed: The admin can decide when to push the app once it is available on the UEM 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 6.0 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 5.0, 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.
  • 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 6.0 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 5.0, 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.

Support Contact Information

To receive support, either submit a ticket via the My Workspace ONE  portal or call your local support line.

 

Best Regards,

The VMware Workspace ONE Team

Other Languages: 日本語

Have more questions? Submit a request

0 Comments

Article is closed for comments.