[colinstone]

Android Webview updated in the last couple of days and I now get this message when attempting to write an email :

Web page not available The web page at data:text/html; charset=utf-8;charset=utf-8;base64, could not be loaded because: net::ERR_INVALID_RESPONSE

Uninstalled the latest update and BB Hub now works correctly drafting emails.

Wondered if anyone else had experienced this??

[conite]

Android Webview updated in the last couple of days and I now get this message when attempting to write an email :

Web page not available The web page at data:text/html; charset=utf-8;charset=utf-8;base64, could not be loaded because: net::ERR_INVALID_RESPONSE

Uninstalled the latest update and BB Hub now works correctly drafting emails.

Wondered if anyone else had experienced this??

Go into developer options and select Chrome as your webview implementation.

[colinstone]

But don't use Chrome.

[conite]

But don't use Chrome.

Install it anyway. You don't need to use it. The webview app is legacy.

[LiamQ]

@colinstone, which Android OS version do you have? Which version of Android System WebView and Chrome?

[nevilleadaniels]

Install it anyway. You don't need to use it. The webview app is legacy.

Chrome from Google is not safe. Or has it now been made safe?

[conite]

Chrome from Google is not safe. Or has it now been made safe?

Not safe? In what regard?

[nevilleadaniels]

Not safe? In what regard?

Sucking up lots of user data and forwarding it to Google

[conite]

Sucking up lots of user data and forwarding it to Google

Don't use it if you don't want do. But install it so Android can use it for Webview.

[joeldf]

Can't say I've had that issue with the latest official Hub (not beta) using Webview. I disabled Chrome (can't delete it from the Galaxy S9). Webview is set in dev options and it did update back on the 14th.

[nevilleadaniels]

Can't say I've had that issue with the latest official Hub (not beta) using Webview. I disabled Chrome (can't delete it from the Galaxy S9). Webview is set in dev options and it did update back on the 14th.

No problems on my Blackberry key2 using webview without Google Chrome and no webview is not Legacy

[conite]

No problems on my Blackberry key2 using webview without Google Chrome and no webview is not Legacy

Yes it is legacy.

The code is much more compact and efficient running from chrome.

"For Chrome to handle WebView rendering, you'll need to be on v51 or higher with Android 7.0. The default behavior in this instance will be for the Chrome APK on your device to render Android System WebViews. Google says this is more memory-efficient than using the current WebView. The standalone WebView APK will no longer be updated via the Play Store as long as the Chrome rendering remains enabled on your device."

https://www.androidpolice.com/2016/0...w-android-7-0/

[nevilleadaniels]

Yes it is legacy.

The code is much more compact and efficient running from chrome.

"For Chrome to handle WebView rendering, you'll need to be on v51 or higher with Android 7.0. The default behavior in this instance will be for the Chrome APK on your device to render Android System WebViews. Google says this is more memory-efficient than using the current WebView. The standalone WebView APK will no longer be updated via the Play Store as long as the Chrome rendering remains enabled on your device."

https://www.androidpolice.com/2016/0...w-android-7-0/

What you quoted is indeed Legacy from 2016.
Since then Apache HTTP stack and client have been removed. All apps targeting API 24 and lower need to update protocols to API 28+

https://developer.android.com/about/...9.0-changes-28

[conite]

What you quoted is indeed Legacy from 2016.
Since then Apache HTTP stack and client have been removed. All apps targeting API 24 and lower need to update protocols to API 28+

https://developer.android.com/about/...9.0-changes-28

I'm not sure what you're referencing here.

Chrome is now the default webview implementation, and has been for some time.

[Invictus0]

System WebView is powered by Chromium so I'm not sure if switching to Chrome will change much.

OP: Hub+ apps work fine for me with WebView but @Vistaus had a similar issue recently. Not sure if he found a solution.

https://forums.crackberry.com/blackb...l#post13391610

[conite]

System Webview is powered by Chromium so I'm not sure if switching to Chrome will change much.

The Chrome version gets faster updates. Chrome Dev faster still.

Plus, the implementation is more memory efficient.

[stevenlcroucher]

I have the same issue on my OnePlus 3T. Looking in the developer options I can see that I'm already using Chrome to render pages and that WebView is disabled.

Any suggestions?

[Vistaus]

The Chrome version gets faster updates. Chrome Dev faster still.

Plus, the implementation is more memory efficient.

Android System WebView gets (semi-)weekly updates on the beta channel, though.

[conite]

Android System WebView gets (semi-)weekly updates on the beta channel, though.

It's still completely redundant since most people already have Chrome on their devices - whether they choose to use it as a browser or not.

[Vistaus]

I have the same issue on my OnePlus 3T. Looking in the developer options I can see that I'm already using Chrome to render pages and that WebView is disabled.

Any suggestions?

This wasa fixed in the latest BB Suite betas. Which is ironic as conite tried to convince me a few weks ago it was an issue on my end and I had to switch WebView implementations (which did not solve it), but BB now fixed it on their end, so in the end, it was not a device issue at all.

[conite]

This wasa fixed in the latest BB Suite betas. Which is ironic as conite tried to convince me a few weks ago it was an issue on my end and I had to switch WebView implementations (which did not solve it), but BB now fixed it on their end, so in the end, it was not a device issue at all.

Except for the fact that I didn't have the issue on any of my devices.

[Vistaus]

Except for the fact that I didn't have the issue on any of my devices.

Sure, but why would BB include a fix in the latest beta if it's a PEBKAC issue? After all, if nothing is broken on their end, they couldn't have fixed it. Or did they add placebo code?

[conite]

Sure, but why would BB include a fix in the latest beta if it's a PEBKAC issue? After all, if nothing is broken on their end, they couldn't have fixed it. Or did they add placebo code?

I'm not blaming anyone or anybody. I'm just pointing out that with the exact same software you had, I did not have the issue.

[LiamQ]

I have the same issue on my OnePlus 3T. Looking in the developer options I can see that I'm already using Chrome to render pages and that WebView is disabled.

Any suggestions?

Which version of Hub are you using? Which version of Chrome?

[GX624]

I have the same issue on my OnePlus 3T. Looking in the developer options I can see that I'm already using Chrome to render pages and that WebView is disabled.

Any suggestions?

Same issue on my Samsung Note 9.
I uninstalled latest Chrome update and BB Inbox works again.

Not sure what else to do.