Hello. We store refresh tokens per user retrieved after OAUTH 2 authentication. We use refresh_token to fetch access_token if it is expired. But recently I noticed that some of our customers get 400 "Bad Request" "invalid_grant" error. While investigating the issue I noticed that refresh_token was expired (or broken), but if you authenticate again you get a new one, and everything starts working again. So my question — is it possible for refresh_token to be expired? Or Google just changed recently the way token was generated? Or maybe we unintentionally corrupted refresh_tokens somehow in our database?
Kind Regards, Petro -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog: https://googleadsdeveloper.blogspot.com/ =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are subscribed to the Google Groups "AdWords API and Google Ads 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 and Google Ads API Forum" group. To unsubscribe from this group and stop receiving emails from it, send an email to adwords-api+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/7f3f9351-2a7b-4b29-b549-e86f6c63068a%40googlegroups.com.
