Facebook credentials are not refreshed
See original GitHub issueDescribe the bug
Facebook credentials don’t refresh in version 1.0.11
. And any API requests just hang.
To Reproduce Steps to reproduce the behavior:
- Implement login with Facebook using Amplify.
- Login is successful.
- After credentials expire Amplify tries to refresh it but just hangs.
Expected behavior Facebook credentials should be refreshed.
Screenshots
Desktop (please complete the following information):
- OS: macOS
- Browser Safari
- Version 11.1.2
The code to test is available in this repo - https://github.com/AnomalyInnovations/serverless-stack-demo-fb-login-client
Issue Analytics
- State:
- Created 5 years ago
- Comments:7 (3 by maintainers)
Top Results From Across the Web
I'm seeing an "Incorrect Password" error message ... - Facebook
If you see an error message saying "Incorrect Password" and you're sure you entered the right password: Remember that passwords are case ...
Read more >Facebook token is not automatically refreshing #4819 - GitHub
Describe the bug We are logging in users with Auth.federatedSignIn({ provider: "Facebook" }); and the login expires after 60 minutes.
Read more >“Something Went Wrong” Error On Facebook [Updated Fixes]
"Sorry, something went wrong" error making it hard for you to log into Facebook ? We'll tell you how to fix this problem...
Read more >Troubleshoot Facebook - Hookle
The browser might remember the credentials of your previously logged Facebook accounts. Thus, make sure you authenticate and reconnect accounts ...
Read more >Reauthorizing the connection between Buffer and Facebook ...
Checking your admin status; Checking your Facebook connection permissions; Removing Buffer from Facebook and refreshing the connection. If you ...
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
@powerful23 It seems like the issue is fixed with the latest release I tried (
1.1.13
). I’m not able to reproduce it. I think we can close this.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
*-help
channels or Discussions for those types of questions.