ReVanced GmsCore APK Details
| App Name | ReVanced GmsCore |
| Category | ReVanced Tools |
| Platform | Android |
| Download Status | Official Source Only |
Tags
Safety Information
ReVanced GmsCore is the component that makes Google sign-in possible in a patched app on a device without root. It is a fork of the open-source microG project, trimmed to the authentication and push paths that patched builds depend on. The ReVanced team maintains it and publishes it from its own GitHub repository.
The problem it solves
When you patch an app, the output is signed with a key generated on your device. Google Play Services checks the signature of any app requesting an account token and refuses anything it does not recognise. The patched app is therefore locked out of your account through the normal route, no matter how correct the rest of the build is.
GmsCore steps into that gap. The ReVanced patches redirect the app's services calls to GmsCore instead of to Play Services, and GmsCore runs its own OAuth flow to obtain a token. From the app's perspective nothing has changed. From Android's perspective two separate service providers now exist side by side.
Install order and battery settings
GmsCore has to be present before you launch the patched app for the first time. A patched build that starts without finding it will either show an error and close or run with no account attached, and the fix is to install the companion and start over rather than to reinstall the patched app.
Battery optimisation causes the majority of intermittent sign-in complaints. Android suspends the GmsCore process to save power, the patched app loses its token, and you get logged out at an apparently random moment. Excluding GmsCore from battery optimisation, and allowing it to run in the background, is not optional on most manufacturer skins.
What it does not do
It is not a full Play Services replacement. It carries enough to support sign-in and push notifications for patched apps, and it does not attempt to provide the wider set of Google APIs that unrelated apps might expect. It also has no effect on playback, ad removal or any patch behaviour, so a video that will not play is not a GmsCore problem.
Rooted installs do not need it. Mounting a patched build over the system app preserves the original Google signature, real Play Services accept the request, and the companion becomes redundant.
Verifying the file
The ReVanced build registers itself as app.revanced.android.gms, kept distinct from both Google's services package and the older Vanced companion so all three can coexist. A ReVanced GmsCore APK reporting any other identifier is not the file it claims to be.
Take the download from the GitHub releases page, where the assets and their hashes are published alongside the source. This component sits directly in the authentication path and hosts the sign-in web view, which makes it the least sensible thing in the stack to source from a random mirror. See the GmsCore guide for the setup sequence.
ReVanced GmsCore APK: Frequently Asked Questions
They share an upstream ancestor in the microG project, but they are different builds with different package identifiers and different maintainers. Patched ReVanced apps expect GmsCore specifically.
Almost always battery optimisation suspending the GmsCore process. Exclude it in your battery settings and allow unrestricted background activity.
No. A root install keeps the original app signature, so genuine Play Services handle the login and the companion is unnecessary.
It should not. It registers under its own identifier and only serves apps that were patched to look for it. Your normal Play Services installation is untouched.
On a non-root install, no. The patched app has no route to an account token without a services provider it is allowed to talk to.