I don't have a project that is directly affected, but I am active in the AJAX APIs Group, which has seen a number of these reports for the Translate API and a handful for the Search API.
Jeremy R. Geerdes Generally Cool Guy Des Moines, IA For more information or a project quote: jrgeer...@gmail.com If you're in the Des Moines, IA, area, check out Debra Heights Wesleyan Church! On Jan 10, 2012, at 5:24 PM, Luke Mahé wrote: > Jeremy, > > Can you please email me directly your project id that you are seeing these > issues on? > > Thanks > > -- Luke > > > On Wed, Jan 11, 2012 at 9:53 AM, Jeremy Geerdes <jrgeer...@gmail.com> wrote: > There is apparently an issue in the APIs Console with validating keys. It has > affected Translate, Custom Search, and Maps APIs. It may affect,more, but > those are by far the highest volume APIs, so the others may go unnoticed yet. > The dev team behind the Console (i.e., the Google APIs team) is almost > undoubtedly aware of the situation, which has been reported on the AJAX APIs > Group as well, but they have not as yet provided a complete solution. > > Jg > > On Jan 10, 2012 4:03 PM, "Andrew Leach" <andrew.leac...@gmail.com> wrote: > On 10 January 2012 20:20, Luke Mahé <lu...@google.com> wrote: > > This isn't really the right solution. You should instead make sure that you > > have generated a key in the apis console > > (https://code.google.com/apis/console/b/0/?pli=1) and make sure that the > > allowed referrals matches your domain(s). > > > > Setting the version to 3.6 will only delay the warning and not fix it. > > Interesting answer. > > If v3.6 is not specified, and the key is correctly generated in the > API console, why are there so many queries here about invalid key > messages which are intermittent? It's that apparently random > inconsistency which setting the version is intended to avoid. Once the > key system is working consistently, there's no reason not to use it; > while it isn't, there's every reason not to use it. > > -- > You received this message because you are subscribed to the Google Groups > "Google Maps JavaScript API v3" group. > To post to this group, send email to google-maps-js-api-v3@googlegroups.com. > To unsubscribe from this group, send email to > google-maps-js-api-v3+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-maps-js-api-v3?hl=en. > > > -- > You received this message because you are subscribed to the Google Groups > "Google Maps JavaScript API v3" group. > To post to this group, send email to google-maps-js-api-v3@googlegroups.com. > To unsubscribe from this group, send email to > google-maps-js-api-v3+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-maps-js-api-v3?hl=en. > > > -- > You received this message because you are subscribed to the Google Groups > "Google Maps JavaScript API v3" group. > To post to this group, send email to google-maps-js-api-v3@googlegroups.com. > To unsubscribe from this group, send email to > google-maps-js-api-v3+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-maps-js-api-v3?hl=en. -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" group. To post to this group, send email to google-maps-js-api-v3@googlegroups.com. To unsubscribe from this group, send email to google-maps-js-api-v3+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.
