Samsung Galaxy Watch provisioning via Esper Device Provisioner requires prior ADB/terminal pairing; Esper Settings app visibility depends on launcher selection

Android

This article helps you resolve three common provisioning issues with Samsung Galaxy Watch devices: getting your watch to appear in the Esper Device Provisioner, hiding the Esper Settings app, and deploying APKs during provisioning.

Before you begin

These steps apply to Samsung Galaxy Watch 8 and other Wear OS devices. You'll need access to the Esper Console and the host machine where you're running the Esper Device Provisioner.

How to make your watch appear in Esper Device Provisioner

Samsung Galaxy Watch devices require an initial ADB (Android Debug Bridge) connection before the provisioner can detect them. Follow these steps:

On your Samsung Galaxy Watch, go to Settings → About Watch → Software.
Tap the Build Number seven times to enable Developer Options.
Return to Settings and select Developer Options.
Turn on ADB Debugging.
Connect your watch to the host machine via USB cable, or enable wireless ADB pairing through your watch's developer settings.
On the host machine, open a terminal and run:
```
adb devices
```
Verify that your watch appears in the output as device (not unauthorized). If it shows unauthorized, accept the RSA key fingerprint prompt on your watch.
Open the Esper Device Provisioner. Your watch will now appear in the Select Devices stage and be ready to provision.

Note: This ADB pairing step is mandatory for watch-form-factor devices and cannot be skipped. This is expected behavior.

How to hide the Esper Settings app from your device

The Esper Settings (Device Management) app is only hidden when you use Esper Launcher as your device launcher. If you're using Android Launcher, the app will remain visible. To hide it:

In the Esper Console, navigate to Blueprints → [Your Blueprint] → Edit.
Scroll to the Branding / Launcher section.
Change the Device Launcher setting from Android Launcher to Esper Launcher.
Click Save and publish the updated Blueprint.
If your device is already provisioned, apply the updated Blueprint: go to Devices & Groups → [Your Device] → Blueprint → Apply.
Wait for the Blueprint to apply. The Esper Settings app should no longer be visible in your device's launcher.

How to deploy APKs without a separate upload step

When you use the Scan method in the Esper Device Provisioner to add devices, Blueprint-assigned APKs are not automatically deployed. To avoid a separate manual upload step, pre-enroll your device into the Esper account first:

Enroll your device into the Esper account so it appears as an account device (rather than scanning it during provisioning).
In the Esper Device Provisioner, select your device from the account device list instead of using the Scan method.
Continue with provisioning. Any APKs you've added to your Blueprint (via Apps in the Esper Console) will be deployed automatically during and after provisioning.
After provisioning completes, verify the APK is installed by going to Devices & Groups → [Your Device] → Apps.

Troubleshooting

Watch still not detected after ADB pairing: Confirm that adb devices shows your watch as device (not unauthorized). If it shows unauthorized, accept the RSA key fingerprint prompt displayed on your watch screen.

Esper Settings app still visible after switching to Esper Launcher: Confirm that you've published the Blueprint update and that the new Blueprint has been applied to your device. Check that the correct Blueprint is assigned by going to Devices & Groups → [Your Device] → Blueprint.

Still need help?

If these steps don't resolve your issue, contact Esper Support and include the following details:

Your device model (for example, Samsung Galaxy Watch 8)
The exact error message or symptom you're experiencing
The version of Esper Device Provisioner you're using
Steps you've already taken to troubleshoot