Open anttironty opened 2 years ago
I have never seen this happen, can you provide a sample app where it can be reproduced?
Apparently safe browsing is enabled by default on any device that supports it, so another option could be to disable safe browsing entirely since Capacitor is not used for browsing.
I have never seen this happen, can you provide a sample app where it can be reproduced?
Sure, I'll try to scramble some kind of a sample together when I have some spare time.
I'm seeing this currently in capacitor 3.3 app that for example needs to listen websocket and generally speaks alot with different api's. The solution I described in Additional Context part above fixed the issue. Disabling Google-Play-Protect on device also stopped the bug from happening.
Feature Request
Description
Play-protect sometimes fails checking urls that the webview will be using, when this happens the whole webview slows down remarkably and hurts the ux massively.
When developer notices that the app suffers from this issue, setting list of hosts (domain names/IP addresses) that are exempt from SafeBrowsing checks would fix the issue.
Error seen at android studio logcat:
Related stackoverflow thread https://stackoverflow.com/questions/58725618/where-does-a-googleclientapiconnected-exception-come-from
Platform(s)
Android
Preferred Solution
capacitor.config.ts
could have property "safeBrowsingWhitelist" which takes list of urls that should be exempt from SafeBrowsing checks.Additional Context
My current solution is to modify loadWebView in Bridge.java like this: