-
Notifications
You must be signed in to change notification settings - Fork 2.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
federated logins are not getting persisted in browser #71
Comments
A related issue with persistent federated logins is that they should stop working if permission for the app is revoked at FB/G. |
When the app loads, the FB code gets the login status and does nothing with it. The Google code does not appear to be getting the initial status. |
This should be fixed in the latest 0.1.30 that is now published, let us know if you still are running into issues here. We are working on furthering federated support. |
This issue has been automatically locked since there hasn't been any recent activity after it was closed. Please open a new issue for related bugs. Looking for a help forum? We recommend joining the Amplify Community Discord server |
Using a browser and the demo React app...
login with user pool
close tab/visit site again
your session is properly restored
this works as expected
login in with google
close tab/visit site again
session is not restored
I see session data for Google stored in the browser local storage
it is just not being used to restore the session
same happens with facebook.
aws-amplify from 12/14
The text was updated successfully, but these errors were encountered: