NFC tag scan plays sound but does not launch app on Esper-managed devices: investigation steps and Esper configuration to check

Android

When you tap an NFC tag on an Esper-managed device, it may play a sound acknowledging the scan but fail to launch the intended app or navigate to a specific page. This article helps you investigate and resolve this issue.

Before you begin

This issue typically occurs when:

NFC tags encode URLs intended to trigger deep-links into an app
The same tags work correctly on non-Esper-managed devices
The device audibly acknowledges the scan but takes no further action

Step 1: Verify NFC is enabled on your device

In the Esper Console, go to Devices & Groups → [Device Name] → Settings and confirm NFC is not disabled by a Blueprint or compliance policy.
On the device itself, navigate to Settings → Connected devices → Connection preferences → NFC and verify it is turned on.

Step 2: Check your active Blueprint for NFC or app launch restrictions

In the Esper Console, go to Blueprints → [Active Blueprint] → Device Settings.
Check whether the device is in Kiosk Mode or Single-App Mode. If it is, confirm that the app you want to launch is included in the allowed app list.
Look for any policies that restrict implicit intents or app launches, as these can prevent NFC tag dispatch from completing.

Step 3: Verify the target app declares NFC intent filters

Confirm that the app you want to launch includes the proper NFC intent filter in its AndroidManifest.xml file. The app must declare an <intent-filter> for android.nfc.action.NDEF_DISCOVERED with the appropriate MIME type or URI scheme matching the NFC tag's URL payload. If you do not have direct access to the app's manifest, contact the app developer to confirm this configuration.

Step 4: Enable Accessibility permission for Esper Management Service

On the device, go to Settings → Accessibility → Esper Management Service and enable it.
Alternatively, in the Esper Console, go to Devices & Groups → [Device Name] → Esper Settings → Accessibility and enable this permission remotely.

Step 5: Test with an unrestricted Blueprint

If your device is currently in Kiosk Mode or Single-App Mode, apply a standard (non-Kiosk) Blueprint to a test device to determine whether the restricted mode is blocking NFC dispatch. Tap the NFC tag on the test device. The target app should open and navigate to the intended deep-linked page without manual intervention.

Step 6: Collect diagnostic logs

If the issue persists after the above steps, collect the following diagnostic information:

Connect the affected device to your computer using a USB cable and enable ADB debugging on the device.
Run the following command to check for NFC-related activity:
```
adb shell dumpsys activity intents | grep -i nfc
```

Pull Esper Management Service logs:

adb shell logcat -d -s EsperDPC > dpc_logs.txt

Run a more detailed system log during an NFC tag scan to identify whether the OS is dispatching the intent:
```
adb logcat -v time NfcDispatcher:V NfcService:V ActivityManager:V *:S
```

Review these logs for entries indicating NFC intent interception or dispatch suppression. If you see no NFC-related activity, the OS may be blocking the dispatch before it reaches your app.

Verify the fix

After applying any Blueprint changes or permission updates, tap the NFC tag on your test device. The target app should launch and navigate to the deep-linked page automatically.

Still need help?

If NFC tags still do not launch your app after completing these steps, contact Esper Support. include:

A screen recording showing the issue on the managed device and on an unmanaged device of the same model for comparison
The diagnostic logs collected in Step 6
Your active Blueprint name and configuration
The device model and Android version