Update: I was able to get a successful 200 response back making a get operation. That means that all my code dealing with the request was fine, the only issue was with the provided example XML.
On Tuesday, May 10, 2016 at 2:49:16 PM UTC-4, Kurt Wheeler wrote: > > Hello, > > It's a shame this didn't ever get resolved. Almost a year later I am > getting the same error using the sample XML provided by the guide. Anthony > said "The error you are getting indicates that your OAuth token may be > expired." but that error does not indicate that the OAuth token is expired. > It may be caused by it, but it certainly doesn't indicate it. However when > I run my code I am generating an OAuth access_token immediately before > making this request so I know that there's no way it could be expired. I > also know that my refresh token is valid for the same reason: if it wasn't > I wouldn't be able to generate the access token. My use case does not > require a mutate operation so I am going to see if I can get this working > with a simple get. It sounds like there's a good chance the error message > being returned is actually unrelated to my issue though so I may run into > the issue doing a get as well. > > It seems like either the sample XML on the "Basic Concepts" should be > changed so that an error message isn't returned or the error handling code > should be changed to return an error message that does indicate what the > error is instead of returning a red herring message related to provided > sample code. > > On Thursday, September 17, 2015 at 5:38:28 PM UTC-4, Orlie wrote: >> >> I'm pretty sure my Oauth is right because I was doing the whole Oauth >> flow separately.. >> >> However: I have been working on it trying to resolve since yesterday, so >> I gave up and used your Google Ads library instead. >> >> Thanks! >> >> On Thursday, September 17, 2015 at 3:54:23 PM UTC-5, Anthony Madrigal >> wrote: >>> >>> Hi Orlie, >>> >>> The error you are getting indicates that your OAuth token may be >>> expired. You could check to see if your token is still valid by appending >>> it to this link in place of MY_TOKEN: >>> https://www.googleapis.com/oauth2/v1/tokeninfo?access_token=MY_TOKEN >>> You may want to generate a new Refresh Token if this is still failing. >>> >>> Please also make sure that your clientCustomerId is an ID that >>> corresponds to an AdWords client account, *not *an MCC manager account. >>> >>> Let me know if you are still running into any issues. >>> >>> Regards, >>> Anthony >>> AdWords API Team >>> >> -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and Google+: https://googleadsdeveloper.blogspot.com/ https://plus.google.com/+GoogleAdsDevelopers/posts =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To post to this group, send email to adwords-api@googlegroups.com To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com 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 adwords-api+unsubscr...@googlegroups.com. Visit this group at https://groups.google.com/group/adwords-api. To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/395597b2-4447-48d5-87e8-f7fab6c60aca%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
