App not installed as package conflicts with an existing package

What Android is telling you

Every app is signed with the developer's private key, and Android will only update an installed app with a package signed by the same key. When the keys differ, Android 11 and later say App not installed as package conflicts with an existing package; older versions just say App not installed. The installed app and the file both carry the same package name, so the system treats the file as an impostor.

Why the keys differ

• The installed copy came from Google Play and the file is a debug build, a beta from a different channel, or a re-signed "mod". Play-signed and developer-signed builds normally match; modified packages never do.
• The developer rotated their signing key. Android supports key rotation only when the new package includes the rotation proof, which official builds do.
• Two apps from different developers reuse a package name. Rare, but it happens with forks of open-source apps.
• The installed copy is the mod and the file is the genuine build. Common when trying to return to the official version.

The fixes

1. Uninstall the existing app, then install the file. This is the only way to switch between differently signed builds. Local data is lost; export what you need first.
2. Keep the installed app and find a build signed with the same key. For an app installed from Play, that means the Play build itself or the developer's own APK, which mirrors carry unchanged.

There is no third option on an unrooted device. Apps that promise to "fix" the conflict re-sign the file, which only produces a different conflict later.

Checking before you install

Package inspection apps such as App Manager (F-Droid) show the signing certificate fingerprint of an APK file and of installed apps. If the fingerprints match, the install will succeed; if not, the install will be refused. The APK safety guide covers the tools.

Work profile and multiple users

Android allows the same package name in a work profile or a second user with a different signature. If you must run two differently signed builds, install one in a work profile (with an app like Shelter) instead of fighting the conflict in the main profile.