Arghhh!!! We have an iPhone app which uses the HTTP geocoder to display data on the iPhone-provided google maps. There is no "key" that matches the domain as theses are plain HTTP requests from an iPhone without any referrer and/or domain. The iPhone is simply doing an address lookup to get lat/long to then display the dot on its own google-driven build-in map. There is no domain involved here... This of course completely "broke" our app as it's now unable to do lookups. It takes *several* weeks for Apple to approve new app upgrades, so we are now in *deep* trouble, as even though we submitted a new version today with a workaround, it will not be available on iPhones for weeks. Our app is not the only one with the problem, we have seen a few others failing as well.
Is there any chance this requirement will be rethought? Or at least exclude iPhone/iTouch devices from this via their browser agent? Help...!!! Roberto F. On Oct 18, 4:52 pm, "pamela (Google Employee)" <[email protected]> wrote: > Hey Sterling - > > The recommended technique there is the GClientGeocoder(), so if they use > that, the geocodes will be counted against the User IP, and they will not go > over the limit. We don't do any per-key limits anymore. > - pamela > > On Mon, Oct 19, 2009 at 2:48 AM, String <[email protected]>wrote: > > > > > > > Any chance of whitelisting the Google gadget server domains > > *.modules.com and *.googleusercontent.com? Given that the GMaps > > geocoder is the recommended technique for gadgets (see > >http://code.google.com/apis/gadgets/docs/fundamentals.html#location), > > there's a strong likelihood that gadgets will run over the gecoder > > limits. > > > Thanks! I'm happy to post this as a feature request if that would be > > more appropriate, just let me know. > > > String > > > On Oct 18, 1:10 pm, "pamela (Google Employee)" <[email protected]> > > wrote: > > > Update: We have gone forward with this change. If you are doing HTTP > > > geocoding and receiving errors suddenly, you should check on the > > > validity and existence of the key parameter that you send in. It > > > should match the referrer. > > > > On Aug 30, 8:12 am, Mike <[email protected]> wrote: > > > > > I am using HTTP request from the server side of a Java GAE > > > > application. What is the proper key to use? http://appspot.cometc. > > > > do not work... > > > > > Thanks, > > > > > Mike > > > > > On Jul 30, 12:54 am, "pamela (Google Employee)" <[email protected]> > > > > wrote: > > > > > > Note: If you are only using GClientGeocoder or ClientGeocoder from > > the > > > > > JS/Flash APIs, then this message is not relevant to you. This message > > > > > applies only to users of the HTTP Geocoder documented here: > >http://code.google.com/apis/maps/documentation/geocoding/ > > > > > > Our system currently permits HTTP Geocoder requests without referers > > to not > > > > > provide a valid key. In the next few weeks, we will be making a > > change that > > > > > enforces that a > > > > > valid key must be provided along with an HTTP Geocoder request. > > Please > > > > > ensure that your HTTP Geocoding requests pass a valid key. > > > > > > Please post in the forums if you have questions about this change. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
