E-Mail Change Caused 2FA Authentication Lockout

[gourdcaptain]

Steps to Reproduce

1. Change e-mail addresses from one you have previously verified.
2. Typo it as "gourd@..." instead of "gourd753@..."
3. omehow in a frenzy of trying to get this to change to happen cause it to lock into the new address, unverified, but with 2FA still enabled.
4. Due to the lack of recovery codes, you cannot log in again to any new systems due to the 2FA going to a black hole address.
5. You cannot change e-mail addresses from your system which is still logged in, getting an error of "This feature is not available when signed in with OAuth. Please manage your account through your hosting provider's website."
6. Since you control the new domain (albeit it's hosted by Fastmail), set the address to point to a valid inbox. Validate this works by emailing yourself at gourd@...
7. Then hit "resend e-mail" and watch nothing happen. Maybe I got spam limited somehow.

welp

Attachments

Blacksky Error.png

What platform(s) does this occur on?

Web (Desktop)

Device Info

Debian 12 Linux desktop

What version of the app are you using?

Build version: 1.122.0; Bundle info: 7cbab2b (prod); Bundle date: 26050722; Platform: web; Platform version: 0.0.0; Device ID: 0f3c20aa-f7eb-4dd4-a825-121b92de3bff

Additional Information

Account gourd.myatproto.social

[gourdcaptain]

Lockout of my account resolved by customer support (thanks!) but it still feels like this shouldn't be able to happen.

[jalcine]

This might be a in-flight issue with https://tangled.org/pds.dad/pds-gatekeeper (because when the email is sent to be updated, pds-gatekeeper catches that). There's a more involved option: rsky-pds taking over all of this work (because it'll know which address to use for sure).

[jalcine]

Kinda weird because pds-gatekeeper does check if the email's verified.