Martin Schuhfuss

I think this behavior at least matches the behavior of the maps API itself. Not sure right now what can be done about it, but I will have a look.

We certainly don't want to trigger these warnings when rendering on the server, but I'm trying to figure out what would be the best way to do that. The suggested...

I've seen this recommended several times, mostly related to unit-testing, but you could give this a shot: Somewhere in the code that exclusively runs on the server (no Idea how...

For now the recommendation is just "avoid rendering components that don't do anything on the server as server-components" (we will probably come up with something better at some point). If...

So one important thing about this is that the loading status will always go from `LOADING` to `LOADED` before eventually changing to `AUTH_FAILURE`. The reason for this is that the...

That the API itself can be successfully loaded with an invalid API key is somewhat by design. The reason for this is that validation of the key will happen after...

This doesn't have anything to do with the react-library, but let's see if I can help you anyway... Have you checked that not only the Routes API is enabled for...

After a bit of searching, I found the answer: the old version of the Places API, the Directions API and the Distance Matrix API as well as their classes in...

yeah, with the places API things are slightly different. At least there are new parts of the Maps JavaScript API to use them with. `PlacesService`, `Autocomplete`, and `SearchBox` from `google.maps.places`...

@sahibjotsaggu It might still be possible using this direct link: https://console.cloud.google.com/apis/library/places-backend.googleapis.com