later use.
return $oauthInfo['refresh_token'];
On Tuesday, January 28, 2014 11:49:27 AM UTC-8, Pere Kyle wrote:
>
> Danial,
>
> It seems it may be related to the google api javascript library and
> specifically using the postback option. I am requesting an auth_code v
Danial,
It seems it may be related to the google api javascript library and
specifically using the postback option. I am requesting an auth_code via a
postback on the js side, then getting a refresh token using the php library
on server side. Should I degrade use of the postback option?
Thanks
Tuesday, January 21, 2014 2:41:13 AM UTC-8, Danial Klimkin wrote:
>
> Hello Pere,
>
>
> Do you get the same error if you provide *only* AdWords scope? Can you
> combine those calls to have a shared refresh token for both GA and AdWords
> API?
>
>
> -Danial, AdWords
Anyone?
On Thursday, January 16, 2014 5:23:43 PM UTC-8, Pere Kyle wrote:
>
> This issue is still live, and it seems to only affect my oauth login when
> using the adwords scope.
>
> On Wednesday, January 15, 2014 12:32:36 PM UTC-8, Pere Kyle wrote:
>>
>> Since about th
This issue is still live, and it seems to only affect my oauth login when
using the adwords scope.
On Wednesday, January 15, 2014 12:32:36 PM UTC-8, Pere Kyle wrote:
>
> Since about the beginning of december the oauth flow for our app has been
> broken. It previously worked for ~3 mo
Since about the beginning of december the oauth flow for our app has been
broken. It previously worked for ~3 months with no changes. It seems to
have coincided with the new permission page for oauth and only affects
functionality after an adwords token has been granted.
Steps to reproduce:
var
