Login does not persist (again)
See original GitHub issueIt looks like issue #69 is back (or maybe it was never fully fixed?). I’m initializing the component as follows and finding that every page load, even a soft refresh, requires users to complete the OAuth consent prompt.
Any thoughts or hints? I’m using v3.2.0.
<GoogleLogin
clientId={MY_CLIENT_ID}
buttonText="Login with Google"
responseType={"id_token"}
accessType={"offline"}
onSuccess={this.loginSuccess}
onFailure={this.loginFailure}
prompt={"consent"}
/>
Issue Analytics
- State:
- Created 5 years ago
- Reactions:3
- Comments:7 (1 by maintainers)
Top Results From Across the Web
Laravel Auth:attempt() will not persist login
I had this problem. Changing primary key for user model helped for me. Try to add something like protected $primaryKey = 'user_id';.
Read more >persistent login does not work [#105289]
I found that the persistent login does not work properly. The users see that they are logged out if they close the current...
Read more >Fix sign-in problems - Chromebook Help
If you have trouble signing in to your Chromebook with your Google Account, try the steps below. Fix email or password problems.
Read more >React Persistent User Login Authentication with JWT Tokens
Learn how to add persistent user login authentication with JWT tokens to your React app. We will not store JWT tokens in local...
Read more >How to force a public Wi-Fi network login page to open
Here's how to force the Wi-Fi login page to open on your computer, phone, ... If that doesn't work, open your network settings...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I added the
isSignedIn={true}
prop and it called my onsuccess handler on refresh.Unfortunately, I found out that if the user is signed out however, there is no way to detect that 😢