If you sign in successfully (or think you did) and the app or website just throws you back to the login screen, that’s usually a session problem: cookies, cached data, blocked storage, or a network/tool interfering.
Here are the fixes that work most often, in order.
1. Check if you’re actually being logged out (look for the “session” clues)
A login loop often looks like “Sign in → brief loading → back to sign in,” with no clear error.
- If you see messages like session expired, invalid token, or cookies required, it’s almost always a browser/app storage issue.
- If it works on one device but not another, it’s usually local data (cache/cookies), not your password.
Keep that in mind as you go through the next steps.
2. Turn off VPN, ad-blocking, and “privacy” features temporarily
VPNs, tracker blockers, private DNS, and some ad blockers can block the authentication handoff (the part that sets your session cookie).
- Disable VPN and retry login.
- If you use an ad blocker, pause it for that site/app (or try a clean browser profile).
- On iPhone/iPad, if you use iCloud Private Relay, turn it off briefly and test.
If login works with these off, re-enable one by one to find the culprit.
3. Clear the right data (cookies/cache for web, app storage for mobile)
This is the most reliable fix for “login loops,” because you’re removing stale session data.
- Web browser: clear cookies + site data for that specific site (better than clearing everything). Then close and reopen the browser.
- Android app: Settings → Apps → (the app) → Storage → Clear cache first. If it still loops, try Clear storage/data (this signs you out and resets the app).
- iPhone app: there’s no universal “clear cache” button. Try deleting the app and reinstalling it (make sure you know your login info first).
After clearing, sign in once and wait an extra 10–20 seconds on the redirect screen—some apps finish the session setup after the visible login.
4. Try a different sign-in route (password vs. SSO, in-app vs. browser)
Many apps use a browser window to complete login (Google/Apple/Microsoft SSO, or a web-based sign-in). If the “handoff” back to the app fails, you get a loop.
- If you normally use “Continue with Google/Apple,” try email + password once (or the other way around).
- If login happens in an in-app browser, try logging in on the main browser first (Chrome/Safari/Firefox), then return to the app.
- On mobile, ensure the default browser isn’t restricted (some “lite” or locked-down browsers break login redirects).
If one route works, stick with it until the app updates.
5. Fix date/time and network oddities (surprisingly common)
Incorrect time can invalidate secure tokens and cause silent failures.
- Set your device to automatic date & time.
- Switch networks: try cellular vs. Wi‑Fi, or another Wi‑Fi.
- If you’re on a work/school network, it may block authentication domains—testing on a different network quickly confirms this.
A quick reboot after changing these can help the network stack reset cleanly.
6. Update, then do the “clean restart” (the step people skip)
Session bugs are often fixed by app/browser updates, but only if the old process is fully closed.
- Update the app (or update your browser).
- Force close the app / fully quit the browser (not just minimize).
- Reopen and sign in once.
If you still get a loop after doing steps 2–6, try the same account on another device. If it fails everywhere, it’s likely a service-side issue and you’ll need the app’s support team (mention “login loop / session not sticking”).
Final thoughts
Most login loops come down to blocked or corrupted session data. Clearing site/app storage and disabling privacy tools briefly usually solves it.
If it only happens on one network or one device, that’s a strong hint where to focus.