Help for owners
My customers cannot log in to my app
Short answer
When users cannot log in, the cause is usually one of four: the server or database behind the login is down, a token or session expired or became invalid, a setting or key changed at a login provider, or an app update broke the sign-in screen. Find out who is affected and when it began, then have the login traced.
Does this sound like your situation?
- Everyone gets an error when they try to log in.
- Only some customers are locked out, and new sign-ups work.
- Users are logged out again and again.
- Login broke right after an app update or a server change.
- The login button spins and nothing happens.
Why does this happen?
The server behind the login is not answering
A login asks your server to check a password or a code. If the server, database or domain is down, the app shows an error or just spins. Other features that need the internet usually fail too.
Technical detail: AxiosError Network Error with code ERR_NETWORK in a React app
The sign-in token expired or is rejected
Many apps keep people signed in with a token that has a lifetime and a secret behind it. If the secret changed or the token is out of date, the server refuses it and the user is thrown back to the login.
Technical detail: jsonwebtoken rejects a token: invalid signature, jwt expired or jwt malformed
A key or setting at a login provider changed
Apps that use Firebase, Cognito or a social login depend on keys and allowed addresses configured in those services. If a key was rotated, a project removed or a setting edited, sign-in fails without any change to the app.
Technical detail: Firebase Auth says the API key is not valid
An app update or a new build changed the sign-in
The version in the store can differ from the one that was tested, for example by being signed differently. Google states that users receive APKs signed with the app signing key, a different key from the upload key used to sign the bundle.
Confirmed by support.google.comTechnical detail: Google Sign-In in Flutter fails with PlatformException sign_in_failed, code 10
It affects one group only
Android vitals and similar tools can split problems by app version, Android version and device model. If only one slice is affected, the cause is in that slice, not in everything.
Confirmed by support.google.com
What can I do about it today?
- Try one account yourselfLog in with your own account and a brand-new account if you can. Note whether either works.
- Write down when it beganDate and time of the first complaint, and whether anything changed that day: an update, a server move, a domain renewal, a password reset.
- Ask two customers what they seeThe exact message, the phone, and whether they use email, phone number or a social login. Screenshots are best.
- Check the basics of your hosting and domainIs your website up? Have the domain and the hosting been paid and renewed? An expired one takes the login with it.
- Do not reset passwords for everyoneA mass reset floods your support and does not fix a broken server or key. Wait until the cause is known.
- Do not delete users or projects in any serviceRemoving an account, a project or a key in a login service can make things worse and cannot always be undone.
When should I bring someone in?
- No one can log in and you take orders or bookings through the app.
- The problem started after an update and your developer cannot say why.
- You do not know which services hold your login, or you have lost access to them.
How do I handle it?
- Find who is affectedI separate everyone from some users, one platform from both, and new sign-ups from returning logins.
- Follow a login from tap to answerI trace the request from the app to your server and the login provider, to see where it stops.
- Read the logs and the configurationServer errors, expired secrets and provider settings are checked without changing anything first.
- Fix it with a backup in placeA backup is taken before production changes, and the repair is tested on a copy where possible, with a rollback ready.
- Leave it easier to watchI add a simple check that alerts you when login fails, so you hear before customers do.
The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.
What do owners ask about this?
Is my data lost?
Usually not. A login failure is mostly a problem with the check, not with the stored accounts. I confirm the data is intact before changing anything.
Can I just ask users to reinstall?
It rarely helps and can lose local data. Wait until the cause is known.
Why does it work for me and not for customers?
Your account, device or app version may differ from theirs. That difference is what points to the cause.
How fast can it be fixed?
It depends on the cause. A written scope comes after a first look, but I cannot promise a time, particularly if a third-party service is involved.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.
For your developer: the technical fixes
JsonWebTokenError: jwt malformedjsonwebtoken rejects a token: invalid signature, jwt expired or jwt malformedFirebase: Error (auth/api-key-not-valid.-please-pass-a-valid-api-key.)Firebase Auth says the API key is not validAxiosError {message: 'Network Error', name: 'AxiosError', code: 'ERR_NETWORK'}AxiosError Network Error with code ERR_NETWORK in a React app{"message":"Unauthorized","statusCode":401}A NestJS route behind the JWT guard always answers 401