Last active
August 28, 2022 23:53
-
-
Save n1lesh/1ba55eae709712ebb38bc65acda0f19e to your computer and use it in GitHub Desktop.
Enable Safe Browsing in WebViews - Android O
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
<manifest> | |
<application> | |
. . . | |
<meta-data android:name="android.webkit.WebView.EnableSafeBrowsing" | |
android:value="true" /> | |
. . . | |
</application> | |
</manifest> |
@n1lesh Ah, just saw this comment. Sorry for the late reply!
Yeah, it's unfortunate that the original blog post was incorrect. Our team must have missed it during review, so that's on us. The mistake slipped into this post as well, but we've since fixed the error 😄
I'll look into who owns that original blog post and see if we can fix that one too.
Glad to hear you've liked Chrome Custom Tabs. That's another great product from the team, and provides a lot of Chrome's power and safety, embedded in your app.
Feel free to ping me if you have any questions on either Safe Browsing or multiprocess, or (even better) ask a question on the android-webview-dev mailing list.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hey @nfischer
Thanks for the correction mate. I wrote that post just after the announcement was made and never really got to try the feature myself, so yeah, I believe I made an honest mistake trusting a post by Google people, sorry! 😞 .
The second part you addressed did bug me at the time of writing that post. As I said, never been able to work with WebViews, I have played with CustomTabs though. I will make corrections to that post soon to reflect the changes. Also, on your part, it would be really nice if you could manage to get that original post corrected. A lot of people (like me) depend on announcement posts like that.
Thanks again for the clarification.