expo-invoke 3.0.1 → 3.0.2

package/build/plugin/src/withInvoke.js

@@ -62,5 +62,5 @@ const withInvoke = (config, options) => {
     });
     return config;
 };
-exports.default = (0, config_plugins_1.createRunOncePlugin)(withInvoke, 'expo-invoke', '3.0.1');
+exports.default = (0, config_plugins_1.createRunOncePlugin)(withInvoke, 'expo-invoke', '3.0.2');
 //# sourceMappingURL=withInvoke.js.map

package/expo-invoke.podspec

@@ -14,13 +14,15 @@ Pod::Spec.new do |s|
 
   s.source_files = 'ios/**/*.{h,m,mm,swift}'
 
-  # PRODUCT_MODULE_NAME overrides the Swift module name (expo_invoke → ExpoInvoke).
-  # DEFINES_MODULE generates a matching ObjC module map so Swift 6 finds a consistent
-  # ExpoInvoke module for both Swift and ObjC — without it every source file emits
-  # "underlying Objective-C module 'ExpoInvoke' not found" on Xcode 26+.
+  # s.module_name tells CocoaPods to name the Swift module "ExpoInvoke" and generate
+  # the module map under that name — identical to what ExpoUI / ExpoModulesCore do.
+  # Setting PRODUCT_MODULE_NAME via xcconfig alone leaves the CocoaPods-generated
+  # module map named "expo_invoke" (derived from s.name), causing Swift 6 to emit
+  # "underlying Objective-C module 'ExpoInvoke' not found" for every source file
+  # because the ObjC module map name doesn't match PRODUCT_MODULE_NAME.
+  s.module_name = 'ExpoInvoke'
   s.pod_target_xcconfig = {
-    'PRODUCT_MODULE_NAME' => 'ExpoInvoke',
-    'DEFINES_MODULE'      => 'YES'
+    'DEFINES_MODULE' => 'YES'
   }
 
   s.dependency 'ExpoModulesCore'

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "expo-invoke",
-  "version": "3.0.1",
+  "version": "3.0.2",
   "description": "The complete native-surface-to-JS bridge for Expo. One intent config → Siri, Google Assistant, home screen widgets, Dynamic Island, app icon menus, notification actions, NFC, QR, deep links and more — all through a single useInvoke() hook.",
   "main": "build/src/index.js",
   "module": "build/src/index.js",