I'm using a developer token, but trying to use OAuth. I've associated an account correctly (as far as I can tell) but the token from OAuth always returns a GOOGLE_ACCOUNT_COOKIE_INVALID. Today, I attempted to grab a token via ClientLogin and now I get 'INCOMPLETE_SIGNUP' as the error. I filled in the billing information / agreed to the T&C, still get the same error.
Why do the token lengths differ between OAuth2 and ClientLogin? Why would one work (ie, getting an INCOMPLETE_SIGNUP) but the other wouldn't? I submitted by test account ID and MCC ID on Friday, but still haven't been able to connect. I'd really prefer to use the OAuth mechanism - am I doing something wrong? I'm getting a authToken / refreshToken back, so it seems to be working? Thanks -Dave -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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 --- You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
