Skip to content

feat: in-app OTA update banner and EAS update workflow fixes - #149

Open
HugoPerard wants to merge 2 commits into
mainfrom
cursor/ota-update-banner-ci-0baf
Open

HugoPerard wants to merge 2 commits into
mainfrom
cursor/ota-update-banner-ci-0baf

Conversation

@HugoPerard

@HugoPerard HugoPerard commented Oct 26, 2026 •

Copy link
Copy Markdown
Member

Summary

Adds a non-blocking in-app update banner for production EAS builds and fixes GitHub Actions so eas update passes the required --environment and --message flags (Expo SDK 55+), with APP_ENV aligned to app.config.ts.

In-app updates

  • UpdateBanner (src/features/updates/update-banner.tsx): uses expo-updates useUpdates() for availability/download state.
  • Checks for updates when the app foregrounds (AppState β†’ active), with errors logged via console.warn.
  • Banner offers Update (fetch + reload) or Reload when isUpdatePending; shows a loading label while downloading.
  • Hidden when __DEV__ or !Updates.isEnabled.
  • Mounted in src/app/_layout.tsx with top safe-area inset.
  • i18n: updates namespace in en and fr.

CI

Target EAS channel / branch --environment APP_ENV
Manual workflow input development --branch development development development
Manual workflow input staging --branch staging preview staging
Manual workflow input production --branch production production production
PR preview PR head ref preview staging

Why staging β†’ EAS preview: EAS only exposes development, preview, and production server environments. The repo’s staging build profile maps naturally to the preview environment for EAS env vars, while the update channel name stays staging per eas.json.

PR previews use APP_ENV=staging so bundled config matches internal/staging identifiers rather than production.

  • eas-preview.yml: added permissions (pull-requests: write, contents: read) for preview comments.

Docs

  • README Over-the-air (OTA) updates section: in-app behavior, CI channel/environment table, and a new Expo / EAS setup subsection (numbered steps for forking: eas init, update:configure, channels/branches, eas env:set, EXPO_TOKEN, first builds, and staging test flow).

Verification

  • pnpm run lint (oxlint + tsc --noEmit): pass
  • pnpm install prepare/lefthook may fail in some cloud agent VMs (core.hooksPath); harmless; not changed in this PR.

Not done (by design)

  • No EAS update published from this agent
  • No store submissions or secrets added
Open in WebΒ Open in CursorΒ 

Add UpdateBanner using expo-updates useUpdates(), foreground update checks,
and i18n strings. Fix eas-update and eas-preview workflows to pass EAS
--environment, --message, and APP_ENV. Document OTA behavior in README.

Co-authored-by: prdHugo <HugoPerard@users.noreply.github.com>
@github-actions

github-actions Bot commented Oct 26, 2026 •

Copy link
Copy Markdown

πŸš€ Expo preview is ready!

  • Project β†’ start-ui-native-v9iizxkbojzedvpfkfzcq
  • Platforms β†’ android, ios
  • Scheme β†’ start-ui-native-staging
Android
(6ee39678e141dd5902ff0eb18bcda0ff349473b6)
More info
iOS
(c2ef455ae413197060d9b4fcd74fc85a95816e9c)
More info

Learn more about 𝝠 Expo Github Action

Document project linking, update:configure, channels/branches, EAS
environments and env vars, EXPO_TOKEN, initial builds, and staging test flow.

Co-authored-by: prdHugo <HugoPerard@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants