ReVanced MicroG / GmsCore Login Fix

ReVanced MicroG login: step-by-step fix

1. Get the current GmsCore from the official ReVanced GitHub. Old MicroG builds and copies from mirror sites are the single most common cause of this, because the sign-in flow on Google's side keeps changing and only a current build follows it.
2. Uninstall any older MicroG or GmsCore before installing the new one. Two of them installed at once means the patched app can bind to the wrong one, which looks exactly like a broken login.
3. Install the GmsCore APK and open it once directly from your app drawer. You should see its own settings screen rather than a crash. If it will not open at all, the download is bad or the build does not match your device architecture.
4. Open ReVanced and start the sign-in. A working setup hands you to a Google account chooser or a browser page. If nothing happens at all when you tap sign in, GmsCore is not installed or not being found.
5. Grant every permission GmsCore asks for, including notifications on Android 13 and newer. GmsCore uses a foreground notification to stay alive, and denying it makes Android treat the process as disposable.
6. Turn off battery optimization for GmsCore under Settings, Battery, then the per app list. This is the fix for the loop where sign-in works, then stops working an hour later.
7. Reboot and try once more before concluding it failed. Some devices only apply the battery exemption after a restart.

Why ReVanced MicroG login fails

• GmsCore is out of date. Google changes its authentication endpoints, and a build from a year ago follows a flow that no longer exists.
• The patched app and GmsCore expect different things. A patched app built with an old bundle paired with a new GmsCore, or the reverse, will not complete the handshake.
• Android killed the process. GmsCore does its work in the background, and any power manager that suspends it turns a working login into a loop.
• The wrong MicroG is installed. Vanced MicroG is a separate, unmaintained project and does not serve ReVanced. GmsCore from the ReVanced organization is the one you want.

If none of this worked

• Re-patch from scratch. Uninstall the patched app and GmsCore, build a new APK from the base version Manager recommends, install GmsCore first, then the app. This rules out a stale pairing, which nothing else does.
• Check whether the account itself is the problem. Sign into the same Google account in a browser on the same device. If Google is asking for a security check there, the app cannot resolve that for you.
• If your network filters DNS, sign-in can fail while everything else works. The no internet guide covers that case.
• If you are actually trying to sign in on old YouTube Vanced rather than ReVanced, stop here. Vanced MicroG has had no maintenance since March 2022, and its login is broken in ways nobody is going to repair. The MicroG login guide explains what that means in practice.
• You can use ReVanced without signing in. You lose your subscriptions, history and playlists, but ad-free playback and most patches work on a signed out app.

Questions people ask

• Do I need GmsCore at all? Only for account features. Without it, a non-root ReVanced install still plays video, it just never knows who you are.
• Is it safe to give GmsCore my Google account? It is an open source reimplementation of the Play Services APIs and it talks to Google directly. The risk is the build you install, which is why the source matters more than the app does.
• Why does the app say it is not verified? That warning appears because the app is signed by you rather than by Google. On a sideloaded install it is expected and does not indicate a failure.
• Will signing in on the official YouTube app help? No. The two apps hold separate account state, and the patched build reads its token from GmsCore, not from Google Play Services.

If sign-in still fails after all of this, the full MicroG login guide covers the individual error messages and the harder edge cases, and the GmsCore guide walks through a clean install from nothing.

One thing worth setting expectations on: sign-in through GmsCore is the least stable part of any ReVanced setup, because it depends on a service that is under no obligation to keep working with it. It breaks occasionally, gets fixed in a later GmsCore release, and breaks again. Keeping GmsCore current is most of the maintenance.

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.