Hi All,
Speaking more broadly, we understand your concerns and whenever possible
try to introduce breaking changes at version boundaries only. This gives
you the time to change and test your application against the new behavior
in an opt-in way. In this case there were reasons that the change
Hi Pete,
You are overstating the risk a bit. We currently have developerToken
required in sandbox and I just tested the Java and Python client libraries
myself - with no token, they receive an error, provide the token, they
succeed. That simple fact guarantees that your code change will be
Hi Kevin
The notable difference between this change and every other breaking change
(that I can remember anyway) is that previously, you would release a new
version and sunset the old, giving developers a chance to phase code
changes from Sandbox into Production with little or no risk.
Other t
Hi,
From a software engineering standpoint, we cannot recommend performing QA
actions against a production environment. QA is meant to catch bugs or
problems before they reach production. The sandbox environment was created
specifically for this type of testing. We're not recommending you p
Hi Kevin. I will clarify my point further. Regardless of whether we do our
coding and unit testing against the sandbox or not, we do *NOT* do QA or
production verification against the sandbox. This has always been the case,
for all search engines that we support. It would require hacking with re
Hi all,
Quick and final update on this:
http://adwordsapi.blogspot.com/2011/11/update2-developer-token-required-in.html
- Kevin Winter
AdWords API Team
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://adwordsapi.blogspot.com
http://grou
Hi Ian,
It's unfortunate that the Location Criterions do not properly work in the
sandbox and we're working to resolve that. However, that does not affect
the functionality of AdHoc reporting (which we know works in the sandbox).
We do recommend using the sandbox to test this change.
- Kevi
The problem with testing against the sandbox(es) in general is that
they are unreliable--see:
http://groups.google.com/group/adwords-api/browse_thread/thread/afe33e8b9d709beb/d701ffe0e13f0fd3?lnk=gst&q=criterion+sandbox#d701ffe0e13f0fd3
behavior is frequently different between the sandboxes and pro
Hi,
We don't recommend testing new code against production as there is a
chance you can change your production account mistakenly. We provide the
sandbox to test these types of changes. You can perform the same test you
describe (test without to confirm it fails, add, test again with to conf
OK I have discussed with our QA and app support teams, and they are *not
OK*with releasing anything that we can't reasonably QA and verify
*against a production API* after a production patch. We don't do either QA
or production verification against sandboxes. Actually we rarely even code
agains
Hi,
Yes, we did make a formal announcement on the blog:
http://adwordsapi.blogspot.com/2011/10/adwords-api-v201109-launch-providing.html
Blog posts are automatically mailed out to the announcements list, which
you can subscribe to right on the homepage of the API documentation under
the How D
No response? There is actually a serious question here about testing this
change that is about to be fast-tracked into production.
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://adwordsapi.blogspot.com
http://groups.google.com/group/adwo
There have been a number of announcements recently about changes to an API
in production that I think are cause for concern. We are currently using
v201101. Just recently I accidentally stumbed over a blog announcement that
this version would be deprecated at the end of Feb 2012. With 3-4 month
13 matches
Mail list logo
