[pythonsst]

Summary

In-app update prompts for both kinds of update, Zepto/Blinkit style, shown only when an update exists:

• New store build (App Store / Google Play): "New version available → Update now"
• OTA update (expo-updates): downloads silently, then "Update ready → Restart now"
• Both waiting: store prompt first; after "Later", the OTA prompt follows

Plus a Settings screen, release tooling aligned with the Agastya app, and a few build/OTA fixes found along the way.

Shipped as 1.0.2 (tag v1.0.2; Android versionCode 29, iOS build 52). Branch is now at 1.0.3.

Visual walkthrough of every scenario: https://claude.ai/artifact/9CukaMG2xRRBrK6sqHQpi5

---

What the user sees

Situation	UI
Up to date	Nothing. Settings shows only Version 1.0.2 (52).
Store update	Bottom sheet "New version available · Update now / Later" (once per app launch) · gold dot on the Home gear · Settings row "Update Available · New ›"
OTA downloaded	Bottom sheet "Update ready · Restart now / Later" · gold dot · Settings row "Restart to get the latest improvements"
Both	Store sheet first → "Later" → sheet slides down → OTA sheet slides up. Settings row shows the store update.
OTA still downloading	Nothing (no action possible yet)

• iOS "Update now" opens the App Store page. From the Settings row, a native alert asks first: "There is an updated version (x) available on the App Store. Would you like to upgrade?" (Upgrade / Cancel).
• Android "Update now" opens Google's in-app update screen (Play Core, immediate flow). No extra alert: Google's screen is the confirmation.
• "Later" hides that sheet until the next cold start. A downloaded OTA also applies automatically on the next cold start.
• Settings → About shows "Last updated" (OTA publish date) only while an OTA bundle is running.

How it works

Check	How
Installed version	react-native-device-info → getVersion() (native MARKETING_VERSION / versionName), not package.json
App Store version	sp-react-native-in-app-updates → https://itunes.apple.com/lookup?bundleId=<production bundle id>, semver compare
Play version	sp-react-native-in-app-updates → Play Core AppUpdateManager (installed vs available versionCode; only works for Play installs)
OTA	expo-updates: checkForUpdateAsync() then fetchUpdateAsync(); useUpdates().isUpdatePending drives "ready"

Checks run on mount and when the app returns to the foreground, throttled to once a minute. All state lives in one shared store (useSyncExternalStore), so the sheet, the gear dot and Settings always agree.

Runtime version = app version (app.config.js, synced to Expo.plist / strings.xml by yarn version:bump). An OTA only reaches builds of the version it was published from. Never bump the version for an OTA; bump only for store builds.

Files

Core: port these

File	Role
src/hooks/useAppUpdates.ts	Shared store + hook: runs checks, exposes storeUpdateAvailable, otaReady, otaDownloading, hasUpdate, latestStoreVersion, applyOta(), goToStore(). Dev-menu previews (Cmd+D → "Preview update prompt: Store / OTA / Store + OTA / Off").
src/hooks/updateState.ts	Pure resolvePrompt(): store first, then OTA, respecting "Later".
src/services/storeUpdate.ts	Store check + open store. Lazy require of sp-react-native-in-app-updates: react-native-device-info throws at import when its native module is missing, so a top-level import crashes any older binary that receives this JS via OTA.
src/constants/appUpdate.ts	App-specific IDs: App Store ID, Android package, iOS production bundle ID (dev/staging builds still look up the production listing).
src/components/AppUpdatePrompt.tsx	Bottom sheet (RN Modal). Mounted once at the app root, hidden prop instead of unmounting (keeps "Later"). Slides out before swapping store → OTA.
src/screens/SettingsScreen.tsx	"Update Available · New ›" row + alerts; About section.
src/screens/HomeScreen.tsx	Gear button with gold dot (hasUpdate).
App.tsx	Mounts <AppUpdatePrompt hidden={screen === 'settings'} /> at the root; Settings route; Android back.
__mocks__/expo-updates.js, __mocks__/sp-react-native-in-app-updates.js, jest.config.js	Jest mocks
Tests: src/hooks/__tests__/updateState.test.ts, src/components/__tests__/AppUpdatePrompt.test.tsx, src/screens/__tests__/SettingsScreen.test.tsx	20 tests incl. the store → Later → OTA sequence

Release tooling (already in Agastya; ported from there)

scripts/sync-version.js (yarn version:bump x.y.z), scripts/confirm-release-notes.js, scripts/sync-release-notes.js, scripts/eas-update.js, WHATS_NEW.txt, eas.json (changesNotSentForReview, APK profiles, environment).

Repo-specific fixes (probably not needed elsewhere)

• fb033e6: Expo.plist / AndroidManifest.xml OTA URL pointed at an old EAS project, so eas update never reached builds.
• d1b891b: Xcode 27: Podfile raises pod deployment targets to 15.1 and builds fmt as C++17.

---

Porting to another app (e.g. Agastya)

1. Dependencies: yarn add sp-react-native-in-app-updates (+ react-native-device-info and expo-updates if missing; pin device-info with resolutions if versions conflict), then pod install. This is native code: it only works after a new store build. OTA alone cannot deliver it; the lazy require keeps older binaries from crashing.
2. Constants (src/constants/appUpdate.ts): App Store numeric ID, Android package, iOS production bundle ID.
3. Mount the sheet once at the root. With React Navigation: inside NavigationContainer, next to the navigator. Pass hidden while the Settings/Profile screen is focused.
4. Settings/Profile row: render the "Update Available" row only when storeUpdateAvailable || otaReady.
5. Theme: replace C, serif, MAX_CONTENT_WIDTH from src/theme.
6. Jest: copy both mocks + moduleNameMapper entries.
7. Check runtime version policy: must be app version (Agastya already is: runtimeVersion = version via sync-version.js).
8. iOS lookup country: no country is passed, so Apple searches the US store. Fine if the app is available in the US; otherwise pass country in checkNeedsUpdate. (Verified: SnapBiodata and Agastya both resolve.)

Test plan

• Unit tests (20): ordering, "Later", hidden-on-Settings, Settings states, iOS/Android tap paths
• Simulator: store sheet, OTA sheet, Settings up-to-date / update-row states (dev-menu previews)
• Real OTA: staging APK + yarn eas:update:staging → "Update ready" → restart → "Last updated" row
• Android store update: install 1.0.2 from Play, upload 1.0.3 to internal testing → prompt → Google update screen
• iOS store update: once 1.0.2 is live, install a Release build marked 1.0.1 → prompt → App Store page

🤖 Generated with Claude Code