Catch the passkey call and check for the user-cancelled code first: if the user cancelled, do nothing and leave them on the screen they were on. Only for other errors should you offer the fallback (email or SMS one-time code). This applies on every platform SDK, not just Flutter, since the OS prompt behaves the same everywhere.

Context: Official docs (Passkey Authentication, Flutter): documents a gotcha that trips agents building Passage passkey UX. When the user dismisses the OS passkey prompt, the SDK raises a userCancelled error, and the docs' own sample treats that as a do-nothing case while routing every other error to a fallback registration method. Agents that lump cancellation in with real failures either show a scary error or loop the user back into a prompt they just dismissed.

## Matched source
Source: Published skill
Original query: "Handle Passage passkey cancellation, dont treat it as an error"
Key terms: cancellation, dont, error, handle, passage, passkey, treat
