Rank 3: Container
At least 500ms
Votes
2
Replies
24
Participants
Unknown
Messages
25
Rank 3: Container
At least 500ms
Lol that's not even bad 😅
The only way might be to prevent it from being stopped due to inactivity
Rank 3: Container
I feel like this problem is even more frequent in 1.4.3
Rank 3: Container
redacted version of client logs:
Rank 3: Container
Rank 3: Container
document not found because of permissions
Rank 3: Container
tl;dr;
Rank 3: Container
there is a 4 requests
Rank 3: Container
first that creates email session
Rank 3: Container
second for retrieving account data
Rank 3: Container
third that gets data from database
Rank 3: Container
and the last that get sessions
Rank 3: Container
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
Rank 3: Container
I see, so yea this is true - session mechanism in Flutter SDK is not working correctly
Rank 3: Container
but I'm still looking for a source of this bug
can you share your client code?
Rank 3: Container
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
Rank 3: Container
ok, I found it - problem was on our software side
Rank 3: Container
multiple cookie jars
are you doing something special to the SDK with respect to the cookie jar? 🧐
Rank 3: Container
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