You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
According to the documentation, It should create the function.
👎 Actual Behavior
When I run npm run start, the creation of a function responds to an error:
Running Create Function API
AppwriteException [Error]: Invalid execute: Roles must be an array of strings.
at Client.call (/Applications/Back/playground-for-node/node_modules/node-appwrite/lib/client.js:172:31)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async Functions.create (/Applications/Back/playground-for-node/node_modules/node-appwrite/lib/services/functions.js:111:16)
at async createFunction (/Applications/Back/playground-for-node/src/app.js:419:22)
at async runAllTasks (/Applications/Back/playground-for-node/src/app.js:537:5) {
code: 400,
type: 'general_argument_invalid',
response: {
message: 'Invalid execute: Roles must be an array of strings.',
code: 400,
type: 'general_argument_invalid',
version: '0.10.45'
}
}
The creation of the function:
constcreateFunction=async()=>{console.log(chalk.greenBright('Running Create Function API'));constresponse=awaitfunctions.create(ID.unique(),"Node Hello World",[Role.any()],"node-16.0");functionId=response.$id;console.log(response);}
🎲 Appwrite version
Version 0.10.x
💻 Operating system
MacOS
🧱 Your Environment
No response
👀 Have you spent some time to check if this issue has been raised before?
👟 Reproduction steps
npm install
.npm run start
.Node: 18.15.0
node-appwrite: 9.0.0
👍 Expected behavior
According to the documentation, It should create the function.
👎 Actual Behavior
When I run
npm run start
, the creation of a function responds to an error:The creation of the function:
🎲 Appwrite version
Version 0.10.x
💻 Operating system
MacOS
🧱 Your Environment
No response
👀 Have you spent some time to check if this issue has been raised before?
🏢 Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: