能否远程更新处于Kiosk模式运行的Android应用？多款MDM尝试无果

Absolutely—remote updates for Kiosk-mode Android apps are totally feasible, but the approach depends on how your Kiosk is configured and which tools you’re using. It sounds like the MDMs you tried might not have deep enough integration with Android’s enterprise policies, so let’s walk through the most reliable solutions:

1. Use an MDM with Full Android Enterprise Integration #

If you’re sticking with MDM tools, prioritize ones that fully support Android Enterprise (Google’s official framework for managed devices). Tools like Microsoft Intune, Soti MobiControl, or IBM MaaS360 are built for this, and here’s why they work where others might fail:

• First, ensure your Kiosk app is set as a managed app in the Android Enterprise console. This gives the MDM permission to push updates directly through Google Play (or your private app store).
• Double-check your Kiosk policy: Make sure it doesn’t block Google Play Services, disable app auto-updates, or restrict network access for the app/Play Store. Some MDMs let you set granular rules, like only allowing updates during off-hours to avoid disrupting Kiosk usage.
• The key difference from tools like Flyve MDM or Cloud4Mobile? Many smaller MDMs only handle basic Kiosk locking but skip the enterprise-level app management hooks needed to trigger updates without user interaction.

2. Build a Custom Update Mechanism into Your Kiosk App #

If you can’t switch MDMs, you can add a custom update flow directly to your Kiosk app—since Kiosk apps are usually set as Device Owners or Profile Owners, they have elevated permissions to install updates silently:

• Step 1: Add required permissions
  You’ll need REQUEST_INSTALL_PACKAGES (for Android 8.0+) and, if you’re downloading APKs locally, MANAGE_EXTERNAL_STORAGE (Android 10+). As a Device Owner, you can also use the PackageInstaller API to bypass user prompts for installation.
• Step 2: Implement a version check
  Add a background service that periodically pings your private server to compare the app’s current version with the latest available. You can trigger this check via a remote signal (like a Firebase Cloud Message) instead of polling to save battery.
• Step 3: Whitelist the update service
  Make sure your Kiosk policy doesn’t kill the background update service—add it to the allowed apps/services list so it can run even when the Kiosk is locked down.

3. Use Managed Configuration Triggers (Android Enterprise) #

If you’re already using Android Enterprise but your current MDM doesn’t support direct app updates, you can leverage managed configurations:

• Define a custom configuration parameter (e.g., force_update) in your Kiosk app’s manifest.
• When you need to push an update, use your MDM to change this parameter’s value (e.g., from false to true).
• Your app listens for changes to managed configurations and triggers the update flow (either via Google Play or your custom mechanism) when it detects the signal.

Common Pitfalls to Avoid #

• Locked-down Play Store: If your Kiosk policy blocks Google Play entirely, you’ll need to use a private app store or custom APK hosting.
• Permission Restrictions: Even if your app is a Device Owner, some OEMs might restrict certain installation permissions—test on your target devices first.
• Android Version Differences: Android 11+ has stricter rules for background services, so make sure your update logic complies with foreground service requirements if needed.

内容的提问来源于stack exchange，提问作者gonzalomelov