Chrome missing from app list on some devices despite identical blueprint assignment

Android

Title: Chrome missing from app list on managed devices — add it to your Blueprint

When Chrome is absent from the app list on one or more of your Android devices despite those devices sharing the same Blueprint assignment, the Esper Console shows no entry for Chrome and you cannot manage or configure it from the console.

Why this happens

Chrome's visibility in the Esper Console is controlled by your Blueprint's app allowlist. Even though Chrome ships as a system app on most Android 13 devices, it must be explicitly added to the Blueprint before the Esper Console will surface it as a manageable app. If some devices show Chrome while others do not, those devices most likely had Chrome enabled at the device level before the Blueprint was applied, creating a configuration difference that is not reflected in the Blueprint itself.

Steps

1. Open the Esper Console and navigate to Blueprints in the left menu.
2. Select the blueprint assigned to your affected devices.
3. Go to the Apps section within the blueprint editor.
4. Click Add App and search for Chrome. If Chrome is a system app on your devices, select it from the system apps list. The package name is com.android.chrome.
5. Set the visibility state to Show and configure any permissions required for your deployment.
6. Click Save, then Publish the updated blueprint. Publishing pushes the change to all devices assigned to this blueprint.
7. Confirm the updated blueprint is applied to your affected devices by navigating to Devices & Groups → [Device Name] → Blueprint and verifying the assigned blueprint version matches the one you just published. If your devices are organized into groups, apply the blueprint at the group level instead.

Verify: Within 5 minutes of the device syncing, Chrome should appear in the app list under Devices & Groups → [Device Name] → Apps with the visibility state you configured. The Blueprint tab on the device should show a compliant sync status and a recent last-synced timestamp.

If this doesn't resolve it

Work through the following checks before contacting support:

• Device is offline: Blueprint updates do not apply until the device reconnects. Check connectivity status under Devices & Groups → [Device Name] and wait for the device to come online and sync.
• Chrome is not pre-installed on this device: Some OEM or AOSP builds do not include Chrome as a system app. Confirm Chrome is present on the device by running:

  adb shell pm list packages | grep chrome

  If no output is returned, Chrome is not installed. Push it as a managed app through Managed Google Play (on devices with Play Services) or sideload the APK directly.
• Chrome is installed but still not appearing: If the ADB command confirms Chrome is installed yet it still does not appear in the Esper Console after the blueprint has synced, there may be a deeper configuration conflict.

If none of the above resolves the issue, contact Esper Support with the following information:

• Device serial number or Device Group ID
• Blueprint ID and published version number
• Esper Agent version on the affected device (found under Devices & Groups → [Device Name] → Device Info)
• Output from

  adb shell pm list packages | grep chrome

• Screenshot of the Blueprint's Apps section showing the current configuration

Still need help?

If Chrome still isn't appearing on your devices after following these steps, submit a support ticket and include your blueprint configuration, the affected device serial numbers, and your app deployment timeline.