appwrite-swift

Use the TablesDB class with listRows and pass Query helpers such as Query.equal, Query.greaterThan, Query.orderDesc, and Query.limit. Prefer cursor pagination with Query.cursorAfter for large datasets, and use named parameters for all method calls.

Create an Account instance from a configured Client, then call createEmailPasswordSession for email login or createOAuth2Session for providers like Google. Retrieve the current user with account.get() and log out with deleteSession using the current session ID.

Use TablesDB for all new code because the Databases class is deprecated. Only use Databases when maintaining an existing codebase that already relies on it or when explicitly required.

Yes, server-side Swift works with two clients: an admin client using an API key to create sessions, and a per-request session client that reads the a_session_<PROJECT_ID> cookie. Set the cookie with isHTTPOnly, isSecure, and sameSite strict.

A 401 means the session or API key is missing or invalid, while 403 means the user lacks permissions on the resource. Check that row or file permissions include the user via Permission.read(Role.user(...)) or appropriate team roles.

Create a Realtime instance and call subscribe with channels such as Channel.tablesdb(databaseId).table(tableId).row(). The closure receives events, payload, channels, and timestamp; call close() on the subscription when done.