Thanks for the suggestion, Roberto. We have an update for those iPhone App developers that are affected:
We will put in a change that will prevent currently affected and active iPhone apps from receiving the HTTP geocoding error. We will retain this for 30 days, with the expectation that iPhone app developers will change their code within that period to send a valid key. We hope to be able to put this change in within the next week, and will update when that happens. On Tue, Oct 20, 2009 at 10:43 AM, ik8sqi <[email protected]> wrote: > > Pamela, > > First of all thanks for the reply. May I suggest/ask that this be used > as a "dry run" to give everyone notice this will be coming in the near > future? By now all iPhone app developers who are affected will have > found out about the problem, will be researching on "what" broke in > the API, and will end up on this thread, just like it happened to me. > Even if we (iPhone developers) found the cause, there is *absolutely > nothing* we all can do do make our apps work again in the near future, > as I repeatedly mentioned it takes Apple weeks to approve app > submissions. If you can "pardon" all of us, now that we know the > disaster we encountered, you can be sure all of us will scramble to > solve this in our next releases. Just give us a few months to figure > out what the best way to proceed is. Apple iPhones just released their > new MapKits in the SDK that allowed us to use the Google maps a few > months ago, and there is little or no guidance on how to write apps > that use all mapping functionality like the one you just took away > from us without any sort of notice. Let this event be our notice. Undo > your changes (which I repeat is the *only* thing which will allow our > apps to work for the next weeks) and allow us some time to make things > right. Please. I hope you hear the desperation in my words, which I'm > confident is being shared by other iPhone developers as well. Being > completely helpless in fixing our applications is a terrible feeling. > In addition to the monetary loss developers are experiencing, please > do remember the negative impact on Google's name to the large number > of customers who now have useless apps. > > You yourselves should have noticed the nightmares we go thru in having > app approved, seeing what happened with your own Google Voice iPhone > app which keeps getting rejected. It will take weeks for us to have > our updates approved by Apple, and having non-functional apps for > weeks is almost a death sentence... > > Thanks for listening, > > Roberto F. > > > > > On Oct 19, 4:57 pm, "pamela (Google Employee)" <[email protected]> > wrote: > > We would recommend using Maps API v3 inside a browser control for > iPhones, > > as there would be no limiting issues there. If you are using the HTTP > > Geocoding API now and aren't using an enterprise client ID or some non-IP > > identifier, then we would count requests against your IP, and you would > > likely run into the issue quite fast. So, I would suggest thinking about > > your expected load if that's the plan, and looking into other options or > > contacting us. > > But, those recommendations do not excuse us from breaking your apps. I > > apologize that we messaged that this was not going to happen, and that we > > didn't find a better way to contact potentially affected apps. > > > > We'll check the logs to see the amount of breakage, but I think that we > will > > be retaining this change, as it improves our authorization code and makes > > apps less likely to break in the future. (A necessary evil). > > > > Feel free to contact me offline regarding best strategy for your iPhone > > Apps. > > > > - pamela > > > > > > > > On Tue, Oct 20, 2009 at 6:17 AM, Rossko <[email protected]> > wrote: > > > > > > The JavaScript client-side geocode is unusable in iPhone devices... > > > > The HTTP method is the only practical one. > > > > > Doesn't change Google's recommendation not to use it in that kind of > > > application. > > > Google is of course not the only HTTP geocoder, but you/they would > > > have to read the packet carefully for those too! > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
