App Won’t Install: Android APK Analysis - Finding the Root Cause
Cross-build comparison · APK Analyzer · ABI diagnostics
The Issue
A new Android POS release was installed successfully on newer hardware but failing on specific merchant devices with an “App not installed” error.
Because the application worked on newer devices, the issue initially appeared to be hardware-specific.
Troubleshooting
The issue persisted into a newer build, and the development team had not been able to identify the cause. Rather than treating the hardware as obsolete, I investigated it independently by comparing the problematic release against a previous working build using Android Studio APK Analyzer.
I inspected the APK contents and compared the native libraries under the lib/ directory.
The working build contained both:
- armeabi-v7a
- arm64-v8a
The problematic build contained only:
- arm64-v8a
I correlated this with the affected POS hardware, which used a 32-bit ARM architecture.
The evidence pointed to a packaging and architecture-compatibility problem rather than a general application or hardware failure.
Resolution
I provided the build-to-build comparison and technical evidence to engineering, identifying the missing armeabi-v7a libraries as the root cause.
The build configuration was corrected to support both required architectures, and the resulting build was verified on the affected POS hardware.
Impact
The affected merchants were able to install the application without replacing their existing POS hardware.
The investigation also turned a reactive installation issue into a standard Android architecture compatibility check before release.