The `^0.2.17` range floated up to 0.2.18 on reinstall, but pnpm matches
patchedDependencies by exact version, so the 0.2.17 patch was orphaned
(ERR_PNPM_UNUSED_PATCH) and the Swift concurrency fix never applied. Pin
to the exact resolved version and move the patch to match; the patch
context is identical in 0.2.18, so it applies cleanly.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
expo-age-range uses SDK-aligned versioning; 56.x targets Expo SDK 56,
but we're on SDK 54. Pin to the 0.2.x line (0.2.17) instead.
Restore the iOS patch (in pnpm format): the 0.2.x Swift captures a
non-Sendable appContext into a MainActor.run closure, which fails to
compile on our toolchain with "task or actor-isolated value cannot be
sent". Capturing utilities into a local nonisolated(unsafe) var before
the closure resolves it. Verified: build fails without the patch, passes
with it.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Eric Bailey