Back

Ghost user?

  • 0
  • Self Hosted
  • Accounts
  • Users
rbiut
6 Feb, 2024, 04:09

I have this strange situation, i have 4 users, two of them has the label "owner" other two has the label "admin" and its data seems consistent, but for some reason one user is a "ghost" for any search term, im using php to get list of users, examples:

if i do this: var_dump($usersow->list()); appwrite return my 4 users if i do this: var_dump($usersow->list([],'admin')); appwrite return the two users that has "admin" label but, if i do this: var_dump($usersow->list([],'owner')); appwrite only return one user that has the 'owner' label, but there are two users with 'owner' label any other valid search term return the user but not the same user that do no list with the 'owner' label, in resume one user (user 3 in array) do not return with any search term, here is the array data of the two users with 'owner' label:

User 2:

TypeScript
$id: "xxxxxx"
$createdAt: "2024-01-25T19:36:38.934+00:00"
$updatedAt: "2024-01-25T20:52:43.031+00:00"
name: "Demo"
password: [Hashed Password]
hash: "argon2"
hashOptions: [Array of Hash Options]
registration: "2024-01-25T19:36:38.932+00:00"
status: true
labels: ["owner"]
passwordUpdate: "2024-01-25T19:36:38.932+00:00"
email: "t@t.com"
phone: "+229876543210"
emailVerification: false
phoneVerification: false
prefs: [Empty Array]
accessedAt: ""

User 3:

TypeScript
$id: "yyyyyyyyyyyyyyyyy"
$createdAt: "2024-02-02T03:48:03.150+00:00"
$updatedAt: "2024-02-02T03:48:03.239+00:00"
name: "demo80"
password: [Hashed Password]
hash: "argon2"
hashOptions: [Array of Hash Options]
registration: "2024-02-02T03:48:03.148+00:00"
status: true
labels: ["owner"]
passwordUpdate: "2024-02-02T03:48:03.148+00:00"
email: "f@f.com"
phone: "+221234567890"
emailVerification: false
phoneVerification: false
prefs: [Empty Array]
accessedAt: ""
TL;DR
The developer is experiencing an issue with a "ghost" user in an app using Appwrite. The search column of the problematic user does not return any results even though it has valid search terms. The user is only listed if an empty list is requested. The developer has provided data for two users with the "owner" label, but only one of them is returning in the search results. The issue persists even after manually editing the users in the Appwrite console. Solution: The developer should check the database directly to see the value of the search column for the problematic user. They should also ensure they are using the latest version of Appwrite
rbiut
6 Feb, 2024, 04:13

in this case, user 3 is the "ghost" all users are returned with any real search term, but is not possible to list user 3 with any valid search terms like "f@f.com", "+521234567890", "demo80", "owner", the user 3 is only listed if i do a empty list().... why? my appwrite version is 1.4.13 using latest php-sdk

rbiut
6 Feb, 2024, 04:25

actually, appwrite dashboard console do not return the user neither if i search for it, it only show it without any search term

Steven
6 Feb, 2024, 04:27

maybe you can look at the user in the database. there should be a search column. what's that value for the users?

rbiut
6 Feb, 2024, 04:30

i manually re-edited (in appwrite console) both demo users, and now i cant search for any of them

rbiut
6 Feb, 2024, 04:30

users are here

rbiut
6 Feb, 2024, 04:31

but if i search for them they are not returned

rbiut
6 Feb, 2024, 04:31
rbiut
6 Feb, 2024, 04:34

where is exactly the search column? i cant see it on the auth (in console)

rbiut
6 Feb, 2024, 04:51

i search directly on mariadb and the search column of the problematic users shows this: user 3: search: xxxxxxxxxxxxxxxxxxx testuser@google.com Usuario Demo +229876543210 label:owner user 4: search: yyyyyyyyyyyyyyyyyyy f@f.com demo80 +221234567890 label:owner

rbiut
6 Feb, 2024, 04:52

so, search column is not empty for any of those users

Reply

Reply to this thread by joining our Discord

Reply on Discord

Need support?

Join our Discord

Get community support by joining our Discord server.

Join Discord

Get premium support

Join Appwrite Pro and get email support from our team.

Learn more