Tx, more info helps!
I should have mentioned that I can currently only reproduce this on non-httpd builds.
Am I right in assuming that you’re seeing a return of the behaviour on httpd builds?
That said, given that I’m now able to attach a native debugger I may have found one explanation of the ORIGINAL blank screen before we started working around with the httpd module.
To cut a long story short it looks like Google are fiddling with their security model and content type detection for content loaded via a custom ContentProvider.
In the past we could leave it up to the WebView to detect content but the latest version on my phone now definitely requires that I explicitly specify a mime type before it’s prepared to load it.
I don’t know if this will fix the issue but I’ll be pushing a new build of
v2.7 with this change shortly and maybe we get a few more data points?