Desktop Flow Errors
Error handling specific to desktop-initiated QR flows.
Two Devices, Two Error Surfaces
Desktop flows involve errors that can appear on the desktop (QR modal) or on the user's phone (redirect pages). You need to handle both.
Desktop-Side Errors
These errors happen before the user scans the QR code or while the desktop is waiting for the phone to complete verification.
Session timeout
The user didn't scan the QR code in time, or the phone-side flow took too long. Start a new session.
Verification failed on phone
The carrier verification failed on the mobile side. The desktop SDK receives this through polling. Show an error and offer retry.
Network / connectivity
Desktop lost connection while waiting. Auto-retry polling. If persistent, show connectivity error.
Phone-Side Errors (Redirect Pages)
After the user scans the QR and completes (or fails) the carrier flow, the redirect chain determines what they see on their phone. See Mobile Auth States for the full redirect chain and Customization for branding options.
| Step | On Error | Your Control |
|---|---|---|
| Glide's redirect | Can show a Glide-hosted error page briefly | Configurable (contact Glide) |
| Your redirect endpoint | Receives error state as query params | Full control over error page |
| Mobile verification page (if used) | Shows error in your branded context | Full control (your code) |
TS.43 via Chrome (CTAP) Errors
When using TS.43 directly from the desktop browser, errors are handled the same as mobile TS.43 flows since the Digital Credentials API is invoked directly. See Mobile Errors for details.
CTAP may fail silently if the user's Android device is not nearby or Chrome's device connection is not established. Handle this as a timeout and offer the QR fallback.
Desktop State Preview
See all possible desktop-side states (success, failed, error) using our interactive preview: