Fix Guide

ReVanced: App Not Installed Fix

The ReVanced app not installed error is Android refusing your patched APK, and patching adds one cause that ordinary sideloading does not have. ReVanced Manager signs every build with a key it generates and keeps locally, and your patched YouTube claims the same package name as the official app. Android will not swap one for the other unless the signing key matches, so a leftover install, or a Manager that regenerated its key, blocks the install with a message that explains none of that.

📅 Last updated: May 2026

How to fix ReVanced app not installed

Uninstall the existing app: Remove every copy of the app already on the device. On a non-root setup that includes the official YouTube app, because the patched build takes its package name
Check for hidden copies: Settings, Apps, then show system apps. A disabled YouTube, or a copy inside a work profile or a second user, still holds the package name and still blocks the install
Disable rather than uninstall where you must: On devices where YouTube is preinstalled and cannot be removed, uninstall its updates and disable it, which frees the package for the patched build
Allow installs from the app you are using: Install permission is granted per app under Settings, Apps, Special access, Install unknown apps. Grant it to your file manager, or install directly from Manager when the build finishes
Check free storage: The installer needs room for the package and the unpacked app together, so a nearly full device fails partway rather than warning you first
Build a fresh APK: If the file still will not install, patch again. A build interrupted mid write, or one signed with a key Manager has since replaced, fails at the installer every time
Install straight from Manager: Finishing the install from Manager's own screen avoids file manager permission problems entirely, and tells you immediately whether the file or the permission was at fault

Why patched builds hit this more often

The signing key is local to Manager. Reinstalling Manager, clearing its storage, or moving to another device gives you a new key, and builds signed with it will not install over builds signed with the old one.
The package name is shared with official YouTube. On a non-root install there is no way around removing or disabling the official app first.
Multi user devices hide conflicts well. A copy in another profile is invisible from your app list but very visible to the installer.
Patched files are large. Storage failures show up here more than with small APKs, and they look identical to every other cause.

If none of this worked

Reboot after uninstalling and before installing. Some devices hold the package registration until the next restart, which makes a correct uninstall look like it did nothing.
If the install fails only from your file manager and works from Manager, the file was never the problem and there is nothing left to fix.
If Manager cannot finish a build at all, this is the wrong guide. Start with patch failed or Manager crashing.
On a managed device, install restrictions may be enforced by policy rather than by settings, and no local change will lift them.
If everything installs but the app then shows nothing, you have moved on to a different problem. The black screen guide picks up there.

Questions people ask

Can I keep official YouTube and patched YouTube together? Not with the same package name on a non-root install. Some patch bundles include a rename patch that makes coexistence possible.
Do I lose subscriptions by uninstalling YouTube? No. Those live on your Google account, not in the app.
Why did it install last month and not now? Almost always a new Manager keystore. The old patched app has to go before a build signed with the new key will install.
Does root avoid this? Root changes how the app is installed and can sidestep the package conflict, but it brings its own maintenance. The root and non-root comparison covers the trade.

The same error appears with old Vanced installs and with any other sideloaded APK, for the same underlying reasons. The general App Not Installed guide covers those cases, and the split APK explainer covers why a package delivered in pieces fails when you install one piece.

If you are setting up for the first time rather than repairing an install, following the sequence in the install guide avoids most of this, because it removes the official app before the patched one is built rather than after it fails.

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.