First: confirm the file
Before touching settings, check the download itself. Open your file manager, find the XAPK, and confirm it reads 213.9 MB. Nine out of ten install failures trace back to a short file, and every fix below assumes the file is complete. If it is short, grab a fresh 9 Kings download hub from the download page on a stable connection and do not skip this check.
Fix 1: App not installed
This is the classic signature conflict. Android refuses to install over an app signed with a different key, which happens if any older, modified, or differently-sourced copy of the game is on the phone. Uninstall every copy of the game completely, restart the phone, then install the XAPK fresh. Do not install over the top in this situation; the conflict must be cleared first.
Fix 2: Parse error
A parse error means the bundle is damaged or incomplete. Re-download the game file and watch the size land on the full 214 MB. If your connection drops mid-download, the browser sometimes reports success on a partial file, so verify in the file manager rather than trusting the notification.
Fix 3: Installer cannot see the file
Move the XAPK into the main Downloads folder, not a subfolder, then open the installer app and rescan. Scoped storage on modern Android hides deep paths from some installer apps, and the main Downloads folder is the one location every installer can read.
Fix 4: Play Protect blocks the install
Play Protect warns on any app installed outside the store. Tap More details, then Install anyway. This warning is about the install source, not a malware finding; the file on this site is scanned before publication, as the safety breakdown documents.
Fix 5: Installs but crashes on launch
Clear the app cache (Settings, Apps, 9 Kings, Storage, Clear cache; do not clear data), then relaunch. If crashes persist, free at least 1 GB of storage and exempt the game from aggressive battery optimization, which can kill Unity games during asset loading on some phones.
When nothing works
Note your phone model, Android version, and the exact error text, then try the install guide from step one with a fresh download. If the failure repeats at the same step, that pattern is exactly what support needs to diagnose it.
