Summary
The template is on React Native 0.83.1; the current npm latest is 0.86.0 (and the 0.83 line itself has newer patches, up to 0.83.10). react is 19.2.0 vs 19.2.7. All @react-native/* packages are pinned to 0.83.1.
Motivation
- Stay current with the RN release line.
- Likely lets us drop the
fmt consteval workaround. We added a Podfile post_install patch forcing FMT_USE_CONSTEVAL=0 because fmt 11.0.2 (pinned by RN 0.83) fails to compile under Xcode 26 ("call to consteval function ... is not a constant expression"). Newer RN lines bundle a fixed fmt / Xcode-26 support, so an upgrade should remove the need for that patch.
Scope / risks
- Bare app on the new architecture with a uniffi TurboModule — the upgrade touches the native project (AppDelegate, Podfile, codegen).
- Verify
uniffi-bindgen-react-native compatibility with the target RN version.
- Re-run the full iOS build gauntlet (Hermes phase, fmt, the
NotificationSound native module) and the maestro flows afterward.
Acceptance
Summary
The template is on React Native 0.83.1; the current npm
latestis 0.86.0 (and the 0.83 line itself has newer patches, up to 0.83.10).reactis 19.2.0 vs 19.2.7. All@react-native/*packages are pinned to 0.83.1.Motivation
fmtconsteval workaround. We added a Podfilepost_installpatch forcingFMT_USE_CONSTEVAL=0because fmt 11.0.2 (pinned by RN 0.83) fails to compile under Xcode 26 ("call to consteval function ... is not a constant expression"). Newer RN lines bundle a fixed fmt / Xcode-26 support, so an upgrade should remove the need for that patch.Scope / risks
uniffi-bindgen-react-nativecompatibility with the target RN version.NotificationSoundnative module) and the maestro flows afterward.Acceptance
@react-native/*+reacton the chosen target versionsfmtPodfilepost_installpatch removed if no longer needed (or kept with a note if still required)