Closed kokuda closed 6 years ago
Using a new API key sometimes results in the stack overflow failure and sometimes works correctly, depending on the key. A fake key always seems to result in a stack overflow. This is likely a bug with Google Maps but the quickest fix might be to upgrade to V3.
Upgraded to Google Maps v3 and the problems are resolved.
This script no longer works as-is with the existing V2 API (either the old API key produces a "development" version or the new API key produces errors when loading the pages.
Using a new API Key provided by Google sometimes results in the following (and sometimes works, depending on the key)
Uncaught RangeError: Maximum call stack size exceeded at common.js:1 at Object..yb (maps?file=api&v=2&key=key=AIzaSyDoak-H2Ga82-X7e3qkLAjfKwdEl7E8EA0:39) at a (common.js:54) at common.js:54 at Object..yb (maps?file=api&v=2&key=key=AIzaSyDoak-H2Ga82-X7e3qkLAjfKwdEl7E8EA0:39) at a (common.js:54) at common.js:54 at Object._.yb (maps?file=api&v=2&key=key=AIzaSyDoak-H2Ga82-X7e3qkLAjfKwdEl7E8EA0:39) at a (common.js:54) at common.js:54
It might be worth upgrading to the V3 API to resolve these issues, but these might also be a bug in the Google Maps API.