# 🐛 Bug Report: All Users.CreateUser... endpoints return a vague server error is null name is provided
[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.
## Context from the issue
gh:appwrite/appwrite#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`.
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...