Are there any special considerations for Google Pixel, Samsung Secure Folder, work profiles, or managed devices?

Yes, there are a few things to keep in mind in these scenarios—but not because our app fundamentally works differently on them. Rather, the device or profile may enforce additional security rules. On Google Pixel devices, the same Google protection mechanisms documented by Google may apply: Play Protect checks apps during installation, and Advanced Protection blocks new installations from unknown sources. As long as Advanced Protection is active, Google says that new installations are essentially allowed only from Google Play, via adb, or from preinstalled app stores. If you have just disabled Advanced Protection or removed the affected Google Account, Google also notes that it may take up to 24 hours for these automatic protection mechanisms to stop completely.

On Samsung devices, Secure Folder also plays an important role. If an older version of our app is already installed there, Android may report a package conflict even though you do not see a second installation on the normal home screen. In such cases, Secure Folder also needs to be checked and cleaned up.

On devices with work profiles and on managed devices, administrators can block installations from unknown sources. This may affect only the work profile or even the entire device. If the switch for unknown apps is grayed out, or if an APK keeps being blocked even though the file itself is correct, a device or company policy is therefore a very likely cause.