When the signed-in account's handle comes back as handle.invalid, auto-open
a dialog (snoozed per account for 24h) that explains the problem and offers
a path to fix it:
- Refresh button: asks the server to re-resolve identity via
com.atproto.identity.refreshIdentity, then re-syncs the session
- Server-resolution diagnostics: recovers the intended handle from the DID
document (describeRepo alsoKnownAs) and resolves it to distinguish
"resolves correctly now", "wrong DID", "not resolving", and
service-provided handle issues
- Static FAQ of likely causes (missing/multiple TXT records, wrong DID,
expired domain, propagation delay, well-known file)
- Handoff to the existing Change Handle dialog and a support link
The invalid handle pill on one's own profile header is now tappable to
reopen the dialog on demand, bypassing the snooze.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01LSXAgZis8iP5KmcUcGXCKw
Claude
780a1bac5c