MicroG Login Not Working? Fix Guide

Fix steps

1. Update GmsCore Take the latest release from the official ReVanced GitHub rather than a mirror. Google changes its sign-in flow, and only a current build follows the current flow
2. Clear GmsCore data App info, Storage, Clear data, then try signing in again. This discards a half completed authentication state, which is what keeps most loops going
3. Disable battery optimization Settings, Battery, GmsCore, Don't optimize. Android suspending GmsCore in the background is the cause when sign-in works and then stops working an hour later
4. Grant the notification permission On Android 13 and newer, GmsCore relies on a foreground notification to stay running. Denying it makes the system treat the process as expendable
5. Check the pairing The GmsCore build has to match what the patched app expects. Old Vanced MicroG alongside a new ReVanced build will not sign in, in either direction
6. Re-patch If nothing above helps, uninstall the patched app and GmsCore, build again from the base version Manager recommends, install GmsCore first, then the app

Common error messages

• "Error signing in" usually means MicroG or GmsCore is out of date, or the build you installed is not the one the patched app expects.
• "Account action required" means Google wants the account verified again. Remove the account from GmsCore, add it back, and complete whatever check it asks for.
• A loop that returns you to the sign-in screen without an error normally clears after wiping GmsCore data, and comes back if battery optimization is still on.
• "This app isn't verified" appears because a sideloaded app is signed by you rather than by Google. It is expected and safe to dismiss.
• A blank or endlessly spinning sign-in page usually means GmsCore could not reach Google at all, which points at DNS filtering or a VPN rather than at the app.

Why MicroG login breaks in the first place

• It is a reimplementation, not an official client. It reproduces the parts of Play Services that sign-in needs, and Google is under no obligation to keep that working.
• Sign-in has more moving parts than playback. The account chooser, the token exchange and the refresh afterwards can each fail on their own, and the app reports all of them the same way.
• It runs in the background. Anything that kills background processes, from the system power manager to a task killer, breaks the refresh step specifically.
• Version pairing matters. GmsCore and the patched app are built separately and only work together within a range, so updating one and not the other causes failures that look random.

If none of this worked

• For old YouTube Vanced there is usually no repair, and it is worth saying that plainly. Vanced MicroG stopped getting updates when the project ended in March 2022, Google's sign-in has moved on repeatedly since, and no one is going to release a fixed build. If a Vanced login broke, it is very likely broken permanently.
• For ReVanced, a full rebuild is the last real step: uninstall both parts, patch the recommended base version with the default patch selection, install GmsCore first, then the app. Anything after that is waiting for a newer GmsCore release.
• Check the account in a browser on the same device. If Google is holding it for a security check, the app cannot clear that on your behalf.
• Running signed out is a legitimate fallback. You lose subscriptions, history and playlists, but playback and most patches work without an account.
• If you need account features and ReVanced sign-in will not hold, a client that does not use a Google account at all, such as NewPipe or LibreTube, may suit you better than fighting this.

Questions people ask

• Is Vanced MicroG the same as GmsCore? No. Vanced MicroG was built for Vanced and is unmaintained. GmsCore is the ReVanced build and is the one to install today.
• Can I install both? You can, and you should not. Two of them at once means the patched app can bind to the wrong one, which produces exactly this problem.
• Does MicroG see my password? Sign-in happens through Google's own web flow. MicroG stores the resulting token, which is why installing it from the official source matters.
• Will a factory reset fix it? No, and it costs you the rest of your device setup. Nothing about this failure lives in system state you would clear that way.

If you are on ReVanced and want the shorter version aimed at that setup specifically, the ReVanced GmsCore login guide covers the same ground with fewer detours, and the GmsCore guide walks through a clean install.

For Vanced users, the realistic path is to stop treating this as a fixable fault. Moving to ReVanced gets you a maintained sign-in with a maintained app behind it, and the alternatives page covers options that avoid Google accounts entirely.

Extra notes before you retry

If the problem comes back after a fix, note your YouTube base version, your ReVanced Manager build, and whether GmsCore is installed before trying anything else. A version mismatch between those is behind most repeat failures.