Android WebView 153/154: Black Screens in Enterprise Apps
What's happening
Since early September 2026, Android devices are showing black or unreadable areas in enterprise apps — black list backgrounds, black buttons, darkened dialog controls, or black overlays covering parts of a screen. The app is working and the data is there; it simply renders incorrectly.
The cause is an update to Android System WebView, the Android operating system component that renders web content inside apps. Google changed how WebView draws graphics starting with version 153. The problem is present in WebView 153 and 154 and has been reported worldwide across many Android apps, not just one vendor's.
It is not a “dark mode” issue, and it is not caused by the app, the device configuration, or the deployment. Nothing in the affected applications changed.
Why it happens, in plain terms
On Android, the component that renders an app’s web-based interface is not part of the app, and not part of the operating system version you installed. It is Google’s WebView, delivered separately and updated automatically through Google Play and Google’s system updates.
This means WebView can change under a fleet with no change to the app, the OS build, or anything the IT team deployed — and IT typically cannot see it happen. WebView 153 introduced a change to the hardware-accelerated rendering path. Apps that draw their interface using hardware rendering hit the defect and render black.
It also explains why several unrelated companies saw the same failure on the same days, on different hardware: the only thing they shared was the WebView update.
How to check whether your devices are affected
Read the WebView version on a device:
Settings > Apps > Android System WebView > version
Or, inside a Dynamics Mobile app: Settings > Sys Info
WebView version | Status |
|---|---|
153.x and 154.x | Affected — black or unreadable rendering possible |
Earlier versions (e.g. 149.x) | Not affected |
A reboot clears the symptom temporarily, which is the quickest way to confirm it is this issue rather than something else.
What to do right now
Restart the device. This clears the symptom for a period and gets the user working again. It is a stopgap, not a fix.
Roll back on one test device to confirm. Settings > Apps > Android System WebView > Uninstall Updates, then restart. Note: this reverts WebView to the version built into the device firmware — if the firmware already includes 153 or newer, the rollback will not help.
Prevent WebView from updating again on those devices through your MDM. Be aware this is only partial: Google’s system updates for WebView are not governed by MDM policies, so WebView can come back after a reboot.
Ask your hardware vendor whether their tools can roll back and hold the WebView version.
Security note: holding WebView below version 153 means the devices do not receive the security fixes included in 153 and later. Treat the rollback as a temporary measure with a defined end date.
What to expect next
Google has corrected the underlying defect in its browser code; the corrected Android WebView build is being confirmed. The corrected version reaches devices on Google’s schedule, and devices receive it with a delay. Until then, the reliable fix is on the application side, because the app can be changed while the WebView version cannot be pinned.
Dynamics Mobile is releasing an updated Android app that renders content differently, so it is no longer affected by this WebView change. The change is controlled by a setting, so it can be enabled for affected fleets and switched off once a corrected WebView version is confirmed in the field.
Two habits pay off for any Android fleet: know which WebView version your devices are running, and keep a way to test an app build on one device before fleet-wide rollout.