Understanding Permissions: Read error when a collection has "any" can "read"
- 0
- React Native
- Cloud
Heya,
I'm messing around with RN and Cloud hosted Appwrite at the moment, and have run into an issue with permissions.
I get the error "The current user is not authorized to perform the requested action" when trying to read all documents in a collection.
The collection has the permission "any" and "read", so I'm not entirely sure where I'm going wrong here.
Here's my collection setup:
{
"$id": "66f541aa0039ba252fa9",
"$permissions": [
"read(\"any\")"
],
"databaseId": "66f4877d00384273b485",
"name": "Questions",
"enabled": true,
"documentSecurity": false,
"attributes": [
{
"key": "question",
"type": "string",
"required": true,
"array": false,
"size": 200,
"default": null
},
{
"key": "entries",
"type": "relationship",
"required": false,
"array": false,
"relatedCollection": "66f487b700228e45ca0f",
"relationType": "manyToOne",
"twoWay": true,
"twoWayKey": "questions",
"onDelete": "cascade",
"side": "child"
}
],
"indexes": []
}
I do not have "database security" enabled, but from my understanding, it doesn't need to be?
My code (slimmed down) is essentially:
const client = new Client();
client
.setEndpoint(appwriteConfig.endpoint)
.setProject(appwriteConfig.project)
.setPlatform(appwriteConfig.platform);
const account = new Account(client);
const databases = new Databases(client);
const questions = await databases.listDocuments(
appwriteConfig.databaseId,
appwriteConfig.questionsCollectionId
);
Recommended threads
- Functions not executing after usage rese...
Hi team, Last month my project hit 100% usage and functions stopped working (expected). Now the new month has started and usage has reset, requests are going ...
- Functions never end and always fail (sta...
Hi ! I'm using Appwrite Cloud Pro and function execution from appwrite website is KO. Deploying starter function template, execution is always Failed and the ...
- My function executions console if overwh...
It seems the requests are getting processed correctly but it is using a older version of the backend. And it seems the cron requests done an hour ago are shown ...