An authenticator app that suddenly stops working can leave you locked out of email, work accounts, banking services, social media, and other accounts protected by two-factor authentication. The frustrating part is that the app may still open normally while verification codes are rejected, approval notifications never arrive, or accounts disappear after changing phones.
The right fix depends on what is actually failing. A six-digit code that is always rejected has different causes from a missing Microsoft Authenticator approval prompt, and both are different from losing your accounts after moving to a new Android phone.
I recommend identifying the symptom first instead of immediately deleting the authenticator app. Removing an account or uninstalling the app before confirming that you have another sign-in method can make account recovery much harder.
This guide focuses on Android while covering Microsoft Authenticator and Google Authenticator separately where their behavior differs.
First, Identify What Is Not Working
“Authenticator app not working” can describe several different problems:
- The authenticator app will not open
- Verification codes appear but are rejected
- Codes have disappeared
- Microsoft Authenticator approval notifications do not arrive
- Notifications arrive too late
- The app stopped working after changing phones
- A restored Microsoft Authenticator account says action is required
- Google Authenticator codes are missing on a new phone
- A QR code will not scan
- A work or school account no longer approves sign-ins
- The app works for one account but not another
This distinction matters because authenticator apps can use different verification methods.
Time-based one-time passwords (TOTP) generate rotating codes on the phone. These can normally be generated without an internet connection after setup.
Push approvals send a sign-in request to the authenticator app. These require network connectivity and working push notifications.
A network problem can therefore break Microsoft Authenticator approval prompts while ordinary rotating codes continue to appear.
Do Not Delete the App Yet
This is the most important precaution.
Do not uninstall the authenticator app, remove an account, clear its storage, or factory-reset the phone until you know how you will sign back into every protected account.
Before making destructive changes, check whether you have:
- Backup or recovery codes
- Another registered authentication method
- A second trusted device
- SMS or email verification where supported
- Access to the old phone
- Access to the account’s security settings
- An IT administrator who can reset MFA for a work or school account
Clearing an Android app’s storage/data is very different from clearing its cache. Storage removal can erase locally stored configuration.
Treat authenticator credentials as security credentials, not ordinary disposable app data.
Check the Phone’s Date and Time
Incorrect time is one of the first things to check when authenticator codes are generated but rejected.
Time-based authentication depends on the phone and authentication server agreeing closely enough about the current time.
On Android, open the phone’s date and time settings and enable automatic time and automatic time zone where available.
The path is commonly:
Settings > System > Date & time
On some Samsung phones, look under:
Settings > General management > Date and time
Restart the phone afterward and generate a fresh code.
Microsoft specifically recommends checking that the device’s date and time are correct when troubleshooting Authenticator.
Do not keep entering a code that is about to expire. Wait for the next code and enter it promptly.
Make Sure You Are Using the Correct Account’s Code
Authenticator apps often contain several accounts with similar names.
Before assuming the code generator is broken, check:
- The account email address
- The service name
- Whether you have duplicate entries
- Whether the website is requesting a code from another account
- Whether an old and new authenticator registration both appear
This is particularly easy to miss after re-registering two-factor authentication.
If two entries have nearly identical names, compare them carefully before removing anything.
Check Your Internet Connection for Approval Requests
Rotating authenticator codes can often work offline, but push approval notifications cannot.
If Microsoft Authenticator is waiting for an approval request that never appears:
- Turn Airplane mode off.
- Confirm the phone can access the internet.
- Switch from Wi-Fi to mobile data.
- If you are using mobile data, try Wi-Fi.
- Temporarily disconnect a VPN and test again.
Microsoft recommends switching between Wi-Fi and mobile data and testing without a VPN when Authenticator has connectivity problems.
If the approval prompt appears immediately on another network, investigate the original Wi-Fi, VPN, proxy, firewall, or network restrictions.
Enable Authenticator App Notifications on Android
A sign-in request can reach Microsoft Authenticator without producing a visible alert if Android notifications are disabled.
Open:
Settings > Notifications > App notifications
Find Microsoft Authenticator and make sure notifications are enabled.
Depending on the phone, you can also open:
Settings > Apps > Microsoft Authenticator > Notifications
Enable the relevant notification categories.
Android menu names can vary by manufacturer. Microsoft also recommends checking Authenticator’s own notification settings and confirming that notifications are enabled.
After changing notification settings, request a new sign-in approval instead of waiting for an expired request.
If notifications are failing across multiple apps, the problem may be broader than Authenticator. My guide to fix Android notifications not working covers system-wide notification problems.
Turn Off Do Not Disturb Temporarily
Do Not Disturb, Quiet mode, and similar focus features can suppress alerts.
Turn the feature off temporarily and request another authentication notification.
If the prompt becomes visible, review the phone’s Do Not Disturb exceptions instead of permanently disabling the feature.
Microsoft specifically lists Do Not Disturb or Quiet mode as something to check when Authenticator notifications do not appear.
Check Battery Restrictions for Microsoft Authenticator
Android battery management can delay or restrict background activity.
Microsoft’s current Authenticator troubleshooting guidance recommends turning off battery optimization for better sync performance.
On many Android phones, open:
Settings > Apps > Microsoft Authenticator > Battery
The wording varies. You may see:
- Unrestricted
- Optimized
- Restricted
- Allow background usage
For troubleshooting missing approval prompts, allow Authenticator to run properly in the background.
Some manufacturers add their own battery-saving controls, so Samsung, Xiaomi, OnePlus, Oppo, Vivo, and other phones may use different menu names.
Be selective with unrestricted background access because it can increase battery consumption.
Make Sure Background Data Is Allowed
Push authentication also depends on the app being able to communicate in the background.
Open the Android app information page for your authenticator and check its mobile data or network settings.
Make sure background data has not been disabled.
Also check whether Data Saver is restricting the app.
If the problem occurs only on mobile data but Authenticator works on Wi-Fi, background-data or Data Saver restrictions deserve particular attention.
Update the Authenticator App
Running an old authenticator version can cause compatibility and security problems.
Open Google Play Store, find the authenticator app, and install any available update.
For Microsoft Authenticator, this is especially important. Microsoft’s current support guidance says it does not support Authenticator versions more than 12 months old.
Also update Android and Google Play services. For managed work devices, keep Microsoft Company Portal or other organization-required security apps current as well.
Restart the phone after major updates and test again.
Check Google Play Services on Android
Microsoft Authenticator relies on Google Play services for some Android functionality, particularly push notifications for work or school accounts.
Microsoft states that to use Authenticator on Android for a work or school account, push notifications must be enabled and Google Play services and Google Play Store must be installed and enabled.
Open:
Settings > Apps > Google Play services
Make sure it is enabled.
Then check Google Play Store as well.
If Google Play services is missing, disabled, badly outdated, or unavailable on the device, Microsoft Authenticator push functionality for organizational accounts may not work as expected.
Restart the Android Phone
A restart can recover stuck notification services, temporary network problems, Google Play services issues, and background processes.
Restart the phone, unlock it normally, connect to the internet, open the authenticator app, and request a completely new authentication attempt.
Do not test with an approval request that has already expired.
Clear the Authenticator App Cache Carefully
If the authenticator app itself freezes, crashes, or displays incorrectly, clearing its cache may help.
The Android path is usually:
Settings > Apps > [Authenticator app] > Storage & cache > Clear cache
Do not select Clear storage, Clear data, or a similar option unless you have verified your recovery options and understand what will be removed.
Clearing cache removes temporary files. Clearing app storage can reset the application and may remove local authentication configuration.
If you are unsure, skip this step.
Fix Microsoft Authenticator Notifications That Never Arrive
When Microsoft Authenticator opens and shows your account but no approval request arrives, troubleshoot the notification path rather than the rotating-code system.
Check these in order:
- Internet connection
- Airplane mode
- Android notification permission
- Authenticator’s notification settings
- Do Not Disturb
- Battery optimization
- Background data
- Google Play services
- App updates
- VPN or network filtering
Microsoft also recommends checking whether notifications work for other apps.
If other apps cannot receive notifications either, troubleshoot Android’s notification or network system.
If Authenticator receives notifications for some accounts but not one particular account, Microsoft recommends removing and adding the problematic account again while allowing notifications.
Only do that after confirming another way to authenticate.
Microsoft Authenticator Says “Enable Push Notifications”
This message points directly toward notification or connectivity configuration.
Make sure Android notifications are enabled, the phone has internet access, background activity is not excessively restricted, and Google Play services is available for applicable work or school configurations.
Microsoft also suggests removing and adding the account again if the problem continues.
For a work or school account, contact your organization’s IT administrator if you cannot re-register the account yourself.
Microsoft Authenticator Says Google Play Services Are Unavailable
For Android work or school accounts, Microsoft says Google Play services and Google Play Store must be installed and enabled, along with push notifications.
Microsoft also recommends checking that:
- A PIN or biometric is configured
- The appropriate work profile has a PIN or biometric
- Hardware encryption is enabled
- Device registration is correct
- The device is not compromised
Check Authenticator > Settings > Device Registration when troubleshooting a work or school passwordless account.
Organization policies can also affect whether the device is allowed to register.
Fix Authenticator Codes That Keep Saying Incorrect
A code can appear normal and still be rejected.
Wait for a fresh code
Do not enter a code during the final seconds of its validity. Wait for the next one and enter it immediately.
Check automatic date and time
Incorrect device time can invalidate time-based codes.
Verify the account
Make sure you are using the code associated with the exact account and service requesting authentication.
Check whether MFA was recently reset
If you or an administrator reconfigured two-factor authentication, an older authenticator entry may no longer correspond to the server’s current registration.
Re-register only when you can still access the account
If every new code fails and the service lets you manage security methods through another authenticated session, remove the obsolete authenticator registration from the service and set it up again.
Do not simply delete the authenticator entry first and hope you can sign back in.
Google Authenticator Not Working
Google Authenticator behaves differently from Microsoft Authenticator in important ways.
Its primary role is generating verification codes rather than receiving Microsoft’s approval prompts.
If Google Authenticator codes are rejected:
- Confirm you selected the correct account.
- Wait for a fresh code.
- Check the phone’s date, time, and time zone.
- Make sure the account has not been reconfigured elsewhere.
- Check whether the service is expecting another verification method.
If codes disappeared after moving phones, investigate account synchronization or transfer rather than treating it as a notification problem.
Google Authenticator Not Working on a New Phone
Current Google Authenticator versions can synchronize codes with a Google Account.
Google says that when you sign in to your Google Account within Google Authenticator on a new device, synchronized codes become available on that device.
Open Google Authenticator on the new phone and check whether you are signed into the same Google Account used for Authenticator synchronization on the old phone.
If you used Google Authenticator without a Google Account, manually transfer the codes while you still have the old device.
On the old phone:
- Open Google Authenticator.
- Open the menu.
- Select Transfer accounts.
- Select Export accounts.
- Choose the accounts.
- Generate the transfer QR code.
On the new device, use Google Authenticator’s transfer/import function to scan it.
Keep the old phone until you have tested the transferred accounts.
What if You No Longer Have the Old Phone?
Losing the old device changes the problem from ordinary app troubleshooting to account recovery.
Do not repeatedly reinstall Authenticator expecting locally stored credentials to reappear automatically.
Check each protected service for:
- Recovery codes
- Backup authentication methods
- Another signed-in device
- Account recovery
- SMS or security key options
- Administrator-assisted MFA reset
For Google Authenticator, codes synchronized to your Google Account may be available after signing into Authenticator on the new device.
If the codes were used without Google Account synchronization and the old device is unavailable, you may need to recover access separately from each protected service.
Microsoft Authenticator Not Working on a New Phone
Installing Microsoft Authenticator on a new phone does not automatically make every previous authentication method fully functional.
Microsoft provides backup and recovery, but what is restored depends on the account type.
Some one-time-password credentials can be restored. Microsoft passwordless accounts may require another sign-in, while work or school accounts may restore the account name but require re-registration.
Microsoft also states that Authenticator backup and restore works only between the same device type. A backup from iOS cannot be restored to Android, and an Android backup cannot be restored to iOS.
That limitation matters when switching platforms.
Restore Microsoft Authenticator on a New Android Phone
If you previously enabled Microsoft Authenticator backup, install Authenticator on the new Android device and use the recovery option before configuring everything manually.
Microsoft’s current recovery procedure provides a Restore from backup or Begin recovery option.
Use the same personal Microsoft account that was used as the recovery account.
After restoration, some accounts may show Action required or ask you to sign in.
That does not necessarily mean the restore failed. Microsoft explains that some credentials require further verification before they can be used again.
Approval Requests Still Go to the Old Phone
Adding Microsoft Authenticator to a new phone does not automatically unregister the old phone.
Microsoft specifically says that even deleting Authenticator from the old device is not enough. The old device must also be removed as an authentication method from the Microsoft account or organizational account.
For a personal Microsoft account, review account security and two-step verification methods.
For a work or school account, use the organization’s security-information page or contact IT.
Do not remove the old method until you have confirmed that the new phone can authenticate successfully.
Work or School Authenticator App Not Working
Corporate and school accounts can be more complicated because the organization controls authentication policy.
A failure may involve:
- Microsoft Entra registration
- Conditional Access
- Device compliance
- Company Portal
- Work Profile
- Required screen lock
- Root detection
- Administrator-disabled authentication methods
- An old device registration
Microsoft introduced root/jailbreak detection for work and school Entra credentials in Authenticator in 2026. A rooted Android device can therefore fail organizational authentication even when ordinary consumer authenticator codes still work.
If only a work or school account is affected while personal accounts work, do not factory-reset the phone. Contact the organization’s IT administrator and provide the exact error.
Check the Android Work Profile
Organizations may deploy Microsoft Authenticator inside an Android Work Profile.
If that applies, make sure:
- The Work Profile is enabled
- Authenticator is installed in the correct profile
- The profile is not paused
- The profile has the required PIN or biometric
- Company Portal is current
- Device compliance is healthy
A personal copy of Authenticator and a work-profile copy can behave like separate app environments.
Authenticator App QR Code Not Working
A QR code problem can happen during setup or re-registration.
First check:
- Clean the camera lens
- Increase the brightness of the screen displaying the QR code
- Hold the phone steady
- Move slightly closer or farther away
- Make sure the complete QR code is visible
- Allow camera permission
Also check whether the QR code has expired.
Some authentication setup QR codes are tied to a temporary registration session. Generate a fresh code if necessary.
Never scan a QR code sent by an unknown person claiming it will “fix” Authenticator. Authentication QR codes can contain account-registration secrets.
Check Camera Permission
If the QR scanner shows a blank screen or cannot use the camera, open:
Settings > Apps > [Authenticator app] > Permissions > Camera
Allow camera access while using the app.
Then return to the legitimate account-security page and generate a new setup QR code if necessary.
Many services also provide a manual setup key. Treat that key as sensitive because it can be used to generate authentication codes.
Force Stop and Reopen the App
When the app itself is frozen or unresponsive, force stopping it is safer than immediately reinstalling.
Open:
Settings > Apps > [Authenticator app] > Force stop
Then reopen it.
Do not confuse Force stop with Clear storage.
What if the Authenticator App Keeps Crashing?
If the app closes immediately or repeatedly crashes:
- Restart Android.
- Update the authenticator app.
- Update Android.
- Update Google Play services.
- Check available phone storage.
- Clear only the app cache.
- Test again.
If it still crashes, verify your account recovery options before reinstalling.
A general app crash and a rejected authentication code are different problems. Reinstalling may repair a damaged app installation, but it will not repair an invalid MFA registration on the service’s server.
Check Available Phone Storage
Extremely low Android storage can cause apps and system services to behave unpredictably.
Open Settings > Storage, or the equivalent menu on your phone.
Free some space if the device is nearly full and restart it.
Avoid aggressive cleaner apps that promise to remove authentication data or hidden files.
Reinstall the Authenticator App Only When You Can Recover It
Reinstallation should be one of the later steps.
Before uninstalling, confirm at least one of these:
- Cloud backup/recovery is available and verified
- Google Authenticator codes are synchronized to your Google Account
- You still have the old phone
- You have recovery codes
- You have another registered sign-in method
- You are already signed into the account and can re-register MFA
- Your administrator can reset your MFA
Then reinstall the official app and restore or re-register the accounts.
Never assume that reinstalling an authenticator works like reinstalling an ordinary social-media app.
Do Not Keep Requesting Approval Prompts Repeatedly
When an approval notification is delayed, repeatedly pressing Send notification can create several pending requests.
Request one new sign-in prompt and compare the number or details shown on the website with the Authenticator request where number matching is used.
If you receive an authentication request you did not initiate, deny it.
Never Approve an Unexpected Authentication Request
An unexpected Authenticator prompt can mean someone else has your password and is attempting to sign in.
Do not approve it merely to make the notification disappear.
Instead:
- Deny the request.
- Change the account password from a trusted device.
- Review recent sign-in activity.
- Remove unfamiliar devices or sessions.
- Check registered security methods.
For a work or school account, report suspicious prompts to IT or the security team.
What Not to Do When Authenticator Stops Working
Avoid:
- Clearing app storage before checking recovery methods
- Deleting every authenticator account
- Factory-resetting the phone as an early fix
- Removing the old phone before testing the new one
- Approving unexpected prompts
- Scanning authentication QR codes from strangers
- Sharing setup keys or recovery codes
- Leaving screenshots of QR setup secrets unprotected
- Repeatedly guessing codes until the account locks
The objective is to restore authentication while preserving secure access.
A Troubleshooting Order That Minimizes Lockout Risk
For an authenticator app that is not working on Android, I recommend this order:
- Identify whether codes, notifications, the app itself, or one account is failing.
- Confirm recovery or alternative sign-in options.
- Check automatic date, time, and time zone.
- Verify the correct account entry.
- Check internet access for push approvals.
- Enable Android notifications.
- Turn off Do Not Disturb temporarily.
- Review battery and background-data restrictions.
- Update the app, Android, and Google Play services.
- Restart the phone.
- Clear only the app cache if the app itself malfunctions.
- Follow the provider-specific new-phone or recovery procedure.
- Re-register one affected account only when you can still access its security settings.
- Reinstall only after verifying credentials can be recovered.
- Contact the provider or IT administrator when the problem is account-side.
This keeps destructive changes near the end.
You might like to read:
- Android Resource Linking Failed: How to Fix the Error
- How to Fix Android Auto Communication Error 8
- Messenger Cache Not Clearing Android? 9 Fixes That Work
- How to fix Android Auto Microphone Not Working
Frequently Asked Questions
Why is my authenticator app not working?
Common causes include incorrect device time, disabled notifications, battery restrictions, network problems, an outdated app, Google Play services problems, an old MFA registration, or incomplete migration to a new phone.
Why are my authenticator codes not working?
Check the phone’s date and time, wait for a fresh code, and verify that you are using the code for the correct account. If MFA was reconfigured, an old authenticator entry may no longer be valid.
Does an authenticator app need internet?
Time-based one-time codes can generally be generated without internet after setup. Push approval requests require network connectivity.
Why am I not getting Microsoft Authenticator notifications?
Check Android notification permission, Authenticator’s notification settings, internet access, Do Not Disturb, battery restrictions, background data, Google Play services, and VPN/network restrictions.
Why is Microsoft Authenticator not working on my new phone?
The new device may not yet be fully registered. Restoring a backup can recover some information, but Microsoft says certain account types require you to sign in or re-register after restoration.
Why do Microsoft Authenticator notifications still go to my old phone?
Adding the new device does not automatically unregister the old one. Microsoft says the old device must also be removed from the account’s authentication methods.
Why is Google Authenticator not showing my codes on a new phone?
If you used Google Account synchronization, sign into Google Authenticator with the same Google Account. If you used it without an account, manually transfer the codes from the old device while you still have access.
Can I clear Authenticator cache?
Clearing cache is much less destructive than clearing storage. Do not clear app storage/data unless you have confirmed how your authenticator credentials will be restored.
Can I uninstall and reinstall Authenticator?
Yes, but only after confirming that you can restore or re-register the protected accounts. Otherwise you can lose the local credentials needed to sign in.
What should I do if my old phone is lost?
Use synchronized credentials where available, recovery codes, another authentication method, account recovery, or an administrator-assisted MFA reset.
Why does Authenticator work for one account but not another?
That usually points toward the individual account’s registration or organization policy rather than a complete app failure.
Can a rooted Android phone stop Microsoft Authenticator from working?
For Microsoft work and school Entra credentials, yes. Microsoft introduced root/jailbreak detection in 2026 that can prevent those credentials from functioning on rooted or jailbroken devices.
Protect Account Access While You Fix the App
The biggest mistake when an authenticator app stops working is treating it like an ordinary misbehaving Android app.
Authentication credentials are part of the account’s security system. Deleting app data, removing registrations, or resetting the phone without a recovery method can make the original problem much worse.
Start with the non-destructive causes: correct the phone’s time, check the right account, restore network and notification access, remove excessive battery restrictions, update the software, and restart the phone. When the problem began after changing devices, use Microsoft or Google’s official migration and recovery process instead of starting from scratch.
Once authentication works again, save fresh recovery codes somewhere secure and make sure you have at least one backup sign-in method. That preparation turns the next phone replacement or app failure into a routine recovery instead of an account lockout.
