OPERATIONAL DEFECT DATABASE
...
...
In Android 7.x, 8.x, and 9.x, proxy settings that are configured via a PAC file may not function. Applications on the device may not send traffic through the proxy configured in the PAC file or honor other traffic rules in said file. This is a known issue identified by Google and resolved in Android 10 and onward.Google tracks this bug internally with identifier b/110762695.
In Android 7.x, 8.x, and 9.x, the two system components responsible for enforcing PAC proxy rules - PacProcessor and ProxyHandler - are not exempted from battery optimization features. If these packages are stopped due to battery optimization, applications on the device will not follow the PAC proxy settings.
Organizations that push: WiFi Profiles with Proxy Mode - Proxy Auto ConfigurationProxy Setting Profiles with Proxy Mode - Pac Script may see that applications do not honor the settings in the PAC file pushed to the device on Android 7.x, 8.x, and 9.x devices. The issue no longer occurs if you: Open the Settings appNavigate to Apps > Special App Access > Battery OptimizationSet PacProcessor and ProxyHandler to Don't optimize
Google has resolved this in Android 10 by exempting PacProcessor and ProxyHandler from battery optimization.
Through OEMConfig applications for OEMs like Samsung and Zebra allow organizations to exempt applications from battery optimization. You can use Workspace ONE UEM to deploy OEMConfig applications through the Managed Play Store.Note: OEMConfig is not supported for devices enrolled in Android (Legacy) mode.For more information, see OEMConfig on Android Enterprise Devices
Click on a version to see all relevant bugs
VMware Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
