Blank In-App Web Page After Sideloading an APK: Cleartext, Mixed Content, and WebView Providers, Diagnosed Step by Step
The APK installed, the home feed loads, images render - but the login page, checkout screen or promo page opens as a blank white screen, or spins forever with no error. This is rarely a connectivity problem. Since Android 9 cleartext HTTP is blocked by default, WebView drops mixed content, the WebView provider can be stale, and the sideloaded build's targetSdk and Network Security Config decide the outcome. A full mechanism table, runnable adb / aapt / curl commands, a nine-step diagnostic path, an error-code reference, version differences, an FAQ, and verified internal links.
There is a class of failure that makes people assume they downloaded a broken APK. The app installs, the icon is there, the home feed loads, local settings pages work, even avatars and images render. But tap "Sign in", "Membership", "Checkout", or "Campaign rules" and the screen turns pure white - or a spinner turns forever with no error and no crash.
So people uninstall and reinstall, clear data, switch download sources, hunt for a "fixed" build. Almost none of that touches the cause. If the feed loads, basic connectivity is fine. The blank page is loaded by a different component under a different policy: an embedded WebView, or a plain HTTP endpoint. Android has blocked cleartext traffic by default since 9.0 and mixed content since 5.0, using rules that have nothing to do with whether the phone is online.
The key distinction: an app "having network" and an embedded page "being able to render" are two separate pipelines. The first is decided by ConnectivityManager and the app's network permission. The second must additionally pass four gates: the WebView component, the Network Security Config cleartext policy, the mixed-content policy, and TLS certificate validation. If any gate refuses, the page is white - and Android usually gives you no human-readable error at all.
This article takes that pipeline apart, gives you a command you can run at every stage, and ends by explaining which cases are not fixable from the device.
1. Distinguish four kinds of "blank screen" before reinstalling anything
Spend one minute identifying which one you have. These four look identical but have completely different causes and fixes.
| Symptom | Most likely layer | How it differs | First check |
|---|---|---|---|
| Only embedded pages are blank; native feed/images fine | WebView / cleartext / mixed content | Other network features work | net::ERR_* in logcat |
| All network features in the app fail | Network permission / system network / DNS | Even native API calls time out | curl, ping, VPN, Private DNS |
| Blank, but pull-to-refresh responds and then shows "network error" | Non-2xx response / timeout | You get an explicit error | curl -vI status code |
| Works on another phone, blank only on this one | WebView provider / system clock / OEM skin | Strongly device-specific | WebView version, device date |
If *every* networked feature of the app is dead, this is not the problem this article covers - start with offline APK installation setup and APK download throttling diagnosis. This article focuses on the first case: only embedded pages go blank.
2. Mechanism table: what each of the four gates blocks
Understanding these gates explains why "clear cache" never helps.
| Gate | Applies when | Default behavior | Typical error | Owner |
|---|---|---|---|---|
| Cleartext policy | targetSdk >= 28 (Android 9+ compile target) | HTTP blocked, HTTPS only | net::ERR_CLEARTEXT_NOT_PERMITTED | Network Security Config |
| Native stack cleartext policy | targetSdk >= 28 | CLEARTEXT communication ... not permitted | java.net.UnknownServiceException | App network security config |
| Mixed-content policy | WebView, Android 5.0+ (API 21) | HTTP subresources inside an HTTPS page are dropped | Mixed Content: ... insecure connection | WebView setMixedContentMode |
| TLS certificate validation | All HTTPS requests | Untrusted / expired / hostname-mismatch chain is rejected | net::ERR_CERT_DATE_INVALID, SSLHandshakeException | System trust store + system clock |
| The WebView component itself | Every embedded page | A crashed or missing provider means a fully blank page | WebView crash logs, blank with no error | WebView provider (updatable component) |
Details that trip people up:
- The cleartext default depends on targetSdk, not the phone's Android version. An old APK compiled in 2018 (targetSdk 26) can still use HTTP on Android 15. A new APK compiled in 2025 (targetSdk 35) cannot use HTTP even on Android 9. This is why the same build behaves differently across OS versions, and it is the single most commonly reversed fact in this diagnosis. See what targetSdkVersion actually controls.
- Apps can relax the policy themselves. If the APK declares
android:networkSecurityConfigpointing at ares/xml/network_security_config.xmlwithcleartextTrafficPermitted="true"on a<domain-config>, HTTP to that domain is allowed. So "high targetSdk" does not automatically mean "blocked" - read the config. - Sideloaded builds are especially exposed. Old versions from third-party sites, ad-free mods, and regional builds pointing at domestic acceleration domains often still serve
http://. Reinstalling a hundred times will not conjure HTTPS into existence. That is a server-side problem the device cannot fix, and we say so explicitly below.
3. Mixed content: the layer most often missed
Suppose the main page is https://m.example.com/login (HTTPS, fine), but a script, a captcha image, or an analytics tag is hardcoded as http://cdn.example.com/verify.js. Since Android 5.0, WebView defaults to MIXED_CONTENT_NEVER_ALLOW and silently drops those HTTP subresources.
The result: the page skeleton renders, but the critical script never runs, buttons do nothing, or the whole page stays white because the render depended on that JS. And this kind of block is usually only a warning line in logcat, far less visible than ERR_CLEARTEXT_NOT_PERMITTED.
| Mode | Constant | Behavior | When seen |
|---|---|---|---|
| Never allow | MIXED_CONTENT_NEVER_ALLOW (default since API 21) | Drops all HTTP subresources | Most legitimate apps |
| Compatibility | MIXED_CONTENT_COMPATIBILITY_MODE | Allows some "safely degradable" resources, still blocks scripts/iframes | Legacy pages |
| Always allow | MIXED_CONTENT_ALWAYS_ALLOW | Everything passes (insecure) | Debug builds only |
This is an application-development decision. Users cannot change it in system settings. If a sideloaded APK cannot be rescued even in compatibility mode, the only realistic options are an HTTPS build of the same app or the official source.
4. Runnable command list
All commands need a computer with adb and a device with USB debugging (or wireless debugging) enabled. Replace com.example.app with the target package and api.example.com with the real domain. Every command is read-only, or only installs/starts something - nothing wipes data.
# 1) Confirm the package is installed; get targetSdk and the network security config resource
adb shell dumpsys package com.example.app | grep -iE 'versionName|targetSdk|networkSecurityConfig'
aapt dump badging app.apk | grep -iE 'package:|sdkVersion:|targetSdkVersion:'
# 2) Capture the key WebView / network-stack errors (run this in a second terminal while reproducing)
adb logcat -c
adb logcat -v brief | grep -iE 'ERR_CLEARTEXT|ERR_BLOCKED|ERR_CERT|ERR_NAME_NOT_RESOLVED|Mixed Content|CLEARTEXT|UnknownServiceException|chromium|WebView'
# 3) Which WebView provider and version is this device using?
adb shell dumpsys webviewupdate
adb shell cmd package list packages | grep -iE 'webview|trichrome'
adb shell dumpsys package com.google.android.webview | grep -i versionName
# 4) Verify the server from the PC side: is HTTP still in use, is HTTPS OK, is the cert valid?
curl -vI --max-time 10 http://api.example.com/
curl -vI --max-time 10 https://api.example.com/
curl -sI --max-time 10 https://example.com/.well-known/assetlinks.json
# 5) Check certificate validity window against the device clock
echo | openssl s_client -connect api.example.com:443 -servername api.example.com 2>/dev/null | openssl x509 -noout -dates -subject
adb shell date
adb shell settings get global auto_time
# 6) Rule out Private DNS / VPN hijacking resolution
adb shell settings get global private_dns_mode
adb shell settings get global private_dns_specifier
adb shell dumpsys connectivity | grep -iE 'NetworkAgentInfo|VPN' | head -20
# 7) Inspect the installed manifest for cleartext declarations
adb shell cmd package dump com.example.app | grep -iE 'usesCleartextTraffic|networkSecurityConfig'Three things to look for in the output:
- If
curl -vI http://...returns200whilehttps://...times out or reports a certificate error, the server is still on HTTP and the cleartext policy is the root cause. - The
notBefore/notAfterfromopenssl x509 -noout -datesmust line up withadb shell date. Flashed ROMs, battery swaps, and devices powered off for months often sit at a 2019 clock, making every current certificate "not yet valid" - which presents as *every* embedded page being blank. - If
private_dns_modeishostnameandprivate_dns_specifierpoints at a dead DoT server, name resolution fails wholesale, and native API calls fail too - go back to the first-row check.
For a full treatment of server-side responses and integrity, see APK integrity and hash/signature verification and download link 403/404 troubleshooting.
5. Nine-step diagnostic path
Follow this order; each step has a clear pass/fail criterion so you stop guessing.
Step 1 - Establish scope. Open a purely native screen (Settings, About) and then an embedded page. If a networked element on the native screen works, you are on the WebView pipeline. If every networked feature is dead, switch to network permissions and DNS.
Step 2 - Capture logcat keywords. Clear the log, reproduce the blank page once, use command group 2. ERR_CLEARTEXT_NOT_PERMITTED points straight at the cleartext policy; ERR_CERT_DATE_INVALID at clock/certificate; ERR_NAME_NOT_RESOLVED at DNS; no error at all but a white page means suspect the WebView provider or the front-end script itself.
Step 3 - Check targetSdk and cleartext declarations. aapt dump badging gives targetSdkVersion. If it is >= 28 and cmd package dump shows neither usesCleartextTraffic=true nor a networkSecurityConfig resource, HTTP is definitively blocked.
Step 4 - Verify the domain from a PC. Hit both HTTP and HTTPS with curl -vI. This is the single most important cut in the whole diagnosis: it separates "the phone's fault" from "the server's fault".
Step 5 - Check the certificate and system clock. An expired certificate or a wrong device clock blanks HTTPS pages wholesale. Turn on Settings -> System -> Date & time -> Set automatically, then reproduce.
Step 6 - Check mixed content. If the main domain is HTTPS but logcat shows Mixed Content warnings, the page mixes in HTTP subresources. That is legacy front-end debt; there is no user-side fix, only a different build.
Step 7 - Check the WebView provider. adb shell dumpsys webviewupdate shows the active provider and whether an update is available. Developer options -> WebView implementation lets you switch; update Android System WebView from an app store, then restart the app. If the provider package was stripped out (common on debloated custom ROMs), reinstall the matching component.
Step 8 - Exclude OEM skins and VPNs. Some vendor ROMs proxy WebView requests through their own "web acceleration / safe browsing" service; a global VPN, ad blocker, or Private DNS can rewrite resolution. Disable them temporarily and reproduce.
Step 9 - Cross-validate. Install the same APK on a second device or emulator. If only one device blanks, it is device-side (provider / clock / ROM). If both blank, it is the APK or its server - stop fiddling with the phone.
If step 4 confirmed the server only offers HTTP, also see APK update failed troubleshooting - legacy update-check endpoints are frequently stuck on cleartext in the same codebases.
6. Error-code reference
| Keyword / code | Meaning | Layer | User-fixable? |
|---|---|---|---|
net::ERR_CLEARTEXT_NOT_PERMITTED | Plain HTTP rejected by network security policy | Cleartext | No (app/server must use HTTPS) |
CLEARTEXT communication to ... not permitted | OkHttp-style stack rejecting cleartext | Cleartext | No |
Mixed Content: ... insecure | HTTP subresource dropped inside HTTPS page | WebView | No |
net::ERR_CERT_DATE_INVALID | Cert not yet valid / expired | Cert or clock | Yes (fix clock); no if expired |
net::ERR_CERT_AUTHORITY_INVALID | Chain not trusted (self-signed / user CA) | Trust store | Partly (use a real cert) |
net::ERR_NAME_NOT_RESOLVED | DNS resolution failed | DNS / Private DNS / VPN | Yes |
net::ERR_CONNECTION_TIMED_OUT | Cannot reach server | Network / firewall | Depends |
net::ERR_BLOCKED_BY_RESPONSE | Blocked by CSP / response headers | Front-end policy | No |
| Pure white, no error | Provider failure or JS never executed | WebView / front-end | Sometimes (update provider) |
7. Version differences
| Android version | Behavior relevant here |
|---|---|
| 5.0 (API 21) | WebView becomes a separately updatable component; mixed content defaults to NEVER_ALLOW |
| 7.0 (API 24) | Network Security Config introduced; apps no longer trust user-installed CAs by default |
| 9.0 (API 28) | targetSdk >= 28 blocks cleartext HTTP by default; usesCleartextTraffic defaults to false |
| 10 (API 29) | TLS 1.3 on by default; RoleManager introduced (affects default browser and friends) |
| 12 (API 31) | Exported components must be declared explicitly, affecting some in-app navigation |
| 14-16 | Tighter install and background rules for low-targetSdk apps |
For why targetSdk decides the cleartext default, read targetSdkVersion explained. If your symptom is "tapping a link opens the browser" rather than "an embedded page is blank", that is a different pipeline - see App Links verification troubleshooting.
8. FAQ
Q1: Will turning off Private DNS / updating WebView fix a cleartext block?
No. The cleartext policy is decided by the APK's targetSdk and networkSecurityConfig, not by DNS or the WebView version. Updating WebView only addresses provider crashes and compatibility.
Q2: Why can app A open an HTTP page on the same phone while app B goes blank?
The policy is evaluated per app (per APK's targetSdk and its own config file), not per device. If A is an old build or explicitly opted into cleartext, it works.
Q3: Can I force-allow cleartext after rooting?
Technically yes, but do not: it strips protection from HTTP traffic for *every* app on the device. Trading whole-device security for one page is a bad deal. Use the HTTPS build of the app instead.
Q4: The same URL opens fine in Chrome, but blanks inside the app. Why?
Chrome is a separate app with its own network security config and rendering engine. The in-app WebView uses the host app's config. Different behavior is expected - and it proves the network itself is fine.
Q5: Is `net::ERR_CLEARTEXT_NOT_PERMITTED` always the server's fault?
Usually: the server still serves HTTP. Occasionally the app forgot to allow cleartext for a LAN/local domain (IoT setup pages often require HTTP), which is a compatibility issue for the app developer.
Q6: Why does a wrong system clock blank every embedded page at once?
TLS validation compares notBefore / notAfter. If the device clock is years behind, every currently valid certificate looks "not yet valid" and the handshake fails. Turning on automatic time usually fixes it immediately.
Q7: Do I need to reboot after updating Android System WebView?
At minimum force-stop the target app and reopen it; some ROMs need a reboot before the provider switch takes effect. Try adb shell am force-stop com.example.app first.
Q8: Is a blank WebView in a sideloaded build related to a modified signature?
Usually not directly. But re-signing changes the signing certificate fingerprint, which can affect App Links verification and endpoints that check the signature. If links also stop opening the app, check how to verify APK signature before installing too.
Q9: Does clearing app data / cache help?
For cleartext policy, mixed content, and certificate validation: no - all three are re-evaluated on every request. It is only worth trying if you suspect corrupted local WebView data.
Q10: Should I switch APK versions or wait for the server to be fixed?
Use step 4: if HTTP works and HTTPS does not, it is the server. If HTTPS is fine but the app still blanks, try a newer official build. If two devices behave identically and logcat points to mixed content, it is that build's legacy front-end. The same reasoning is in safe APK download & install guide.
9. Further reading
- offline APK installation setup: first rule out "the whole app is offline"
- APK download throttling diagnosis: DNS, VPN, proxy layers
- Links still open in the browser after sideloading: link ownership and domain verification
- targetSdkVersion explained: why it decides the cleartext default
- App crashes on launch: logcat guide: distinguish a crash from a blank page
- How to verify APK integrity and checksum: confirm the file is not damaged
- Download link 403/404 troubleshooting: server response codes
- APK update failed troubleshooting: legacy endpoints stuck on cleartext
- install unknown apps settings by brand: sideload prerequisites
- safe APK download & install guide: the full flow from download to verification
Bottom line
A blank in-app page is not "no network" - it is one of four gates (cleartext, mixed content, certificate/clock, WebView provider) refusing to pass. Two actions do almost all the work: capture logcat keywords once, and hit HTTP and HTTPS separately with `curl -vI` from a PC. The first tells you which layer blocks; the second tells you whether to fix the app or the server. Once you confirm the server still serves HTTP, stop reinstalling on the phone - that part is not yours to fix.