[SOLVED] Invalid, chaotic database responses after update to 1.3

Yes, I have.

All users can create documents. Other things handles document level security.

Out of curiosity, could you do following?

• Disable document security
• Add read permission to any

With those changes, does offset still miss-behave?

On my end, offset seems to behave as expected. With 685 documents and offset of 600, I get 85 documents.

Thank you. Please give me 10 minutes please. I must do something first.

Sorry for waiting. Other problems aroused.

Yeah. Like this it works. Seems to be the case with document level security.

Another thing. I don't know if I am not doing something wrong. But It seems to be that I received only 852 documents with unique ids. Because the two received I already have in my map of elements {docId: value}. So 2 documents I didn't received.

But why It wouldn't work for a new project in the appwrite instance?

@Jake any idea if 1.3 could be affecting counting and offset pagination of document that have document-security enabled?

I am also having this issue, receiving 1 or 2 documents less in request.

• If I call list documents with equal query for specific attribute I always receive all documents
• If I list documents without query it is always missing some documents in response
• Currently I don't have more than 10 documents per user in collections, but if I use limit query >= 40 I get all the documents, otherwise if limit query < 40 or if I don't include it - response is always missing some documents. I have no idea why 40, was just trying bunch of stuff while debugging these issues and somehow bigger query limit on list documents returns everything 🤷‍♂️

I am using android and ios sdk - same results on both.

It's possible, will take a look

That could all be related to bug in document security. Let's wait and see if Jake can spot any issue in the 1.3 codebase.

@Jake I can confirm this is indeed bug with 1.3 and document security. I believe this will be worth 1.3.2 release.

Yep same here, looking into a fix

Any update on the issue?

@Meldiron sorry for tagging. But I am a lot dependent on fixing this. Without this, everything breaks for me.
Do you have please some information when I could expect the fix?

I believe this is a high priority. Let's wait for @Jake on this.

That would be great. Thank you for responding.

@Argel, apologies for the delay. We've found the problem and are working through the fix. It's kind of big so it's taking some time. We'll give an ETA in a couple days after we make some more changes and write some more tests.

No, problem. I was just quite nervous: no backup, need to submit it soon, app synchronization broken, almost zero experience.

Take your time to deliver fantastic software ❤️ . Downgrading to 1.2 worked, so I am fine.

Thank you for the info.

[SOLVED] Invalid, chaotic database responses after update to 1.3

We just released 1.3.2! See https://discord.com/channels/564160730845151244/636818236310159360/1101246221089263617

Thanks for the info 🙂