#Google maps for mac computer pro#
#Google maps for mac computer code#

#Google maps for mac computer pro#

How was this closed? It is definitely not working on my M1 Pro on simulator, seems there's a difference between arm64 for phone and for simulator?Д«uilding for iOS Simulator, but linking in object file built for iOS, file './Pods/GoogleMaps/Base/Frameworks/amework/GoogleMapsBase' for architecture arm64 Now you can use this XCFramework on both an iOS device and a Simulator on a Mac ARM рџЋ‰

#Google maps for mac computer code#

Paste the following code inside the ist file:.Now copy-paste the framework inside the iOS folder into the ios-arm64_armv7 folder and the framework inside the Sim folder into the ios-arm64_i386_x86_64-simulator.Enter into that folder and create a couple of folders: ios-arm64_armv7 and ios-arm64_i386_x86_64-simulator.The final step is to manually create the XCFramework: Replace the Sim/SDK.framework/SDK with the newly fat one.Дelete the iOS/SDK.framework/SDK without the armv7 architecture and get back the original one. Lipo -create iOS/SDK.framework/SDK Sim/SDK.framework/SDK -output SDK Now that we have the Simulator arm64 architecture, we should merge it with the other Simulator ones: i386 and x86_64: Next, convert the remaining arm64 architecture from LC_VERSION_MIN_IPHONEOS to IOSSIMULATOR:Дelete the old SDK executable and replace it with the SDK.reworked one. Lipo -remove armv7 iOS/SDK.framework/SDK -output SDK The first step is removing the armv7 architecture inside the iOS executable. If we try to just change it on the arm64 for iOS, while building the XCFramework by using xcodebuild we will get the binaries with multiple platforms are not supported.ДЄn XCFramework is just a folder with inside a couple of folders (one for Simulator and one for iOS) and its plist. So, by following the guide, we should change the Mach-O header to let it run on the arm64 for Simulator.

iOS framework ( armv7 and arm64 architectures) - Inside a Sim folder.

Simulator framework ( i386 and x86_64 architectures) - Inside an iOS folder.

I don't know if it works for your framework because our third-party framework only supported iOS, but this is the guide: I found a similar solution for a third-party framework that we had on our app, by using the following Bogo's guide and by manually creating an XCFramework instead of using xcodebuild.