Hi bhavin,
I believe this fix was rolled out correctly. You can numeric offsets like
"-08:00" or POSIX timezone strings like "America/New_York".
Best,
- Eric Koleda, AdWords API Team
On Tuesday, March 6, 2012 11:15:18 PM UTC-5, bhavin wrote:
>
> Hello Eric,
>
> Can you please post if there are
Hello Eric,
Can you please post if there are any updates on this issue? I am using
v201109 but I am still seeing this issue.
My findings so far on the values given to initialize DateTimeRange object
used in CustomerSyncSelector class.
- If no time-zone is provided the time is assumed to be acc
Use UTC. Always works.
Others fail with out regularity.
-tim
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://adwordsapi.blogspot.com
http://groups.google.com/group/adwords-api
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
You receiv
Hi Brian,
It looks as if the fix didn't roll out as planned. I'm working with the
core engineering team to determine the cause.
Best,
- Eric
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://adwordsapi.blogspot.com
http://groups.google.c
Still getting the same INVALID_TIMEZONE error today using numerical
offsets (haven't tried "" specifier yet). I thought the fix would
be rolled out by now (currently using v201008). When will it be
fixed?
On Dec 5, 9:32 am, David Torres wrote:
> Hi Brian,
>
> The fix should be rolling out t
Hi Brian,
The fix should be rolling out today so you can start using GMT-offset type
of timezone formats tomorrow, in the meantime if you use (and I'm assuming
you are using Java) a "" specifier should give you the timezone in
letters as "Eastern Standard Time" but only if it knows the loca
Eric,
Can you give me the acceptable format string to use in the min/max
dateTimeRange request for the API. Currently, I'm using this format:
"MMdd HHmmss zzz"
Thanks,
Brian
On Nov 30, 2:59 pm, Eric Koleda wrote:
> Hi,
>
> A fix should be going out next week or so that will allow numerical
Hi,
A fix should be going out next week or so that will allow numerical offsets
again. In the mean time you can use named timezones like
"America/New_York", etc.
Best,
- Eric
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://adwordsapi.
What format is the API expecting for the data range then? How should
I format the named timezones?
On Nov 29, 2:43 pm, Eric Koleda wrote:
> Hi,
>
> Thank you for reporting this issue. It looks like there was recently some
> changes in the validation code for timezones in this service. Using na
Hi,
Thank you for reporting this issue. It looks like there was recently some
changes in the validation code for timezones in this service. Using named
timezones should still work, but numerical offsets are currently being
rejected. I'm in contact with the core engineering team about this is
This error hasn't happened before. Did Google change requirements for
this service? I've always sent my request with my current timezone
and never received this error before. Please reply ASAP since this
error is causing our clients to panic during Black Friday. Thank you
in advance for your he
11 matches
Mail list logo
