Skip to content

Expo: Introduction

kizunasync/expo supplies the platform ports a React Native app needs: the SQLite driver, the NetInfo connectivity signal, the AppState foreground signal, the file sandbox for attachments, and the native download half of the transfer port. The client itself is built with createSupabaseKizunaSync, and the hooks come from kizunasync/react.

Version#

kizunasync/expo 0.2.6-alpha.3 (Alpha). npm package kizunasync, import path kizunasync/expo; Expo SDK and React Native optional peers. See Installing.

What this reference covers#

What Supabase covers#

ConcernUse
Sign-in, sessions, and token refresh on React NativestartAutoRefresh and Auth sessions
Row Level Security policiesWrite a policy for each operation
Realtime channels behind the wake-up doorbellsubscribe
Storage buckets, objects, and their policiesupload and Access control

Kizuna adds one thing to each row above. A foreground signal refreshes the session before the next run, so an attempt never runs on an expired access token. The server judges the policies when a queued write reaches it, not when the component renders. A Realtime message wakes a sync run instead of carrying data. Attachment bytes move through the transfer port that Media and attachments describes.

Found a problem? Edit this page on GitHub