You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on May 13, 2019. It is now read-only.
Repository navigation
This repository was archived by the owner on May 13, 2019. It is now read-only.
Is {{CLIENT_ID}} what you are seeing or have you configured your actual client ID in client_secrets.json? If you run curl localhost:4567 | grep -i "data-clientId=" are you seeing your client ID correctly?
Yes, I set it in the json file. I have since discovered that the client
credentials don't work if set up from my Google Apps account, but it works
fine from a vanilla Google account. I have raised an issue in the Google
code project mentioning this.
On 6 Jan 2014 18:18, "Gus Class" notifications@github.com wrote:
Is {{CLIENT_ID}} what you are seeing or have you configured your actual
client ID in client_secrets.json?
—
Reply to this email directly or view it on GitHubhttps://github.com//issues/10#issuecomment-31671901
.
Hi @cartland, sorry for the delay in responding. I eventually worked out what was causing the problem I was seeing - even if I can't understand why.
The issue seems to occur when you try to log in to an application that uses OAuth twice using the same Google account without signing out in between. This could be either because the browser window was closed and then reopened, so any session was lost, or it could be that the user is logging in from multiple devices simultaneously.
Activity
cartland commentedon Dec 17, 2013
Can you tell me the URL in the browser when you see the error? Feel free to remove the client ID from the URL before sharing.
mrpotes commentedon Dec 18, 2013
@cartland the URL is:
cartland commentedon Dec 18, 2013
@mrpotes have you turned on the Google+ API? This is in the API section.
mrpotes commentedon Dec 20, 2013
@cartland I hadn't, but have just retried with it turned on and still get the same response.
gguuss commentedon Jan 6, 2014
Is {{CLIENT_ID}} what you are seeing or have you configured your actual client ID in client_secrets.json? If you run
curl localhost:4567 | grep -i "data-clientId="are you seeing your client ID correctly?mrpotes commentedon Jan 6, 2014
Yes, I set it in the json file. I have since discovered that the client
credentials don't work if set up from my Google Apps account, but it works
fine from a vanilla Google account. I have raised an issue in the Google
code project mentioning this.
On 6 Jan 2014 18:18, "Gus Class" notifications@github.com wrote:
cartland commentedon Feb 27, 2014
@mrpotes does this work from each of your accounts now?
mrpotes commentedon Mar 4, 2014
Hi @cartland, sorry for the delay in responding. I eventually worked out what was causing the problem I was seeing - even if I can't understand why.
The issue seems to occur when you try to log in to an application that uses OAuth twice using the same Google account without signing out in between. This could be either because the browser window was closed and then reopened, so any session was lost, or it could be that the user is logging in from multiple devices simultaneously.
mrpotes commentedon May 27, 2014
Hi @cartland, I was just wondering if you had any insight into this issue, as it's still a problem?
gguuss commentedon Jun 9, 2015
@mrpotes - have you tried using an incognito window on the page that is causing the problem?