Hi All,
On accessing properties of payload showing undefined on Appwrite cloud using node.js server sdk
Data:
messageFor: 'web',
token: 'test-token',
userToken: 'test-user-token',
deviceToken: 'test-device-token'
}```
Sample Code:
```module.exports = async function (req, res) {
const payload = req.payload;
res.json({
messageFor: 'messageFor - ' + payload.messageFor,
token: 'token - ' + payload.token,
userToken: 'userToken - ' + payload.userToken,
deviceToken: 'deviceToken - ' + payload.deviceToken,
});```
Sample Response:
```{
"messageFor":"messageFor - undefined",
"token":"token - undefined",
"userToken":"userToken - undefined",
"deviceToken":"deviceToken - undefined"
}```
On accessing properties of payload showing undefined
req.payload is a string. You'll need to parse it
As per your suggestion, I have implemented the same but getting the below error.
Updated Sample Code
module.exports = async function (req, res) {
const payload = JSON.parse(req.payload);
res.json({
messageFor: 'messageFor - ' + payload.messageFor,
token: 'token - ' + payload.token,
userToken: 'userToken - ' + payload.userToken,
deviceToken: 'deviceToken - ' + payload.deviceToken,
});
Error Response
SyntaxError: Unexpected token m in JSON at position 10
at JSON.parse (<anonymous>)
at module.exports (/usr/code-start/src/index.js:126:24)
at /usr/local/src/server.js:68:19
at processTicksAndRejections (node:internal/process/task_queues:96:5)
I have google it and found it seems might be due to incorrect json string but couldn't able to identify where I am missing it
the data you're passing into the function is not valid JSON. you must wrap keys with double quotes
It worked! Thanks 🫡
Actually, I followed the sample JSON provided while executing from the console. Their keys are not wrapped with double quotes. Hope it will be fixed
yes, it has already been fixed in a newer version of Appwrite
[SOLVED] On accessing properties of payload showing undefined
Recommended threads
- 408 Timeout / Curl Error 7 in Executor w...
Hey everyone, I am losing my mind over a routing loop/timeout issue on a fresh self-hosted setup. I have a single Linux VPS (IP: 45.141.37.105) and one domain (...
- functions returning error 401 in local
I updated to 1.9.0, and the functions that used to work fine in 1.8.1 are now giving me a 401 error. I can't seem to find a solution. If anyone is running versi...
- router_deployment_not_found
I updated my function a few times and now i am getting the error: router_deployment_not_found I even reverted back to my original code but i am still getting th...