@jacques_gordon/expo-mapbox-navigation 2.2.19 → 2.2.20

package/app.plugin.js

@@ -275,6 +275,39 @@ def _expo_mapbox_nav_add_spm(installer)
         puts "[ExpoMapboxNavigation] Added PODS_CONFIGURATION_BUILD_DIR to SWIFT_INCLUDE_PATHS (#{config.name})"
       end
     end
+
+    # ── FRAMEWORK_SEARCH_PATHS / OTHER_LDFLAGS fix for MapboxNavigationNative ───
+    # React Native's own SPM manager (react-native/scripts/cocoapods/spm.rb,
+    # SPMManager#apply_on_post_install) unconditionally deletes ALL
+    # XCRemoteSwiftPackageReference/XCLocalSwiftPackageReference entries not
+    # registered through its own official spm_dependency() API, then only
+    # re-adds the ones it knows about. Since we don't use that API (to avoid
+    # the static-linking duplicate-symbol issues it's known to cause with
+    # Expo modules), our manually-added package_product_dependency for
+    # MapboxNavigationNative keeps getting wiped. Running this whole hook
+    # from post_integrate (see bottom of file) works around the *timing* of
+    # that wipe, but as a second, independent line of defense that doesn't
+    # depend on hook ordering at all, we also force-link the actual compiled
+    # MapboxNavigationNativeWrapper.framework directly via raw build
+    # settings. clean_spm_dependencies_from_target only ever touches
+    # package_references - it never touches FRAMEWORK_SEARCH_PATHS or
+    # OTHER_LDFLAGS, so this survives regardless of what wipes the package
+    # graph entries.
+    expo_target.build_configurations.each do |config|
+      existing_fsp = config.build_settings['FRAMEWORK_SEARCH_PATHS'] || '$(inherited)'
+      unless existing_fsp.to_s.include?('PackageFrameworks')
+        config.build_settings['FRAMEWORK_SEARCH_PATHS'] =
+          "#{existing_fsp} \\"${podsBuildDir}/PackageFrameworks\\""
+        puts "[ExpoMapboxNavigation] Added PackageFrameworks to FRAMEWORK_SEARCH_PATHS (#{config.name})"
+      end
+
+      existing_ldflags = config.build_settings['OTHER_LDFLAGS'] || '$(inherited)'
+      unless existing_ldflags.to_s.include?('MapboxNavigationNativeWrapper')
+        config.build_settings['OTHER_LDFLAGS'] =
+          "#{existing_ldflags} -framework MapboxNavigationNativeWrapper"
+        puts "[ExpoMapboxNavigation] Added -framework MapboxNavigationNativeWrapper to OTHER_LDFLAGS (#{config.name})"
+      end
+    end
   else
     puts '[ExpoMapboxNavigation] WARNING: ExpoMapboxNavigation target not found!'
     puts '[ExpoMapboxNavigation] Available targets:'

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jacques_gordon/expo-mapbox-navigation",
-  "version": "2.2.19",
+  "version": "2.2.20",
   "description": "Expo module for Mapbox Navigation SDK with 16KB page size support, NDK27, and Mapbox Maps v11.11.0+",
   "main": "build/index.js",
   "types": "build/index.d.ts",

package/plugin/src/index.js

@@ -275,6 +275,39 @@ def _expo_mapbox_nav_add_spm(installer)
         puts "[ExpoMapboxNavigation] Added PODS_CONFIGURATION_BUILD_DIR to SWIFT_INCLUDE_PATHS (#{config.name})"
       end
     end
+
+    # ── FRAMEWORK_SEARCH_PATHS / OTHER_LDFLAGS fix for MapboxNavigationNative ───
+    # React Native's own SPM manager (react-native/scripts/cocoapods/spm.rb,
+    # SPMManager#apply_on_post_install) unconditionally deletes ALL
+    # XCRemoteSwiftPackageReference/XCLocalSwiftPackageReference entries not
+    # registered through its own official spm_dependency() API, then only
+    # re-adds the ones it knows about. Since we don't use that API (to avoid
+    # the static-linking duplicate-symbol issues it's known to cause with
+    # Expo modules), our manually-added package_product_dependency for
+    # MapboxNavigationNative keeps getting wiped. Running this whole hook
+    # from post_integrate (see bottom of file) works around the *timing* of
+    # that wipe, but as a second, independent line of defense that doesn't
+    # depend on hook ordering at all, we also force-link the actual compiled
+    # MapboxNavigationNativeWrapper.framework directly via raw build
+    # settings. clean_spm_dependencies_from_target only ever touches
+    # package_references - it never touches FRAMEWORK_SEARCH_PATHS or
+    # OTHER_LDFLAGS, so this survives regardless of what wipes the package
+    # graph entries.
+    expo_target.build_configurations.each do |config|
+      existing_fsp = config.build_settings['FRAMEWORK_SEARCH_PATHS'] || '$(inherited)'
+      unless existing_fsp.to_s.include?('PackageFrameworks')
+        config.build_settings['FRAMEWORK_SEARCH_PATHS'] =
+          "#{existing_fsp} \\"${podsBuildDir}/PackageFrameworks\\""
+        puts "[ExpoMapboxNavigation] Added PackageFrameworks to FRAMEWORK_SEARCH_PATHS (#{config.name})"
+      end
+
+      existing_ldflags = config.build_settings['OTHER_LDFLAGS'] || '$(inherited)'
+      unless existing_ldflags.to_s.include?('MapboxNavigationNativeWrapper')
+        config.build_settings['OTHER_LDFLAGS'] =
+          "#{existing_ldflags} -framework MapboxNavigationNativeWrapper"
+        puts "[ExpoMapboxNavigation] Added -framework MapboxNavigationNativeWrapper to OTHER_LDFLAGS (#{config.name})"
+      end
+    end
   else
     puts '[ExpoMapboxNavigation] WARNING: ExpoMapboxNavigation target not found!'
     puts '[ExpoMapboxNavigation] Available targets:'