quak login: do not call an account without SRP attributes missing
check / check (push) Successful in 5m14s

The Ente server answers /users/srp/attributes with 404 and the code
NOT_FOUND when the account exists but has no SRP attributes, and with
404 and {} when no account has the email. Both were reported as "no
account with this email on the server". Only a 404 whose JSON body has
no code is named that way now.

Model: opus-5-5
This commit is contained in:
sneak committed 2026-11-19 07:04:39 +00:00
1 parent 6e361ace8a
commit 41d3e6f72f
2 files changed
+29 -4

No files matched your search

+6 -4
View File
@@ -123,14 +123,16 @@ export const beginLogin = async (
{ email },
));
} catch (err) {
// The Ente server answers 404 with a JSON body when no account has the
// email. A server address that points somewhere else also answers 404,
// but not with JSON, so that error keeps its bare status.
// The Ente server answers 404 with `{}` when no account has the email.
// It answers 404 with the code NOT_FOUND when the account exists but
// has no SRP attributes. A server address that points somewhere else
// answers 404 without JSON. Those two errors stay as they are.
if (
err instanceof ApiError &&
err.status === 404 &&
typeof err.body === "object" &&
err.body !== null
err.body !== null &&
err.code === undefined
) {
throw withMessage(err, "no account with this email on the server");
}