Skip to content

Upgrade expo version and deps - #105

Open
patrickdemers6 wants to merge 1 commit into
mainfrom
chore/upgrade-expo-android-sdk
Open

patrickdemers6 wants to merge 1 commit into
mainfrom
chore/upgrade-expo-android-sdk

Conversation

@patrickdemers6

Copy link
Copy Markdown
Owner

Summary

  • Bumps Expo 49.0.9 → 57.0.15 and React Native 0.72.4 → 0.86.2 (React 18.2.0 → 19.2.3) so EAS/Play builds use a currently supported SDK.
  • Android compile/target SDK goes from Expo 49’s default (33) to Play’s current requirement (36 / Android 16) via expo-build-properties.
  • Aligned Expo modules with expo install --fix; expo-doctor is clean (21/21).
  • runtimeVersion policy sdkVersion → appVersion (sdkVersion policy is deprecated).
  • Metro now uses expo/metro-config. Lockfile is Bun (bun.lock) because the upgrade was applied with the Expo-compatible installer on this machine; EAS profiles pin Node 22.18.0.

Old vs new

Before After
Expo SDK 49 57 (expo@57.0.15)
React Native 0.72.4 0.86.2
React 18.2.0 19.2.3
Android compile/target 33 (SDK 49 default) 36
Node (EAS) unspecified 22.18.0

Test plan

  • eas build -p android --profile production (or beta APK) and confirm Play Console accepts target API 36
  • Install on a current Android phone; map, location, route select, favorites still work
  • Confirm OTA: new native runtime needs a new store build before eas update
  • iOS smoke (bundle id/signing unchanged)

Notes / blockers

  • No signing key changes.
  • App JS behavior was not rewritten (Recoil, Paper, maps kept). Recoil is unmaintained on React 19 — worth a later migration if you see runtime warnings.
  • A production Play/App Store build is required after this; Expo 49 binaries cannot load this JS.

@patrickdemers6
patrickdemers6 force-pushed the chore/upgrade-expo-android-sdk branch from 09d9fbb to 33c92dd Compare August 23, 2026 21:41
Comment thread .nvmrc Outdated
@@ -0,0 +1 @@
22.18.0

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why v22 this is already in maintenance

@patrickdemers6 patrickdemers6 Aug 23, 2026 •

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

22 was Expo 57’s documented minimum (22.13+), not a preference. Bumped .nvmrc / EAS node / engines to 24.14.0.

🤖 Grok Bot

Comment thread app.config.js Outdated
'expo-build-properties',
{
android: {
compileSdkVersion: 36,

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

any reason to not target latest? 37.0.1

@patrickdemers6 patrickdemers6 Aug 23, 2026 •

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

36 was Expo 57’s documented compile/target SDK. Bumped to compile/target 37 and build tools 37.0.1. Untested on a new APK yet — the APK you have is still API 36.

🤖 Grok Bot

@patrickdemers6 patrickdemers6 changed the title Upgrade Expo SDK 49 → 57 (Android API 33 → 36) Upgrade expo version and deps Aug 23, 2026
@patrickdemers6
patrickdemers6 force-pushed the chore/upgrade-expo-android-sdk branch from 4090d13 to 3378bbd Compare August 23, 2026 22:25
@patrickdemers6
patrickdemers6 force-pushed the chore/upgrade-expo-android-sdk branch from c4b641e to 8c90db1 Compare September 28, 2026 07:07
Bump the SDK and version to 1.3.1. Keep the route list and settings in
modals so the map stays mounted, and patch stop pins, pinch zoom, and
bus markers. Fall back to the production backend when an update has no env.
@patrickdemers6
patrickdemers6 force-pushed the chore/upgrade-expo-android-sdk branch from 8c90db1 to cb233af Compare September 28, 2026 07:12
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.

1 participant