# Better Auth on Expo: SecureStore sessions, cookiePrefix match, getCookie APIs

Better Auth’s Expo client already solves the hard part of native sessions: it caches session data in `expo-secure-store`, filters cookies with `cookiePrefix`, and exposes `getCookie()` so your own API calls can send the same credentials the auth client uses. Wire those three pieces once and signed-in screens stop flashing empty on cold start, and authenticated `fetch` / tRPC calls stop arriving as anonymous.

This is the Expo-native path documented in the [Better Auth Expo integration](https://better-auth.com/docs/integrations/expo): `expoClient` + SecureStore storage, server `trustedOrigins` for your app scheme, and manual Cookie headers with `credentials: "omit"` when you call non-auth endpoints.

---

*This is an excerpt. Read the full post at [otf-kit.dev/blog/better-auth-expo-session-gate](https://otf-kit.dev/blog/better-auth-expo-session-gate) — full-stack kits your AI coding agent can actually ship to production. [Browse the kits →](https://otf-kit.dev)*