Now that you got a new `refresh_token`, does your app refresh the
`access_token` automatically or do you need to do that manually as well?
On Tuesday, April 14, 2015 at 12:22:30 PM UTC-4, Danial Klimkin wrote:
>
> Sample app works for me (though I had to get a new refresh token as well).
>
> I understand you could get requests to succeed, so the immediate problem
> was resolved for you?
>
>
> -Danial.
>
>
> On Tuesday, April 14, 2015 at 7:15:30 PM UTC+3, Seth wrote:
>>
>> Ok thanks, let me know? Did you get your sample app working?
>>
>> On Tuesday, April 14, 2015 at 12:12:39 PM UTC-4, Danial Klimkin wrote:
>>>
>>> Interesting. Thanks for reporting. I'll check if something has changed
>>> with the new signet version.
>>>
>>>
>>> -Danial.
>>>
>>>
>>> On Tuesday, April 14, 2015 at 7:01:24 PM UTC+3, Seth wrote:
>>>>
>>>> Ok so i refreshed and im getting the same error. However, when I change
>>>> `issued_at` back to blank the request works.
>>>>
>>>> On Tuesday, April 14, 2015 at 11:54:41 AM UTC-4, Danial Klimkin wrote:
>>>>>
>>>>> Hello Seth,
>>>>>
>>>>>
>>>>> I suggest re-generating your refresh token. From the error below it
>>>>> looks like the refresh is triggered correctly but the token was not valid.
>>>>>
>>>>>
>>>>> -Danial.
>>>>>
>>>>>
>>>>> On Tuesday, April 14, 2015 at 6:47:16 PM UTC+3, Seth wrote:
>>>>>>
>>>>>> Ok now im getting `rescue in refresh_token!': OAuth2 token refresh
>>>>>> failed (AdsCommon::Errors::AuthError)
>>>>>>
>>>>>> On Tuesday, April 14, 2015 at 11:40:16 AM UTC-4, Danial Klimkin wrote:
>>>>>>>
>>>>>>> Try setting it to the timestamp of token generation, or to an old
>>>>>>> date. Eg.:
>>>>>>>
>>>>>>> :oauth2_token:
>>>>>>> :access_token: ****
>>>>>>> :refresh_token: ****
>>>>>>> :issued_at: 2014-05-13 14:29:18.110177979 +04:00
>>>>>>>
>>>>>>>
>>>>>>> -Danial.
>>>>>>>
>>>>>>> On Tuesday, April 14, 2015 at 6:34:30 PM UTC+3, Seth wrote:
>>>>>>>>
>>>>>>>> right now its blank
>>>>>>>>
>>>>>>>> On Tuesday, April 14, 2015 at 11:31:40 AM UTC-4, Danial Klimkin
>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>> Do you also have :issued_at: defined? What is its value?
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> -Danial.
>>>>>>>>>
>>>>>>>>> On Tuesday, April 14, 2015 at 6:12:28 PM UTC+3, Seth wrote:
>>>>>>>>>>
>>>>>>>>>> Yes, so when I go on OAuth 2.0 Playground and get new tokens my
>>>>>>>>>> app runs (using both tokens in my yml file). However, once the
>>>>>>>>>> token
>>>>>>>>>> expires it stops working and i'm getting the
>>>>>>>>>> AuthenticationError.OAUTH_TOKEN_INVALID error.
>>>>>>>>>>
>>>>>>>>>> Not sure if this makes a difference, but, I am keeping the
>>>>>>>>>> `adwords_api.yml` in my apps root directory and passing as a param
>>>>>>>>>> like
>>>>>>>>>> this `AdwordsApi::Api.new("./adwords_api.yml")`.
>>>>>>>>>>
>>>>>>>>>> On Tuesday, April 14, 2015 at 11:02:43 AM UTC-4, Danial Klimkin
>>>>>>>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>> I'll try to create a fresh setup and reproduce.
>>>>>>>>>>>
>>>>>>>>>>> In the meanwhile, can you describe the original issue in more
>>>>>>>>>>> detail? Did some of the request succeed but then stop?
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> -Danial.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Tuesday, April 14, 2015 at 5:57:45 PM UTC+3, Seth wrote:
>>>>>>>>>>>>
>>>>>>>>>>>> Sorry i meant `access_token`, I always had both the
>>>>>>>>>>>> `access_token` and `refresh_token`. I also just created a sample
>>>>>>>>>>>> app with a
>>>>>>>>>>>> fresh install of everything and its not working without the
>>>>>>>>>>>> `access_token`
>>>>>>>>>>>>
>>>>>>>>>>>> On Tuesday, April 14, 2015 at 10:53:25 AM UTC-4, Danial Klimkin
>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>> Yes, you do need refresh_token on the config.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Please let me also now the ads-common and signet gem versions
>>>>>>>>>>>>> you are using.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> -Danial.
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Tuesday, April 14, 2015 at 5:48:32 PM UTC+3, Seth wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Yeah, thats all the same. But until now i always had the
>>>>>>>>>>>>>> `refresh_token` as well. When did that change?
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Tuesday, April 14, 2015 at 10:45:45 AM UTC-4, Danial
>>>>>>>>>>>>>> Klimkin wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Hi Seth,
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Did you make any changes to the configuration file between
>>>>>>>>>>>>>>> versions? There were no auth-affecting changes so the new
>>>>>>>>>>>>>>> version should
>>>>>>>>>>>>>>> work the same way with the same configuration file.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Make sure you still have
>>>>>>>>>>>>>>> :oauth2_client_id
>>>>>>>>>>>>>>> :oauth2_client_secret
>>>>>>>>>>>>>>> :oauth2_token
>>>>>>>>>>>>>>> :refresh_token
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> defined.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Note, refresh token is a subkey of oauth2_token.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> -Danial, AdWords API Team.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Tuesday, April 14, 2015 at 5:40:10 PM UTC+3, Seth wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> now im getting this
>>>>>>>>>>>>>>>> error AuthenticationError.OAUTH_TOKEN_HEADER_INVALID
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On Tuesday, April 14, 2015 at 10:32:54 AM UTC-4, Danial
>>>>>>>>>>>>>>>> Klimkin wrote:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Please make sure you don't have access_token specified in
>>>>>>>>>>>>>>>>> the adwords_api.yml, just the refresh_token.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> -Danial.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> On Tuesday, April 14, 2015 at 5:26:26 PM UTC+3, Seth wrote:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Ruby
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> On Tuesday, April 14, 2015 at 10:25:34 AM UTC-4, Seth
>>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> google-adwords-api (0.14.2)
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> On Tuesday, April 14, 2015 at 10:21:23 AM UTC-4, Danial
>>>>>>>>>>>>>>>>>>> Klimkin wrote:
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Hello Seth,
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> What client library are you using?
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> -Danial, AdWords API Team.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> On Monday, April 13, 2015 at 11:48:47 PM UTC+3, Seth
>>>>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> Hey,
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> I just updated my app to V201502 a few days ago and
>>>>>>>>>>>>>>>>>>>>> now the access token no longer gets automatically
>>>>>>>>>>>>>>>>>>>>> refreshed. Any idea why
>>>>>>>>>>>>>>>>>>>>> that might be?
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>>>>>>>> Seth
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
--
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 [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].
Visit this group at http://groups.google.com/group/adwords-api.
To view this discussion on the web visit
https://groups.google.com/d/msgid/adwords-api/cf08835f-eb7d-4d50-bbe4-254a0c81f43a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
