feat: implement eas updates

[weitingsun]

Description

This PR implements Over the Air update using EAS updates. In this PR, I've implemented the following:

• install eas-updates package
• set up eas updates configs in app.config.js, AndroidManifest.xml, Expo.plist, Info.plist
• Add eas updates configs in app information as part of the easter egg so we can check channel + runtimeVersion
• create a build script to set EAS updates channel and runtimeVersion. These values are set in build time:

1. Only set configs for non production envs such as RC, EXP ...etc so we don't ship it to production by accident
2. We are setting eas updates to disabled for now until the Rive Animation issue is resolved in the next PR
3. We set runtimeVersion the same as app version
4. No real changes in the existing app

For more details on why we do this: https://docs.google.com/document/d/1yFJPGr30HXtc5geDVRX_99vb6_TDtTh1dExeR415ulY/edit?tab=t.0#heading=h.n03xwvqkz3ix

See build 2942
In these builds, you can't really see much since the EAS updates is disabled. As long as the app functioning normally we are good. In my next PR where I will enable EAS updates, you can test updates if needed.

Changelog

CHANGELOG entry: Added EAS updates base

Related issues

Fixes: #21214

Manual testing steps

To confirm channel and runtimeVersion:

1. Go to app information screen
2. Press down Fox image for 10 seconds
3. Should see OTA Update enabled is set to false

Screenshots/Recordings

Before

After

Pre-merge author checklist

• I’ve followed MetaMask Contributor Docs and MetaMask Mobile Coding Standards.
• I've completed the PR template to the best of my ability
• I’ve included tests if applicable
• I’ve documented my code using JSDoc format if applicable
• I’ve applied the right labels on the PR (see labeling guidelines). Not required for external contributors.

Pre-merge reviewer checklist

• I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
• I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.

---

Note

Introduces EAS OTA updates with runtime/channel config at build time, adds required Expo/iOS deps, and surfaces OTA info in App Information.

• OTA/EAS Updates:
  • Add expo-updates and expo-asset deps; install iOS pods (EXUpdates, EASClient, etc.) and add ios/Expo.plist to Xcode project.
  • Configure Expo in app.config.js with runtimeVersion, updates url, and Hermes JS engine for iOS.
  • New ota.config.js (single source of truth) and app/constants/ota.ts to append OTA version; import expo-asset in index.js for asset resolution.
  • New scripts/update-expo-channel.js and hook in scripts/build.sh to set channel/runtime and toggle updates (non-production) at build time; CODEOWNERS updated for the script.
  • Settings > App Information: show OTA status, channel, runtime version, and full version string; add Jest mock for expo-updates.
• iOS/Tooling:
  • Enable Hermes in Podfile and iOS config; update Podfile.lock and Podfile.properties.json.
  • Jest config maps expo-updates to new mock.
  • .js.env.example: add EXPO_PROJECT_ID.

^{Written by Cursor Bugbot for commit a5b4e41. This will update automatically on new commits. Configure here.}

[github-actions]

CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	npm/​expo-updates@​0.27.4

View full report

[Cal-L]

left a comment

[Cal-L]

LGTM. Let's make sure to update Bitrise with any env vars that we need

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
89.5% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud