🐛 Bug Report: Collection not found error

[devmarwat]

👟 Reproduction steps

db.ListDocument() with Query parameters but not Attributes yet created in Collection.

👍 Expected behavior

When there is no attribute yet created in Collection, it gives Collection not found error. It should give attribute not found.
Same, when no index is created for Query.search(), it gives no Collection Found error, instead of giving Index not found error.

👎 Actual Behavior

Should give exception of Attribute not created and Index not created.

🎲 Appwrite version

Version 1.2.x

💻 Operating system

Linux

🧱 Your Environment

1.3.7

👀 Have you spent some time to check if this issue has been raised before?

• I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

• I have read the Code of Conduct

[devmarwat]

The same happens when Permissions are not set yet, giving Collection not found.

[joeyouss]

Hi @devmarwat
Your issue template says version 1.2.x but your header says 1.3.7, what is the version on which you are facing this?

[TechComet]

this issue in all versions
+1

[devmarwat]

Hi @devmarwat Your issue template says version 1.2.x but your header says 1.3.7, what is the version on which you are facing this?

1.3.7 is the version

[stnguyen90]

@devmarwat,

it gives no Collection Found error

I'm pretty sure you're seeing this because the user does not have access to the collection. I tested this by giving a user access to the collection and the List Documents API returned with 0 documents as expected.

It's expected to show 404 when the user does not have access to the collection. This is in order to hide the fact that the collection exists.

[stnguyen90]

@devmarwat, have you had a chance to verify the user has access to the collections?

[stnguyen90]

Closing due to inactivity