PasskeySignals
Tells credential providers about server-side changes (WebAuthn Signal API). Requires PasskeyCapabilities.signals.
Every signal returns SignalOutcome.Applied when the provider took it, or SignalOutcome.Skipped when this OS or provider can't apply it. A skipped signal is normal: never show it to users. A PasskeyResult.Failure means something you can fix or should log (PasskeyError.Misconfigured, PasskeyError.InvalidOptions, PasskeyError.Unknown), so signals.syncAccount(...).onFailure { log(it) } is enough.
userHandle is the WebAuthn user handle: the base64url user.id your server put in the creation options, also returned as PasskeyAssertion.userHandle. Never pass your account id or an email address. Credential IDs are the base64url PasskeyRegistration.credentialId / PasskeyAssertion.credentialId.
Signals show no sheet. Like every Passkeys call they are main-safe, and cancelling the calling coroutine ends the call with CancellationException; they don't take part in the one-sheet-at-a-time rule.
Implementing this interface is supported (e.g. for fakes; prefer passki-test's FakePasskeys). New members will only ever be added with default implementations, so implementations stay source- and binary-compatible.
Functions
The complete list of valid credential IDs for userHandle; providers may remove others.
The user's current name / display name, so providers can update saved passkeys.
Tells the provider everything it should know about one account: its complete list of passkeys (acceptedCredentials) and its current label (currentUserDetails). Call it whenever you load the account's passkeys, for example when the passkey settings screen opens.
The server doesn't recognise credentialId; providers may hide or delete it.