fix(ios): support use_frameworks! consumers via conditional Swift bridge import

CocoaPods exposes the generated `RNMotionTag-Swift.h` differently depending
on host linkage. In default static-library mode (Expo, vanilla RN) it stays
in DerivedSources and is only reachable as `"RNMotionTag-Swift.h"`. With
`use_frameworks!` (commonly required by Firebase, MapBox, Sentry, and other
Swift-only iOS SDKs) it lands inside the framework's Headers and is reachable
as `<RNMotionTag/RNMotionTag-Swift.h>`. The previous quoted-only form
produced `fatal error: 'RNMotionTag-Swift.h' file not found` for any
`use_frameworks!` consumer. Using `__has_include` selects the right form at
compile time so both linkage modes build with no host-side workaround.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: jaymaycry

README.md

@@ -144,6 +144,11 @@ The host's `Info.plist` must declare:
 - `FirebaseAppDelegateProxyEnabled = false` if the app uses Firebase,
   so its swizzling doesn't interfere with MotionTag's background URLSession.
 
+Tested with both CocoaPods' default static-library linkage and
+`use_frameworks! :linkage => :static` (commonly enabled by Firebase,
+MapBox, and other Swift-only iOS SDKs) — no host-side workaround needed
+in either mode.
+
 ### Android — `Application.onCreate`
 
 ```kotlin

example/package-lock.json

@@ -5,7 +5,15 @@
 // MotionTagDelegate (used as a protocol conformance on
 // MotionTagDelegateImpl) is satisfied.
 #import <MotionTagSDK/MotionTagSDK.h>
+// Swift generated header: CocoaPods only exposes it via the framework-style
+// include when the pod is built as a framework (use_frameworks!). In the
+// default static-library mode it stays in DerivedSources and is only
+// reachable via the quoted form.
+#if __has_include(<RNMotionTag/RNMotionTag-Swift.h>)
+#import <RNMotionTag/RNMotionTag-Swift.h>
+#else
 #import "RNMotionTag-Swift.h"
+#endif
 #import <RNMotionTagSpec/RNMotionTagSpec.h>
 
 // Codegen protocol conformance lives here, not on the public @interface,