Package A (Old / Base Version)
Click or drop first .apk / .xapk file
Package B (New / Update Version)
Click or drop second .apk / .xapk file
Why Comparing APK Versions Prevents Failed Updates
When you install a newer version of an Android app over an existing installation, Android's PackageManager enforces two strict rules: the new package's versionCode must be greater than or equal to the installed build, and its signing certificate inside META-INF/ (or the APK Signing Block v2/v3) must be byte-for-byte identical.
- Signing Certificate Digest Match: Computes the SHA-256 fingerprint of the .RSA / .DSA / .EC signature block in both packages so you know immediately if an in-place update will succeed without uninstalling.
- Native ABI & DEX Diffing: Highlights whether an update stripped 32-bit armeabi-v7a libraries or added new classes*.dex files.
- CRC32 Entry Delta: Lists exact files added or removed between builds.
How Android Evaluates Package Updates (INSTALL_FAILED_UPDATE_INCOMPATIBLE)
One of the most frequent errors users encounter when updating a sideloaded app is "App not installed as package conflicts with an existing package" (known in ADB logs as INSTALL_FAILED_UPDATE_INCOMPATIBLE). This happens whenever the installed app came from the Google Play Store (signed with the developer's private release key) and the update was converted from a split .xapk archive (which had to be re-signed with a converter signing key after merging splits).
However, if both your old version and your new version were converted using xapktoapk.com, our deterministic signing pipeline uses the same consistent signing certificate across conversions—meaning you can install the new converted APK directly on top of the old converted APK without uninstalling or losing your in-app progress! Use the comparison tool above to confirm that both files share the same certificate digest before you install.