From da0d6fb97eb848c553a5a55f0c817d79c2e56462 Mon Sep 17 00:00:00 2001 From: Eduardo Dorantes Date: Wed, 30 Sep 2026 20:44:16 -0600 Subject: [PATCH] Fix the install steps and add 0.86.2/0.86.3 entries --- CHANGELOG.md | 12 ++++++++++++ README.md | 23 +++++++++++++++++++---- packages/react-native/README.md | 2 +- 3 files changed, 32 insertions(+), 5 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 29583674b0..099153fb0d 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -15,6 +15,18 @@ broken podspecs. - **Prebuilt artifacts were looked up under this package's own version.** React Native publishes the prebuilt Core and Dependencies xcframeworks under *its* release number, and Gradle resolves `com.facebook.react:react-android` the same way, so a patch release of this package that upstream has not made pointed every lookup at a version nobody published. The result was silent: the iOS build fell back to compiling React Native from source, which under `use_frameworks! :linkage => :dynamic` left ~38 core pods dynamic and failed `pod install` on *"transitive dependencies that include statically linked binaries"*, while Gradle simply could not find the artifact. `reactNativeUpstreamVersion` in `package.json` now names the release the artifacts come from, and the reported runtime version stays on that base. - **The package went unrecognized when installed under the `react-native` alias.** An app that builds iOS, Android and visionOS from this one package installs it that way, so there is a single copy of React Native and a single set of pods. Codegen's scan treated the `react-native` entry as upstream's copy and skipped it, dropping this package's own codegen libraries; it now compares the name in the `package.json` the entry resolves to. +## v0.86.3 — 8 September 2026 + +Superseded by 0.86.4, which carries the podspec fixes above. + +### Fixed + +- **`pod install` died on duplicate turbo modules when installed alongside `react-native`.** Both packages declare the same turbo modules, and codegen identifies a library by package name, so the pair was rejected as duplicates. Codegen now skips upstream `react-native` instead. Published as a patch bump because npm does not accept a republish of 0.86.2. + +## v0.86.2 — 8 September 2026 + +The first release under `@reactvision/react-native-visionos`: React Native 0.86.2 with Callstack's visionOS out-of-tree platform carried forward — the `visionos` platform and its CLI commands, the `XR` and `WindowManager` modules, and the SwiftUI scene helpers. Superseded by 0.86.4. + ## v0.85.2 ### Added diff --git a/README.md b/README.md index b1e363b260..d6d891e24b 100644 --- a/README.md +++ b/README.md @@ -8,10 +8,10 @@ npm version - + MIT licensed - + Discord

@@ -58,10 +58,25 @@ React Native from source. ## Installation ```bash -npm install @reactvision/react-native-visionos +npm install --save-dev @reactvision/react-native-visionos \ + @callstack/out-of-tree-platforms @react-native-community/cli ``` -Then create the `visionos/` folder once, and build: +`@callstack/out-of-tree-platforms` is what Metro resolves the `visionos` platform through, and the +`visionos/` Podfile autolinks through `@react-native-community/cli`. + +Then create the `visionos/` folder once — `expo prebuild` does not generate it. It comes from +[`@reactvision/visionos-template`](https://github.com/ReactVision/visionos-template), a whole +React Native project of which only the `visionos/` folder is lifted out: + +```bash +npx @react-native-community/cli@latest init MyApp \ + --template @reactvision/visionos-template \ + --directory .visionos-template --skip-install +mv .visionos-template/visionos ./visionos && rm -rf .visionos-template +``` + +And build: ```bash npx expo prebuild diff --git a/packages/react-native/README.md b/packages/react-native/README.md index b1e363b260..e69ac08053 100644 --- a/packages/react-native/README.md +++ b/packages/react-native/README.md @@ -11,7 +11,7 @@ MIT licensed - + Discord