magic-js: OAuth is not persisted after app restart
✅ Prerequisites
- Did you perform a cursory search of open issues? Is this bug already reported elsewhere?
- Are you running the latest SDK version?
- Are you reporting to the correct repository (
magic-sdk)?
🐛 Description
m.user.isLoggedIn() returns false after successful social log in (Google in my case) and app restart.
🧩 Steps to Reproduce
- Log in using
m.oauth.loginWithPopup({ provider: 'google', redirectURI: REDIRECT_URI }) - Restart the app
- Call
m.user.isLoggedIn()
🤔 Expected behavior
m.user.isLoggedIn() returns true
😮 Actual behavior
m.user.isLoggedIn() returns false
🌎 Environment
| Software | Version(s) |
|---|---|
magic-sdk |
8.1.0 |
| Browser | |
yarn |
1.22.10 |
| Operating System | macOS 12.1, iPhone simulator with iOS 15.2 |
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 29 (13 by maintainers)
Appreciate the update – looking forward to a resolution. Thanks
Hey @pkayfire, I apologize for the misinformation. As promised, we aim to have this problem resolved by the end of this week. The PR is under review, and it’s been our top priority. I’ll notify you once it’s been released to prod. Thank you for your patience!
Got it – thanks for letting us know. Will watch for updates on this issue. Thanks!
got it – thanks for letting me know. We’ll report back if we still encounter the issue.
Hey. There are messages above that people got the same issue on Web. I also see the same in Google Chrome. Please, take a look on this. The issue in Chrome is 100% the same. After reload -
user.isLoggedIn()returnsfalse, so the session is not persisted. This happens only if you use social login (I’ve tried with google auth)My gut feeling is, they are different problems because we don’t receive issues reported from customers who are on a Chrome Desktop. I’ll make sure the OAuth session persistence issue for mobile is completely out of your way first, and then I’ll take a deeper look at the desktop problems.
Hi I just wanted to follow up here to see if your team is on track to release a fix for this issue in the first half of Q4. Thanks!