ErrorsSupabase Auth
Invalid login credentials
Sign-in was refused
The email and password combination did not match an account. The message is deliberately vague — it does not say which half was wrong, so it cannot be used to discover which emails have accounts.
In an AI-built app, specifically
Often exactly what it says. But in a published app it also appears when the app is pointed at a different Supabase project than the one the account was created in — the account genuinely does not exist there. If it works locally and fails in production, that is the cause.
What it is not: Not a row-level security problem. This fails before any table is touched.
How to fix it
- 01Confirm the published app and the place you created the test account use the same Supabase project.
- 02Check whether the account needs email confirmation first — an unconfirmed account can refuse sign-in depending on your settings.
- 03Reset the password if you are unsure of it, rather than guessing at it repeatedly.
If the steps did not do it
An error is one symptom, and the cause is often somewhere else entirely. The broken-app check reads your published site and looks at everything at once — and if it cannot tell either, connecting your repository is what lets Refinar read the code and fix it.