What you will learn
Fix Android install failures caused by missing splits, signature conflicts, SDK mismatch, corrupt files or OBB data.
Start with the exact failure
Android often shows the same friendly message for different technical problems. Before retrying, inspect the package structure and write down whether you are installing one APK, split APKs or an XAPK with OBB data.
| Symptom | Likely reason | Best check |
|---|---|---|
| App not installed | Signature conflict or missing split. | Check signing files and package structure. |
| Missing split error | Only base.apk was installed. | Look for split_config APK files. |
| Parse error | Corrupt file or unsupported device. | Check archive integrity and min SDK. |
| Game opens without data | OBB files are absent or misplaced. | Verify Android/obb/package.name/. |
Missing split APK files
If a package includes base.apk plus split_config files, install all splits together. Missing one split can trigger INSTALL_FAILED_MISSING_SPLIT.
Use XAPK to APK or APKS to APK to list the package parts before another install attempt.
Signature conflict
Android blocks updates when the installed app and new APK use different signing certificates. This often happens when mixing store builds, test builds and modified builds.
If you remove the installed app to bypass a signature conflict, you may lose local app data. Back up important data first when the app supports it.
| Scenario | Why Android blocks it | Safer choice |
|---|---|---|
| Store build over modified APK | The signing identity is different. | Use the same source as the installed app. |
| Debug build over release build | Debug and release certificates usually do not match. | Uninstall only if data loss is acceptable. |
| Older version over newer version | Downgrades may be blocked or require special handling. | Compare version code first. |
| Same package name from unknown source | Package name alone does not prove trust. | Check hashes, permissions and signing signals. |
Wrong Android version
Check the minimum SDK in the manifest. Older devices may reject packages that target newer platform requirements.
Wrong CPU architecture
Architecture splits such as arm64-v8a, armeabi-v7a or x86 must match the device.
Corrupt download
If extraction fails or file hashes do not match, download the package again from the trusted original source.
Corrupt archives often show up as missing files, failed extraction, impossible file sizes or hashes that do not match a published value.
Missing OBB files
Some games install but fail to launch because expansion files are missing. Use the OBB Extractor to find data files and the package folder.
Diagnosis workflow
| File you have | Use first | What to confirm |
|---|---|---|
| APK | APK Analyzer | Package name, version, SDK, permissions and hashes. |
| XAPK | XAPK to APK | Whether it contains one APK, split APKs, OBB files or metadata. |
| APKS | APKS to APK | Base APK and every required split APK. |
| APKM | APKM to APK | Base APK, config splits and install guidance. |
| OBB | OBB Extractor | Package folder and file placement. |
- Check whether the file is APK, APKS or XAPK.
- Inspect package name, SDK version and signing signals in APK Analyzer.
- Look for split APK files and install them together.
- Look for OBB files and place them in the matching package folder.
- Retry only after you know which install path the package needs.
Inspect before retrying
Open the APK or XAPK in APK Analyzer to review package name, SDK version, permissions, signing signals and file structure before another install attempt.
Clean retry checklist
- Remove any conflicting installed version only if you understand the data-loss risk.
- Re-download the package from the trusted original source.
- Install all required split APK files together.
- Place OBB files after confirming the package name.
- Recheck permissions and signing signals before opening the app.
FAQ
Why does Android only say "App not installed"? Android often hides the technical reason in the normal installer UI. Inspecting the package can reveal likely causes such as splits, SDK mismatch or signatures.
Can I fix a signature mismatch? You cannot safely make two differently signed apps update each other. Install the matching signed build or remove the conflicting app if you accept the data-loss risk.
Why does a game install but then fail? The APK may be installed correctly while required OBB expansion files are missing or stored in the wrong folder.
Responsible use note
Use these tools only with apps you own, develop, or have permission to analyze. Avoid modifying, redistributing, or installing packages from sources you do not trust.