Known issues

This section describes the following known issues that are found in the current release of Mobile@Work for Android. For known issues found in previous releases, see the "Known issues" sections in the release notes for those releases, available in Mobile@Work for Android Product Documentation.

There are known issues for this release.

• AC-20820: Post-migration of Mobile@Work in Work Profile on Company Owned Device mode, when the device user tries to send logs from Mobile@Work, it is exiting instead.

  Workaround: Reboot the device and then try to send logs. Device user will be prompted with the list of available apps on the device and Mobile@Work will not exit.

• AC-20780: For Android Enterprise devices in Managed Device with Work Profile mode, after migration, the device user is prompted to "Enable Phishing protection." Even though the device user has set the client as the default browser before migration, Mobile@Work gets stuck in a loop.

  Workaround: Reboot the device and launch the migrated client. The "Enable Phishing protection" will not display and the UI is loaded properly.

• AC-20349: Previously, device users were able to access the Mobile@Work Home screen and browse the internet on a Chrome browser without completing device enrollment in Android Enterprise Work Managed device (DO) mode. There is no workaround.
• AC-19878: Microsoft Intune Device Compliance Support - generate notification: If a device does not check-in with AAD, a notification is sent to Core. If Mobile@Work fails to get the deviceID on subsequent check-ins, an error message displays. There is no workaround.
•