How to solve "App not installed as package conflicts with an existing package"

"App not installed as package conflicts with an existing package"

Does the error "App not installed as package conflicts with an existing package" appear when you try to install an updated APK? Have you tried rebooting, using ApkEditor Pro, and changing the app's permissions, but nothing seems to be working? Most of us get this error when trying to reinstall an app on Android that we previously deleted but are now trying to reintsall. 

I had this issue once when I uninstalled a Poweramp mod, then uninstalled it but also selected the keep app data option. Any time I tried to install the app from APKs, I got the Android app not installed as package conflicts with an existing package. I tried different solutions, like using Lucky Patcher to sign the application using different keys, but it never worked. Checking the Android data folder in my phone storage did not help because I could not locate the application's data file. Either it was hidden in the phone's root folder or something.

Lucky for you, you no longer have to go through this trial-and-error process because, thanks to my ordeal, I now have a list of common fixes for this issue. 

The Master Solution to App not installed as package conflicts with an existing package For Previously Uninstalled Apps is ADB.

Alright, here's what actually worked. First things first, if you're on a Samsung phone, remove the secure folder — trust me, it'll just get in the way otherwise. Next, grab a PC and connect your phone with a USB cable, then head into your settings and enable Developer Options, followed by USB Debugging.

Now you'll need ADB Shell. I already had it installed from Android Studio, but if you don't, just search for how to download it on YouTube — that's exactly what I did the first time around too.

Once you've got it, open up CMD (and make sure ADB is added to your PATH variables, or none of this will work), then type adb devices. Your device should pop up, and on your phone screen you'll probably get an "allow access" prompt — go ahead and accept it.

Before you go any further, you'll need your app's package name, which you can just look up on Google. In my case, the app was Cube ACR, and the package name turned out to be com.catalinagroup.callrecorder.

With that in hand, run this command: adb shell cmd package list packages -u. This pulls up every package on your phone, installed and uninstalled, so don't skip that -u flag, because that's the whole trick here. Once you've got the list, scroll through it (or copy it into Notepad and hit Ctrl+F) to check whether your app actually shows up.

If it does, you're basically there. Reinstall it using adb shell cmd package install-existing package-name, swapping out "package-name" for your actual package name, obviously :D. Then, to really clear things out for good, uninstall it properly with adb shell pm uninstall package-name — again, replacing "package-name" with yours.

And that's it. Go ahead and install your app like normal. Now you won't see that annoying "update" prompt anymore, just a regular "install," and this time it'll actually work. 100%.

Here is The Step By Step Procedure of Solving the "App not installed as Package Conflicts with existing package " error for Previously Unistalled apps.

Remove the secure folder (Samsung phones only)

Get a PC and connect the phone with a USB cable

Enable Developer Options

Enable USB Debugging

Download ADB Shell (I already had it from Android Studio, but you can find how to download it on YouTube — that's what I did)

Open CMD (make sure ADB is in your PATH variables) and type: adb devices

A device should show up, and on your phone there should be an "allow access" prompt — you must give it access.

Check your app's package name on Google. For example, my app was Cube ACR, and the package name was: com.catalinagroup.callrecorder

Run this command: adb shell cmd package list packages -u
This will show all installed packages and uninstalled ones too. Don't forget the -u because it includes uninstalled apps.

Check whether your app exists in the list or not. (You can copy the output into Notepad and search it using Ctrl+F if you want.)

Reinstall the package using this command:
adb shell cmd package install-existing package-name
Replace "package-name" with your actual package name :D

Uninstall it permanently from your device using this command:
adb shell pm uninstall package-name
Again, replace "package-name" with your actual package name :D

Congrats. Go ahead and install your app now. You won't see "update" again; it'll say "install," and it will work 100%.

Your Issue Might Be an App In Secure Folder For Samsung Devices

Quick heads up for anyone with a Samsung S6 Lite running into this same issue. Turns out your problem could actually be a Samsung S6 Lite app in Secure Folder giving a conflicting packages issue, and you totally forgot about it, lol. When you uninstalled the app from your home screen, it looked gone, but it was still sitting there in your Secure Folder the whole time. So go in, uninstall it from Secure Folder too, and your problem is solved. Some of us just forget Secure Folder even exists sometimes, you know? So before you go down the whole ADB rabbit hole like I did, just double-check your Secure Folder first. Might save you a ton of time, lol.