When compiling for ARM64 simulator (used with m1 Mac), the pod install fails because this package, I think, relies on Google Places pod which doesn't support ARM64. As a workaround, I could change my iOS app project's architecture I think but that's more of a temporarily workaround instead of a solution.
Is this an issue that can be resolved or do we need to open/find a PR at Google Places iOS package?
Logs:
Error (Xcode): Building for iOS Simulator, but linking in object file built for iOS, file '<path_to_flutter_project>/ios/Pods/GooglePlaces/Frameworks/GooglePlaces.framework/GooglePlaces' for architecture arm64
Could not build the application for the simulator.
Error launching application on iPhone 12 Pro.
That comment basically says that its not possible when using Google Places plugin from Cocoapods, but there are 2 other ways to get a beta version of this Google Places plugin installed that supports ARM64 natively with XCFramework:
https://developers.google.com/maps/documentation/ios-sdk/config#download-sdk
I guess it has nothing to do with @matanshukry's package, more of a Google Places issue 👎 . Any thoughts?
When compiling for ARM64 simulator (used with m1 Mac), the pod install fails because this package, I think, relies on Google Places pod which doesn't support ARM64. As a workaround, I could change my iOS app project's architecture I think but that's more of a temporarily workaround instead of a solution.
Is this an issue that can be resolved or do we need to open/find a PR at Google Places iOS package?
Logs:
I've found this PR with a comment that explains what is happening with Google Places: https://github.com/googlemaps/google-maps-ios-utils/issues/355#issuecomment-1060959728
That comment basically says that its not possible when using Google Places plugin from Cocoapods, but there are 2 other ways to get a beta version of this Google Places plugin installed that supports ARM64 natively with XCFramework: https://developers.google.com/maps/documentation/ios-sdk/config#download-sdk
I guess it has nothing to do with @matanshukry's package, more of a Google Places issue 👎 . Any thoughts?