Troubleshooting Blank FusionAuth Login Pages in Android WebViews on Specific Devices

wesley

We received a report from a customer who is unable to log in to our mobile application. The app uses a standard embedded webview that loads the FusionAuth-hosted login page, a flow that has been in place and working reliably for all users until now.

In this specific case, the webview appears to be completely blank and does not load the login page at all.

Additional context:

Device: Xiaomi Redmi Note 13
OS: Android

Clearing app data/cache did not resolve the issue

Logging in as the same user works correctly on other devices

Have you encountered a similar issue before, or do you have any guidance on what could cause this behavior?

wesley

This is indeed unusual, especially since the issue appears to affect only a single user and device, which makes a FusionAuth configuration issue unlikely.

A few things to check and try:

Open in External Browser
Ask the user to tap the three-dot menu (if available) in the webview and choose “Open in Chrome” or their default browser.
If the page loads correctly there, the issue is likely related to the embedded webview rather than FusionAuth itself.

WebView / Browser-Specific Issues

Some Android devices (including certain Xiaomi models) ship with custom WebView implementations or aggressive privacy/security settings that can interfere with embedded web content.

Ensure the device has the latest Android System WebView and browser updates installed.

Domain / CNAME Edge Cases

There have been rare cases where mobile browsers or webviews behave unexpectedly if the domain includes characters such as underscores (_) or dashes (-) in certain positions.

While this typically results in explicit errors (like “Address not found”), it’s still worth reviewing your domain and CNAME setup—especially since you’re self-hosting.

Given that the login works for the same user on other devices, this is most likely a device- or WebView-specific issue rather than a problem with FusionAuth itself. If opening the login page in a full browser works, that should help narrow the root cause to the embedded webview implementation on that device.