Although in general it’s basically pretty rare that you’ll ever encounter an error in Xposed at all.
Nonetheless, once you do, this is most likely the error you’ll get:
What’s Seems To Be The Problem?
As you can see, the error message is quite skimpy and doesn’t reveal much about the essence or the cause of the problem. Instead, all it tells us is the outcome of it.
It gets even more puzzling once you learn that the issue isn’t recorded in Xposed logs per se, nor Android installer has a specific log of its own.
So how do we get to the bottom of this?
The answer: use adb.
For those who aren’t familiar with it, ADB (Android Debugging Bridge) is the official Android tool for developers to debug problems on Android platform, and it’s part of the Android SDK (Software Development Kit), you can get it from here.
Obviously, it’d be a bit of exaggeration to expect anyone to use these tools, as they can be quite difficult to install or manipulate in case you’re not a tech savvy person.
However, the curious among you may want to give it a try (if you got to a point where you’re using Xposed then installing ADB might be just another step forward towards user empowerment).
Once you have ADB installed, open up a command line tool such as CMD / PowerShell / Terminal and issue the following command to find the cause of the problem:
adb shell logcat | grep <NAME-OF-THE-APP>
The command should filter the log output and retrieve relevant results.
You won’t see it in the above screenshot (since it was taken after a reboot), however the actual error should and will be shown once issuing the above command, making it easier on you to analyze the problem.
In my case, the issue I got was about a non matching signature between current installed app and the updated one.
Now that we learned how to locate the problem, we can move on to the fixing part.
How To Fix?
Note: since ‘App not installed’ is a rather generic error message, the following may not work in all cases. Nevertheless, if yours is one of the common cases then this is probably what you need to do.
Simply go inside Xposed Installer, go into Modules and uninstall the app which is giving you the issue.
Now go back and access Download section, reinstall the the app’s latest version directly.
That’s it! once you’ve uninstalled the app, its former signature was uninstalled along with it, therefore removing the cause of the update issue.