Project Doesn't Build With SwiftPM

[michael-mckenna]

Environment details

OS type and version: Xcode 12 Beta 4, MacOS Catalina
Library version and other environment information: 3.2.1

Steps to reproduce

1. Create a new Xcode project with Storyboard
2. Add this dependency via SwiftPM
3. Build (CMD+B)

Code example

No Code Required

Stack trace

Undefined symbols for architecture x86_64:
  "_OBJC_CLASS_$_GMSMutablePath", referenced from:
      objc-class-ref in GoogleMapsUtils(GMUGeoJSONParser.o)
      objc-class-ref in GoogleMapsUtils(GMUKMLParser.o)
  "_OBJC_CLASS_$_GMSGroundOverlay", referenced from:
      objc-class-ref in GoogleMapsUtils(GMUGeometryRenderer.o)
  "_OBJC_CLASS_$_GMSCoordinateBounds", referenced from:
      objc-class-ref in GoogleMapsUtils(GMUGeometryRenderer.o)
      objc-class-ref in GoogleMapsUtils(GMUDefaultClusterRenderer.o)
      objc-class-ref in GoogleMapsUtils(GMUGeoJSONParser.o)
  "_OBJC_CLASS_$_GMSPolygon", referenced from:
      objc-class-ref in GoogleMapsUtils(GMUGeometryRenderer.o)
  "_OBJC_CLASS_$_GMSMarker", referenced from:
      objc-class-ref in GoogleMapsUtils(GMUGeometryRenderer.o)
      objc-class-ref in GoogleMapsUtils(GMUDefaultClusterRenderer.o)
      __OBJC_$_CATEGORY_GMSMarker_$_GMSMarker_GMUClusteritem in GoogleMapsUtils(GMSMarker+GMUClusteritem.o)
  "_OBJC_METACLASS_$_GMSSyncTileLayer", referenced from:
      _OBJC_METACLASS_$_GMUHeatmapTileLayer in GoogleMapsUtils(GMUHeatmapTileLayer.o)
  "_OBJC_CLASS_$_GMSPolyline", referenced from:
      objc-class-ref in GoogleMapsUtils(GMUGeometryRenderer.o)
  "_OBJC_CLASS_$_GMSSyncTileLayer", referenced from:
      _OBJC_CLASS_$_GMUHeatmapTileLayer in GoogleMapsUtils(GMUHeatmapTileLayer.o)
  "_kGMSTileLayerNoTile", referenced from:
      -[GMUHeatmapTileLayer tileForX:y:zoom:] in GoogleMapsUtils(GMUHeatmapTileLayer.o)
  "_GMSProject", referenced from:
      -[GMUGridBasedClusterAlgorithm clustersAtZoom:] in GoogleMapsUtils(GMUGridBasedClusterAlgorithm.o)
      -[GMUWeightedLatLng initWithCoordinate:intensity:] in GoogleMapsUtils(GMUWeightedLatLng.o)
      -[GMUClusterItemQuadItem initWithClusterItem:] in GoogleMapsUtils(GMUNonHierarchicalDistanceBasedAlgorithm.o)
      -[GMUNonHierarchicalDistanceBasedAlgorithm clustersAtZoom:] in GoogleMapsUtils(GMUNonHierarchicalDistanceBasedAlgorithm.o)
  "_GMSUnproject", referenced from:
      -[GMUGridBasedClusterAlgorithm clustersAtZoom:] in GoogleMapsUtils(GMUGridBasedClusterAlgorithm.o)
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)

[michael-mckenna]

@arriolac I had a bunch of misc build errors I had to resolve. After resolving I tried building the project but got an issue with this library. I was able to replicate on a brand new project.

[arriolac]

hmm strange. x86_64 is a supported architecture. I will take a look

[arriolac]

I was able to add this library via SPM on the SwiftDemoApp under samples/SwiftDemoApp. You can check my branch chris/fix/326.

Are there other steps you can share so I can try to repro? I also double checked the architectures included in the .xcframework and confirmed that "x86_64" was included.

[michael-mckenna]

I couldn't load your sample.

even after logging in.

However, I noticed the url you're using is [email protected]:googlemaps/google-maps-ios-utils.git but I'm using https://github.com/googlemaps/google-maps-ios-utils.git. Not sure if that will make a difference.

I have pushed a sample app here. All I did was:

1. Create a new Xcode project with Storyboard selected
   

2. Add this dependency via SwiftPM at version 3.2.1 with url https://github.com/googlemaps/google-maps-ios-utils.git
   
   

3. Add -ObjC under "Other Linker Flags"
   

4. Build (CMD+B)
   

[michael-mckenna]

Using the linked repo on another device I was able to replicate the same issue. So unlike the Carthage issue I had a while back, I don't think the issue is device based this time =P

[arriolac]

Have you included the Maps SDK (either via CocoaPods or Carthage) to your project? Note that the Maps SDK does not support SPM yet.

[michael-mckenna]

Awkward, no I did not lol. Makes sense. In all fairness I thought it would've been automatically pulled in, which seemed to be the case with Carthage where google maps was a transitive dependency so I didn't add a separate line for that

[arriolac]

Maps SDK can definitely be packaged transitively. I choose not to go that route, but now thinking about it, that's probably a lower friction integration.

[arriolac]

@michael-mckenna I'm going to close this issue. Let's continue the discussion of packaging Maps SDK for iOS transitively in #329. Thanks for bringing this up, hopefully implementing #329 will ease some integration pains!