-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Google Sign-In now returning error popup_closed_by_user #506
Comments
I'm encountering the exact same issue with Electron. Working fine on Chrome. |
Same exact issue with Electron starting on Feb 6th. No changes were made to our end. |
I do not seem to see recent changes to the gapi client. |
Just like to chip in here and say we're experiencing the |
Hi, We do have the same issue. EDIT : this issue affects only users who have to signIn, already connected ones are not affected. |
Hello, Same for our project, React app running in electron gives We use |
Hi, Also can report that this is no longer working for our electron app, but is working fine in any browser. |
Any updates here? @grant |
@JorgenPhi If there a specific something specific I can do, LMK. However, I cannot debug other projects that use this project like Electron. |
@grant |
@grant It is unlikely that this change is anything other than a change to the auth api given the steps we took to verify the issue and the google authentication being the only common factor. Was something changed in policies? Is this a part/byproduct of the g+ shutdown (we are in the process of removing g+ for auth and profile info)? Our project uses electron-prebuilt and was tested against 3.x and 4.x builds. All fail with the same error. Apologies for the callout, we have thousands of users affected by this and having some support would be great. |
This may be related. Or not at all. Timeline coincides. https://developers.google.com/terms/api-services-user-data-policy |
Any update about this issue? I'm also having the same problem |
I have notified the Google team this issue. |
If what @bodhi3032 mentioned is true, then migrating to the alternative oauth scopes may help. https://developers.google.com/identity/sign-in/web/quick-migration-guide |
@SatoshiOoO My app has always been using the alternative scopes and wasn't using the G+ scopes nor the G+ specific APIs, but instead the generic Google Sign-In APIs which haven't been deprecated. This issue is also only affecting our Electron app, but not our website login which continues to work fine. The issue may definitely still be the result of an inadvertent change made alongside the G+ login/changes, but not likely due to lack of a migration needed on our side. |
I'd generally agree with @sachinrekhi that this is not g+ shutdown related, as our web (which also uses g+) still works. Also if you check G's own docs, you'll find there appears to have issues as well: https://developers.google.com/identity/protocols/OAuth2UserAgent Click the demo link, you'll see the auth is busted there. So i think this is a policy issue, perhaps G itself didn't realize the full ramifications of the last updates. My guess is it may have to do with this (from the policy update link i posted earlier):
Whoever initially set this up on our project did so for web, and indeed the electron app follows the browser flows but using electron generated windows, though it does handle via the website (anyone else find this stuff overly convoluted at times?). I am wondering if perhaps something in this flow is failing the above criteria of Which brings back to the My next step is to look at migrating to the Desktop Flow for oauth. I'm curious if others affected here used the web browser flow or desktop, or some variation thereof? Best of luck everyone, I will post back my results when I have some. |
@bodhi3032 I’m using the web browser flow in both our web client and Electron client. Can you link to the docs for the desktop flow? |
OK, good news, looks like they fixed the problem, now it works as expected with no changes on our side. Check your apps ;-) |
I can confirm it's working now in our Electron app. |
Same for us. Great news !! |
Same here! \o/ |
Same, Thanks for the fix!! |
I can also confirm that Google login is once again working in our Electron app without any required changes. Thanks so much! |
While it's nice that all is working again, the fact it went down and there was no acknowledgement of the issue or report of findings is troublesome. I for one will be looking to adapt user flows to mitigate such outages, but the trade off is more friction in the sign up process. Keeping the devs who use such platforms in the loop is important in maintaining trust and building community support. But hurrah? i guess.. |
I think it came back. I'm experiencing the same issue in Brave browser, but not in Chrome not Firefox. |
i get this issue today using Chromium - Version 76.0.3809.100 |
The error is present on Version 78.0.3904.108 (Official Build) (64-bit) |
OK. I was hitting this issue and realized the bug might be in the original code. Anyone care to verify this address the error? Original: var googleAuth
gapi.load('auth2', function() {
googleAuth = gapi.auth2.init({
client_id: 'XXX',
scope: 'email profile',
fetch_basic_profile: false
})
})
function beginGoogleAuth() {
googleAuth.grantOfflineAccess({
prompt: 'select_account',
redirect_uri: 'postmessage'
}).then(function(response) {
document.getElementById('login-google-auth-code').value = response.code
document.getElementById('login-form').submit()
})
} Fix is to use the var googleAuth
gapi.load('auth2', function() {
googleAuth = gapi.auth2.init({
client_id: 'XXX',
scope: 'email profile',
fetch_basic_profile: false
})
})
function beginGoogleAuth() {
googleAuth.grantOfflineAccess({
prompt: 'select_account',
redirect_uri: 'postmessage'
}).then(function(response) {
document.getElementById('login-google-auth-code').value = response.code
document.getElementById('login-form').submit()
}).catch(function(error) {
console.log(error)
})
} |
Hi All, I have a react app, when run locally everything works fine but when I build the project using "yarn build" and move the contents of build folder to aws s3 bucket and enable static hosting, it fails and says "popup_closed_by_user". I have made sure all the necessary URL have been whitelisted in the oauth credentials side. But still it says that s3 bucker URL is not whitelisted. Thanks in advance. |
Seems to be happening again. Same symptoms as listed previously. Everything works fine in chrome, but is busted in electron. |
Hey, I'm also facing the same issue, it works in my machine but not working in my colleague's machine, please help me to fix this. |
For those still struggling with the |
It also happens in React App all browsers with me |
@edouardmercier thank you so much! That fixed the issue for us on electron! |
I'm also facing the same issue with Electron. Working fine on Chrome. |
I can verify this works, thank you for this 👍 |
thanks @edouardmercier |
I'm getting this error even in chrome if I login in incognito tab. I'm using the following code
|
Facing the same issue in react app in all browser. Someone please help. |
For authentication/authorization issues please note that gapi.auth2 has been deprecated and replaced with Google Identity Services. See https://developers.googleblog.com/2021/08/gsi-jsweb-deprecation.html for more information. If you have questions related to authentication/authorization please look at the associated documentation or post questions on Stack Overflow with the google-oauth tag. |
You can use google loign npm. Module and just pass clientId and secret id
…On Tue, 17 May, 2022, 10:05 Sai Swaroop Bedamatta, ***@***.***> wrote:
Facing the same issue in react app in all browser. Someone please help.
—
Reply to this email directly, view it on GitHub
<#506 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AMUTJQSTSUDXU6AOR7PNDTTVKMOXNANCNFSM4GWJQF4A>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Are you taking about “https://www.npmjs.com/package/react-google-login”
this one ??
On Sat, 21 May 2022 at 1:21 PM, Neeraj ***@***.***> wrote:
You can use google loign npm. Module and just pass clientId and secret id
On Tue, 17 May, 2022, 10:05 Sai Swaroop Bedamatta, ***@***.***>
wrote:
> Facing the same issue in react app in all browser. Someone please help.
>
> —
> Reply to this email directly, view it on GitHub
> <
#506 (comment)
>,
> or unsubscribe
> <
https://github.com/notifications/unsubscribe-auth/AMUTJQSTSUDXU6AOR7PNDTTVKMOXNANCNFSM4GWJQF4A
>
> .
> You are receiving this because you commented.Message ID:
> ***@***.***>
>
—
Reply to this email directly, view it on GitHub
<#506 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AI3TIWJ6OPYULSNEUSDMDILVLCIXNANCNFSM4GWJQF4A>
.
You are receiving this because you commented.Message ID:
***@***.***>
--
Sai Swaroop Bedamatta
|
Yes, it is.
On Sat, 21 May, 2022, 15:42 Sai Swaroop Bedamatta, ***@***.***>
wrote:
… Are you taking about “https://www.npmjs.com/package/react-google-login”
this one ??
On Sat, 21 May 2022 at 1:21 PM, Neeraj ***@***.***> wrote:
> You can use google loign npm. Module and just pass clientId and secret id
>
>
> On Tue, 17 May, 2022, 10:05 Sai Swaroop Bedamatta, ***@***.***>
> wrote:
>
> > Facing the same issue in react app in all browser. Someone please help.
> >
> > —
> > Reply to this email directly, view it on GitHub
> > <
>
#506 (comment)
> >,
> > or unsubscribe
> > <
>
https://github.com/notifications/unsubscribe-auth/AMUTJQSTSUDXU6AOR7PNDTTVKMOXNANCNFSM4GWJQF4A
> >
> > .
> > You are receiving this because you commented.Message ID:
> > ***@***.***>
> >
>
> —
> Reply to this email directly, view it on GitHub
> <
#506 (comment)
>,
> or unsubscribe
> <
https://github.com/notifications/unsubscribe-auth/AI3TIWJ6OPYULSNEUSDMDILVLCIXNANCNFSM4GWJQF4A
>
> .
> You are receiving this because you commented.Message ID:
> ***@***.***>
>
--
Sai Swaroop Bedamatta
—
Reply to this email directly, view it on GitHub
<#506 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AMUTJQVP2ULDXD5GFCIV32TVLCZHXANCNFSM4GWJQF4A>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Can you please tell me google login issue you are facing in development
mode or production mode.
If you are facing in development mode/production mode , it means you need
to set in
webPresences:{
nodeIntegration:true,
nativeWindowOpen:true,
webSecurity:false
}
in electron.js file
If again it is not fixed then you need implement through deeplinking
By the use of electron.shell
Thanks and Regards
Neeraj Maurya
MERN Stack Developer
…On Tue, 24 May, 2022, 15:02 Neeraj Moriya, ***@***.***> wrote:
Yes, it is.
On Sat, 21 May, 2022, 15:42 Sai Swaroop Bedamatta, <
***@***.***> wrote:
> Are you taking about “https://www.npmjs.com/package/react-google-login”
> this one ??
>
>
> On Sat, 21 May 2022 at 1:21 PM, Neeraj ***@***.***> wrote:
>
> > You can use google loign npm. Module and just pass clientId and secret
> id
> >
> >
> > On Tue, 17 May, 2022, 10:05 Sai Swaroop Bedamatta, ***@***.***>
> > wrote:
> >
> > > Facing the same issue in react app in all browser. Someone please
> help.
> > >
> > > —
> > > Reply to this email directly, view it on GitHub
> > > <
> >
> #506 (comment)
> > >,
> > > or unsubscribe
> > > <
> >
> https://github.com/notifications/unsubscribe-auth/AMUTJQSTSUDXU6AOR7PNDTTVKMOXNANCNFSM4GWJQF4A
> > >
> > > .
> > > You are receiving this because you commented.Message ID:
> > > ***@***.***>
> > >
> >
> > —
> > Reply to this email directly, view it on GitHub
> > <
> #506 (comment)
> >,
> > or unsubscribe
> > <
> https://github.com/notifications/unsubscribe-auth/AI3TIWJ6OPYULSNEUSDMDILVLCIXNANCNFSM4GWJQF4A
> >
> > .
> > You are receiving this because you commented.Message ID:
> > ***@***.***>
> >
> --
> Sai Swaroop Bedamatta
>
> —
> Reply to this email directly, view it on GitHub
> <#506 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AMUTJQVP2ULDXD5GFCIV32TVLCZHXANCNFSM4GWJQF4A>
> .
> You are receiving this because you commented.Message ID:
> ***@***.***>
>
|
Our Electron desktop application has been using Google Sign-In for months now without any issues. But all of a sudden, starting today, Google Sign-In from our Electron desktop app started returning the "popup_closed_by_user" error. The login pop-up properly renders and you can successfully login to your Google account, but when the pop-up closes, instead of it properly logging in the user, it returns the popup_closed_by_user error.
Google Sign-In continues to work fine for our website from web browsers like Chrome, Safari, and Firefox, but no longer works from our Electron desktop app.
It appears there has been some kind of regression in the Google Sign-In service?
Our google auth code for reference:
The text was updated successfully, but these errors were encountered: