Locked out, all at once

App Login Not Working: Sort Who Is Locked Out, Check the Keys That Expire, and Fix It Without Locking Out More

An app with a broken login is a locked shop with the lights on. Customers can see the door, tap the button, and get nowhere. The support inbox fills with screenshots of the same spinner. The cause is usually small and specific, and the first hour is for finding it before anyone resets everything.

November 20, 2026 · 10 min read

acmegymapp.com · sign-in funnel, one afternoon
Sign in with Apple, step by step
Users get through Apple, then the server says no
Sample
Tapped Sign in with Apple1,000
Approved on the Apple sheet940(94%)
Token sent to the server930(99%)
Server validated the token40(4%)
Reached the home screen40(100%)

client secret past Apple's six-month limit

Illustrative: sample sign-in funnel for a fictional gym's member app

The short answer

When users cannot log in to your app, first find out who is affected: everyone, one platform, one sign-in method, or only new accounts. Then check the login provider's status page, any secrets or keys that expire, and the last change to the app or server. Many login failures are fixed on the server with no app update. If a new app version is needed, test the full sign-in path before release.

On this page
  1. Who exactly is locked out decides where to look
  2. The first hour behind a locked door
  3. Secrets with an expiration date nobody wrote down
  4. Apple's login rule, read word for word
  5. Repairs that lock out more people than the bug
  6. Getting the fix to users: server first, store second
  7. Your call, or ours

Who exactly is locked out decides where to look

"Login is broken" is the report. It is rarely the whole truth. A login failure that hits everyone points somewhere different from one that hits only Android users or only people who sign in with a social account. Spend ten minutes sorting before anybody touches code, and the list of suspects drops from twenty to two.

Patterns of login failure and the place each one usually points
Who cannot log inLook here firstWhy
Everyone, on every platformYour auth server or login provider, its status page, your last server deployThe shared piece in the middle has failed
Only iPhone users, or only Android usersThat platform's app version, its sign-in library, platform keys and settingsSomething specific to one build or one store
Only one sign-in method, such as a social loginThat provider's status and your keys, secrets and redirect settings for itOne connection broke; the others still work
Only new sign-upsEmail delivery, verification links, account creation codeThe front door works; the welcome mat does not
Only some long-time usersTokens, session expiry, accounts migrated or changed recentlyOld credentials meeting new rules

Ask two or three affected users exactly what they see and on which phone. One precise screenshot of an error message is worth more than fifty reviews saying "can't log in." If the app closes outright instead of showing an error, the problem overlaps with our pages on Android crashes and iOS crashes.

The first hour behind a locked door

The steps below cost nothing and change nothing, which is the point. Every one of them gathers facts. The changes come after, and they will be smaller because of it.

  1. 1

    Check the login provider's status page

    If you sign users in through a third-party identity service, its status page is the first stop. A provider outage means you communicate and wait, not rewrite.

  2. 2

    Read the server's response to a failed login

    Your logs or error tracker will show the status code. Under the HTTP standard, RFC 9110, a 401 means the request "lacks valid authentication credentials," and a 403 means the server "understood the request but refuses to fulfill it." They lead to different fixes.

  3. 3

    List every secret and its end date

    Signing keys, client secrets, API keys, certificates. Note when each was created and who holds it. The next section covers one that runs out every six months.

  4. 4

    Line up the last changes

    App releases, server deploys, a domain change, a new redirect, a password policy update, a migrated user table. Login breaks follow changes the way thunder follows lightning.

  5. 5

    Try it yourself on a clean phone

    Use a test account on a phone that has never had the app. Logged-in sessions on your own device can hide the failure for days.

  6. 6

    Post one honest note

    In the app if you can, on your site and in reply to reviews: logins are failing for some users, we are working on it, accounts and data are safe if you know they are.

If the logs show 429 responses or a key that stopped being accepted, the login is failing as an integration, and our API integration repair page covers that family of failures.

Secrets with an expiration date nobody wrote down

Some login failures are scheduled months in advance and nobody notices the appointment. Sign in with Apple is the clearest example. Apple's token validation documentation, read in November 2026, says authorization code and refresh token validation requests require a client secret: "A secret JSON Web Token, generated by the developer, that uses the Sign in with Apple private key associated with your developer account."

Apple's page on creating that client secret adds the date that bites: "It's an error to request an expiration time more than 15777000 seconds (six months) in the future," as of November 2026. A server that generated its secret once, at launch, and never again can stop validating Apple sign-ins on a quiet afternoon half a year later. The fix is to generate a fresh secret and automate the renewal, not to rebuild the app.

Layered colored-paper scene of a phone with a blank screen, a paper padlock and a key beside it, a small bandage across the corner, soft shadows
A login emergency often comes down to one expired or mismatched credential, not a broken app.

Other keys do not expire on a published schedule but get rotated, revoked or deleted. Google Cloud's API key guidance says to "Periodically create new API keys, update your applications to use the new API keys, and delete the old keys," in that order. Deleting first is how a security tidy-up becomes a lockout. Push notifications have their own keys and certificates; if those stopped instead of logins, see our push notifications page.

Apple's login rule, read word for word

A login repair often tempts a team to bolt on a social sign-in as a quick escape route. On iOS that choice carries a rule. Apple's App Review Guidelines, last updated October 16, 2026, say in guideline 4.8 that apps using "a third-party or social login service (such as Facebook Login, Google Sign-In, Log in with X, Sign In with LinkedIn, Login with Amazon, or WeChat Login) to set up or authenticate the user's primary account with the app must also offer as an equivalent option another login service" that meets three conditions.

Limits data to name and email

The equivalent option collects no more than the user's name and email address.

Lets users keep email private

Users can choose to keep their email address hidden from you.

No ad tracking without consent

It does not collect interactions with your app for advertising without consent.

Some apps are exempt

Exceptions include apps that use only the company's own account system, education, enterprise or business apps that require an existing account, government or industry-backed ID, and clients for a specific third-party service.

Note what the guideline does and does not say. It asks for an equivalent option with those properties; as read, it does not name a specific product. Whatever you add, add it deliberately, not at midnight. If your fix is rejected anyway, our app store rejection page covers Apple's appeal path.

Repairs that lock out more people than the bug

  • Forcing a password reset for every user. If the reset emails also fail, you have locked out the people who could still log in.
  • Putting a new secret directly into the app. Google Cloud warns that keys "hardcoded in the source code or stored in a repository are open to interception or theft," and says the client should pass requests to the server, which adds the credential.
  • Deleting the old key before the new one is live everywhere. Older app versions on users' phones may still depend on it.
  • Wiping sessions to "start fresh." It turns a problem for new logins into a problem for every user at once.
  • Changing the domain, redirect address or bundle settings without updating every place the login provider stores them.

Lost access to the developer accounts or the login provider is its own crisis. If the person who set up Sign in with Apple, the identity service or the server has left, start with our developer disappeared page.

Getting the fix to users: server first, store second

The fastest login fix is one that ships without an app update. Expired secrets, provider settings, server code and redirect addresses can all be corrected on the server, and users get in again the moment it is deployed, with no store review in the way. Only when the bug lives inside the app does the fix have to pass review.

Apple, as Apple states it

  • App Review typically reviews "at least 50% of submissions in less than 24 hours and 90% in less than 48 hours," as of November 2026
  • Expedited review exists for extenuating circumstances such as "fixing a critical bug"; include steps to reproduce it
  • For apps already on the store, bug fixes "will not be delayed over guideline violations except for those related to legal or safety issues"
  • Give reviewers a working demo account, and "turn on your back-end service"

Google Play, as Google states it

  • A rejected update "will not be made available on Google Play"
  • A staged rollout lets the fix reach a percentage of users first
  • Halting a rollout stops new users getting it; those who have it stay on it
  • Review times are not stated in the sources we read, so we quote none

The review times and expedite rules above come from Apple's App Review page; the bug-fix and demo account lines come from its guidelines, which add a caution: "Please respect your fellow developers by seeking expedited review only when you truly need it," and abuse can get future requests rejected. A login that keeps paying customers out is the kind of critical bug the expedite exists for. We promise no approval and no review time, because neither is ours to give.

Your call, or ours

Handle it yourself when the provider's status page shows an outage, or when your developer is reachable and the logs point to one expired secret. Generating a new one is a short job for the person who knows where it lives. Call us when nobody knows how the login was built, the person who set it up is gone, the fix requires an app release you cannot make, or logins keep breaking every few months. We respond the same business day (hours on our contact page).

Login repairs are from $575, depending on complexity, with a written estimate before work starts; emergency pricing explains what moves it. A broken connection to a login provider or API is restored the same day once we have access to the accounts, the server and the code. The mobile offer, including the access we need in App Store Connect and Google Play Console, is on our emergency app repair page. Longer work falls under fixing broken mobile apps, iOS app development and API integrations. If it is a WordPress site's admin login rather than an app, our WordPress login fix is the faster route. Browse every scenario on the emergency repair hub, see our work, or read about DataCram, a San Antonio studio building for the web since 1999. Call (210) 346-0848.

Questions owners ask in an emergency

The common causes are a login provider outage, an expired or rotated secret or key, a recent server or app change, or a change to the domain or redirect settings the provider expects. Sort who is affected first: everyone, one platform, one sign-in method or only new users. That pattern points to the cause faster than reading code.

Yes. Apple's documentation on creating a client secret says it is an error to request an expiration time more than 15777000 seconds, six months, in the future, as of November 2026. Apple's token validation docs say validation requests require that secret. A server that never regenerates it will stop validating Apple sign-ins.

Apple's guideline 4.8, as last updated October 16, 2026, says apps using a third-party or social login for the primary account must also offer an equivalent login service that limits data to name and email, lets users keep their email private, and does not collect interactions for advertising without consent. As read, it does not name a specific product. Some apps are exempt.

Often not. Expired secrets, provider settings, redirect addresses and server code can be fixed on the server, and users can log in as soon as it deploys. Only bugs inside the app need a new release, which then passes Apple or Google review. Apple offers expedited review for critical bugs, as it states on its App Review page.

Not as a first move. If the reset emails or the reset flow are part of the failure, a mass reset locks out the users who could still get in. Find the cause first. If you suspect accounts were taken over, treat it as a security incident, involve your attorney and insurer, and read our data breach page.

DataCram's app and login repairs are from $575, depending on complexity, with a written estimate before work starts. We respond the same business day, and a broken connection to a login provider is restored the same day once we have access. We promise no store approval or review time.

Keep reading

Free · No obligation

Get your users back in

Tell us which users cannot log in, on which platform, and what changed recently. We reply the same business day with the likely cause, the access we need and a written estimate.

Which of these sounds like you? (pick any)

Rather talk now? Call (210) 346-0848.

CallGet a quote