100% error rate on Geolocation API

[Evangelos Foutras]

Starting around January 17th, almost all requests get a 4xx error code. It doesn't seem like Arch's distro API key is going over quota. The following warning on the Maps overview page in the Cloud Console seems relevant:

The billing account "Google Maps Platform Transition Account" is not open

Can someone from the Chromium team help us with this?

[Olivier Tilloy]

The chromium packages in Ubuntu are similarly affected. According to
the metrics on the cloud console this started happening on Friday the
17th of January.

This situation looks similar to what happened in July 2018:
https://groups.google.com/a/chromium.org/d/msg/chromium-packagers/1LDZZnYJ0SU/OCCtVl78BQAJ.

I second Evangelos's request for help from someone on the chromium
team to sort this out. Thanks in advance!

Olivier

[Lei Zhang]

Done!

> --
> You received this message because you are subscribed to the Google Groups "chromium-packagers" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to chromium-packag...@chromium.org.
> To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-packagers/CAKyXnk9obrpnT1CZVm84DekrkPMuKvM7ZnxRW8C3jSnC9_L70Q%40mail.gmail.com.

[Olivier Tilloy]

On Mon, Jan 27, 2020 at 8:26 PM Lei Zhang <the...@chromium.org> wrote:
>
> Done!

Thanks for the prompt reply. Unfortunately I'm still seeing a 100%
error rate for the credentials used by the chromium package in Ubuntu.

[Lei Zhang]

On Mon, Jan 27, 2020 at 11:36 PM Olivier Tilloy
<olivier...@canonical.com> wrote:
> Thanks for the prompt reply. Unfortunately I'm still seeing a 100%
> error rate for the credentials used by the chromium package in Ubuntu.

Sorry to hear that. I'm just playing messenger.

[Olivier Tilloy]

Ack, no worries. I thought by "done" you meant it was fixed. Thanks
again for passing the message along, I'll be monitoring the console in
the hope that it gets sorted out soon.

Cheers,

Olivier

[Evangelos Foutras]

Lei, thank you for relaying the message. Please let us know if this can't be fixed on your end so we can consider our options downstream.

[Lei Zhang]

I contacted more folks who work on the Geolocation API. Hopefully
someone can reply and give some guidance.

[Evangelos Foutras]

Lei, thanks again for passing along our request. By the lack of response, I gather it's not a simple issue to address and/or is very low priority for the relevant teams.

Perhaps it might be a good time to consider moving away from the "one key per distro" policy started in 2013. It has had nontrivial overhead for distro maintainers and also Google folks who have helped adjust quotas and stuff throughout the years. Providing a single key that could be used in distro builds would simplify things quite a bit. I believe this approach was rejected internally back in 2013 but could be worth a reconsideration.

Not sure what other options we have; shipping Chromium builds with broken geolocation is definitely awkward for me to continue to do.

[Lei Zhang]

Sorry to hear this hasn't been resolved yet. I will keep pinging
people on your behalf.

> --
> You received this message because you are subscribed to the Google Groups "chromium-packagers" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to chromium-packag...@chromium.org.

> To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-packagers/CAA407mxCPa-JJONiA%2B9O-Guo-2mmwS9YSfdOMRS8KPQBfOJ9wg%40mail.gmail.com.

[Olivier Tilloy]

Hi Lei, Evangelos,

Geolocation is still not working in Ubuntu chromium builds.

I'm wondering if there was ever a response from the geolocation API folks, and/or how this was mitigated in Arch (and other distros)?

Cheers,

 Olivier

[Tom Callaway]

It's still broken in Fedora as far as I know.

Tom

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-packagers/CAKyXnk_o4a%2BXRg4id1KaPa60DW%2B996ZdTgKjv1eQ5WgLqnP-Yw%40mail.gmail.com.

[Lei Zhang]

2 things here:

1) Geolocation API access - I have no idea what's going on there.
2) Mitigation - On Windows and macOS, there's work to enable using the
OS geolocation APIs as an alternative. The bugs for these are
crbug.com/968883 and crbug.com/1051591, respectively. If there is a
common geolocation API for Linux, maybe file a bug for Chromium to
integrate with that API?

> To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-packagers/CAKyXnk_o4a%2BXRg4id1KaPa60DW%2B996ZdTgKjv1eQ5WgLqnP-Yw%40mail.gmail.com.

[Olivier Tilloy]

On Wed, Jun 3, 2020 at 6:44 PM Lei Zhang <the...@chromium.org> wrote:

2 things here:

1) Geolocation API access - I have no idea what's going on there.
2) Mitigation - On Windows and macOS, there's work to enable using the
OS geolocation APIs as an alternative. The bugs for these are
crbug.com/968883 and crbug.com/1051591, respectively. If there is a
common geolocation API for Linux, maybe file a bug for Chromium to
integrate with that API?

Ack, I filed crbug.com/1093873 for this. Thanks for your help and support Lei.

[Evangelos Foutras]

For the record, geolocation started working again on July 29th. I am not optimistic it won't break again though.