diff --git a/CHANGELOG.md b/CHANGELOG.md index 932751a..a9f8501 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.6] - 2026-11-05 + ### Upgrading from 0.1.0-alpha.5 - `rn-xtool run` rebuilds and reinstalls the app after this upgrade, which gives it the app icon and, for apps without expo-dev-client, the reload after Allow. @@ -37,11 +39,11 @@ versions follow [Semantic Versioning](https://semver.org/) with `alpha` prerelea every requirement, downloads the files on your machine into `~/.cache/rn-xtool/pods`, wraps each framework for SwiftPM (a headers-only xcframework, and its arm64 archive linked once with `-force_load`), and writes the local package `ios/build/pod-binaries` that the scaffold links. @react-native-ml-kit/text-recognition 2.0.0 builds this way - on bare React Native 0.88.1 (checked by building on 2026-11-05; not run on a device yet): ten Google pods, their - five OCR model bundles at the root of `App.app`, and GoogleToolboxForMac, GoogleUtilities, GoogleDataTransport and - GTMSessionFetcher from their SwiftPM packages through the pod table. The app grows by about 53 MB. Other shapes - (dynamic or Swift frameworks, vendored libraries, compiled sources) stop with a message naming the pod. See - [troubleshooting.md](docs/troubleshooting.md#cocoapods-binaries). + on bare React Native 0.88.1 (checked on a device on 2026-11-05: it recognized printed text from a photo): ten Google + pods, their five OCR model bundles at the root of `App.app`, and GoogleToolboxForMac, GoogleUtilities, + GoogleDataTransport and GTMSessionFetcher from their SwiftPM packages through the pod table. The app grows by about + 53 MB. Other shapes (dynamic or Swift frameworks, vendored libraries, compiled sources) stop with a message naming the + pod. See [troubleshooting.md](docs/troubleshooting.md#cocoapods-binaries). - `rn-xtool-pods.lock.json`, at the project root, records each binary pod's version, URL, size and sha256: "ℹ pods — recorded the sha256 of 10 downloads in rn-xtool-pods.lock.json; commit it, so other machines check that they get the same files." Later builds keep the locked versions and check every download against it; a file with another sha256 @@ -54,7 +56,8 @@ versions follow [Semantic Versioning](https://semver.org/) with `alpha` prerelea - Scaffolded libraries' `resource_bundles` reach the app: each unconditional entry whose name and globs are plain strings becomes `.bundle` at the root of `App.app`, as CocoaPods places it, with `.lproj` folders kept. react-native-svg gets `RNSVGFilters.bundle` with its prebuilt Metal filters, and react-native-device-info its - privacy bundle (checked by building; svg's filters are not checked on a device yet). + privacy bundle (checked by building; svg's filters also on a device on 2026-11-05: a `FeComposite` xor filter + rendered). - `doctor --project` has a `pods` line for binary pods, from the lock and the cache, or probed online within its 10 s budget: "✔ pods — 10 CocoaPods binaries for @react-native-ml-kit/text-recognition, in rn-xtool's cache and in rn-xtool-pods.lock.json", "ℹ pods — …, 10 to download from dl.google.com (40.3 MB)", and the lock entries no library @@ -486,7 +489,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.5...HEAD +[Unreleased]: https://github.com/WillyAntunez/react-native-xtool/compare/v0.1.0-alpha.6...HEAD +[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 [0.1.0-alpha.3]: https://github.com/WillyAntunez/react-native-xtool/compare/v0.1.0-alpha.2...v0.1.0-alpha.3 diff --git a/README.md b/README.md index a2e029d..9f0faf1 100644 --- a/README.md +++ b/README.md @@ -7,8 +7,11 @@ 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.5` 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. +**Status:** alpha, [`react-native-xtool@0.1.0-alpha.6` 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. Demo video coming soon. @@ -119,7 +122,7 @@ rn-xtool's own version) and compares them with the last successful build and ins Some libraries depend on CocoaPods pods that ship prebuilt static binaries instead of sources, such as Google's ML Kit behind @react-native-ml-kit/text-recognition. rn-xtool reads their specs from the CocoaPods CDN, downloads the files on your machine, wraps them for SwiftPM and links them, with no CocoaPods or Ruby. ML Kit text recognition 2.0.0 builds -this way on bare React Native 0.88.1 (checked by building on 2026-11-05; not run on a device yet). +this way on bare React Native 0.88.1, and recognizes text on a physical iPhone (checked on 2026-11-05). - Before the first download, `build` names the files, their sizes, the host and the vendor, with the vendor's terms: `ℹ pods — @react-native-ml-kit/text-recognition needs 10 CocoaPods binaries that are not in rn-xtool's cache, 40.3 MB @@ -189,7 +192,7 @@ prints a `⚠` line for each key a free team does not get, such as push notifica script phases, storyboards, asset catalogs (except the app icon) and `.xib` files are not used; entitlements come from the Debug `CODE_SIGN_ENTITLEMENTS` file ([details](docs/bare-react-native.md#limits)). - Metal shaders are not compiled on Linux. react-native-svg's filters use the prebuilt `*.metallib` files it ships, - which reach the app in `RNSVGFilters.bundle` (checked by building; not yet on a device). + which reach the app in `RNSVGFilters.bundle` (checked on a physical iPhone on 2026-11-05). - `doctor --project` and `build` refuse early, with the reason and a link, the setups rn-xtool knows it cannot build yet: CocoaPods-only libraries with prebuilt binaries of their own (async-storage 3.x) or that depend on a CocoaPods pod from a git source without a known SwiftPM package, Expo modules that build vendored C sources (expo-sqlite), diff --git a/docs/design/plans/2026-11-05-binary-pods.md b/docs/design/plans/2026-11-05-binary-pods.md index 0d9a0f0..efe0ada 100644 --- a/docs/design/plans/2026-11-05-binary-pods.md +++ b/docs/design/plans/2026-11-05-binary-pods.md @@ -1595,12 +1595,16 @@ No commit. It needs the owner's OK: a `create-expo-app` download and about 1 GB No commit by the implementer. Until the owner confirms an item, the docs call it build-verified only. -- [ ] The app from G2 installs and launches (row 52). -- [ ] `TextRecognition.recognize()` on a photo of a printed page returns its blocks and lines, and the first call shows - no "Invalid model path." (rows 54–56). +**Run 2026-11-05 (the owner, iOS 26, install over Wi‑Fi): pass.** The G2 app (bare React Native 0.88.1 with ML Kit +text recognition 2.0.0, react-native-svg 15.16.0 and an entitlements file): install's re-run of the post-pack checks +passed silently, and the app installed and launched. Fast Refresh works. The item left unchecked below was not run. + +- [x] The app from G2 installs and launches (row 52). +- [x] `TextRecognition.recognize()` on a photo of a printed page returns its blocks and lines, and the first call shows + no "Invalid model path." (rows 54–56). (A photo of printed text; the text came back.) - [ ] Optional: one Japanese or Chinese sample through the matching script option. -- [ ] react-native-svg: an `` or another Metal filter renders (OQ3). -- [ ] The results go into `docs/libraries.md`'s dates, in one `docs:` commit by the controller. +- [x] react-native-svg: an `` or another Metal filter renders (OQ3). (`FeComposite` xor.) +- [x] The results go into `docs/libraries.md`'s dates, in one `docs:` commit by the controller. --- diff --git a/docs/design/specs/2026-11-04-binary-pods-design.md b/docs/design/specs/2026-11-04-binary-pods-design.md index c97798e..f9ccccb 100644 --- a/docs/design/specs/2026-11-04-binary-pods-design.md +++ b/docs/design/specs/2026-11-04-binary-pods-design.md @@ -642,11 +642,11 @@ The process, end to end: | 49 | SwiftPM fetch | another package pins GoogleUtilities, GTMSessionFetcher or GoogleDataTransport at another exact version (Firebase, GoogleSignIn) | user: SwiftPM's version conflict naming both | accept: block 2's row 25; the docs name the table as the one place to align pins | | 50 | xtool | a binary target is embedded as a dynamic framework (#130) | user: post-pack check 2 stops the build before install | handle: library-type slices never match `.framework/`; post-pack check | | 51 | xtool | a bundle is not copied, or lands under another name | user: post-pack check 1 | handle | -| 52 | xtool | a bundle's `Info.plist` is refused at signing or install | user: xtool's or the iPhone's error | handle: CocoaPods' keys (goal 4.1); the owner's device pass | +| 52 | xtool | a bundle's `Info.plist` is refused at signing or install | user: xtool's or the iPhone's error | handle: CocoaPods' keys (goal 4.1); the owner's device pass (2026-11-05: installed) | | 53 | xtool | the app grows by about 53 MB (G2), so installs over Wi-Fi take longer; the per-app copies in `ios/build/pod-binaries` and `ios-xtool/Resources` take about 66 MB more on disk (58 MB of xcframeworks and archives, 8 MB of models) | user: a slower install | accept: present tense in `docs/libraries.md` | -| 54 | Runtime | the model bundle is not found: "Invalid model path." at the first recognition, not at launch | user on the device | handle: post-pack check 1, and the device pass | -| 55 | Runtime | a `+load` registration is missing: the recognizer is nil, or `process` fails | user on the device | handle: `-force_load`, post-pack check 3, and the device pass | -| 56 | Runtime | dead stripping removes data that is found only by name | user on the device: "Invalid model path." with the bundle present | handle: the device pass decides; the slice is an archive, so d-date's relink-as-dynamic cause does not apply (fact 4) | +| 54 | Runtime | the model bundle is not found: "Invalid model path." at the first recognition, not at launch | user on the device | handle: post-pack check 1, and the device pass (checked 2026-11-05) | +| 55 | Runtime | a `+load` registration is missing: the recognizer is nil, or `process` fails | user on the device | handle: `-force_load`, post-pack check 3, and the device pass (checked 2026-11-05) | +| 56 | Runtime | dead stripping removes data that is found only by name | user on the device: "Invalid model path." with the bundle present | handle: the device pass decides (checked 2026-11-05); the slice is an archive, so d-date's relink-as-dynamic cause does not apply (fact 4) | | 57 | Runtime | the privacy manifests inside the frameworks are not in the app | nobody for a development build | accept: they are read at App Store submission (Non-goals); the ℹ line names them | | 58 | Runtime | the iPhone's iOS is older than a pod's minimum | user: a launch crash | accept: rn-xtool's minimum is 16.4, ML Kit's 15.5; row 35 covers the general case | | 59 | Disk | not enough space for the downloads, their unpacked and wrapped copies and the per-app copies | user: a stop before the first download, with what is needed and where | handle: goal 5.5; the factor is 8 (G2 measured 7.5× with the per-app copies of row 85); with the project on another filesystem than the cache (row 36), the project's filesystem gets its share of the factor, 2 for the per-app copies, and the cache's the other 6 (final review M5); a file HEAD gives no length counts with the size the lock records (E/F review M3), and a cached file that fails its re-hash is announced and counted like a missing one (E/F review M2) | @@ -731,6 +731,16 @@ The process, end to end: - optional: one Japanese or Chinese sample through the matching script option. Until the owner confirms these, the docs call ML Kit text recognition build-verified only. +- **Device pass, run 2026-11-05** (the owner, iOS 26), on the G2 app (bare React Native 0.88.1 with + @react-native-ml-kit/text-recognition 2.0.0, react-native-svg 15.16.0 and an entitlements file): + - installed over Wi‑Fi: the re-run of the post-pack checks before the install (row 88) passed silently, and the app + installed and launched (row 52); + - `TextRecognition.recognize()` on a photo of printed text returned the text, with no "Invalid model path." (rows + 54–56 checked); + - react-native-svg: a Metal filter shape (`FeComposite` xor) rendered from `RNSVGFilters.bundle` (OQ3); + - Fast Refresh works. + + Not part of this pass: the optional Japanese or Chinese sample. ## Open questions diff --git a/docs/how-it-works.md b/docs/how-it-works.md index ec8b26f..7d456f5 100644 --- a/docs/how-it-works.md +++ b/docs/how-it-works.md @@ -525,7 +525,8 @@ the pods' bundles again from the lock and the cache when they are gone since the GoogleToolboxForMac), with GoogleToolboxForMac's checked `outsideRequirement` and its `emptyTargets`. `data/pod-terms.json` maps a spec homepage to its vendor's terms page, for the line before the first download. -**ML Kit text recognition**, in the build-only proof on bare React Native 0.88.1 (2026-11-05; not run on a device yet): +**ML Kit text recognition**, in the build-only proof on bare React Native 0.88.1 (2026-11-05; the same app then +recognized printed text on a physical iPhone): ten binary pods and four source pods; 40.3 MB downloaded from dl.google.com; the `pods` step took 7.5 s on the first build and 0.1 s offline later; nine `-force_load`s; the cache took 237 MB and the app's copies 66 MB; `App.app` grew by 53 MB (the App binary by 40.3 MB); `ios-xtool/.build` took about 0.84 GB. diff --git a/docs/libraries.md b/docs/libraries.md index 91926c2..e60af2a 100644 --- a/docs/libraries.md +++ b/docs/libraries.md @@ -7,16 +7,16 @@ nobody has tested should still build when its iOS code is ordinary Swift / Objec depends on is linked through its SwiftPM package when rn-xtool's pod table, or the `pods` of your `rn-xtool.config.json`, names one ([details](troubleshooting.md#libraries-that-depend-on-cocoapods-pods)). A pod that ships prebuilt static binaries is read from the CocoaPods CDN, downloaded, checked against the project's -`rn-xtool-pods.lock.json` and linked; only ML Kit text recognition is verified, and only by building so far, and it -makes the app about 53 MB larger. Those files are the vendor's: ML Kit's are Google's, under the ML Kit Terms -(https://developers.google.com/ml-kit/terms). rn-xtool downloads them for your own build and does not accept the terms -on your behalf ([details](troubleshooting.md#cocoapods-binaries)). What does not work yet, on any library: a library's -own vendored `.xcframework` binaries (`binaryTarget`), pods from a git source without a SwiftPM package, other shapes -of binary pods (dynamic frameworks, Swift binaries), and anything that needs Xcode's tools (asset catalogs, -storyboards, Metal shaders). A scaffolded library's `resource_bundles` reach the app as `.bundle` when their -names and globs are plain strings; its plain `resources`, and bundles written as Ruby code, do not, and `build` names -them in one `ℹ Not copied into the app` line ([details](troubleshooting.md#scaffolded-libraries)). If a library -fails, please open an issue with the "My library does not build" template and the output of `rn-xtool doctor --report` +`rn-xtool-pods.lock.json` and linked; only ML Kit text recognition is verified (on a physical iPhone, on React Native +0.88.1), and it makes the app about 53 MB larger. Those files are the vendor's: ML Kit's are Google's, under the ML +Kit Terms (https://developers.google.com/ml-kit/terms). rn-xtool downloads them for your own build and does not accept +the terms on your behalf ([details](troubleshooting.md#cocoapods-binaries)). What does not work yet, on any library: a +library's own vendored `.xcframework` binaries (`binaryTarget`), pods from a git source without a SwiftPM package, other +shapes of binary pods (dynamic frameworks, Swift binaries), and anything that needs Xcode's tools (asset catalogs, +storyboards, Metal shaders). A scaffolded library's `resource_bundles` reach the app as `.bundle` when their names +and globs are plain strings; its plain `resources`, and bundles written as Ruby code, do not, and `build` names them in +one `ℹ Not copied into the app` line ([details](troubleshooting.md#scaffolded-libraries)). If a library fails, please +open an issue with the "My library does not build" template and the output of `rn-xtool doctor --report` ([details](troubleshooting.md#reporting-a-problem)); that is how this table grows. The table lists what has been checked by hand on a physical iPhone. @@ -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 only in that app, then with react-native-svg 15.16.0 added (its filters' bundle reaches `App.app`), so its cell says "build" and keeps "device ⏳". +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 `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. @@ -50,7 +50,7 @@ Legend: ✅ works · ⚠️ works with caveats · ❌ fails · ⏳ not tested ye | 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` | | 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` (build ✅ 2026-11-05 on React Native 0.88.1, the bundle and `RNSVGFilter` in the app; a filter rendering on a device ⏳). 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-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 | ⏳ | | | 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)` | @@ -67,7 +67,7 @@ Legend: ✅ works · ⚠️ works with caveats · ❌ fails · ⏳ not tested ye | 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` (`@import AppAuthCore;`, `@import AppAuth;`) 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 | ⏳ | ⏳ | ⏳ | build ✅ 2026-11-05 (React Native 0.88.1; device ⏳) | ⏳ | ⏳ | ⏳ | 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. `TextRecognition.recognize()` has not run on a device yet | +| @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 | "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 b2a10e6..dca7f9b 100644 --- a/docs/troubleshooting.md +++ b/docs/troubleshooting.md @@ -453,8 +453,8 @@ Some libraries depend on CocoaPods pods that ship prebuilt static binaries inste specs from the CocoaPods CDN, downloads the files the specs name, checks each one against `rn-xtool-pods.lock.json` at the project root, and keeps them in its own cache, `~/.cache/rn-xtool/pods` (`$XDG_CACHE_HOME/rn-xtool/pods` when `XDG_CACHE_HOME` is set). The copies a build puts in the project are git-ignored. ML Kit text recognition 2.0.0 is -the verified case, checked by building only: it has not run on a device yet ([libraries.md](libraries.md)). The steps -are in [how-it-works.md](how-it-works.md#cocoapods-binaries). +the verified case: it builds, and recognizes text on a physical iPhone (2026-11-05; [libraries.md](libraries.md)). +The steps are in [how-it-works.md](how-it-works.md#cocoapods-binaries). A pod takes this route when no pod table entry maps it and its spec downloads an archive (`.tar.gz`, `.tgz` or `.zip`) that holds static `vendored_frameworks` (`.framework` or `.xcframework`), or only headers (GoogleMLKit's `MLKitCore`). @@ -786,7 +786,7 @@ an `ios/build/pod-binaries` from an earlier build stays on disk, unused ([Leavin `RNSVGFilters.bundle`, declared in the podspec through `s.ios.resource_bundles`. rn-xtool builds that bundle from the two `*.iphoneos.metallib` files the package ships and copies it to `App.app` ([resource bundles](#resource-bundles)), so skipping the `.metal` sources costs nothing there. This is checked by - building (2026-11-05); a filter rendering on a device is not checked yet. + building and on a physical iPhone, where a `FeComposite` xor filter rendered (2026-11-05). - **An Expo config plugin change is missing from the app** (for example expo-image-picker's photo library text in Info.plist): `build` runs `expo prebuild` only when `ios/` is missing. After adding or changing a config plugin in `app.json`, run `rn-xtool build --clean` (or `run --clean`), which re-runs `expo prebuild --clean`. diff --git a/package-lock.json b/package-lock.json index 29998c0..5b5cf4b 100644 --- a/package-lock.json +++ b/package-lock.json @@ -1,12 +1,12 @@ { "name": "react-native-xtool", - "version": "0.1.0-alpha.5", + "version": "0.1.0-alpha.6", "lockfileVersion": 3, "requires": true, "packages": { "": { "name": "react-native-xtool", - "version": "0.1.0-alpha.5", + "version": "0.1.0-alpha.6", "license": "MIT", "os": [ "linux" diff --git a/package.json b/package.json index 3395198..0583ecd 100644 --- a/package.json +++ b/package.json @@ -1,6 +1,6 @@ { "name": "react-native-xtool", - "version": "0.1.0-alpha.5", + "version": "0.1.0-alpha.6", "description": "Build Expo and bare React Native iOS dev builds on Linux via xtool", "keywords": [ "expo",