Add OTA update checks to mobile settings

[juliusmarminge]

What Changed

Added an interactive version row in mobile Settings that lets users check for, download, and apply available OTA updates. The row now displays checking, downloading, restarting, and up-to-date states, with a loading indicator while an update is being processed. Update failures are reported with an alert.

Why

Users need a discoverable way to receive OTA updates without waiting for an automatic check. Reusing the existing Version row keeps the control compact while clearly communicating update progress and failures.

UI Changes

The Version row is now pressable when OTA updates are enabled and includes a refresh icon or activity indicator. No screenshots or video were provided.

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes
• I included a video for animation/interaction changes

---

Note

Medium Risk
User-triggered OTA fetch and app reload can disrupt an active session; logic is localized to Settings but touches the update delivery path.

Overview
When expo-updates is enabled, the Settings Version row is now tappable and runs a full manual update flow: check → download → reloadAsync, with inline status text and a spinner while work is in flight.

Idle state still shows the embedded vs OTA bundle hint; during a check it cycles through Checking…, Downloading…, Restarting…, or a brief Up to date before reverting after three seconds. A ref blocks double-taps before disabled re-renders.

runUpdateCheck also handles EAS rollback-to-embedded (isRollBackToEmbedded) when isAvailable / isNew would otherwise look like “nothing to do.” Failures go through reportUpdateFailure (logging plus a native alert).

^{Reviewed by Cursor Bugbot for commit 2a43228. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Add OTA update checks to the mobile settings version row

• Tapping the Version row in SettingsRouteScreen.tsx triggers an OTA update check via Expo Updates when Updates.isEnabled is true.
• UI transitions through 'Checking…', 'Downloading…', 'Restarting…', and 'Up to date' states, showing a spinner while busy; 'Up to date' auto-clears after 3 seconds.
• Handles both normal OTA updates and rollback-to-embedded directives; a successful reload tears down the JS context with no resolution.
• Failures are reported through existing telemetry and surfaced to the user via an Alert.

^{Macroscope summarized 2a43228.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: fb4cc628-31f9-4e85-9de8-50b2c7967d2e

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch t3code/add-ota-update-button

---

_{Comment @coderabbitai help to get the list of available commands.}

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{Bugbot Autofix is ON, but a cloud agent failed to start.}

^{Reviewed by Cursor Bugbot for commit 0e88bb4. Configure here.}

[macroscopeapp]

Approvability

Verdict: Needs human review

This PR introduces a new user-facing feature (manual OTA update checks) with new UI interactions and runtime behavior including network calls, download operations, and app restart functionality. New features warrant human review even when well-scoped.

^{You can customize Macroscope's approvability policy. Learn more.}