Eric Bailey
61845cfb96
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>
17 lines
679 B
Diff
17 lines
679 B
Diff
diff --git a/ios/AgeRangeModule.swift b/ios/AgeRangeModule.swift
|
|
index faf1089f4ddfb290105e959bb1f96a7250586f54..dafd2addb0c8d39a4a453bdeecbe27f7278e20f7 100644
|
|
--- a/ios/AgeRangeModule.swift
|
|
+++ b/ios/AgeRangeModule.swift
|
|
@@ -11,8 +11,9 @@ public class AgeRangeModule: Module {
|
|
return AgeRangeResponse()
|
|
}
|
|
|
|
- let currentVc: UIViewController? = await MainActor.run { [appContext] in
|
|
- appContext?.utilities?.currentViewController()
|
|
+ nonisolated(unsafe) let utilities = appContext?.utilities
|
|
+ let currentVc: UIViewController? = await MainActor.run {
|
|
+ utilities?.currentViewController()
|
|
}
|
|
|
|
guard let currentVc else {
|