DatabasesReact NativeFunctionsREST API

Empty listRows() response

Jan 5, 2026, 04:00Last activity 7 months ago

View on Discord

Votes

Replies

Participants

Messages

SherrizOriginal post

React Developer

Jan 5, 2026, 03:24

Hi there, I'm shehryar, I'm new to react native and appwrite as well, I'm following a tutorial, what's surprising is the listRows({databaseId, tableId, queries}) is returning an empty response like {rows :[], total :0} but on the other hand when i call getRow({databaseId, tableId, rowId}) it works and I get an expected response. I'm not following what I am doing wrong.
i have all permissions checked as well.

🙏 Will appreciate the help.

Summary

User's code was returning an empty array due to querying without checking if the user exists. By updating the code to first check for the user's existence before fetching, the issue was resolved. Additionally, there was a discussion about potential security risks and the analogy of searching for Elon Musk on the moon when he doesn't exist.

Devika

Jan 5, 2026, 07:16

First of all, can you please tell whether that tutorial is new or old? I mean does it mentions old Collection based schema?

Sherriz

Rank 1: Thread

Jan 5, 2026, 07:22

https://stackoverflow.com/questions/79860378/appwrite-new-listrows-is-returning-empty-array-even-with-permissions-granted-i

Sherriz

Rank 1: Thread

Jan 5, 2026, 07:34

Please check this

Sherriz

Rank 1: Thread

Jan 5, 2026, 07:41

it's not collection rather tables I believe.

Devika

Jan 5, 2026, 08:34

I've found something in your code which possibly could be a reason behind this

Devika

Jan 5, 2026, 08:35

You're querying without even checking that if the user exists or not in the first place

Devika

Jan 5, 2026, 08:46

So, try checking for the user first by updating your code like this -

Change no. 1

useEffect(() => {
   fetchHabit();
}, []);

Change no. 2

const fetchHabit = async () => {
  if (!user?.$id) return;

  const response = await databases.listRows({
    databaseId: DATABASE_ID,
    tableId: "habits",
    queries: [Query.equal("createdBy", user.$id)],
  });

  console.log(response);
};

Sherriz

Rank 1: Thread

Jan 5, 2026, 09:13

Okay its working but shouldn't it just give an error if the user doesn't exist since I'm using try catch

Axistro

Jan 5, 2026, 09:39

Thats bad for security.
You dont want anyone to know if a certain user exists or not.

Sherriz

Rank 1: Thread

Jan 5, 2026, 09:40

Definitely but in a dev environment, shouldn't it be throwing an error

Axistro

Jan 5, 2026, 09:41

How could appwrite determine if its a dev build or a production.
Plus when you are doing query, the db does not know what UserId means.
It just says, hey there is no document by this query.

Sherriz

Rank 1: Thread

Jan 5, 2026, 09:44

UserId is something I'm creating from the ID module, secondly if it's a security measure from appwrite I suppose I can wrap my head around it.

Axistro

Jan 5, 2026, 10:00

No
I meant like
You are querying by an atrribute.
It did not throw an error, cause the oparation isself correct.
You tried to fetch something, which may or may not exist.
Like alone in Moon calling elon musk.
Is the calling incorrect?
No
Is elon musk a wrong thing?
No
But no one responded cause there is no elon musk on the moon 😅
The process is correct, the placement is wrong

Sherriz

Rank 1: Thread

Jan 5, 2026, 16:43

Thanks 👍

Join the discussion

Reply to this thread by joining our Discord.

Reply on Discord

Need support?_

Join Discord Get premium support