Fixing sign-in problems in your app

Overskill is the sign-in provider for your app. Most "redirect mismatch" or login-loop problems come from a rename-sync lag and clear up on their own — re-publishing forces it.

Users can't sign in to your app, or they're getting bounced straight back to the login screen, or someone reported a redirect_uri_mismatch error. Here's what's actually happening and how to clear it.

💬 Ask your AI to fix it Paste this into your app's chat:

My users are getting bounced back to login (or a redirect_uri_mismatch) after I renamed my app. Re-publish my app to reseat the sign-in connection, and tell me if any integration needs reconnecting. If you can't re-publish for me, tell me exactly where to click. If this isn't something you can do, say so honestly instead of guessing.

Re-publishing reseats the sign-in connection against your app's current name, which clears the most common cause. The AI can walk you through it or, where it can, do it for you.

How sign-in works in your app

Overskill is the sign-in provider for the apps you build. When one of your users signs in, they're briefly handed to Overskill to authenticate, then bounced back into your app already logged in. You don't wire up a login system yourself — it's built in.

Because of that, sign-in problems almost never mean something is broken in your app's code. They usually mean the connection between your app and Overskill's sign-in got briefly out of sync.

The most common cause: you just renamed your app

Right after you rename an app, the sign-in connection needs a moment to catch up to the new name. During that short window, users can hit a redirect_uri_mismatch or get bounced back to login in a loop.

This self-heals. Give it a few minutes and it resolves on its own. If you want to force it immediately:

• Re-publish your app. Publishing reseats the sign-in connection against the current name and clears the mismatch right away.

Fixing a stale connection

If sign-in still misbehaves after a re-publish — or a particular integration that involves signing in stopped working — reconnect it:

1. Open the editor's settings sidebar → Integrations.
2. Find the connection that's acting up.
3. Reconnect it.

That re-establishes a fresh connection and clears out anything stale.

What this is not

You do not need to add a redirect URI to a Google OAuth client, and there's no per-app Google client to configure. If you've seen that advice anywhere, ignore it — it doesn't apply to Overskill apps. Sign-in runs through Overskill, so the fix is on the Overskill side (re-publish, or reconnect from Integrations), not inside a Google developer console.

A worked example

You rename my-app to acme-portal. Minutes later a tester reports it keeps kicking me back to login. Nothing's broken — the sign-in connection is still catching up to the new name. You hit Publish once. The connection reseats against acme-portal, the tester refreshes, and sign-in works. Total fix time: under a minute.

Still stuck?

If sign-in is still failing after re-publishing and reconnecting, open a ticket and tell us the app name and the exact error your users see — we can look at the connection directly.

What to read next

• How your app's users sign up — the full sign-up and sign-in flow
• My users get a 401 when they log in — the other common login gotcha (they need to sign up first)
• Adding social login — Google and Apple sign-in