User with session cannot execute function with "Users" execute permissions right after signing in
- 2
- Functions

At least 500ms

Lol that's not even bad 😅

The only way might be to prevent it from being stopped due to inactivity

I feel like this problem is even more frequent in 1.4.3

redacted version of client logs:


document not found because of permissions

tl;dr;

there is a 4 requests

first that creates email session

second for retrieving account data

third that gets data from database

and the last that get sessions

cookie saved after first request is only used in second request, but not in third

sorry i think i misunderstand your problem originally

i don't understand this 😅
can you share your code?

someone else is facing a similar problem https://discord.com/channels/564160730845151244/1149666906857545759

I see, so yea this is true - session mechanism in Flutter SDK is not working correctly

but I'm still looking for a source of this bug

can you share your client code?

not really - its a production code, I will try to prepare something simpler but what I found for now if you init SDK not being authenticated - you can authorize and right after call database without problems if you init SDK while being authenticated - you cannot call database again after logging out and logging in

ok, I found it - problem was on our software side

multiple cookie jars

are you doing something special to the SDK with respect to the cookie jar? 🧐

that was one of the most basic problems tbh 😄 in one of our projects we forgot to have appwrite sdk clients as singletons so there were more than 1 client
Recommended threads
- How to get event payload/source from fai...
Hi everyone, I'm currently working with Appwrite's database triggers, specifically for document creation events. I've encountered a potential issue and was h...
- Creating a custom function ID in the con...
Console Version 1.8.0 Google chrome Version 139.0.7258.66 (Official Build) (64-bit)
- Function stuck and has exceeded timeout
I have a function, or more specifically, an execution that has been running for 20+ minutes. It still says "processing". I have a timeout of 6 minutes for that...
