What exactly did you do with the CLI?
1.4.2 function syntax problem
Votes
0
Replies
24
Participants
Unknown
Messages
25
Rank 2: Process
upgraded the CLI globally (today).
Created the function locally with the CLi. This was added to appwrite.json
{
"$id": "purge",
"name": "purge",
"runtime": "dart-2.18",
"execute": [],
"events": [],
"schedule": "",
"timeout": 55,
"enabled": true,
"logging": true,
"entrypoint": "lib/main.dart",
"commands": "dart pub get",
"ignore": [
".packages",
".dart_tool"
],
"path": "functions/purge"
}
dart 2.18 is set in .env
It gets built. But it throws. Bad definition IMO.
and you never had a function w/ id purge?
Rank 2: Process
never
Rank 2: Process
I am using this as a woraround.
List<String> log = [];
log.add("Profile image pruning initiated...");
But I still can't .send anything back.
you're executing the code in appwrite, right?
what are you talking about?
Rank 2: Process
Yes. From the console.
i just tried deploying the 2.18 function starter and it worked fine
Rank 2: Process
created using the CLI?
yes
did you upgrade to appwrite 1.4.2?
Rank 2: Process
yes. from 141<140<133
Rank 2: Process
Migration were ok
did you run the upgrade command?. btw...you probably should have upgraded to 1.3.8 and ran the migrate command before upgrading to 1.4...
Rank 2: Process
you mean like entrypoint="upgrade"? yes
what other changes did you make to the function starter before deploying?
Rank 2: Process
I think I deployed it as 2.17 then 2.18
try deleting the function from appwrite, your local file system, and the appwrite.json. then, initialize and deploy the dart starter and test that in Appwrite
Rank 2: Process
The currecy exchange sample ?
no appwrite init function
Rank 2: Process
the starter runs fine.
I may have changed dart_appwrite: 8.0.0 to dart_appwrite: ^10.0.0
then some change you made caused problems...work incrementally to narrow down what the problem is
Rank 2: Process
Thanks. Can't live w/o proper logs.
Rank 2: Process
I haven't had much time since 1.3.3 to keep up with changes