Support & Troubleshooting

Note: This extension requires both the browser extension AND the companion app installed on your computer.

Common Issues

"Native host not found" or "Disconnected"

This usually means the companion app is not installed or the browser cannot find it.

Ensure you have downloaded and installed the companion app for your OS (Windows, macOS, or Linux).
Restart your browser completely after installation.

Reader Not Detected

If the extension says "No reader found":

Check if your USB reader (e.g., ACR122U) is properly plugged in.
Ensure the LED on the reader is on.
On Windows, ensure the "Smart Card" service is running.

macOS Specific Issues

"Missing binaries" or "App is damaged"

If you see an error about missing binaries or the app being damaged/unidentified:

This is often due to macOS security settings (Gatekeeper).
Go to System Settings > Privacy & Security and look for a message about "nfc-reader-host" being blocked. Click "Open Anyway".
If the binary is missing, try reinstalling the companion app. The binary should be located at /Applications/nfc-reader-host.app/Contents/MacOS/nfc-reader-host.

Browser doesn't see the host

The installer places a manifest file in /Library/Google/Chrome/NativeMessagingHosts/. Ensure this file exists and points to the correct binary path.

Linux Specific Issues

Permission Denied

If the extension connects but cannot read cards, you might have a permission issue accessing the USB device.

Ensure your user is part of the plugdev or pcscd group.
You may need to install pcscd and libpcsclite1 packages.
Check if the pcscd service is running: systemctl status pcscd.

Advanced: Manual Configuration

If you are still having trouble, you can check the "Native Messaging Manifest" files to ensure they point to the correct executable.

Windows: Registry key or file at C:\Program Files\NFC Reader Host\info.nfcreader.host.json
macOS: /Library/Google/Chrome/NativeMessagingHosts/info.nfcreader.host.json
Linux: /etc/opt/chrome/native-messaging-hosts/info.nfcreader.host.json

The path field in these JSON files must point to the actual executable location.

Contact

If you need further assistance, please email us at: