Skip to content

chore: upgrade to Expo SDK 58 canary - #32

Draft
janicduplessis wants to merge 2 commits into
mainfrom
upgrade/expo-58-canary
Draft

chore: upgrade to Expo SDK 58 canary#32
janicduplessis wants to merge 2 commits into
mainfrom
upgrade/expo-58-canary

Conversation

@janicduplessis

@janicduplessis janicduplessis commented Sep 5, 2026

Copy link
Copy Markdown
Contributor

Description

Upgrade Trailhead to the pinned Expo SDK 58 canary / React Native 0.87 stack for the next benchmark campaign. This remains a canary dependency set, not a stable SDK release, and does not by itself fix cross-worktree C++ cache misses.

Solution

Use compatible native-library versions where the canary recommendations fail to build, and keep those overrides explicit so expo install --fix does not undo them. Scoped npm peer overrides and Worklets' explicit Metro dependency make the regenerated lockfile installable without ignoring peer dependencies.

Build only ExpoVideo from source on iOS: the canary's prebuilt framework aborts at launch with Library not loaded: @rpath/Testing.framework/Testing. Other prebuilt Expo modules remain enabled. Keep both committed native projects rather than regenerating them.

Test plan

  • Fresh npm ci, full npm ls --all, expo install --check, Expo Doctor, typecheck, lint, and Android Metro export.
  • Native Android arm64 and iPhone simulator builds; verify Settings and inspect runtime errors.
  • iOS before: prebuilt ExpoVideo terminates before requesting JavaScript. After: source-built ExpoVideo allows launch, Settings proof, and clean runtime logs.
  • Same-checkout PCH checks passed (6/6); cross-worktree cache misses remain.

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