Battle Net Authenticator Not Working | No Lockout Fix

If you’re stuck at the login screen with a spinning wheel, a missing push request, or codes that get rejected, you’re not alone. The Battle.net authenticator is simple when it behaves, and maddening when it doesn’t. This page walks you through the fixes that solve most cases on iPhone and Android today, plus a safe way to recover access if you changed phones.

You’ll start with fast checks that take a minute, then move into deeper fixes that deal with clock drift, app resets, and reattaching the authenticator to your account. If there’s an outage on Blizzard’s side, you’ll also see how to spot it early so you don’t waste time reinstalling apps for nothing.

What Battle.net Uses For Two Step Login

Blizzard’s two-step login can show up in a few forms. Some accounts get a push request in the Battle.net mobile app. Others get a rotating code you type in. In some cases you might be asked for a one-time code sent to email or SMS, depending on what security options are enabled on your account.

One detail trips people up. Blizzard moved authenticator features into the Battle.net mobile app, and the older standalone “Battle.net Authenticator” app was phased out. If you’re still trying to use the old app, or you restored it from a backup, you may see restore failures or missing prompts. Blizzard’s migration notice explains the switch and the dates around store removal and transfer steps.

• Check which app you have — Open your phone’s app list and confirm you’re using the Battle.net app, not the retired standalone authenticator.
• Confirm your login method — On the login screen, note whether it asks for a push approval, a 6–8 digit code, or an email/SMS code.
• Keep your recovery path ready — If you can’t approve a login, you’ll need your restore code or the account recovery flow to get back in.

If you want Blizzard’s own directions for moving from the old authenticator app to the Battle.net app, read the official post here: Blizzard’s Battle.net app migration notice.

Battle Net Authenticator Not Working On Mobile Devices

When battle net authenticator not working shows up, start by separating “your phone” problems from “Battle.net” problems. A phone issue is usually fixed with settings, time sync, and a reset. A Battle.net issue may clear on its own once Blizzard finishes maintenance or fixes a backend bug.

Quick Checks That Save Time

• Try a second login route — On the login screen, switch between push and manual code entry if both are offered.
• Test another connection — Swap Wi-Fi to mobile data, or the other way around, to rule out a network block.
• Restart the phone — A clean reboot can restore notification delivery and background services.

On PC, the launcher can hang on an old session and keep prompting for approval. Quit it fully, reopen, then try one browser login to confirm your account details are fine.

• Sign out everywhere — Use account security settings, then try a fresh login.
• Disable VPN — Some networks delay repeated auth requests.
• Try the web login — If it works, the launcher issue is local.

Common Symptoms And Fix Direction

If you suspect Blizzard is having a wider authenticator problem, check the Battle.net launcher notice area and Blizzard’s status feeds before you start deleting apps. Blizzard has also publicly acknowledged authenticator outages in the past, including a restoration issue reported in November 2025.

Fix Codes That Get Rejected

Rejected codes almost always mean the authenticator token is out of sync. That can happen after a phone restore, an OS time change, or a long period with the app sleeping in the background. The fastest repair is the built-in resync option in the Battle.net app.

Resync The Authenticator Inside The App

1. Open the Authenticator screen — In the Battle.net app, tap Authenticator so you’re looking at the code entry view.
2. Enter code manually — Tap the option to enter the code manually, even if you prefer push.
3. Tap Resync — Use the resync option shown on that screen, then follow the prompts.
4. Try a fresh code — Wait for the next code cycle, then type the new code on the login screen.

Those steps match Blizzard’s help article for “Mobile Authenticator – Resync Failed,” which also notes that you can remove and reattach the authenticator if resync still fails. You can read Blizzard’s instructions here: Resync steps for the mobile authenticator.

Reset The Authenticator If Resync Doesn’t Stick

If resync runs but the next code still gets rejected, reset the authenticator state inside the app. This clears the local token and forces a clean setup flow.

1. Open the app menu — On the authenticator screen, tap the menu icon in the corner.
2. Tap Reset — Choose Reset and complete the prompts inside the Battle.net app.
3. Sign in again — Log back into the Battle.net app with your account email and password.
4. Re-check the code — Return to the login screen and enter the newly generated code.

If you’re still blocked, check your phone’s date and time settings next. A manual time setting can drift enough to break time-based codes.

• Set time to automatic — Turn on automatic date and time and automatic time zone in system settings.
• Toggle airplane mode — Flip airplane mode on for 10 seconds, then off, to force a clean network time sync.
• Update the app — Install the latest Battle.net app build from the App Store or Google Play.

Fix Push Requests That Never Arrive

Push approvals fail when your phone blocks the app from running in the background, or when notifications are muted. This is extra common after an OS update, a new phone setup, or switching battery modes.

Notification And Background Settings On iPhone

1. Allow notifications — In iOS Settings, allow notifications for Battle.net, and allow lock screen alerts.
2. Disable Focus blocks — If Focus is active, add Battle.net to the allowed apps list.
3. Allow background refresh — Enable Background App Refresh for Battle.net so it can receive pushes.
4. Check cellular access — Allow cellular data for Battle.net if Wi-Fi is unstable.

Notification And Battery Settings On Android

1. Allow notifications — Long-press the Battle.net icon, open App info, then enable all notification categories.
2. Remove battery restrictions — Set Battery to Unrestricted or No limits for Battle.net.
3. Allow background data — Turn on background data and unrestricted data usage if your phone offers it.
4. Clear cache — In App info, clear cache, then reopen the app and sign in.

If you’re seeing delayed pushes, keep the Battle.net app signed in and avoid task killers. Many “cleaner” apps cut background processes and break push delivery.

Switch Phones Or Reinstall Without Getting Locked Out

A phone upgrade is the moment most people get stuck. You wipe the old device, then realize your authenticator lived there. The safest order is to transfer or detach the authenticator while you can still log in, then attach it on the new phone.

Before You Wipe The Old Phone

• Open the Battle.net app — Confirm the authenticator is visible and generating codes or receiving pushes.
• Save your restore code — Store the restore code in a password manager or offline note you can reach later.
• Add a second method — Enable email verification as a backup, so you can still get in if the app fails.

If You Already Lost Access

If you can’t approve a login and you don’t have your restore code, use Blizzard’s authenticator restore flow. It’s designed for cases where the phone is gone or reset.

1. Open the restore page — Go to Blizzard’s authenticator restore page in a browser.
2. Sign in if you can — If you can’t pass the authenticator gate, use the recovery options shown on the page.
3. Follow identity checks — Complete the steps Blizzard asks for, then attach the authenticator again in the Battle.net app.

You can reach the restore page here: Battle.net authenticator restore.

Reattach Cleanly After A Reinstall

Reinstalling can help when the app state is corrupted. It also resets permissions, which can fix missing pushes. Do it in a way that avoids a lockout loop.

1. Install the Battle.net app — Download it fresh from the official store listing.
2. Sign in first — Log into the app and reach your account home screen.
3. Add the authenticator — Attach it from the account security area, then confirm it’s generating a code.
4. Test a login — Log out on a second device or browser and confirm you can get back in.

Keep The Authenticator Stable Day To Day

Once you’re back in, a few habits reduce repeats. Most problems come from time drift, muted notifications, or the app being signed out in the background.

Small Habits That Cut Errors

• Leave time on automatic — Automatic time and time zone keep codes aligned.
• Update the app monthly — App updates often fix login bugs and push delivery issues.
• Keep one backup path — Email verification or SMS can be a backup when push is down.
• Test after big changes — After an OS update or phone transfer, do a quick test login while you’re not in a rush.

Keep a printed restore code at home, separate from your phone, so you can recover fast.

One Page Checklist When The Authenticator Fails

1. Check for outages — Look at launcher messages and status pages before you change settings.
2. Swap connections — Try Wi-Fi and mobile data to rule out a network block.
3. Resync the authenticator — Use Enter Code Manually, then Resync inside the Battle.net app.
4. Reset the authenticator — Use the in-app Reset option, then sign back in.
5. Fix notifications — Allow alerts and background activity so push requests can arrive.
6. Use restore flow — If the phone is gone, use the Battle.net restore page to attach again.

If battle net authenticator not working still blocks you after all steps above, pause and avoid repeated login attempts for a bit. Too many failed attempts can trigger security holds. After a short break, try again with a fresh code and a stable connection.

Send us your feedbackTell us what you thought about this post

Name * Email *

Your comment *

Quick check — what is …? *

Send feedback