@jacques_gordon/expo-mapbox-navigation 2.2.16 → 2.2.17
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
@@ -5,6 +5,18 @@ import CoreLocation
|
|
|
5
5
|
// re-exported by MapboxNavigationCore in Navigation SDK v3.
|
|
6
6
|
import MapboxNavigationCore
|
|
7
7
|
import MapboxNavigationUIKit
|
|
8
|
+
// IMPORTANT: MapboxNavigationCore depends internally on MapboxNavigationNative
|
|
9
|
+
// (native ObjC classes like MBNNAmenity), but we never call its APIs
|
|
10
|
+
// directly, so no code in this module naturally references it by name.
|
|
11
|
+
// React Native/Expo's CocoaPods post_install SPM step re-derives which
|
|
12
|
+
// package products a pod target actually needs (independently of our own
|
|
13
|
+
// config-plugin hook that explicitly registers it), and that derivation
|
|
14
|
+
// appears to work off of literal `import` statements in Swift source. Without
|
|
15
|
+
// this explicit import, that step silently drops the MapboxNavigationNative
|
|
16
|
+
// product dependency after our hook adds it, causing "Undefined symbols"
|
|
17
|
+
// for MBNN* classes at the final app link step even though the package
|
|
18
|
+
// resolves and MapboxNavigationCore itself compiles fine.
|
|
19
|
+
import MapboxNavigationNative
|
|
8
20
|
|
|
9
21
|
public class ExpoMapboxNavigationView: ExpoView {
|
|
10
22
|
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@jacques_gordon/expo-mapbox-navigation",
|
|
3
|
-
"version": "2.2.
|
|
3
|
+
"version": "2.2.17",
|
|
4
4
|
"description": "Expo module for Mapbox Navigation SDK with 16KB page size support, NDK27, and Mapbox Maps v11.11.0+",
|
|
5
5
|
"main": "build/index.js",
|
|
6
6
|
"types": "build/index.d.ts",
|