WebView Cookie/DOM Storage Blocked in Kiosk Mode: Use Google Play Web App with Chrome Managed Config to Suppress First-Run Prompt

Android

When you use a kiosk app to display a website on an Esper-managed device, the underlying WebView may block cookies and DOM storage, preventing the page from loading or maintaining login sessions. This article explains how to replace the third-party app with a Google Play Web App and configure Chrome to suppress the first-run prompt on unattended devices.

Before you begin

Ensure that:

• Your device is enrolled and locked down in Kiosk mode via an Esper Blueprint.
• You have access to the Esper Console with permissions to edit Blueprints.
• You know the target website URL you want to display.

Step 1: Create a Google Play Web App

Google Play Web Apps use Chrome as the rendering engine, which provides better support for cookies and session persistence than third-party WebView implementations.

1. Follow the Esper Help Center guide to create and deploy a Google Play Web App.
2. Specify the target URL when prompted.

Step 2: Add Google Chrome to your Blueprint

1. In the Esper Console, navigate to Blueprint → Apps → Add App.
2. Search for and select Google Chrome.
3. Set the App State to Show or Launchable but Hidden. Chrome must be available as the rendering engine for the Web App.

Step 3: Suppress Chrome's first-run prompt with managed configuration

On unattended remote devices, Chrome's first-run setup wizard can block the website from loading if no one is present to dismiss it. You can suppress this prompt by applying a managed configuration.

1. In the Esper Console, navigate to Blueprint → Apps → Google Chrome → Managed Config.
2. Add the following key-value pair:
   • Key: SuppressFirstRunBubble
   • Value: true
3. Confirm that the managed config is applied to the com.android.chrome package (not Chrome Beta or Chrome Dev).

If the first-run prompt persists, you can also try setting these additional policies:

• BrowserSignin set to 0 (disables browser sign-in)
• WelcomePageOnOSUpgradeEnabled set to false

Step 4: Set the Google Play Web App as the Kiosk app

1. In the Esper Console, navigate to Blueprint → Kiosk → Select App.
2. Choose the Google Play Web App you created in Step 1.

Step 5: Apply the Blueprint

1. Navigate to Devices & Groups.
2. Select the device or group where you want to apply the Blueprint.
3. Go to Blueprint → Apply.

Step 6: Verify the configuration

Once the Blueprint is applied, verify that:

• The website loads correctly on the device.
• Cookies and session data persist across page refreshes.
• No Chrome sign-in or welcome prompt appears on first launch or after a device reset.

Troubleshooting

Chrome first-run prompt still appears

The managed configuration key may not be taking effect. Confirm that:

• The correct Chrome package (com.android.chrome) is targeted in the Blueprint app list, not a Chrome variant like Chrome Beta or Chrome Dev.
• The managed config key-value pair is spelled correctly.

Cookies still not persisting with Chrome or the Web App

1. Navigate to Devices & Groups → [Device] → Device Details → Apps.
2. Confirm that Chrome is the active WebView provider. Some devices use AOSP WebView instead; if so, Chrome may not be rendering the Web App content.

Your third-party kiosk app must remain in use

If you cannot replace the third-party app, contact the app vendor directly to determine whether their WebView implementation supports managed configuration options to enable cookie storage and DOM storage.

Still need help?

If the Chrome managed configuration key is not suppressing the first-run prompt across your device models, or if the Web App still blocks storage after following these steps, contact Esper Support.