-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
🐛 Bug Report: Google auth Appwriteexception: user (role: guests) missing scope
#7875
Comments
ppwriteexception: user (role: guests) missing
Appwriteexception: user (role: guests) missing
Appwriteexception: user (role: guests) missing
Appwriteexception: user (role: guests) missing scope
I have the same issue as well.
|
Are you trying to do a SSR call? |
no. Its normal client-side call in next.js app |
Can you create a new topic in discord? I don't think this is a bug, but it's easier and faster to check in discord |
This issue has been labeled as a 'question', indicating that it requires additional information from the requestor. It has been inactive for 7 days. If no further activity occurs, this issue will be closed in 14 days. |
👟 Reproduction steps
I am following the official docs to create a google OAuth login flow using the AppWrite 1.5.4 version.
once the user is logged in using google sign-in page, the flow redirects to appwrite's callback URL with token etc and it remains there and throws
there is error: AppwriteException: User (role: guests) missing scope (account)
👍 Expected behavior
It should do below:
👎 Actual Behavior
once the user is logged in using Google sign-in page, the flow redirects to appwrite's callback URL with token, etc and it remains there and throws
there is error: AppwriteException: User (role: guests) missing scope (account)
🎲 Appwrite version
Version 1.5.x
💻 Operating system
Linux
🧱 Your Environment
Appwrite version: 1.5.4
front-end: Next.Js
👀 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: