The relay refuses to mint a device token for an account with an
unverified address, email_unverified 403, with a sentence telling the
person to enter the code. iOS shows that sentence and a sheet to enter
it in: SignInView branches on the code and VerifyEmailSheet spends
it through AuthService.verifyEmail.
Android maps the refusal to RelayException.EmailUnverified, which is
constructed in two places and caught in none, and RelayAccounts.verifyEmail has no call site anywhere in */src/main/*.kt. An Android user signs up, is refused, and has no
screen that takes the code.
Off by default and not set in production, so nothing is broken today.
It is a trap for the first self-hoster who turns it on, and the
configuration page is where they would look.
The relay refuses to mint a device token for an account with an
unverified address, `email_unverified` 403, with a sentence telling the
person to enter the code. iOS shows that sentence and a sheet to enter
it in: `SignInView` branches on the code and `VerifyEmailSheet` spends
it through `AuthService.verifyEmail`.
Android maps the refusal to `RelayException.EmailUnverified`, which is
constructed in two places and caught in none, and
`RelayAccounts.verifyEmail` has no call site anywhere in
`*/src/main/*.kt`. An Android user signs up, is refused, and has no
screen that takes the code.
Off by default and not set in production, so nothing is broken today.
It is a trap for the first self-hoster who turns it on, and the
configuration page is where they would look.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The relay refuses to mint a device token for an account with an
unverified address,
email_unverified403, with a sentence telling theperson to enter the code. iOS shows that sentence and a sheet to enter
it in:
SignInViewbranches on the code andVerifyEmailSheetspendsit through
AuthService.verifyEmail.Android maps the refusal to
RelayException.EmailUnverified, which isconstructed in two places and caught in none, and
RelayAccounts.verifyEmailhas no call site anywhere in*/src/main/*.kt. An Android user signs up, is refused, and has noscreen that takes the code.
Off by default and not set in production, so nothing is broken today.
It is a trap for the first self-hoster who turns it on, and the
configuration page is where they would look.
Co-Authored-By: Claude Opus 5 noreply@anthropic.com
assigned to @paulhitt
mentioned in commit
7d16105f35