A patch release for the setup and build failures reported against 0.10.0. No public API changed.
Bug fixes
- Apps built with
use_frameworks!install and compile again. The pod is now declared a static framework, and only the Objective-C entry points are public headers, so Xcode no longer fails withMultiple commands produce .../Headers/Types.hfrom the 21 header basenames that repeat across the library. The C++ headers stay reachable throughHEADER_SEARCH_PATHS(#1448 by @msluszniak, root cause found by @barhanc). - The podspec's build attributes are no longer confined to the OpenCV branch. An unclosed
if enable_opencvmeantpod_target_xcconfig,vendored_frameworks,static_framework,librariesandframeworkswere assigned only when OpenCV was on, so an app that turned it off through thelibsconfig block installed cleanly and then failed to compile or link. A checkout without anrne-build-config.jsonalso raisedNoMethodErrorduringpod install(#1452 by @msluszniak). - The
react-native-workletspeer range is now>=0.10.0 <0.13.0. The previous^0.10.0excluded worklets 0.11 and 0.12, the current releases, which carry the same API. 0.10 stays the floor because it is the first release to serialize anArrayBufferViewnatively; below it, a view over part of a buffer arrives with the length of the whole buffer (#1449 by @msluszniak). - Setup failures now name their own cause instead of surfacing somewhere else. The podspec and
build.gradle.ktscheck that the native artifacts were downloaded and point atpnpm approve-buildsornpm rebuildwhen a blocked postinstall hook skipped them, thereact-native-executorchconfig block is read from the app's package in a monorepo rather than only the workspace root, and the AndroidminSdkVersiondefault moves to 26 to match the shipped.sofiles (#1450 by @msluszniak).
Documentation
- A Troubleshooting page keyed by the exact error text covers the remaining setup failures, and Getting Started states the worklets range along with what Expo SDK 55 and 56 users need to install.
Full changelog: v0.10.0...v0.10.1