Web app fails to launch: enable Chrome browser in Blueprint app state configuration

Android

If your web app closes immediately after launching or your device's mobile data toggle is unavailable, the issue is likely that Google Chrome is not enabled in your Blueprint's app state configuration. Web apps in Esper require a browser to run. This article walks you through enabling Chrome so your web apps function properly.

Before you begin

Confirm that:

You have access to the Esper Console
You know which Blueprint is assigned to your affected devices
Your device has an internet connection (or will obtain one after the fix is applied)

How Esper web apps work

Esper web apps are launched through your device's default browser (typically Google Chrome). If Chrome is disabled or hidden in your Blueprint configuration, the browser cannot open, and your web app closes immediately on launch. This is not a bug—it's a configuration issue that you can fix in minutes.

Fix 1 (Recommended): Enable Chrome in your Blueprint

This approach updates Chrome for all devices using the Blueprint, ensuring the fix persists even after future Blueprint updates.

In the Esper Console, open Blueprints.
Select the Blueprint assigned to your affected devices.
Go to Apps & Configurations.
Under Preloaded Apps, find Google Chrome (com.android.chrome).
Change the app state to either Launchable but Hidden (recommended for kiosk deployments) or Show.
Click Publish.
Navigate to Devices & Groups, select your affected devices or device group, and apply the Blueprint to push the changes to your devices.

After the devices finish updating (usually within minutes), your web app should launch successfully.

Fix 2 (Single Device): Enable Chrome directly on one device

Use this method if you need to test the fix on a single device before updating your entire Blueprint.

In the Esper Console, open Devices & Groups.
Select the affected device.
Open the Apps tab.
Search for Google Chrome (com.android.chrome).
Change the app state to Launchable but Hidden or Show.
Save your changes.

Important: This change applies only to that single device. If you apply Blueprint again your Blueprint with Chrome still disabled in the Blueprint configuration, Chrome will be disabled again on this device. Use Fix 1 for a permanent, scalable solution.

Verify the fix

After your devices update:

Open your web app from the device launcher.
Confirm it loads in a browser and remains open (does not auto-close).

Troubleshooting

Web app still closes after enabling Chrome

Check the web app URL: In the Esper Console, go to Blueprints → Apps & Configurations → Web Apps and confirm the URL is correct and reachable on your device's network.
Check for a different default browser: Some devices use a custom OEM browser instead of Chrome. If that browser is your system default, enable that browser's app state in your Blueprint instead (or in addition to Chrome).

Mobile data toggle is unavailable

Confirm a physical SIM card is installed in your device and that your carrier has completed service activation.
If the SIM is active, check your Blueprint for any network or connectivity restrictions. In the Esper Console, open Blueprints → [Your Blueprint] → System Settings and review any policies that may block mobile data configuration.
If you find no Blueprint-level restriction and the issue persists, contact Esper Support.

Issues persist across all devices

If the problem continues after enabling Chrome and re-converging your Blueprint across all devices, gather the following information before contacting support:

Your Blueprint ID
The name of the affected device group
Your Esper Agent version (found in device settings)
Device bug reports (available at Devices & Groups → [Device Name] → Bug Report)

Still need help?

If you've followed these steps and your web app still doesn't launch, submit a support ticket. Include your Blueprint ID, affected device group name, and any error messages you see on your devices.