Google Maps API embed throws error- because of cached auth param?
-
Hi,
We are seeing a JS error on that indicates the Google Maps script is not loaded from the correct URL.
On the page:
Oops! Something went wrong. This page didn't load Google Maps correctly. See the JavaScript console for technical details.
In the console:
c3410.js?81a11:sourcemap:46 Google Maps JavaScript API error: NotLoadingAPIFromGoogleMapsError https://developers.google.com/maps/documentation/javascript/error-messages#not-loading-api-from-google-maps-error _.Qe @ c3410.js?81a11:sourcemap:46
I think it can be caused by caching, as described here: https://stackoverflow.com/questions/61092932/notloadingapifromgooglemapserror-occurring-randomly-with-google-maps-javascript. The problem is solved – for about a day – when the Lightspeed cache is cleared. When I exclude the whole page from caching, the issue is solved (but the page becomes extremely slow).
Do you think the hypothesis is correct, and then, how to solve?
Thanks already,
Ivan
Viewing 11 replies - 1 through 11 (of 11 total)
Viewing 11 replies - 1 through 11 (of 11 total)
- The topic ‘Google Maps API embed throws error- because of cached auth param?’ is closed to new replies.