Reference Architecture – Known Limitations
Mobile Access Management works alongside your MDM to deliver enhanced functionality across platforms like iOS, macOS, and Android.
Each of these ecosystems has unique restrictions and design choices that can affect the availability or behavior of certain features. As a result, some capabilities may vary by platform. Imprivata is committed to providing the best possible experience while accommodating each platform's built-in design.
iOS
Symptom
Under certain conditions, devices running iOS 26 can kernel panic and spontaneously enter recovery mode during Check In. This issue is intermittent and is not reproducing consistently. A ticket is open with Apple and the investigation of the root cause is in progress.
Resolution
To mitigate the issue, ensure that:
-
Imprivata Locker for iOS has been upgraded to 4.2.1 on all devices.
-
The Check In Workflow contains the Perform MDM Command action to Clear Passcode.
-
The Check In Workflow contains the On Failure action to Retry this workflow.
For more information on Workflows, see Standard Workflows for iOS.
Symptom
In certain conditions, you may see a new pane appear in Setup Assistant after a device has been upgraded to iOS 26 from iOS 18 or earlier. The new pane welcomes the user to iOS 26 and describes new features such as Liquid Glass and other user interface updates.
Resolution
Apple has introduced a new SkipKey to bypass this pane. The resolution is pending your MDM partners' update to Automated Device Enrollment (ADE) SkipKeys.
Symptom
During Check In, Locker iOS may display a black screen with an error message "Push notifications are disabled for this app", even though push notifications are enabled.
This issue occurs rarely and can occur regardless of how push notifications for the Imprivata Locker app are enabled (manually or by configuration profile).
Mitigation
To clear this error, reboot the device and check it back in.
Symptom
A device with a passcode set, that is connected to a Launchpad in an unlocked state, may fail to check in if the user locks the screen by pressing the side button (the sleep/wake button) on the device during a check in workflow.
Mitigation
Instruct users to avoid pressing buttons on the device after it has been connected to a Smart Hub via the USB connection.
Additionally, Imprivata recommends 'On Failure' retries to automatically remediate devices that fail an initial workflow for this reason. See Standard Workflows for iOS.
Symptom
On iOS 26, if a user presses the side button (the sleep/wake button) while the device is locked by the Imprivata Locker app, they will not be able to return to the Locker app. This behavior can occur in two different scenarios:
-
Users attempting to manually check out (no badge tap) with username and password may get stuck on device locked screen. This can occur if a user takes a device from a dock then either presses the side button or waits for the display to go to sleep.
-
If Require a second factor to unlock the device is enabled in Check Out settings, this issue can also prevent a user from completing multi-factor authentication. In that scenario, if a user presses the side button before completing MFA, they will not be able to return to Locker.
Resolution
To resolve the issue, upgrade devices to iOS 26.1.
Symptom
Using the Set Wallpaper action to apply a Home Screen wallpaper to an iOS 26 device incorrectly applies it to both the Home and Lock Screens.
Using Set Wallpaper for the Lock Screen alone functions correctly, however applying a Home Screen always overrides the Lock Screen.
This issue is reproducible using both MAM and Apple Configurator for iOS devices running iOS 26 or higher.
Resolution
There is currently no mitigation for this issue. Feedback has been filed with Apple.
Symptom
Device wallpaper may appear incorrectly sized in several scenarios:
-
After an upgrade.
-
When Workflows apply a wallpaper to a newly provisioning device.
Resolution
To resolve this issue, depending on the device type, you will need to apply a new wallpaper size.
If your environment is using Custom Options to assist with provisioning, note that the Launchpad Custom Options guidance has been updated.
In some cases this can also prevent Locker from launching, with an error in the Activity log like 'APNS Lock process cancel: Device token is unavailable.'
macOS
Symptom
On macOS 26, the Launchpad app will crash repeatedly when a Smart Hub is connected to the host.
Resolution
To resolve the issue, upgrade to Launchpad 7.1, if you are using macOS 26.