When signing in with a passkey did not complete, the button simply became usable again and nothing was shown. Every possible cause looked identical from the member's side:

• no passkey had been created on the account yet
• the browser or device cannot use passkeys
• the site's address did not match the relying party ID the passkeys were registered against (usually www versus non-www)
• the prompt was dismissed

Only the last of those is something the member did on purpose. The other three are faults, and the application knew which one had happened every time without ever saying so — which meant an administrator had no way to tell a broken setup from a member changing their mind, and neither did we when it was reported.

Fixed in 1.0.12. Each cause now names itself beneath the button, the address mismatch points at the setting responsible, and a community where nobody has enrolled a passkey yet is detected before the prompt rather than after the failure. The settings screen also warns about the two states in which sign-in cannot succeed at all.

Sign-in itself is unchanged on communities where it was already working, and no passkey needs re-registering.