The current user is not authorized to perform the requested action (401)
- 0
- Android
- Flutter
- Databases
- Auth
I want to create a document associated with user after log in with OAuth. The user were logged in, but Appwrite said user is unauthorized. User is logged in with Google Oauth. When I want to get the document user is associated with after that, appwrite returned this.
I/flutter (26735): session created
I/flutter (26735): 2
I/flutter (26735): Check user document
I/flutter (26735): Get user document
I/flutter (26735): <my name> 675b1cd649fddd34b9b8 2024-12-12T17:26:46.304+00:00
I/flutter (26735): get document by id
I/flutter (26735): AppwriteException: user_unauthorized, The current user is not authorized to perform the requested action. (401)
When I hover over the user id in document's permission, it return the correct user. Here are the functions
print("Get user document");
print("${_currentUser.name} ${_currentUser.$id} ${_currentUser.$createdAt}"); // Here it print the current user info, which are correct
String id = _currentUser.$id;
return await DatabaseAPI().getUserDocumentById(id);
}```
``` Future<Document> getUserDocumentById(String id) async {
print("get document by id");
try {
await account.get();
return await databases.getDocument(
databaseId: DATABASE_ID,
collectionId: USERS_COLLECTION_ID,
documentId: id,
); // <-- this said user is unauthorized
} catch (e) {
print(e.toString());
return await createBlankDocument(id);
}
}```
Since I keep logging in and out because of this, I'm not sure will this affect my account.
Recommended threads
- general_route_not_found - Auth Guide
If you’ve just added a subdomain to your project, verified your DNS records, and confirmed your SSL certificate is working, but you're still hitting a `general_...
- Impossible to get USER after createEmail...
Am using provider to deal with functions linked to appwrite. Here is my login. Future<String?> login(String email, String password) async { try { aw...
- User ID case sensitivity
I see that through REST (and SDK as well), getting a user is not case sensitive. And even though documentation does not clearly state that it is, the wording "V...