-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
馃悰 Bug Report: OAuth Login Fails if Browser Session Already Exists for Another User #7021
Comments
Maintainer could you please assign the issue to me? I would like to work on it. |
This issue will occur on clearing app data as well. |
can i work on this? |
馃憻 Reproduction steps
馃憤 Expected behavior
There is nothing wrong with actual behavior, but I believe additional steps are necessary; otherwise, it may become challenging for the user to log back in. There are two potential solutions:
Upon reinstallation, programmatically enable the creation of a new in-app session for an existing browser session, if possible.
Provide a method for detecting the currently active browser session because there is no other way for the user to log in with an identity linked to a different user. Please note that
account.deleteSession(sessionId: 'current')
andaccount.deleteSessions()
result in an error.馃憥 Actual Behavior
Error
user_already_exists
with code 409.馃幉 Appwrite version
Version 1.4.x
馃捇 Operating system
Linux
馃П Your Environment
Appwrite Instance - 1.4.3
Appwrite Flutter SDK - 11.0.0
馃憖 Have you spent some time to check if this issue has been raised before?
馃彚 Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: