OK, uploaded the 2.7.2 library and that solved the issue. But why did
I have to go through loads of stuff to find that out. Also, the idea
of using a blog of all things to announce important updates is just
daft. There has to be a better way. I just switch off with blog stuff
it just gets lumped into all the chatter and becomes part of the
drone. As someone else said, this sort of thing that can break scripts
needs to be flagged in a better way.

On Jan 19, 4:30 pm, opalepatrick <[email protected]> wrote:
> Using php, I have always had the developers token in the auth.ini, so
> why am I getting this message?
>
> On Jan 19, 3:12 pm, Eric Koleda <[email protected]> wrote:
>
>
>
>
>
>
>
> > Hi Alexander,
>
> > We first communicated this change in November of last year, and then again
> > about a week ago:
>
> >http://adwordsapi.blogspot.com/2011/11/update2-developer-token-requir......
>
> > Sunil,
>
> > Please make sure you are using the latest version of the .NET client
> > library, as older versions may not send the developer token along with
> > report download requests.
>
> > Best,
> > - Eric

-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://adwordsapi.blogspot.com
http://groups.google.com/group/adwords-api
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups "AdWords API Forum" 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/adwords-api?hl=en

Reply via email to