Oh my, those clowns again. They cannot even tell servers apart, but want to play the "Safety Police"? What are they doing for a living, by the way (apart from slurping and selling our data)?

Yes, that's the same file as in January. On a different server. But they flag yet another, that does not even have that file. Incompetent folks, they should shut down that "service". Will they ever stop that nonsense?!?

#Google #SafeBrowsing #failure

Oh, did I mention that that file does not even exist – for 2 month now? 🤦‍♂️ So even if it would have been malicious: a timely warning for those who trust that snake oil, would you agree? How often do they update, I wonder…

Of course the review failed (as usual, without a notification mail). Now they pick random APK files: remove one, then it's the next. Until the repo is empty, I guess. Snippet updated.

Disable "Safe" browsing, it's snake oil as you can see. We've been libeled now many times, always false positives. See https://gitlab.com/-/snippets/4909577#notes-on-how-to-disable-google-safebrowsing-in-browsers-on-android for how to disable it.

Of course all our APKs have been scanned, multiple times, with many engines. They're clean. Says even G's own scanner.

#Google #SafeBrowsing

Netcraft false positives, Google Safebrowsing shenanigans ($4909577) · Snippets · GitLab

GitLab.com

GitLab
@IzzyOnDroid I think this far beyond the point it can be justified with incompetence on their part. People will complain less about the developer registration if most 3rd party "app stores" implode before it's rolled out.