This is not an allowlist. Any library with a podspec is tried automatically: Expo modules come through Expo's SwiftPM
plugin, React Native libraries that ship a Package.swift link directly, and CocoaPods-only libraries get a
Package.swift generated by React Native's spm scaffold (with the generic fixes rn-xtool patches in). A library that
nobody has tested should still build when its iOS code is ordinary Swift / Objective-C. A CocoaPods pod a library
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). 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 (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). 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 <name>.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). 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); that is how this table grows.
The table lists what has been checked by hand on a physical iPhone.
Each library is tested on the reference app (expo-ios-linux/app, Expo SDK 58 / RN 0.88) on its own
feature/lib-<name> branch: npx expo install <lib> → smoke usage in App.tsx → rn-xtool run →
checked by hand on a physical iPhone. Dates are the test dates.
The SDK 58 columns (Version, SDK 58 build, SDK 58 runtime) are Expo SDK 58. rn-xtool now builds SDK 58 on the
58.0.21 set (expo 58.0.21 or newer 58.x, react-native 0.88.1; see how-it-works.md).
Cells marked 58.0.21 set were checked on it, on 2026-10-28 in the default template (create-expo-app --template default@sdk-58: expo 58.0.21, react-native 0.88.1; the app launches, its tabs work and Fast Refresh works), and in
the reference app moved to the 58.0.21 set (expo-router with two native-stack routes and safe-area insets). A fresh
template also builds without any manual patch for reanimated's and worklets' CFGetTypeID (2026-10-28, build
checked): the patches step makes their Package.swift portable itself. react-native-device-info's SDK 58 build
cell was checked by building only, on 2026-11-04, in a blank-typescript@sdk-58 template (expo 58.0.23, react-native
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 ✅. 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.
Legend: ✅ works ·
| 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 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 <rnscreens/X.h> 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); 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/<Name>/ 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 ⏳); 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 |
| 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) |
rn-xtool start announces and opens it, with "Match bundle identifier" on, its default); 2026-10-23 (runs; icons missing) |
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); 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) |
| expo-secure-store | Expo source package | ✅ 2026-10-23 | ✅ 2026-10-23 | ⏳ | ⏳ | — | — | — | ||
| 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 | — | ⏳ | ⏳ | ⏳ | ⏳ | 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). expo-sqlite is not yet buildable here — vendored C sources; doctor --project and build refuse it early as well (details), 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 |
| @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) | ⏳ | ⏳ | 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. With Ruby the podspec reads as with a Podfile that sets no globals, so its location APIs are compiled in (VISION_CAMERA_ENABLE_LOCATION), as under CocoaPods; with the reduced reader they stay compiled out, since that reader does not evaluate the podspec's Ruby ternary (fix 24). CameraView is in the binary. On a device (checked before the Ruby reader, location compiled out) 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 <OIDAuthState.h> to #import <iOS/OIDExternalUserAgentCatalyst.h>) for #import <AppAuth/AppAuth.h>. 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); 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). 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
project's patches/).
Scaffolded libraries' resource_bundles are built by rn-xtool, not as SwiftPM resources (SwiftPM would name the bundle
<package>_<target>.bundle, not the name the code looks up): each becomes <name>.bundle at the root of App.app,
as CocoaPods places it, which also gives react-native-svg its Metal filters
(details).