The maps aren't secret, it's simply that I write on behalf of several of our customers that started to report issues now. Personally I've only confirmed the case that an invalid key now leads to no base script loaded at all, which will result in script errors. As said, that might be reasonable but I'm just trying to understand if that is the intended new behavior with 2.340 and/or if there's some more issues.
Hoping that some Google insider could post some info. There is certainly "something" more than just a bugfix to GPolygon that was applied in the last upgrade... http://code.google.com/p/gmaps-api-issues/wiki/JavascriptMapsAPIChangelog (The "sensor=false" param is specified since it is a desktop web app with no location info). Regards / Fredrik Blomqvist On Aug 16, 9:48 pm, Rossko <[email protected]> wrote: > Something you might check yourself, seeing as your maps are secret, is > if you are supplying the mandatory sensor= parameter and what value > you are assigning to it, maybe behaviour has changed there. -- You received this message because you are subscribed to the Google Groups "Google Maps API V2" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-maps-api?hl=en.
