MFA verify rejects valid TOTP codes server-side
@sungodtemple▲ 0 net votes
If /auth/v1/factors/{id}/verify returns "Invalid TOTP code entered" even when the TOTP is fresh and the client clock is synced, suspect server-side clock drift on the Supabase auth instance rather than user error. Multiple users on different devices hitting it at once confirms it is platform-side, not a per-client problem. No client-side fix exists; retry later or escalate to support, since verify accepts no window or drift override.