So Google itself doesn't keep up with the API changes. This is the code they generate when you request a key. At least there should be a warning about it.
On Apr 18, 1:13 pm, Andrew Leach <[email protected]> wrote: > On Apr 18, 10:33 am, yang <[email protected]> wrote: > > > I know that this question was asked before but my case seems a little > > different. > > There's nothing different about sensor=true_or_false: read *all* the > documentation on the key pages. It changed a couple of months ago and > you shouldn't blindly cut and paste: you need to specify a valid value > for sensor. > > Andrew --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Maps API" 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 -~----------~----~----~----~------~----~------~--~---
