Why Chrome asks twice before an APK installs.
One prompt protects the download. The next protects the installation source.
The browser and Android have different jobs
Chrome decides whether to download the file. Android decides whether that source is allowed to start package installation. Seeing both prompts is normal for an APK obtained outside an app store.
Neither prompt should be treated as a security certificate. They are checkpoints where the user can review the route and stop if something looks wrong.
Keep the source, action and evidence in the same chain.
The permission belongs to the source app
‘Install unknown apps’ is granted to Chrome, a file manager or another source app—not to every APK at once. Approve only the source you are using and turn it off after the installation completes.
Follow the full installation guideRead the device message before changing a setting.
Why the downloaded file may not open
The file can be incomplete, storage can be low, a device policy can block it or Android can detect a conflict with an installed package. Read the exact message before downloading the same file again.
Keep the source, action and evidence in the same chain.
Common questions.
Short answers first. The linked guides carry the full context.
Is the unknown-app prompt an error?
No. It is Android asking whether that particular source may start an APK installation.
Should I leave the permission enabled?
No. Turn it off after installation so the next APK requires another explicit review.
Does Chrome install the APK itself?
Chrome downloads and opens the file; Android’s package installer performs the installation.
Ready for the current COME download?
Download COME APK