Fixing Cleartext Traffic Errors in Android Pie 9.0 and higher
It’s been a couple of months now since Android Pie 9.0 was released, on August 2018. And, per the official distribution dashboard, over 10% of devices run this version at this time. Anyways, it is always a good idea to have your apps target the latest release.
When I tried upgrading my apps to Android Pie, I came across the error below due to a behavior change aiming at improving security defaults:
Before Android Pie, apps could communicate with remote servers over unencrypted protocols, such as HTTP, which could easily be eavesdropped or liable to a wide range of attacks.
Android Pie 9.0 and higher enforce the use of secure traffic in apps by default, unless developers really really do need to use Cleartext (which, again, is strongly discouraged). In such cases, the error above can be fixed using any of the approaches depicted below:
- Obviously, the best option is to only communicate using a secure protocol, such as HTTPS. This implies configuring your remote servers to use such secure connections, if possible. A lot of solutions exist out there to that end, such as Let’s Encrypt, Caddy or CertMagic, just to name a few.
- Altering the default behavior by authorizing Cleartext traffic throughout the entire app, at the risk of exposing your app to potential data integrity issues.
To do so, you need to update your AndroidManifest.xml, by including the “usesCleartextTraffic” attribute:
- A better alternative is to leverage an explicit network security configuration file, which allows you to selectively define the domains against which the app is authorized to communicate over Cleartext traffic, on a case by case basis.
To do so, you need to first create a new XML file under src/main/res/xml (say network_security_config.xml), with the “cleartextTrafficPermitted” attribute set to true for the domain of interest. For example:
Then update your AndroidManifest.xml to point to that file, using the “networkSecurityConfig” attribute:
Note that, as far as I can tell, it is not yet possible at this time to programmatically configure domains in such network security configuration file.