diff --git a/CHANGELOG.md b/CHANGELOG.md index 15b8309..c11ebf4 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -5,6 +5,8 @@ versions follow [Semantic Versioning](https://semver.org/) with `alpha` prerelea ## [Unreleased] +## [0.1.0-alpha.7] - 2026-11-06 + ### Upgrading from 0.1.0-alpha.6 - The scaffolder is now revision 7, so every scaffold patch rn-xtool persisted in your `patches/` before this release gets a warning at each `build`: "⚠ patches/ was written by an older rn-xtool scaffolder (revision 4, now 7); @@ -18,6 +20,12 @@ versions follow [Semantic Versioning](https://semver.org/) with `alpha` prerelea public header directories of its SwiftPM targets (`["OIDAuthState.h", "iOS/OIDAuthState+IOS.h", …]`), instead of module names; a module name is refused with a message saying to list the headers. rn-xtool's AppAuth entry lists the headers of AppAuth-iOS 3.0.0's umbrella header. +- A part of a scaffolded library's xcconfig value that only CocoaPods computes (in `OTHER_CFLAGS`, + `GCC_PREPROCESSOR_DEFINITIONS`, `HEADER_SEARCH_PATHS` or `SWIFT_ACTIVE_COMPILATION_CONDITIONS`) is still left out, + and `build` now names it in a `! : Left out of …` line instead of dropping it silently: + react-native-worklets' and react-native-reanimated's static feature flags (all off, worklets' + `IOS_DYNAMIC_FRAMERATE_ENABLED` included) and react-native-vision-camera's frame processor and location switches + (off). See [troubleshooting.md](docs/troubleshooting.md#rctthirdpartycomponentsprovider-thirdpartyfabriccomponents). ### Fixed - A bare app target with an Objective-C `main.m` (the React Native templates before 0.77) builds, instead of stopping @@ -45,12 +53,15 @@ versions follow [Semantic Versioning](https://semver.org/) with `alpha` prerelea crashed at start: the podspec reader evaluates Ruby locals, interpolation, `ENV` lookups, ternaries, `if`/`unless` blocks, `push` on a local array, hashes and the library's `package.json`, and leaves out the branches a condition rules out; a source glob, `compiler_flags`, `header_dir` or `frameworks` value it cannot evaluate stops that - library's scaffold with the podspec, the field and the expression, and an xcconfig flag it cannot evaluate is left - out with a warning that names it. react-native-worklets 0.8.3 keeps its `WORKLETS_VERSION` and - `REACT_NATIVE_MINOR_VERSION` defines. + library's scaffold with the podspec, the field and the expression (an xcconfig flag it cannot evaluate is left out, + see Changed). react-native-worklets 0.8.3 keeps its `WORKLETS_VERSION` and `REACT_NATIVE_MINOR_VERSION` defines. - `build` and `install` stop, and remove the packed app, when a class React Native's codegen providers name is not in the app, naming the class, its component or module and its library, instead of installing an app that would crash at start in `+[RCTThirdPartyComponentsProvider thirdPartyFabricComponents]`. +- With these fixes, a production bare React Native 0.85.0 app with an Objective-C app target (`main.m`, + `AppDelegate.h` and `AppDelegate.mm` next to the project, a bridging header and a Swift file) and 20 native + libraries builds, installs over USB and launches on a physical iPhone (checked on 2026-11-06: the JS bundle loaded + from Metro and the app's own UI appeared; its features are not checked yet). ## [0.1.0-alpha.6] - 2026-11-05 @@ -536,7 +547,8 @@ First public release, as `react-native-xtool` (command `rn-xtool`). - No Xcode tools on Linux: asset catalogs, storyboards and Metal shaders are skipped; library resource bundles and vendored xcframeworks are not supported yet. -[Unreleased]: https://github.com/WillyAntunez/react-native-xtool/compare/v0.1.0-alpha.6...HEAD +[Unreleased]: https://github.com/WillyAntunez/react-native-xtool/compare/v0.1.0-alpha.7...HEAD +[0.1.0-alpha.7]: https://github.com/WillyAntunez/react-native-xtool/compare/v0.1.0-alpha.6...v0.1.0-alpha.7 [0.1.0-alpha.6]: https://github.com/WillyAntunez/react-native-xtool/compare/v0.1.0-alpha.5...v0.1.0-alpha.6 [0.1.0-alpha.5]: https://github.com/WillyAntunez/react-native-xtool/compare/v0.1.0-alpha.4...v0.1.0-alpha.5 [0.1.0-alpha.4]: https://github.com/WillyAntunez/react-native-xtool/compare/v0.1.0-alpha.3...v0.1.0-alpha.4 diff --git a/README.md b/README.md index 9f0faf1..6779ac5 100644 --- a/README.md +++ b/README.md @@ -7,11 +7,12 @@ SwiftPM pipeline. [![npm](https://img.shields.io/npm/v/react-native-xtool/alpha?label=npm%20%40alpha)](https://www.npmjs.com/package/react-native-xtool) [![license](https://img.shields.io/badge/license-MIT-blue)](LICENSE) -**Status:** alpha, [`react-native-xtool@0.1.0-alpha.6` on npm](https://www.npmjs.com/package/react-native-xtool) under the +**Status:** alpha, [`react-native-xtool@0.1.0-alpha.7` on npm](https://www.npmjs.com/package/react-native-xtool) under the `alpha` tag. Verified end to end on a physical iPhone on 2026-11-04 and 2026-11-05: the first launch without Reload, the dev client and the app icon; bare React Native 0.85; react-native-vision-camera, react-native-video, react-native-device-info and @react-native-community/netinfo, with react-native-app-auth linked and an entitlements -file; and ML Kit text recognition with react-native-svg's Metal filters. +file; and ML Kit text recognition with react-native-svg's Metal filters. On 2026-11-06 a production bare React Native +0.85.0 app with an Objective-C app target and 20 native libraries built, installed and launched on a physical iPhone. Demo video coming soon. @@ -39,6 +40,11 @@ with one error naming these floors. Expo SDK 57 and 58 work the same way: newer with a warning, older ones stop, and react-native stays exact (0.86.3 on SDK 57, 0.88.1 on SDK 58) ([details](docs/troubleshooting.md#newer-than-the-verified-versions)). +Apps that grew from older React Native templates build too: a production bare React Native 0.85.0 app with an +Objective-C app target (`main.m`, `AppDelegate.h` and `AppDelegate.mm` next to the project, a bridging header and a +Swift file) and 20 native libraries builds, installs over USB and launches on a physical iPhone (checked on +2026-11-06; its features are not checked yet, [details](docs/bare-react-native.md#react-native-085)). + `rn-xtool doctor --project` shows which line your project is on and what rn-xtool finds in it (the SwiftPM scripts and prebuilt artifacts it would use, Expo's plugin and modules, podspec features), without the toolchain, login and device checks ([details](docs/troubleshooting.md#doctor---project)). diff --git a/docs/bare-react-native.md b/docs/bare-react-native.md index f23ead7..59d584c 100644 --- a/docs/bare-react-native.md +++ b/docs/bare-react-native.md @@ -31,7 +31,8 @@ artifacts, passed the precompiled framework check (G4) and produced `App.app`; t [React Native 0.85](#react-native-085)). The same day, on a physical iPhone (iOS 26), that 0.85.0 app (`@react-native-community/cli` 20.0.0, reanimated 4.3.4 and worklets 0.8.3) passed `build`, install over Wi‑Fi, the first launch (tap Allow, and the app reloaded by itself), Hermes, reanimated animating and Fast Refresh. 0.85.3 has -not been run on a device. +not been run on a device. On 2026-11-06 a production 0.85.0 app with an Objective-C app target and 20 native libraries +built, installed over USB and launched on a physical iPhone (see [React Native 0.85](#react-native-085)). On 0.86.3 the first build downloads about 1.3 GB of artifacts (about 3 minutes in our test; it depends on the connection) and adapts them (about 2 s); later builds reuse the adapted slots (`rn-artifacts` 0.0 s). The library @@ -166,8 +167,16 @@ build-verified only. "Not among" warning; both name 0.85.3 as the version to move to, which is build-verified only. - **Expo modules:** 0.85 with expo-modules-core is refused ("React Native 0.85.0 with Expo modules is not supported. Expo SDK 58 needs React Native 0.88.1."), like 0.86 and 0.87. -- **What is proved:** the template app and the reanimated/worklets pair, on a device with 4.3.4 + 0.8.3 on 0.85.0. - Other libraries are untested on 0.85 (⏳ in [libraries.md](libraries.md)). +- **A production app:** on 2026-11-06 a bare React Native 0.85.0 app with an Objective-C app target (`main.m`, + `AppDelegate.h` and `AppDelegate.mm` next to the `.xcodeproj`, a bridging header and a Swift file) and 20 native + libraries, from react-native-screens 4.24.0, react-native-reanimated 4.3.0 with react-native-worklets 0.8.1 and + react-native-vision-camera 4.7 to @react-native-ml-kit/text-recognition and react-native-app-auth (the full list is in + [libraries.md](libraries.md)), was built (`rn-spm` about 10 minutes, `xtool-build` about 4.5 minutes), installed + over USB and launched on a physical iPhone (iOS 26): the JS bundle loaded from Metro and the app's own UI appeared. + Its feature checks (the camera, text recognition, the AppAuth login, Fast Refresh) are not done yet. +- **What is proved:** the template app and the reanimated/worklets pair, on a device with 4.3.4 + 0.8.3 on 0.85.0, + and the production app above, up to its launch. Other libraries are untested on 0.85 (⏳ in + [libraries.md](libraries.md)). ## Detection @@ -238,7 +247,9 @@ the app's entry point from the App library, so a C-family `main` file is copied Xcode. An app file already named `AppMain.` is an error, as two files with the same name are. A `main.swift` is refused, by `build` and `doctor --project`, because Swift allows top-level code only in a file named `main.swift`: mark the app delegate class `@main`, as the template's `AppDelegate.swift` does, move any other top-level code into it, and -remove `main.swift` from the app target. +remove `main.swift` from the app target. Verified on a physical iPhone on 2026-11-06 with a React Native 0.85.0 app +whose `main.m`, `AppDelegate.h` and `AppDelegate.mm` sit next to the `.xcodeproj` +([React Native 0.85](#react-native-085)). ## Mixed Swift + Objective-C/C++ app target @@ -248,7 +259,8 @@ mechanism as the scaffolded mixed libraries (the two manifests described in and your header search paths and defines are applied. The target's `.mm` and `.cpp` files compile with the project's `CLANG_CXX_LANGUAGE_STANDARD` (C++20 when unset), passed to them as `-std=` because Swift Build does not apply the package's `cxxLanguageStandard` to a mixed target. Verified on a device with an Objective-C module next to a Swift -module. +module, and on 2026-11-06 with the Objective-C app target of a production React Native 0.85.0 app, whose +`AppDelegate.mm` imports `` and `` ([React Native 0.85](#react-native-085)). Swift Build names the generated Swift header `App-Swift.h` (the SwiftPM target is `App`), so `build` also writes `Sources/App/include/-Swift.h`, which imports it: Objective-C keeps `#import "-Swift.h"` as in Xcode, diff --git a/docs/how-it-works.md b/docs/how-it-works.md index 6d4b668..73cd952 100644 --- a/docs/how-it-works.md +++ b/docs/how-it-works.md @@ -593,6 +593,9 @@ identity, not from the team itself; on every device run so far it matched the Te On a warm cache: patches 3.6 s, RN SwiftPM 11.1 s, ExpoModulesJSI 12.7 s, xtool build 24.5 s. The resulting `App.app` is about 99 MB with 8 embedded frameworks. +A bare React Native 0.85.0 app with 20 native libraries, its scaffolds made again (2026-11-06): `rn-spm` 578 s, +`frameworks` 35 s, `xtool-build` 273 s. + ## Further reading - [recipe.md](recipe.md): the full technical recipe, with file locations. diff --git a/docs/libraries.md b/docs/libraries.md index dc4fd7a..4d9b3f2 100644 --- a/docs/libraries.md +++ b/docs/libraries.md @@ -36,7 +36,7 @@ cell was checked by building only, on 2026-11-04, in a `blank-typescript@sdk-58` 0.88.1), so it says "build" and keeps "device ⏳". Every other SDK 58 date was checked on earlier SDK 58 versions (react-native 0.88.0), before the 58.0.21 set. -The `Bare 0.88` column is the same library on a bare React Native 0.88 app (`@react-native-community/cli init`, no Expo; checked on a physical iPhone, 2026-10-26, on React Native 0.88.0). On 2026-10-28 the same app, moved to React Native 0.88.1 with its scaffold patches regenerated for 0.88.1, launched again with its libraries, react-native-screens included. `Bare 0.87.1` and `Bare 0.86.3` are the same on bare apps of those versions (vendored SwiftPM scripts), checked the same way on 2026-10-27. `Bare 0.85.0` is a fresh React Native 0.85.0 template app (`@react-native-community/cli init`, moved to `@react-native-community/cli` 20.0.0), checked on 2026-11-04: it ran on a physical iPhone (iOS 26) with react-native-reanimated 4.3.4 and react-native-worklets 0.8.3 (install over Wi‑Fi, Hermes, the animation and Fast Refresh), so that cell is ✅; every other cell was checked by building only, so it says "build" and keeps "device ⏳". Libraries marked ⏳ in a Bare column are untested there, not known to fail. On 2026-10-28 the `Bare 0.88` and `Bare 0.86.3` apps were rebuilt with scaffold revision 3 (their persisted scaffold patches regenerated) and launched again with their libraries. On 2026-11-04 react-native-vision-camera, react-native-video, react-native-device-info and @react-native-community/netinfo were checked together by building only, with scaffold revision 4, in a fresh React Native 0.88.1 template app (`@react-native-community/cli init`): each library's classes are in the app binary. On 2026-11-05 react-native-app-auth 8.5.1 was checked the same way in that app, and in an Expo SDK 58 app (expo 58.0.23, react-native 0.88.1) with its config plugin. On 2026-11-05 that bare app, with the five libraries and an entitlements file, ran on a physical iPhone (iOS 26, install over Wi‑Fi, Fast Refresh), so the four libraries' `Bare 0.88` cells are ✅, with what was checked in the notes; react-native-app-auth is linked there, and its login flow was not run. On 2026-11-05 @react-native-ml-kit/text-recognition 2.0.0 was checked by building in that app, then with react-native-svg 15.16.0 added (its filters' bundle reaches `App.app`). The same day that app ran on a physical iPhone (iOS 26, install over Wi‑Fi, Fast Refresh): `TextRecognition.recognize()` returned the text of a photo of printed text, and a react-native-svg Metal filter (`FeComposite` xor) rendered, so the ML Kit `Bare 0.88` cell is ✅. +The `Bare 0.88` column is the same library on a bare React Native 0.88 app (`@react-native-community/cli init`, no Expo; checked on a physical iPhone, 2026-10-26, on React Native 0.88.0). On 2026-10-28 the same app, moved to React Native 0.88.1 with its scaffold patches regenerated for 0.88.1, launched again with its libraries, react-native-screens included. `Bare 0.87.1` and `Bare 0.86.3` are the same on bare apps of those versions (vendored SwiftPM scripts), checked the same way on 2026-10-27. `Bare 0.85.0` is a fresh React Native 0.85.0 template app (`@react-native-community/cli init`, moved to `@react-native-community/cli` 20.0.0), checked on 2026-11-04: it ran on a physical iPhone (iOS 26) with react-native-reanimated 4.3.4 and react-native-worklets 0.8.3 (install over Wi‑Fi, Hermes, the animation and Fast Refresh), so that cell is ✅; every other cell was checked by building only, so it says "build" and keeps "device ⏳". Libraries marked ⏳ in a Bare column are untested there, not known to fail. On 2026-10-28 the `Bare 0.88` and `Bare 0.86.3` apps were rebuilt with scaffold revision 3 (their persisted scaffold patches regenerated) and launched again with their libraries. On 2026-11-04 react-native-vision-camera, react-native-video, react-native-device-info and @react-native-community/netinfo were checked together by building only, with scaffold revision 4, in a fresh React Native 0.88.1 template app (`@react-native-community/cli init`): each library's classes are in the app binary. On 2026-11-05 react-native-app-auth 8.5.1 was checked the same way in that app, and in an Expo SDK 58 app (expo 58.0.23, react-native 0.88.1) with its config plugin. On 2026-11-05 that bare app, with the five libraries and an entitlements file, ran on a physical iPhone (iOS 26, install over Wi‑Fi, Fast Refresh), so the four libraries' `Bare 0.88` cells are ✅, with what was checked in the notes; react-native-app-auth is linked there, and its login flow was not run. On 2026-11-05 @react-native-ml-kit/text-recognition 2.0.0 was checked by building in that app, then with react-native-svg 15.16.0 added (its filters' bundle reaches `App.app`). The same day that app ran on a physical iPhone (iOS 26, install over Wi‑Fi, Fast Refresh): `TextRecognition.recognize()` returned the text of a photo of printed text, and a react-native-svg Metal filter (`FeComposite` xor) rendered, so the ML Kit `Bare 0.88` cell is ✅. On 2026-11-06 a production bare React Native 0.85.0 app with an Objective-C app target (`main.m`, `AppDelegate.h` and `AppDelegate.mm` next to the `.xcodeproj`, a bridging header and a Swift file) and 20 native libraries (@aws-amplify/react-native, @react-native-async-storage/async-storage 1.24, @react-native-community/netinfo, @react-native-ml-kit/text-recognition, react-native-app-auth, react-native-device-info, react-native-get-random-values, react-native-in-app-review, react-native-keychain, react-native-linear-gradient, react-native-localize, react-native-reanimated 4.3.0, react-native-safe-area-context, react-native-screens 4.24.0, react-native-svg 15.15, react-native-video, react-native-vision-camera 4.7, react-native-webview 13.16, react-native-wifi-reborn and react-native-worklets 0.8.1) was built, installed over USB and launched on a physical iPhone (iOS 26): the JS bundle loaded from Metro and the app's own UI appeared. The libraries of that app that have a row say "linked on a device" in their `Bare 0.85.0` cell, with "features ⏳": the app's own feature checks (the camera, text recognition, the AppAuth login, Fast Refresh) are not done yet. Its other seven libraries have no row yet. The `Expo 57` column is the same library on an Expo SDK 57 app (expo 57.0.31, React Native 0.86.3), at the version `npx expo install` picks for SDK 57 (in the cell), checked on a physical iPhone on 2026-10-28; `npx expo install --check` passed with all of them installed. Bare apps need `plugins: ['react-native-worklets/plugin']` in their own `babel.config.js` for reanimated/worklets (`babel-preset-expo` adds it for Expo apps). The reanimated/worklets `Package.swift` fix needs no patch: rn-xtool applies it on every build. @@ -45,13 +45,13 @@ Legend: ✅ works · ⚠️ works with caveats · ❌ fails · ⏳ not tested ye | Library | Version | Linkage seen | SDK 58 build | SDK 58 runtime | Expo 57 | Bare 0.88 | Bare 0.87.1 | Bare 0.86.3 | Bare 0.85.0 | Notes | |---|---|---|---|---|---|---|---|---|---|---| | expo-haptics | ~58.0.7 | Expo source package (autolinked) | ✅ 2026-10-23 | ✅ 2026-10-23 | ✅ 2026-10-28 (57.0.3) | **58.0.21 set** ✅ 2026-10-28 (hybrid: bare + Expo modules, expo 58.0.21, React Native 0.88.1); ✅ 2026-10-26 on React Native 0.88.0 and expo 58.0.19, a set this release refuses | — | — | — | notificationAsync + impactAsync vibrate on device | -| react-native-safe-area-context | ~5.10.1 | RN lib with its own Package.swift (self-managed) | ✅ 2026-10-23 | ✅ 2026-10-23 | ✅ 2026-10-28 (5.7.0, insets on a native-stack screen) | ⏳ | ⏳ | ⏳ | 5.11.1: build ✅ 2026-11-04 (in the template; device ⏳) | linked without changes | -| react-native-screens | ~4.30.0 | CocoaPods-only → `npx react-native spm scaffold` generated Package.swift | ✅ 2026-10-23 | ✅ 2026-10-23 (after scaffolder fixes 3-5); **58.0.21 set** ✅ 2026-10-28 (4.30.1, scaffolded, in the template) | ✅ 2026-10-28 (4.26.2, native-stack through expo-router) | ✅ 2026-10-26 | ✅ 2026-10-27 | ✅ 2026-10-27 | ⏳ | the app crashed at startup (`Screen native module hasn't been linked`): the scaffolder could not resolve the Ruby locals in `RNScreens.podspec` (`source_files_exts`, `source_files`), so `ios/` sources were missing; see `docs/upstream/react-native-scaffolder.md` #3. Fix 4 then merges the `common` subspec (`common/cpp`, `cpp/`) that fix 3 had stopped leaking in, which `RNSTabsHostShadowNode.h` needs (#4). Fix 5 emulates the `common` subspec's `header_dir = "rnscreens"` so `` resolves (#5). Scaffold persisted with patch-package (`patches/react-native-screens+4.30.0.patch` in the app); rn-xtool runs `scaffold` automatically when RN reports a missing Package.swift. 4.24.0 builds its globs from Ruby locals set under conditions, which the scaffolder read in part before fix 28: its `ios/` sources were missing, and a bare 0.85 app built, installed and crashed at start in `+[RCTThirdPartyComponentsProvider thirdPartyFabricComponents]` ([troubleshooting](troubleshooting.md#rctthirdpartycomponentsprovider-thirdpartyfabriccomponents)); since fix 28 (scaffold revision 6) it scaffolds its `ios/` sources, and `build` checks that every codegen class is in the app. 4.24.0 with fix 28: build ⏳, device ⏳ | +| react-native-safe-area-context | ~5.10.1 | RN lib with its own Package.swift (self-managed) | ✅ 2026-10-23 | ✅ 2026-10-23 | ✅ 2026-10-28 (5.7.0, insets on a native-stack screen) | ⏳ | ⏳ | ⏳ | 5.11.1: build ✅ 2026-11-04 (in the template; device ⏳); linked on a device 2026-11-06 (production app; features ⏳) | linked without changes | +| react-native-screens | ~4.30.0 | CocoaPods-only → `npx react-native spm scaffold` generated Package.swift | ✅ 2026-10-23 | ✅ 2026-10-23 (after scaffolder fixes 3-5); **58.0.21 set** ✅ 2026-10-28 (4.30.1, scaffolded, in the template) | ✅ 2026-10-28 (4.26.2, native-stack through expo-router) | ✅ 2026-10-26 | ✅ 2026-10-27 | ✅ 2026-10-27 | 4.24.0: linked on a device 2026-11-06 (production app; features ⏳) | the app crashed at startup (`Screen native module hasn't been linked`): the scaffolder could not resolve the Ruby locals in `RNScreens.podspec` (`source_files_exts`, `source_files`), so `ios/` sources were missing; see `docs/upstream/react-native-scaffolder.md` #3. Fix 4 then merges the `common` subspec (`common/cpp`, `cpp/`) that fix 3 had stopped leaking in, which `RNSTabsHostShadowNode.h` needs (#4). Fix 5 emulates the `common` subspec's `header_dir = "rnscreens"` so `` resolves (#5). Scaffold persisted with patch-package (`patches/react-native-screens+4.30.0.patch` in the app); rn-xtool runs `scaffold` automatically when RN reports a missing Package.swift. 4.24.0 builds its globs from Ruby locals set under conditions, which the scaffolder read in part before fix 28: its `ios/` sources were missing, and a bare 0.85 app built, installed and crashed at start in `+[RCTThirdPartyComponentsProvider thirdPartyFabricComponents]` ([troubleshooting](troubleshooting.md#rctthirdpartycomponentsprovider-thirdpartyfabriccomponents)); since fix 28 (scaffold revision 6) it scaffolds its `ios/` sources, and `build` checks that every codegen class is in the app. 4.24.0 with fix 28: build ⏳, device ⏳ | | react-native-gesture-handler | 3.3.0 | CocoaPods-only → scaffold | ✅ 2026-10-23 (auto-scaffold + patched scaffolder) | ✅ 2026-10-23; **58.0.21 set** ✅ 2026-10-28 (3.3.0, scaffolded, in the template) | ✅ 2026-10-28 (2.32.0, Pan and Tap) | ✅ 2026-10-26 | ✅ 2026-10-27 | ✅ 2026-10-27 | ⏳ | RN scaffolder bugs found: (1) `read-podspec` keeps only the first value of `s.source_files = "a", "b"` (lost `shared/**`); (2) `publicHeadersPath: "apple"` holds an umbrella header next to subdirs → SwiftPM rejects; using the `include//` shim fixes it. Both are generic → patched in rn-xtool and to be upstreamed to RN | -| react-native-reanimated (+ worklets) | 4.7.1 (+ worklets 0.13.0) | ships Package.swift (self-managed) | ✅ 2026-10-23 | ✅ 2026-10-23; **58.0.21 set** ✅ 2026-10-28 (4.7.1 + worklets 0.13.0, in the template) | ✅ 2026-10-28 (4.5.1 + worklets 0.10.1; keeps animating while the JS thread is blocked) | ✅ 2026-10-26 (needs the worklets Babel plugin) | ⏳ | ✅ 2026-10-27 | 4.3.4 + worklets 0.8.3: ✅ 2026-11-04 (on a device; needs the worklets Babel plugin and scaffolder fix 19); 4.5.1 + worklets 0.10.1: build ✅ 2026-11-04 (device ⏳) | manifest uses CFGetTypeID → fails on Linux host; rn-xtool rewrites it in the `patches` step (by content, so later versions with the same snippet too; old project `patches/` stay harmless), upstream PR pending; see `docs/upstream/reanimated-worklets-manifest.md` | +| react-native-reanimated (+ worklets) | 4.7.1 (+ worklets 0.13.0) | ships Package.swift (self-managed) | ✅ 2026-10-23 | ✅ 2026-10-23; **58.0.21 set** ✅ 2026-10-28 (4.7.1 + worklets 0.13.0, in the template) | ✅ 2026-10-28 (4.5.1 + worklets 0.10.1; keeps animating while the JS thread is blocked) | ✅ 2026-10-26 (needs the worklets Babel plugin) | ⏳ | ✅ 2026-10-27 | 4.3.4 + worklets 0.8.3: ✅ 2026-11-04 (on a device; needs the worklets Babel plugin and scaffolder fix 19); 4.5.1 + worklets 0.10.1: build ✅ 2026-11-04 (device ⏳); 4.3.0 + worklets 0.8.1: linked on a device 2026-11-06 (production app; features ⏳) | manifest uses CFGetTypeID → fails on Linux host; rn-xtool rewrites it in the `patches` step (by content, so later versions with the same snippet too; old project `patches/` stay harmless), upstream PR pending; see `docs/upstream/reanimated-worklets-manifest.md` | | expo-router | ~58.0.28 | Expo source package (Swift that imports react-native-screens' module) | **58.0.21 set** ✅ 2026-10-28 (the template) | **58.0.21 set** ✅ 2026-10-28 (the template's tabs; the reference app's two native-stack routes with safe-area insets) | ✅ 2026-10-28 (57.0.29) | ⏳ | — | — | — | needs screens + safe-area-context. Swift that imports a scaffolded library needs its header search paths: scaffolder fix 17 records them (the `rn-xtool-swift-importer-paths` line) and rn-xtool's Expo patch passes them on, see `docs/upstream/react-native-scaffolder.md`. It also pulls in `@react-native-masked-view/masked-view` 0.3.2 (scaffolded) and `@expo/ui` (a mixed Expo module). On SDK 57, npm's default peers (react-native-reanimated 4.7.1, react-native-worklets 0.13.1, react-native-gesture-handler 3.4.0, react-native-screens 4.30.1) also build and launch (2026-10-28, launch only), after scaffolder fixes 17 (clang-only part) and 18 for screens 4.30. On SDK 57, run `npx expo install react-dom` after adding expo-router, see [troubleshooting](troubleshooting.md#expo-sdk-57) | -| react-native-svg | 15.16.0 | CocoaPods-only → auto-scaffold | ✅ 2026-10-23 | ✅ 2026-10-23 | ⏳ | ✅ 2026-10-26 | ✅ 2026-10-27 | ✅ 2026-10-27 | ⏳ | needed scaffolder fixes 6, 8 and 9. The Metal filters load prebuilt `*.metallib` files from `RNSVGFilters.bundle`, declared via `s.ios.resource_bundles`: rn-xtool builds that bundle from the package's two `*.iphoneos.metallib` files and copies it to `App.app` (✅ 2026-11-05 on React Native 0.88.1: the bundle and `RNSVGFilter` are in the app, and on a device a `FeComposite` xor filter rendered). The `apple/Filters/MetalCI/*.metal` sources are skipped (`exclude:` in Package.swift) because SwiftPM cannot run the `metal` compiler on Linux; `RN_SPM_SKIP_METAL=1` forces the same on macOS. Other rendering is unaffected | -| react-native-webview | 14.0.1 | CocoaPods-only → auto-scaffold | ✅ 2026-10-23 | ✅ 2026-10-23 | ⏳ | ✅ 2026-10-26 | ✅ 2026-10-27 | ✅ 2026-10-27 | ⏳ | | +| react-native-svg | 15.16.0 | CocoaPods-only → auto-scaffold | ✅ 2026-10-23 | ✅ 2026-10-23 | ⏳ | ✅ 2026-10-26 | ✅ 2026-10-27 | ✅ 2026-10-27 | 15.15: linked on a device 2026-11-06 (production app; features ⏳) | needed scaffolder fixes 6, 8 and 9. The Metal filters load prebuilt `*.metallib` files from `RNSVGFilters.bundle`, declared via `s.ios.resource_bundles`: rn-xtool builds that bundle from the package's two `*.iphoneos.metallib` files and copies it to `App.app` (✅ 2026-11-05 on React Native 0.88.1: the bundle and `RNSVGFilter` are in the app, and on a device a `FeComposite` xor filter rendered). The `apple/Filters/MetalCI/*.metal` sources are skipped (`exclude:` in Package.swift) because SwiftPM cannot run the `metal` compiler on Linux; `RN_SPM_SKIP_METAL=1` forces the same on macOS. Other rendering is unaffected | +| react-native-webview | 14.0.1 | CocoaPods-only → auto-scaffold | ✅ 2026-10-23 | ✅ 2026-10-23 | ⏳ | ✅ 2026-10-26 | ✅ 2026-10-27 | ✅ 2026-10-27 | 13.16: linked on a device 2026-11-06 (production app; features ⏳) | | | expo-notifications (local) | ~58.1.6 | Expo source package (pure Swift) + expo-application (mixed) | ✅ 2026-10-23 | ✅ 2026-10-23 | ⏳ | ⏳ | — | — | — | was blocked by expo-application, which Expo's plugin refused (mixed Swift/ObjC, no Package.swift, no prebuilt xcframework in SDK 58). Fixed by the Expo plugin patch: modules without a manifest are emitted as one mixed-language target; see `docs/upstream/expo-spm-plugin-mixed-modules.md`. Remote push needs a paid Apple account | | expo-application | ~58.1.2 (via expo-notifications) | Expo source package, mixed Swift + ObjC → one generated mixed-language target | ✅ 2026-10-23 (`_OBJC_CLASS_$_EXProvisioningProfile` and `ApplicationModule` in the binary) | ⏳ | ⏳ | ⏳ | — | — | — | Swift uses the module's own `EXProvisioningProfile` through the generated umbrella header; `swift-tools-version: 6.4;(experimentalMultiLang)` | | expo-dev-client | ~58.0.15 | meta pod (no sources) over the chain below: expo-dev-launcher 58.0.15 and expo-dev-menu 58.0.11 (circular mixed Swift ⇄ ObjC → one generated mixed-language target each), expo-dev-menu-interface, expo-manifests (pure Swift), expo-updates-interface (pure Swift + placeholder `noop-file.m`, excluded), expo-json-utils (pure ObjC → Clang target) | ✅ 2026-10-23 (builds and links; `EXDevLauncherController`, `DevLauncherModule`, `ExpoDevLauncherAppDelegateSubscriber`, `DevMenuModule` in the binary; ExpoModulesProvider registers them in Debug) | ⚠️ 2026-11-04 (the launcher lists the server `rn-xtool start` announces and opens it, with "Match bundle identifier" on, its default); 2026-10-23 (runs; icons missing) | ⚠️ 2026-11-04 (Metro on port 8083: the link and the QR code `install` prints open the project, the launcher lists the server, and a relaunch goes straight to the project); 2026-10-28 (57.0.20; launcher, bundle and dev menu work) | ⏳ | — | — | — | needed four Expo plugin fixes (Xcode-only resources excluded, CocoaPods module names from `header_dir`, generated packages depending on each other, `pod-headers/` forwarders + dependency module maps), RN fix 12 (header-less `ReactAppHeaders` module map) and two app-target changes in rn-xtool (`EXPO_CONFIGURATION_DEBUG`, clang importer paths for mixed Expo modules); see `docs/upstream/expo-spm-plugin-mixed-modules.md` ("Dev client chain"). Known gaps: the launcher's and menu's `Assets.xcassets` are not compiled (no `actool` on Linux) so their icons are missing; the launcher finds Metro through `start`'s announcement under the installed bundle id, its default URL, or the link `install` prints ([details](troubleshooting.md#dev-client)); podspec defines are ignored (no launcher version string, engine shown as JSC, network inspector compiled out). `expo prebuild --clean` with the dev client leaves `ios/app/AppDelegate.swift` the stock template (copied as is): SDK 58 wires the launcher through ExpoModulesProvider (app delegate subscriber + React delegate handler) | @@ -59,15 +59,15 @@ Legend: ✅ works · ⚠️ works with caveats · ❌ fails · ⏳ not tested ye | expo-file-system | | Expo precompiled xcframework (`ExpoFileSystem.framework`, shipped in the npm package) | ⏳ | ⏳ | ✅ 2026-10-28 (57.0.7, `File`/`Paths` write and read back) | ⏳ | — | — | — | | | expo-image-picker | | Expo source package | ✅ 2026-10-23 | ✅ 2026-10-23 | ✅ 2026-10-28 (57.0.20) | ⏳ | — | — | — | needs the Expo umbrella-import patch: `StatusBarVisibilityController.swift` has no imports and uses UIKit; see `docs/upstream/expo-spm-plugin-umbrella.md` | | @gorhom/bottom-sheet | 5.2 | pure JS (needs reanimated + gesture-handler) | ✅ 2026-10-23 | ✅ 2026-10-23 | ⏳ | ⏳ | ⏳ | ⏳ | ⏳ | needs reanimated + gesture-handler, already ✅ | -| @react-native-async-storage/async-storage | 3.x | mixed ObjC→Swift (`AsyncStorage.mm` imports `AsyncStorage-Swift.h`) + vendored static xcframework | ❌ not scaffoldable | — | ⏳ | ⏳ | ⏳ | ⏳ | ⏳ | The mixed part is now handled by scaffolder fix 10 (one mixed-language target, as for pager-view); the vendored `SharedAsyncStorage.xcframework` still needs a `binaryTarget`, which the scaffolder does not emit yet, so `rn-xtool doctor --project` and `build` refuse it early ([details](troubleshooting.md#libraries-with-prebuilt-binaries)). expo-sqlite is not yet buildable here — vendored C sources; `doctor --project` and `build` refuse it early as well ([details](troubleshooting.md#libraries-that-build-vendored-c-sources)), so `expo-sqlite/kv-store` is not an option yet. Interim: async-storage 2.x, whose iOS side is pure Objective-C (no Swift, no xcframework), should scaffold like the other ObjC libraries (not tested here). Analysis: [docs/upstream/async-storage-analysis.md](upstream/async-storage-analysis.md) | +| @react-native-async-storage/async-storage | 3.x | mixed ObjC→Swift (`AsyncStorage.mm` imports `AsyncStorage-Swift.h`) + vendored static xcframework | ❌ not scaffoldable | — | ⏳ | ⏳ | ⏳ | ⏳ | 1.24: linked on a device 2026-11-06 (production app; features ⏳) | The mixed part is now handled by scaffolder fix 10 (one mixed-language target, as for pager-view); the vendored `SharedAsyncStorage.xcframework` still needs a `binaryTarget`, which the scaffolder does not emit yet, so `rn-xtool doctor --project` and `build` refuse it early ([details](troubleshooting.md#libraries-with-prebuilt-binaries)). expo-sqlite is not yet buildable here — vendored C sources; `doctor --project` and `build` refuse it early as well ([details](troubleshooting.md#libraries-that-build-vendored-c-sources)), so `expo-sqlite/kv-store` is not an option yet. Interim: async-storage 2.x, whose iOS side is pure Objective-C (no Swift, no xcframework), should scaffold like the other ObjC libraries (not tested here). Analysis: [docs/upstream/async-storage-analysis.md](upstream/async-storage-analysis.md) | | @react-native-community/datetimepicker | 9.2.1 | CocoaPods-only → auto-scaffold | ✅ 2026-10-23 | ✅ 2026-10-23 | ⏳ | ✅ 2026-10-26 | ⏳ | ⏳ | ⏳ | | | react-native-pager-view | 9.0.7 | CocoaPods-only, mixed Swift + ObjC++ (`RNCPagerViewComponentView.mm` imports `react_native_pager_view-Swift.h`) → auto-scaffold as one mixed-language target | ✅ 2026-10-23 | ✅ 2026-10-23 | ⏳ | ⏳ | ⏳ | ⏳ | ⏳ | needed scaffolder fixes 10 (mixed-language target: `swift-tools-version: 6.4;(experimentalMultiLang)`, Swift umbrella, `RN_SPM_SWIFT_HEADERS_DIR`, `-std=c++20`) and 11 (bare `#import "RCTFabricComponentsPlugins.h"`). Its podspec depends on the CocoaPods pod `SwiftUIIntrospect ~> 1.0`: scaffolder fix 13 maps it through the pod table to `.package(url: "https://github.com/siteline/swiftui-introspect", exact: "1.5.0")` + `.product(name: "SwiftUIIntrospect", package: "swiftui-introspect")`, and the manifest records the pin (`// rn-xtool-pods: SwiftUIIntrospect=1.5.0`), so no hand edit is needed (SwiftPM fetches it from GitHub on the first build of a clean `.build`). The scaffold is persisted in the app's `patches/react-native-pager-view+9.0.7.patch` | -| react-native-vision-camera | 4.7.3 | CocoaPods-only, mixed Swift + ObjC++ → auto-scaffold as one mixed-language target | ⏳ | ⏳ | ⏳ | ✅ 2026-11-05 (React Native 0.88.1, on a device) | ⏳ | ⏳ | ⏳ | needed scaffolder fixes 20 and 21 (Swift 5 language mode). Without react-native-worklets-core, frame processors are left out: the `FrameProcessors` subspec goes with its sources, headers and settings, as CocoaPods leaves it out, and the scaffold prints `Dependency "react-native-worklets-core" is not installed (or not linked for iOS); left out with the subspec "FrameProcessors" that declares it (its sources, headers, settings and dependencies), as CocoaPods leaves it out.` Location tagging stays compiled out: the podspec switches `VISION_CAMERA_ENABLE_LOCATION` with a Ruby ternary, which the scaffolder does not evaluate (fix 24). `CameraView` is in the binary. On a device the camera permission prompt appears, then the back-camera preview shows | -| react-native-video | 6.19.3 | CocoaPods-only, mixed Swift + ObjC++ → auto-scaffold as one mixed-language target | ⏳ | ⏳ | ⏳ | ✅ 2026-11-05 (React Native 0.88.1, on a device) | ⏳ | ⏳ | ⏳ | needed scaffolder fix 21 (Swift 5 language mode; in Swift 6 it failed with strict-concurrency errors). Google IMA ads and video caching, which the podspec adds only when the Podfile sets `$RNVideoUseGoogleIMA` or `$RNVideoUseVideoCaching`, are not wired: their three pods (GoogleAds-IMA-iOS-SDK, SPTPersistentCache, DVAssetLoaderDelegate) have no SwiftPM package, the scaffold prints one "is a CocoaPods pod with no known SwiftPM equivalent" warning for each, and the code behind them is not built. `RCTVideo` is in the binary. On a device a remote MP4 plays with the native controls | -| react-native-device-info | 15.0.2 | CocoaPods-only, ObjC → auto-scaffold with the `include/RNDeviceInfo/` shim | build ✅ 2026-11-04 (expo 58.0.23, react-native 0.88.1; device ⏳) | ⏳ | ⏳ | ✅ 2026-11-05 (React Native 0.88.1, on a device) | ⏳ | ⏳ | ⏳ | needed scaffolder fix 22 (its `ios/RNDeviceInfo/RNDeviceInfo.h` umbrella directory sits next to `RNDeviceInfo.xcodeproj/`). Its privacy-manifest resource bundle is built and copied to the app as `RNDeviceInfoPrivacyInfo.bundle` (checked by building, 2026-11-05). On SDK 58 it scaffolds through rn-xtool's driver with Expo's autolinking command, and no other library is re-scaffolded. `RNDeviceInfo` is in the binary. On a device (bare) the model and the iOS version are shown. The real device name needs the restricted `com.apple.developer.device-information.user-assigned-device-name` entitlement, which a free team does not get: without it the name is the generic model name, and with the key in the app's entitlements `build` prints a `⚠` line for it | -| @react-native-community/netinfo | 11.5.2 | CocoaPods-only, ObjC++ → auto-scaffold | ⏳ | ⏳ | ⏳ | ✅ 2026-11-05 (React Native 0.88.1, on a device) | ⏳ | ⏳ | ⏳ | needed scaffolder fix 23: `RNCNetInfo.mm` imports its codegen header as `"RNCNetInfoSpec.h"`, which resolves through a forwarder in the per-app header farm. `RNCNetInfo` is in the binary. On a device it reports the type `wifi` and connected `true`. The Wi-Fi network name (SSID) needs the `com.apple.developer.networking.wifi-info` entitlement, which a free team does not get: without it the SSID is empty, and with the key in the app's entitlements `build` prints a `⚠` line for it | -| react-native-app-auth | 8.5.1 | CocoaPods-only, ObjC → auto-scaffold; its pod `AppAuth` → AppAuth-iOS 3.0.0 through the pod table | build ✅ 2026-11-05 (expo 58.0.23, react-native 0.88.1, with the config plugin; device ⏳) | ⏳ | ⏳ | build ✅ 2026-11-05; linked on a device 2026-11-05 (React Native 0.88.1; login flow ⏳) | ⏳ | ⏳ | ⏳ | its podspec depends on `AppAuth >= 1.7.6`; rn-xtool's pod table maps it to `.package(url: "https://github.com/openid/AppAuth-iOS", exact: "3.0.0")` + `.product(name: "AppAuth", package: "appauth-ios")`, fetched by SwiftPM on the first clean build. AppAuth's umbrella header is outside its SwiftPM targets, so the scaffold adds the forwarder `rn-spm-pod-headers/AppAuth/AppAuth.h` (one `#import` per header of AppAuth's umbrella, `#import ` to `#import `) for `#import `. AppAuth's privacy bundles (`AppAuth_AppAuth.bundle`, `AppAuth_AppAuthCore.bundle`) reach `App.app`: they come from the SwiftPM package, not the scaffold. On Expo SDK 58 use 8.5.1: 9.0.0's config plugin stops `expo prebuild` there ([details](troubleshooting.md#libraries-that-depend-on-cocoapods-pods)); with 8.5.1 the plugin's bridging header import compiles. The login's redirect needs its URL scheme in Info.plist (`CFBundleURLTypes`; on Expo the plugin's `redirectUrls`). `RNAppAuth` and `OIDAuthState` are in the binary. On a device (bare) the module is linked (`authorize` is present); the login flow was not run | -| @react-native-ml-kit/text-recognition | 2.0.0 | CocoaPods-only → auto-scaffold; its pod `GoogleMLKit` → ten CocoaPods binary pods wrapped into `ios/build/pod-binaries`, and four source pods through the pod table | ⏳ | ⏳ | ⏳ | ✅ 2026-11-05 (React Native 0.88.1, on a device: recognized printed text from a photo) | ⏳ | ⏳ | ⏳ | the first build prints what it downloads (10 files, 40.3 MB from dl.google.com, Google's, with the ML Kit Terms URL), records their sha256 in `rn-xtool-pods.lock.json` (commit it) and keeps them in `~/.cache/rn-xtool/pods` ([details](troubleshooting.md#cocoapods-binaries)). Each ML Kit framework becomes a headers-only xcframework, and its thin arm64 archive is linked once with `-force_load` on the App target (nine archives; GoogleMLKit itself is headers only). The source pods are GTMSessionFetcher 3.5.0, GoogleUtilities 8.1.5, GoogleDataTransport 10.1.1 and GoogleToolboxForMac 6.0.1 (outside ML Kit's `< 5.0`: 4.x ships no `Package.swift`; one `ℹ` line says so). The five model bundles (`LatinOCRResources`, `ChineseOCRResources`, `DevanagariOCRResources`, `JapaneseOCRResources`, `KoreanOCRResources`) are at the root of `App.app`, and no ML Kit framework is embedded. `MLKTextRecognizer`, `MLKITx_SRLRegistry`, `TextRecognition` and `GTMLogger` are in the binary, and `App.app` grows by about 53 MB. On a device `TextRecognition.recognize()` returned the text of a photo of printed text; the Japanese, Chinese, Devanagari and Korean models were not tried | +| react-native-vision-camera | 4.7.3 | CocoaPods-only, mixed Swift + ObjC++ → auto-scaffold as one mixed-language target | ⏳ | ⏳ | ⏳ | ✅ 2026-11-05 (React Native 0.88.1, on a device) | ⏳ | ⏳ | 4.7: linked on a device 2026-11-06 (production app; features ⏳) | needed scaffolder fixes 20 and 21 (Swift 5 language mode). Without react-native-worklets-core, frame processors are left out: the `FrameProcessors` subspec goes with its sources, headers and settings, as CocoaPods leaves it out, and the scaffold prints `Dependency "react-native-worklets-core" is not installed (or not linked for iOS); left out with the subspec "FrameProcessors" that declares it (its sources, headers, settings and dependencies), as CocoaPods leaves it out.` Location tagging stays compiled out: the podspec switches `VISION_CAMERA_ENABLE_LOCATION` with a Ruby ternary, which the scaffolder does not evaluate (fix 24). `CameraView` is in the binary. On a device the camera permission prompt appears, then the back-camera preview shows | +| react-native-video | 6.19.3 | CocoaPods-only, mixed Swift + ObjC++ → auto-scaffold as one mixed-language target | ⏳ | ⏳ | ⏳ | ✅ 2026-11-05 (React Native 0.88.1, on a device) | ⏳ | ⏳ | linked on a device 2026-11-06 (production app; features ⏳) | needed scaffolder fix 21 (Swift 5 language mode; in Swift 6 it failed with strict-concurrency errors). Google IMA ads and video caching, which the podspec adds only when the Podfile sets `$RNVideoUseGoogleIMA` or `$RNVideoUseVideoCaching`, are not wired: their three pods (GoogleAds-IMA-iOS-SDK, SPTPersistentCache, DVAssetLoaderDelegate) have no SwiftPM package, the scaffold prints one "is a CocoaPods pod with no known SwiftPM equivalent" warning for each, and the code behind them is not built. `RCTVideo` is in the binary. On a device a remote MP4 plays with the native controls | +| react-native-device-info | 15.0.2 | CocoaPods-only, ObjC → auto-scaffold with the `include/RNDeviceInfo/` shim | build ✅ 2026-11-04 (expo 58.0.23, react-native 0.88.1; device ⏳) | ⏳ | ⏳ | ✅ 2026-11-05 (React Native 0.88.1, on a device) | ⏳ | ⏳ | linked on a device 2026-11-06 (production app; features ⏳) | needed scaffolder fix 22 (its `ios/RNDeviceInfo/RNDeviceInfo.h` umbrella directory sits next to `RNDeviceInfo.xcodeproj/`). Its privacy-manifest resource bundle is built and copied to the app as `RNDeviceInfoPrivacyInfo.bundle` (checked by building, 2026-11-05). On SDK 58 it scaffolds through rn-xtool's driver with Expo's autolinking command, and no other library is re-scaffolded. `RNDeviceInfo` is in the binary. On a device (bare) the model and the iOS version are shown. The real device name needs the restricted `com.apple.developer.device-information.user-assigned-device-name` entitlement, which a free team does not get: without it the name is the generic model name, and with the key in the app's entitlements `build` prints a `⚠` line for it | +| @react-native-community/netinfo | 11.5.2 | CocoaPods-only, ObjC++ → auto-scaffold | ⏳ | ⏳ | ⏳ | ✅ 2026-11-05 (React Native 0.88.1, on a device) | ⏳ | ⏳ | linked on a device 2026-11-06 (production app; features ⏳) | needed scaffolder fix 23: `RNCNetInfo.mm` imports its codegen header as `"RNCNetInfoSpec.h"`, which resolves through a forwarder in the per-app header farm. `RNCNetInfo` is in the binary. On a device it reports the type `wifi` and connected `true`. The Wi-Fi network name (SSID) needs the `com.apple.developer.networking.wifi-info` entitlement, which a free team does not get: without it the SSID is empty, and with the key in the app's entitlements `build` prints a `⚠` line for it | +| react-native-app-auth | 8.5.1 | CocoaPods-only, ObjC → auto-scaffold; its pod `AppAuth` → AppAuth-iOS 3.0.0 through the pod table | build ✅ 2026-11-05 (expo 58.0.23, react-native 0.88.1, with the config plugin; device ⏳) | ⏳ | ⏳ | build ✅ 2026-11-05; linked on a device 2026-11-05 (React Native 0.88.1; login flow ⏳) | ⏳ | ⏳ | linked on a device 2026-11-06 (production app; features ⏳) | its podspec depends on `AppAuth >= 1.7.6`; rn-xtool's pod table maps it to `.package(url: "https://github.com/openid/AppAuth-iOS", exact: "3.0.0")` + `.product(name: "AppAuth", package: "appauth-ios")`, fetched by SwiftPM on the first clean build. AppAuth's umbrella header is outside its SwiftPM targets, so the scaffold adds the forwarder `rn-spm-pod-headers/AppAuth/AppAuth.h` (one `#import` per header of AppAuth's umbrella, `#import ` to `#import `) for `#import `. AppAuth's privacy bundles (`AppAuth_AppAuth.bundle`, `AppAuth_AppAuthCore.bundle`) reach `App.app`: they come from the SwiftPM package, not the scaffold. On Expo SDK 58 use 8.5.1: 9.0.0's config plugin stops `expo prebuild` there ([details](troubleshooting.md#libraries-that-depend-on-cocoapods-pods)); with 8.5.1 the plugin's bridging header import compiles. The login's redirect needs its URL scheme in Info.plist (`CFBundleURLTypes`; on Expo the plugin's `redirectUrls`). `RNAppAuth` and `OIDAuthState` are in the binary. On a device (bare) the module is linked (`authorize` is present); the login flow was not run | +| @react-native-ml-kit/text-recognition | 2.0.0 | CocoaPods-only → auto-scaffold; its pod `GoogleMLKit` → ten CocoaPods binary pods wrapped into `ios/build/pod-binaries`, and four source pods through the pod table | ⏳ | ⏳ | ⏳ | ✅ 2026-11-05 (React Native 0.88.1, on a device: recognized printed text from a photo) | ⏳ | ⏳ | linked on a device 2026-11-06 (production app; features ⏳) | the first build prints what it downloads (10 files, 40.3 MB from dl.google.com, Google's, with the ML Kit Terms URL), records their sha256 in `rn-xtool-pods.lock.json` (commit it) and keeps them in `~/.cache/rn-xtool/pods` ([details](troubleshooting.md#cocoapods-binaries)). Each ML Kit framework becomes a headers-only xcframework, and its thin arm64 archive is linked once with `-force_load` on the App target (nine archives; GoogleMLKit itself is headers only). The source pods are GTMSessionFetcher 3.5.0, GoogleUtilities 8.1.5, GoogleDataTransport 10.1.1 and GoogleToolboxForMac 6.0.1 (outside ML Kit's `< 5.0`: 4.x ships no `Package.swift`; one `ℹ` line says so). The five model bundles (`LatinOCRResources`, `ChineseOCRResources`, `DevanagariOCRResources`, `JapaneseOCRResources`, `KoreanOCRResources`) are at the root of `App.app`, and no ML Kit framework is embedded. `MLKTextRecognizer`, `MLKITx_SRLRegistry`, `TextRecognition` and `GTMLogger` are in the binary, and `App.app` grows by about 53 MB. On a device `TextRecognition.recognize()` returned the text of a photo of printed text; the Japanese, Chinese, Devanagari and Korean models were not tried | "Linkage seen" records how the library reached the SwiftPM graph: Expo source package, Expo precompiled xcframework, RN library with its own Package.swift, or CocoaPods-only (→ Package.swift generated automatically by `spm scaffold` and persisted in the diff --git a/docs/troubleshooting.md b/docs/troubleshooting.md index e8d0784..358e641 100644 --- a/docs/troubleshooting.md +++ b/docs/troubleshooting.md @@ -1071,10 +1071,19 @@ module is unavailable.` `Package.swift` of its own. - **"! : Left out of s.pod_target_xcconfig OTHER_CFLAGS: `#{feature_flags}`, which the podspec reader cannot evaluate; CocoaPods passes its value."** (also `GCC_PREPROCESSOR_DEFINITIONS`, `HEADER_SEARCH_PATHS`, - `SWIFT_ACTIVE_COMPILATION_CONDITIONS`): the scaffold left that part of the value out. CocoaPods computes it from the - app or the Podfile: react-native-worklets' and react-native-reanimated's static feature flags (their defaults - apply), react-native-vision-camera's frame processor and location switches (both off). To set such a value, edit - the library's `Package.swift` and persist it in `patches/`. + `SWIFT_ACTIVE_COMPILATION_CONDITIONS`): the scaffold left that part of the value out, and the library compiles as if + it were empty. CocoaPods computes it from the app or the Podfile, so these libraries differ from a CocoaPods build: + - react-native-worklets and react-native-reanimated: every static feature flag reads as off, also the ones their + `src/featureFlags/staticFlags.json` turns on, such as worklets 0.8's `IOS_DYNAMIC_FRAMERATE_ENABLED` (the + worklets display link asks for 120 fps throughout, instead of lowering its frame rate on a ProMotion iPhone when + frames take longer) and reanimated 4.3's `USE_SYNCHRONIZABLE_FOR_MUTABLES`, + `USE_COMMIT_HOOK_ONLY_FOR_REACT_COMMITS` and `FORCE_REACT_RENDER_FOR_SETTLED_ANIMATIONS`. A `staticFeatureFlags` + block in the app's `package.json` is not read. + - react-native-vision-camera: frame processors and location tagging are compiled out + (`VISION_CAMERA_ENABLE_FRAME_PROCESSORS` and `VISION_CAMERA_ENABLE_LOCATION` are not set). CocoaPods turns location + tagging on by default, and frame processors when react-native-worklets-core is installed. + + To set such a value, edit the library's `Package.swift` and persist it in `patches/`. - **A hand-edited `Package.swift`** that leaves out the files defining a class: put them back. - **"ℹ The packed app's binaries list no Objective-C class symbols, so rn-xtool could not check the classes React Native's codegen providers name.":** the binaries have no symbol table, so nothing is checked and the build goes on. diff --git a/docs/wifi-install.md b/docs/wifi-install.md index ea1a5ab..3fa86d5 100644 --- a/docs/wifi-install.md +++ b/docs/wifi-install.md @@ -35,6 +35,12 @@ answered for the whole run (without it iOS drops every service connection over W daemons, no root. A 139 MB app takes about a minute. Debugging and `launch` over the network are not supported: open the app by hand. +**What the lookup checks.** After the install, rn-xtool asks the iPhone for the app's bundle id, version and build +number, and prints them: `Installed on iPhone over Wi‑Fi ()`. It compares +nothing else, so a reinstall of the same version and build number cannot be told from an unchanged app: the line +reads the same whether the iPhone replaced the app or kept the one it had. Development builds usually keep both +numbers from build to build (on a bare app, the Xcode project's `MARKETING_VERSION` and `CURRENT_PROJECT_VERSION`). + The iPhone is authenticated: its TLS certificate must be the `DeviceCertificate` of the pair record, and its UDID is read only inside that session, so nothing is uploaded to another host on the address. diff --git a/package-lock.json b/package-lock.json index 5b5cf4b..8c9306b 100644 --- a/package-lock.json +++ b/package-lock.json @@ -1,12 +1,12 @@ { "name": "react-native-xtool", - "version": "0.1.0-alpha.6", + "version": "0.1.0-alpha.7", "lockfileVersion": 3, "requires": true, "packages": { "": { "name": "react-native-xtool", - "version": "0.1.0-alpha.6", + "version": "0.1.0-alpha.7", "license": "MIT", "os": [ "linux" diff --git a/package.json b/package.json index 0583ecd..dc97b23 100644 --- a/package.json +++ b/package.json @@ -1,6 +1,6 @@ { "name": "react-native-xtool", - "version": "0.1.0-alpha.6", + "version": "0.1.0-alpha.7", "description": "Build Expo and bare React Native iOS dev builds on Linux via xtool", "keywords": [ "expo",