Pin expo-age-range to 0.2.18 so the patch applies

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>
2026-06-29 19:37:52 -05:00
parent 369cf5edd3
commit 5d2359ef6c
4 changed files with 8 additions and 8 deletions
@@ -0,0 +1,16 @@
+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 {