I certainly hope the problem and fix is that simple. Initial eror reports from end-users are often incomplete though.. A note in the changelog or similar place about this would've helped track this down.
Not getting an actual map to display with an invalid key is ok (of course!), but I think it could be nice to still get the js-code (or a mock). Quite commonly you have code that use GMap API immediately, like inherit from GControl etc. This would avoid script errors and enable more (easy) graceful handling of the case within an app. Well, unless someone with inside knowledge posts here we're just speculating... Regards / Fredrik Blomqvist On Aug 17, 11:36 am, Rossko <[email protected]> wrote: > > The maps aren't secret, it's simply that I write on behalf of several > > of our customers that started to report issues now. > > They remain a mysterious secret to everybody else. > > > 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. > > Okay, that rather sounds like it is supposed to happen. > > > 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. > > It probably always was the intended behaviour i.e. an invalid key > shouldn't work. I wouldn't expect Google to enter into great detail > about their security measures. > > From memory the key checking has to do with the loader/bootstrap and > has a Google-server based element, and not the actual maps API version > anyway. > > If the "fix" is 'use a valid key', there doesn't seem to be much more > to say about it. -- 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.
