Issues with Dynamic Service Instances

Hi everyone,

I’m developing a .NET client app using Appwrite and encountered issues with dynamic service instances. Specifically:

Dynamic Service Problem:

Logging in a user with one service instance and performing a subsequent operation (e.g., updating the user name) with a new instance fails. Keeping a single service instance for both operations works fine. Postman Behavior:

Requests fail in Postman due to missing scopes, but work in my app using AppWriteService. This suggests the Client stores something (e.g., session info) that enables these operations. Questions What exactly does Client retain after login that allows subsequent requests? How should I handle authentication flow in Appwrite? What’s returned by CreateEmailPasswordSession (session, token, or both)? When should I use JWT vs session-based authentication? Is it recommended to use a single service instance for all operations, or is there a way to make dynamic instances work? Thanks in advance!