Hello,
Thanks for reaching out to Hexnode Connect.
Based on the behavior you described, the kiosk policy itself is not actively blocking the print workflow. If printing immediately resumes after Mopria is opened manually, the print service is likely being suspended by the Android OS’s battery management and app lifecycle restrictions until it is brought back to the foreground.
For stable, unattended printing in an Android Multi-App Kiosk without forcing users to open the app manually, you need to implement two key configurations:
1. Allowlist the Print Packages as Background Apps
You do not need to make Mopria visible on the kiosk launcher for users to click. Instead, you must ensure that both the Mopria application and the native Android print spooler are explicitly permitted to run silently in the background of your kiosk.
- Edit your Multi-App Kiosk policy.
- Navigate to Kiosk Lockdown > Android Kiosk Lockdown > Background Apps.
- Add the Mopria app (e.g., org.mopria.printplugin) and the Android Print Spooler (com.android.printspooler). This explicitly tells the kiosk lockdown to allow these packages to process intents from your web app.
2. Disable Battery Optimization for Mopria
Because Android will aggressively put background applications to sleep to save power, you must exempt the print service from these optimizations.
- In your Hexnode portal, navigate to Policies > App Management > App Permissions.
- Add the Mopria app.
- Locate the Battery Optimization permission and set it to Disable.
- Save and associate the policy to your tablets.
By allowlisting the print spooler in the background and preventing the OS from putting Mopria to sleep, your web app will be able to call the print workflow reliably without any manual user intervention.
I hope this helps. If you find any more issues or need further assistance feel free to reach out.
Best regards,
George,
Hexnode UEM