React-google-login: Log In not working

[michaelryancaputo]

For some reason all of a sudden log in using this component has stopped this morning. I see that they are deprecating webview logins today, however, I took a peek at the code and it doesn't seem to be using webviews.

Steps to reproduce:
1- pull this repo
2- install it
3- run npm run start
4- try logging in via google

The behaviour i'm seeing is the pop up window shows a 500 error message. Closing sends a "modal window closed" error message to the onFailure callback.

[scandinaro]

I am experiencing the same issue.

[michaelryancaputo]

I've confirmed that my client ID works with this component: https://github.com/kennetpostigo/react-google-login-component

[scandinaro]

@michaelryancaputo I just get Uncaught Object {error: "popup_closed_by_user"} and the console.log within responseGoogle is never called.

[scandinaro]

@michaelryancaputo Actually, the react-google-login-component is working for me now. Thanks!

[trenthogan]

I have been having the same problem this morning.

[pedrofernandezm]

I'm experiencing the same problem

[erlinis]

Same problem here !

[weihuali0509]

I am seeing the same problem as well :(

[modosc]

i'm looking into it now.

[weihuali0509]

@modosc does this solve the issue?
https://github.com/google/google-api-javascript-client/issues/291

[modosc]

it's part of it yes, i'll have the pr up in a few minutes.

[modosc]

see #64

[trenthogan]

@modosc Looking at your code. What was the problem exactly ?

[anthonyjgrove]

published PR to NPM hopefully that fixes it.

[trenthogan]

@anthonyjgrove You should make a new semver tag after the fix. :) https://docs.npmjs.com/getting-started/publishing-npm-packages
See the Updating the package part ☝️

[holyxiaoxin]

@anthonyjgrove can you publish your PR changes to npm please? Thanks.

[AlphaDork]

npm update -f pulled the updates in for me! Works great - Thanks!

[michaelryancaputo]

I agree, this warrants a new semver tag.

[michaelryancaputo]

Yeah... I'm still getting the previous version with running yarn and having to force with the npm update -f command, I can't put this into production (or even staging for that matter) without a semver.

[ghost]

I only need to do:

$ npm update
[email protected] my-react-app
└── [email protected]

And it updates without problems.

I confirm that the update fixes the problem! It works like a charm!!

[adamrmelnyk]

It's a little weird that in master we have 2.8.6 https://github.com/anthonyjgrove/react-google-login/blob/master/package.json#L3
but it's 2.8.7 in npm?

[michaelryancaputo]

Hmm, must not have committed the changes?

[anthonyjgrove]

I am not currently using this in any of my projects at the moment. Are any of you interested in being added as a collaborator to help me maintain this package?

[trenthogan]

@anthonyjgrove Sure