Known issues

These are cumulative release notes. If a release does not appear in this section, then there were no associated known issues.

  • 1591019: When a device is retired from Work Profile on Company Owned Device mode and subsequently registered in Work Profile mode, any app that was previously whitelisted during Work Profile on Company Owned Device mode registration remains pinned in the Play Store.

  • 1729772: When the configuration is undistributed, the eSIM profile is not deleted from the device. This behavior is observed only on Android 16 in Work Profile and Work Profile on Company Owned Device modes.

  • 1909820: On Samsung devices running Android 13, the accessibility settings flow may not function as expected when the device is in kiosk mode. This occurs if com.android.settings and com.samsung.accessibility are not included in the kiosk whitelist on the server.

  • 1908370: During account upgrade using an enrollment token, the Skip option may still appear on the Google authentication screen for some devices when account migration is configured.

  • 1920265: Samsung Pass pop-ups may appear on devices in Lockdown & Kiosk mode if the associated system apps are not disabled. To prevent this, administrators must add the following packages under the Disable system app section:

    • com.samsung.android.samsungpassautofill

    • com.samsung.android.samsungpass

    • com.samsung.android.authfw

  • 1920268: While configuring a Gmail account on Samsung EAT devices operating in Kiosk mode, Google Services may crash unexpectedly. As a result, users may be able to exit the Kiosk environment during the account configuration process.

  • 1937845: Anti-phishing status updates may not be displayed immediately on all devices. While some devices reflect the updated status right away, others may experience a delay before the status is refreshed. In certain cases, users may need to minimize and reopen the app to view the latest anti-phishing status.

  • 1966536: On Android 9 devices, the Skip option may not appear on the Google authentication screen during device enrollment when the Authenticate Using Google feature is enabled through the Google Admin Console. As a result, users may be required to complete Google authentication before proceeding with enrollment.

  • 1713003: On Samsung devices with dual SIM capability, fetching the Embedded Identity Document (EID) is not supported.

  • 1777426: During device provisioning, the AMAPI SDK may encounter a timeout while preparing the environment. If this step fails, the device does not complete the provisioning process.

    Workaround: You can retry the provisioning operation.

  • 1726207: After a fresh device enrollment, the initial EID request may fail with a timeout error. The device may need additional time to complete these updates before the EID can be retrieved successfully.

    Workaround: IT administrators can send the request EID server command again to retry the process once the device has completed its background initialization.