Repository navigation
Support RN 0.82.1 with fmt 12.1.0 and complete native recovery repairs - #333
Merged
Merged
Conversation
This was referenced Oct 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
React Native 0.82.1 iOS builds fail with fmt 11.0.2 on Xcode 27. This change adds the upstream fmt 12.1.0 backport and lowers the RN minimum to 0.82.1. The supported RN range is
>=0.82.1 <0.84.0. RN 0.82.1 applications must apply the documented patch to their own RN dependency.The change also includes the approved native migration, cursor, and historical replay repairs. The shared schema scenario verifies these repairs through Swift, Kotlin, and both RN bridges. The candidate is
0.4.0-rc.2, with iOS 17 as the Apple minimum. Existingdevchanges, including #300, remain preserved.Validation uses clean commits and preserved structured results. SDK inputs are unchanged between
e2c3024380e288a65efdf2f9cbae27b7aefe87c0andcfdd99f7e3037c3efc7a0e6dfab7815d3bf8e666.Server and conformance inputs are unchanged between
b536bbf94a125d58629a7532975342c93b733a5band that final commit.make ci-source-qualitycfdd99f7cfdd99f7make ci-candidate-serverb536bbf9make test-consumer-serverb536bbf9b536bbf9make ci-candidate-swifte2c30243make ci-candidate-kotline2c30243make ci-candidate-rn-androide2c30243make ci-candidate-rn-iose2c30243e2c30243cfdd99f7cfdd99f7Both RN versions built through the native bridge on both platforms. Each support cell verified connect, push, pull, process termination, and durable resume. Independent source review included deletion and simplification checks.
Evidence records: Mac cells, Android cells, source quality and audits, server, and emulator archive control.
Earlier candidate helper fixture restarts failed after completed SDK phases. Their failures remain recorded. Separate fresh fixtures passed all eight support cells. No registry activation check was weakened.
The full package-manager audits still fail for upstream dependency findings tracked in #312, #328, #330, and #319. No advisory suppression, unsupported major override, or release exception was added. These issues block publication. The local support-cell results do not certify sealed release packages.
Related issues: #303, #331, #298, #329, #214.
This pull request targets
dev. Master, release tags, and published packages remain unchanged.