🐛 Bug Report: All Users.CreateUser... endpoints return a vague server error is null name is provided

TL;DR

[ChiragAgg5k (maintainer)]: This was a server bug, fixed in Appwrite 1.9.0 (PR #11413): create-user endpoints typed name as non-nullable string, so passing name: null threw a vague server error. If you hit it, upgrade to 1.9.0 or newer, or just omit the name field entirely as a workaround.

Steps

1. [ChiragAgg5k (maintainer)]: This was a server bug, fixed in Appwrite 1.9.0 (PR #11413): create-user endpoints typed name as non-nullable string, so passing name: null threw a vague server error. Handlers now accept ?string $name and treat null as empty string. If you hit it, upgrade to 1.9.0 or newer, or just omit the name field entirely as a workaround.

When to use

You are seeing this: https://github.com/appwrite/appwrite/issues/8785: Issue appwrite/appwrite#8785 (closed, 71 comments): ### 👟 Reproduction steps POST to /v1/users or any of the "create user with ___ password" endpoints Create body with a defined UserId, and a name: null. Use this skill when you run into "🐛 Bug Report: All Users.CreateUser... endpoints return a vague server error is null name is provided".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

Versions mentioned in the source: Appwrite 1.9.0. If you are on something much newer or older, the details may have shifted.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Sources

• https://github.com/appwrite/appwrite/issues/8785:

Issue gh:appwrite/appwrite#8785: the reporter asked: Issue appwrite/appwrite#8785 (closed, 71 comments): ### 👟 Reproduction steps

POST to /v1/users or any of the "create user with ___ password" endpoints Create body with a defined UserId, and a name: null. Observe the vague server error

👍 Expected behavior

No server error, should continue creating the user with no name. Name is optional anyway, so specifying it as null should not create this error.

👎 Actual Behavior

[image]

🎲 Appwrite version

Appwrite Cloud

💻 Operating system

Windows

🧱 Your Environment

I am developing my own SDK, hence running into this issue. I can work around it of course, but there shouldn't... The verified answer was: [ChiragAgg5k (maintainer)]: This was a server bug, fixed in Appwrite 1.9.0 (PR #11413): create-user endpoints typed name as non-nullable string, so passing name: null threw a vague server error. Handlers now accept ?string $name and treat null as empty string. If you hit it, upgrade to 1.9.0 or newer, or just omit the name field entirely as a workaround. Evidence thread: https://github.com/appwrite/appwrite/issues/8785