Using Xperience

Native app

What the Xperience Expo app supports today and where its boundaries are.

The retained Expo workspace is now a working native guest and crew surface. It uses the Xperience API and keeps native sign-in separate from browser Studio.

What is implemented

  • Email OTP and Google sign-in through Better Auth for Expo, with account credentials kept in SecureStore. Google sign-in is hidden on iOS so the app uses its own email sign-in only (App Store guideline 4.8); Android and web keep it.
  • Explore with event search, categories and past-event labels; free public registration with published pass questions, version checks and conflict recovery. Paid-only events open the trusted web booking journey. Web sign-in may be required.
  • Joined events, organiser event links, event schedules, map directions and in-app event notifications.
  • An account-bound encrypted ticket wallet and event hub. Saved tickets include signed QR codes, attendee/pass names and schedules, and expire 24 hours after the event. The web preview uses memory-only storage.
  • Work invitations with Accept/Reject, accepted assignments and an online-only scanner whose authority is checked by the server.
  • Profile onboarding, privacy controls, export and erasure.

Studio links open in the organiser browser surface and require its own sign-in. The native app does not silently share browser cookies or authority.

Current native release candidate: 1.7.1

The current local source adds public crew recruitment with paginated opportunities, applications and invitation status; same-account refresh retention for the signed-in session; account-bound native push registration and notification tap handling; coarse location consent for event discovery; direct interest editing; and one participant QR per event with combined active-pass access. These capabilities are source-verified and remain subject to the release gates below.

Limits and release status

On 17 October 2026, source dependencies were aligned to the Expo SDK 57 patch ranges while keeping React/React DOM at 19.2.3. Expo Doctor reports 20/21 checks: its remaining same-version Bun path-duplication warning is visible, while actual Apple and Android autolinking each resolve one canonical expo-font and expo-linking module. This is source readiness evidence; no current candidate build, installation, store upload or physical-device acceptance is claimed here.

The production profile builds a store Android App Bundle and an iOS distribution archive with the existing my.xperience.app identifiers. Candidate build counters are Android 2 and iOS 1, managed locally with automatic increments disabled. Increase the appropriate counter before each later candidate; confirm store-side maximums before uploading. This avoids modifying dynamic configuration during a build and makes the uploaded source reproducible. Public production origins are explicit in the profile; server secrets and review sign-in codes never belong in it.

Build source archives omit local design reviews, environment files and signing material via the root .easignore. Use the authenticated existing Expo project; do not create a replacement app or rotate signing keys to work around a prompt.

cd apps/tickets
EXPO_NO_DOTENV=1 bunx eas-cli@25.1.1 build --platform android --profile production --non-interactive --no-wait
EXPO_NO_DOTENV=1 bunx eas-cli@25.1.1 build --platform ios --profile production --non-interactive --no-wait

These build commands do not submit to stores. Record the exact source commit, provider build IDs, signing result and artifact type; install on physical devices and check email sign-in, booking handoff, ticket QR, Work and online scanning before store upload. App Store/Play credentials, listing/privacy disclosures, reviewer access and store-side build counters are independent acceptance steps.

The retained native surface also includes personal scan activity for accepted Work assignments: today's accepted scans, total accepted scans, unique people and counts by area. Return from the scanner or tap Refresh scan activity to update the snapshot. JavaScript export checks and installed-device verification remain separate from this source capability.

The Expo project is configured as @victor_lee071200/xperience with EAS project ID 7785f766-7b80-4871-afe6-f7d0476f94d6. Native JavaScript exports and the application/database CI checks pass. The earlier Android 1.1.0 internal preview build was recorded as finished, but the inspected Expo URL now reports that no internal distribution build exists there. It is historical evidence only; installation and native-device QA remain pending.

On 21 September 2026, iPhone Mirroring checks exercised the live Safari app: joined events, the ticket QR, accepted Work assignment, Profile, the date picker and scanner/back navigation. These checks do not validate the Expo iOS binary. Apple disables camera access during Mirroring, so a physical QR scan must be completed directly on the phone. Neither store readiness nor complete native-device validation is claimed.

Native push registration is present in source but the EXPO_PUSH_ENABLED flag remains disabled by default. No installed-device notification proof, Expo provider delivery proof, App Store publishing or Play publishing is claimed. Native updates are in-app only. Offline tickets are encrypted and account-scoped, but an already-saved ticket cannot be remotely revoked while the phone is offline. Scanning requires a live connection and remains subject to the server's current crew and zone authority.

Store review sign-in

App Store and Google Play reviewers cannot receive email codes, so the API can give one review address a fixed sign-in code. This is an approved production exception, not the development login: the reviewer uses the same email-code screens as every guest, in the native app and on the web, and Better Auth still verifies the code, limits attempts, expires codes, rate-limits requests, checks origins and issues an ordinary session.

Set both on the API service only, never on a frontend or Expo build:

VariableValue
REVIEW_LOGIN_EMAILOne dedicated address used only for store review
REVIEW_LOGIN_CODESix digits, not repeated or consecutive (not 000000 or 123456)

Leaving both empty turns the feature off. Setting only one, several addresses or an invalid code stops the API at startup. Give the address and code to the reviewer in App Store Connect or Play Console review notes, never in this repository, the docs or a chat channel.

  • No email is sent to the review address, including codes and magic links. Every other address receives its normal random code.
  • The account is an ordinary guest. Platform administration is refused for it. Never invite it into a real organisation, merchant team or event crew.
  • Each code request, failed check and successful sign-in writes a [review-login] log line on the API without the code. Watch these during a review.
  • After 20 wrong codes for the review address, that API instance stops accepting the fixed code until it restarts. Redeploying or restarting the API clears this.
  • Rotate REVIEW_LOGIN_CODE after each review cycle and empty both values when no review is pending. A change takes effect when the API restarts.

Local commands

From the repository root:

bun --no-env-file packages/cli/src/lib/app-runner.ts tickets start
bun --no-env-file packages/cli/src/lib/app-runner.ts tickets build

The app reads EXPO_PUBLIC_API_ORIGIN, EXPO_PUBLIC_APP_ORIGIN and EXPO_PUBLIC_PARTNER_ORIGIN. When omitted, these resolve to the configured production Xperience hosts. Use environment-specific values for local work; native configuration contains public origins only. For a physical device use a trusted HTTPS API origin; loopback only works on the machine hosting the API.

Sign-in uses the custom xperience:// scheme. Use a development build or an EAS preview for native authentication; Expo Go is not a supported sign-in environment.

17 October role-fix build attempt

The local candidate source is commit 8c289db2cc56c67051858aae8702fe9e9c22e152. Android store build 1.7.1 (2) finished successfully at 17:39 MYT. Its signed Android App Bundle was downloaded and structurally checked; installed-device acceptance remains pending. iOS 1.7.1 (1) stopped before a build was created because production signing credentials are not set up. The Apple Developer member must complete interactive signing setup. Neither platform was submitted to a store or accepted on a physical device in this verification.

An authorised interactive retry reached Apple verification, but Apple's service refused to send the phone verification code. No signing objects were created. Confirm the enrolled account and use trusted-device verification, following Expo's guidance. Passwords and verification codes belong in the local Apple sign-in flow.

On this page