Troubleshooting Guide

Repair cross-device passkey login flow

Q: Can I do cross-device without Bluetooth?

Many current implementations require Bluetooth proximity checks even when a QR code starts the flow.

Q: Why does QR disappear too quickly?

Challenge windows are intentionally short for security. Generate a new code and start immediately.

Q: Is this less secure than same-device passkeys?

It is still phishing-resistant but has more operational failure points, so same-device is more reliable.

Cross-device login adds extra moving parts: camera permissions, Bluetooth availability, and synchronized session timing. Small interruptions break the flow.

Quick fixes

Enable Bluetooth on both devices before scanning QR.
Keep both devices unlocked and within close range.
Use the latest browser versions on both ends.
Retry from a clean tab and new QR challenge.

Understand the handshake path

QR code starts a secure session pairing. Bluetooth presence confirms physical proximity before approval.

If either channel is interrupted, the login request expires and silently fails.

Most reliable recovery pattern

Complete one same-device passkey login first. Then retry cross-device to isolate handshake issues from account issues.

If same-device works and cross-device fails repeatedly, treat it as transport issue and refresh Bluetooth/network permissions.

Avoid repeat failures

Use stable network, avoid battery saver modes, and keep camera permission permanently allowed for login browser.

For high-frequency use, set up passkeys directly on each primary device.

FAQ

Can I do cross-device without Bluetooth?

Why does QR disappear too quickly?

Is this less secure than same-device passkeys?

Also searched as

cross device passkey not working
passkey qr code not working
passkey bluetooth login failed
use phone passkey on computer not working