--- title: "Google introduces a 24-hour 'cooling-off' period for installing APKs from unverified developers on Android" description: "Google is implementing a 24-hour waiting period in Android for installing APKs from unverified developers. The mechanism works through Android Developer Verifier and is tied to the mandatory identification of app authors." date: 2026-08-19T23:51:02.000Z lang: en url: https://xab.info/en/posts/google-introduces-24-hour-cooling-off-period-for-installing-apks-from-unverified-developers-on-android tags: [android, google, apk, side-loading, developer-verifier] publisher: "XAB.info" --- # Google introduces a 24-hour 'cooling-off' period for installing APKs from unverified developers on Android ![Transparent glass Android figurine with green liquid and a circuit-board pattern inside — a symbol of Google's new security rules for installing APK files](https://xab.info/media/2026/08/20/google-android-24-chasa-ozhidaniya-apk/google-android-24-chasa-ozhidaniya-apk-1.webp) ## 🎯 Key Points - Installing APKs from unverified developers now requires a 24-hour waiting period after the first permission. - The mode is activated through developer options; access can be granted for 7 days or indefinitely. - Installation via ADB is not restricted; developer options can be turned off while keeping the choice. - The system is handled by Android Developer Verifier, announced in March; the update is being rolled out gradually. - From September 30, the new developer identification rules apply in Brazil, Indonesia, Singapore, and Thailand, and in 2027 — in other markets. Google has begun the phased rollout of a new 'extended' mode for installing apps from third-party sources in Android. The key innovation concerns apps from developers that have not passed official verification: after a user allows the installation of such software, they must observe a mandatory 24-hour waiting period before the installation becomes possible. The mechanism is already being rolled out to devices gradually, and its launch is tied to a broader initiative on mandatory identification of Android app developers. ### How the 24-hour waiting period works To allow the installation of apps from unverified developers, the user must now open the developer options and enable the 'Allow apps from unverified developers' item. After that, Android displays several warnings about possible risks and offers to start a one-time 24-hour waiting period. Once it is over, the user will have to return to the same settings section and reconfirm the permission. Access to installing unverified apps can be enabled temporarily — for seven days — or left active for an indefinite period. ### Exceptions and working with ADB The new restrictions do not apply to installing apps via ADB — this mechanism continues to work as before. In addition, after activating the new mode, the developer options can be turned off again without canceling the choice made earlier. Thus, Google does not ban sideloading entirely, but deliberately complicates the procedure specifically for those APKs whose authors have not passed verification. ### The role of Android Developer Verifier and the timeline The new system is handled by the Android Developer Verifier app, which Google announced in March of this year. At the time of publication of this article, the corresponding update is being rolled out to devices gradually, which explains why some users already see the new scenario while others do not yet. The company emphasizes that the introduced warnings and delay are intended to protect users from malware and social engineering tactics. ### Connection to mandatory developer identification Changes to APK installation are directly linked to the introduction of mandatory identification of Android app developers. From September 30, Google will begin applying the new rules in Brazil, Indonesia, Singapore, and Thailand, and in 2027 it plans to extend the system to other markets. This means that in the coming months and years the barrier to entry for authors of apps from third-party sources will be systematically raised, and 'gray' APKs without a verified developer will fall under enhanced control. ### Assessment of the impact on the ecosystem For a typical user who installs apps from Google Play, the changes are practically unnoticeable. However, for an audience accustomed to sideloading modified versions of software, custom ROM apps, and unregistered utilities, the procedure becomes noticeably more burdensome: now a multi-day barrier is inserted between the intention to install a file and the actual installation. Experts note that the combination of the 24-hour wait, multiple warnings, and mandatory developer identification forms one of the strictest anti-sideloading regimes in Android's history, while still not blocking legitimate debugging scenarios via ADB. ## 🔍 Fact-Check Verification - [Google tightens the screws: installing some APKs on Android now requires a 24-hour wait](https://www.ixbt.com/news/2026/08/19/429138-google-zakrucivaet-gaiki-ustanovka-nekotoryx-apk-na-android-teper-trebuet-24-casov-ozidaniia.html) - Подтверждает 24-часовое ожидание, работу через параметры разработчика и исключение ADB. - [Google has made installing APK files on Android more complicated](https://hi-tech.mail.ru/news/153626-google-uslozhnila-ustanovku-apk-fajlov-na-android/) - Совпадает по механизму усложнения установки APK от непроверенных разработчиков. - [Google introduced a 'cooling-off' period for installing APK files on Android](https://www.rosbalt.ru/news/2026-08-19/google-vvel-period-ohlazhdeniya-dlya-ustanovki-apk-faylov-na-android-5663352) - Использует термин «период охлаждения», подтверждает 24-часовую задержку. - [Google introduced a 'cooling-off' period when installing APK files on Android](https://www.gazeta.ru/tech/news/2026/08/20/29140471.shtml) - Подтверждает введение периода ожидания и связь с идентификацией разработчиков. ## ❓ FAQ ### Q: How long do you have to wait after allowing the installation of an APK from an unverified developer? **A:** 24 hours. After the first permission, Android starts a one-time waiting period, at the end of which you need to return to the settings and reconfirm the permission. ### Q: Is it possible to not install APKs from third-party sources at all? **A:** Yes, Google does not ban sideloading entirely. The restrictions apply only to apps from developers that have not passed official verification. ### Q: Does installation via ADB work the same way as before? **A:** Yes, the restrictions do not apply to installation via ADB — this mechanism continues to work as before. ### Q: For how long can access to unverified apps be enabled? **A:** Either temporarily for seven days, or left active for an indefinite period. ### Q: When will the new developer identification rules take effect? **A:** From September 30 in Brazil, Indonesia, Singapore, and Thailand, and in 2027 Google plans to extend the system to other markets.