capacitor-google-tag-manager 0.1.0 → 0.1.1

package/CapacitorGoogleTagManager.podspec

@@ -17,4 +17,6 @@ Pod::Spec.new do |s|
   # Any 9.x from 9.1.0, as in Package.swift. An app pins another one in its Podfile: pod 'GoogleTagManager', '9.3.0'
   s.dependency 'GoogleTagManager', '~> 9.1'
   s.swift_version = '5.9'
+  # The SDK's categories, as Package.swift's -ObjC; CocoaPods' own default already adds it for most apps.
+  s.user_target_xcconfig = { 'OTHER_LDFLAGS' => '$(inherited) -ObjC' }
 end

package/Package.swift

@@ -18,13 +18,18 @@ let package = Package(
         .package(url: "https://github.com/googleanalytics/google-tag-manager-ios-sdk.git", "9.1.0"..<"10.0.0")
     ],
     targets: [
-        // References the SDK's classes so the linker takes its static archive into the app (see the .m file).
+        // References the SDK's classes so the linker takes its static archive into the app (see the .m file), and
+        // links with -ObjC so the archive's categories come too. A class reference loads only the object file that
+        // defines the class; the SDK adds class methods in categories that live in other object files, and without
+        // them the container's first load ends in "+[... runtimeScript]: unrecognized selector" and the app aborts.
+        // CocoaPods sets -ObjC for every app, which is why the SDK worked there; SwiftPM does not.
         .target(
             name: "GoogleTagManagerLinkage",
             dependencies: [
                 .product(name: "GoogleTagManager", package: "google-tag-manager-ios-sdk")
             ],
-            path: "ios/Sources/GoogleTagManagerLinkage"),
+            path: "ios/Sources/GoogleTagManagerLinkage",
+            linkerSettings: [.unsafeFlags(["-ObjC"])]),
         .target(
             name: "GoogleTagManagerPlugin",
             dependencies: [

package/README.md

@@ -75,8 +75,10 @@ Google ships the iOS SDK as a static archive, and an app never calls it: `TAGMan
 takes a member of a static archive only when something references a symbol it defines, and Swift Package Manager links
 without `-ObjC`, so an app that merely depends on the package gets the SDK's (empty) framework folder in its bundle and
 none of its code. The plugin's `GoogleTagManagerLinkage` target references every class the SDK exports, which makes the
-linker take them; `isAvailable` then looks each of them up in the running app. CocoaPods links with `-ObjC` and is
-unaffected either way.
+linker take them, and links with `-ObjC`, which takes the SDK's categories as well: they add class methods from object
+files no class reference pulls in, and without them the first container load aborts the app with
+`+[... runtimeScript]: unrecognized selector`. `isAvailable` then looks each class up in the running app. CocoaPods links
+with `-ObjC` for most apps, and the podspec asks for it too.
 
 ## Use
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "capacitor-google-tag-manager",
-  "version": "0.1.0",
+  "version": "0.1.1",
   "description": "Brings the Google Tag Manager SDK into a Capacitor app on Android and iOS, with its preview activity, so a container shipped with the app is loaded",
   "main": "dist/plugin.cjs.js",
   "module": "dist/esm/index.js",