Wear OS watch app management: Esper support status and provisioning approach

Android

Title: Wear OS device management — support status and provisioning guide

When managing Wear OS smartwatches with Esper, some standard Android management features may behave differently, produce unexpected results, or not function at all compared to phones and tablets.

Why this happens

Wear OS runs a modified version of Android with a different hardware and software stack than standard Android devices. Esper supports Wear OS on a best-effort basis — core features such as provisioning, app deployment, and device commands are available, but behavior is not guaranteed across all manufacturers, OS versions, and hardware models. Features that rely on a standard Android launcher, such as kiosk lockdown and Remote Viewer, may not function correctly because Wear OS does not expose the same UI surfaces.

Before you begin

Review these constraints before provisioning a Wear OS device:

Wear OS behavior varies significantly by manufacturer. A Samsung Galaxy Watch running Wear OS may behave differently than a Google Pixel Watch running the same OS version.
Some Wear OS devices restrict Device Owner provisioning or policy enforcement at the OS level, independent of Esper's capabilities.
Test your specific use case — including app installation and device commands — against your exact target device model and OS version before committing to a production deployment.

How to provision a Wear OS device

Use the Esper Device Provisioner to provision Wear OS watches. This is the recommended provisioning path for non-standard Android form factors because it does not rely on QR code scanning or NFC, which Wear OS devices often do not support.

Open the Esper Console and navigate to Devices & Groups → Provisioning → Device Provisioner.
Follow the on-screen setup flow to generate a provisioner configuration for your Wear OS device.
Run the Esper Device Provisioner tool on your development machine and connect the watch via USB when prompted.
Wait for the provisioner to complete. The watch will reboot automatically when provisioning finishes.
Confirm the device appears under Devices & Groups in the Esper Console with an active status.

Verify: The Wear OS device should appear in Devices & Groups with a status of Active within 5 minutes of provisioning completing. If the device does not appear, check that the watch has a stable Wi-Fi or cellular connection.

How to test app deployment on a Wear OS device

After provisioning, validate that app management commands work as expected on your specific device before deploying to a fleet.

Navigate to Apps & Configuration in the Esper Console and upload or select a Wear OS-compatible APK.
Deploy the app to your provisioned Wear OS device. Wear OS requires APKs built specifically for the Wear OS platform — standard Android APKs will not install correctly.
Confirm the app appears and launches on the watch.
Test update and uninstall commands from Apps & Configuration to confirm they execute as expected on the device.
Document the device model, Wear OS version, and any behavior that differs from a standard Android device for your records.

Verify: Each command — install, update, and uninstall — should reflect a completed status in the Activity Feed for the device, and the change should be visible on the watch within a few minutes.

If this doesn't resolve it

If provisioning fails or app commands do not execute as expected, collect the following information before contacting support:

Device manufacturer, model name, and Wear OS version
Any error messages displayed on the watch screen or in the Esper Console
Esper Agent logs from the device
ADB logcat output captured by running the following command on your development machine while reproducing the issue:

adb logcat

Contact Esper Support with these details. Include the specific step at which the failure occurs and whether the issue is consistent or intermittent.

Still need help?

Still need help? When you submit a support ticket, please include your Wear OS device model, the specific app management issue you're experiencing, and your current provisioning method.