#Server Error at Client

1 messages · Page 1 of 1 (latest)

simple glen
#

Hello 🙂 When I am trying to create a user document in my user database during registration (any can create) it successfuly creates the document but according to the console it fails during
const newDocument = await databases.createDocument(databaseId, collectionId, documentId, data);
with a Error 500 and then throws an error

    at Client.<anonymous> (```

Logs state:
```Method: GET
2024-04-29T15:33:23.653360420Z [Error] URL: /v1/account
2024-04-29T15:33:23.653365730Z [Error] Type: Appwrite\Extend\Exception
2024-04-29T15:33:23.653371320Z [Error] Message: User (role: guests) missing scope (account)
2024-04-29T15:33:23.653376472Z [Error] File: /usr/src/code/app/controllers/shared/api.php
2024-04-29T15:33:23.653380947Z [Error] Line: 273```

Is this error due to creating a document without an active session? Can this be safely ignored or is there anyway around this/best practice how to store newAccounts in the Database?
eternal heath
#

Make sure to use three backticks ` to format code blocks to make it easier to read

The logs usually mean you aren't signed in

simple glen
forest swift
#
  1. make sure the permissions are correct, any for create, update, reqd, delete. this isn't secure though. fine for testing.
  2. log the user in, if the permissions only allow performing crud ops. for users, guests, etc.
simple glen
# forest swift 1. make sure the permissions are correct, any for create, update, reqd, delete. ...
  1. I only applied Create for any, not update, read, delete - just creating should be fine, is like a signup no? Or still a safety issue?
  2. Issue I am having is, I do not know how else to do it. User Data needs to be stored in the user Database. All the tutorials I found online usually create the User in the DB during the registration and store it in the DB. It makes sense to me because this way Auth Database and User Database are always synchronous. THe only alternative I can think of is checking on login if the user exists in the database and creating it if not, but that also seems quite inefficient no?