Hello @nevaeh ,
This usually happens when one or more packages required by Samsung Keyboard are blocked while the device is in kiosk mode.
Try the following:
- Reproduce the issue on the device.
- From the Hexnode UEM portal, run a Scan Device action.
- Go to Manage > Endpoints > [select the device] > Applications.
- Check the Blocked Packages section.
- If you see Samsung Keyboard, spell check, predictive text, or related keyboard packages listed as blocked, copy the package or bundle ID.
- Go to Apps > +Add Apps > With Bundle ID and add the package.
- Open the kiosk policy applied to the device.
- Navigate to Kiosk Lockdown > Android Kiosk Lockdown > Background Apps.
- Add the keyboard-related package from Local Apps and save the policy.
- Confirm that the updated policy is associated with the device, then test Samsung Keyboard settings again.
Adding the package as a background app allows it to run while the device remains in kiosk mode. This is different from adding it as a visible kiosk app; background apps can support system/app functionality without appearing as apps the user can freely open.
Regards,
Simon Scott
Hexnode UEM