Building for iOS Simulator, but the linked and embedded framework ‘XX.framework‘ was built for

Hey everyone, I'm encountering an issue when trying to run my iOS application, which integrates a Unity project, on the iOS Simulator. I'm consistently getting a dlopen error 232 related to UnityFramework.framework. The full error message is: Error loading ...UnityFramework.framework/UnityFramework (232): dlopen(...UnityFramework.framework/UnityFramework, 0x0109): tried: '...UnityFramework.framework/UnityFramework' (mach-o file (...UnityFramework.framework/UnityFramework), but incompatible platform (have 'iOS', need 'iOS-sim')) It seems like the UnityFramework.framework is built for a physical iOS device (ARM architecture), but the simulator requires a different architecture (x86_64 for Intel Macs or arm64 for Apple Silicon Macs). I've already tried: Cleaning the build folder in Xcode. Checking the Frameworks, Libraries, and Embedded Content settings in my target's General tab. Could anyone provide guidance on h

I create a new project, and drag the Google WebRTC.framework in it, Embed and Sign. But there is a error occurring when the project build. Building for iOS Simulator, but linking in dylib built for iOS, file '/Users/xxx/Desktop/WrtcDemo/WrtcDemo/WebRTC.framework/WebRTC' for architecture arm64 And I add the Run Script on the Build Phases # Type a script or drag a script file from your workspace to insert its path. APP_PATH=${TARGET_BUILD_DIR}/${WRAPPER_NAME} echo $APP_PATH find $APP_PATH -name 'WebRTC.framework' -type d | while read -r FRAMEWORK do FRAMEWORK_EXECUTABLE_NAME=$(defaults read $FRAMEWORK/Info.plist CFBundleExecutable) FRAMEWORK_EXECUTABLE_PATH=$FRAMEWORK/$FRAMEWORK_EXECUTABLE_NAME echo Executable is $FRAMEWORK_EXECUTABLE_PATH EXTRACTED_ARCHS=() for ARCH in $ARCHS do echo Extracting $ARCH from $FRAMEWORK_EXECUTABLE_NAME lipo -extract $ARCH $FRAMEWORK_EXECUTABLE_PATH -o $FRAMEWORK_EXECUTABLE_PATH-$ARCH

Hello there, I'm struggling with the following issue since Xcode 15 arrived and haven't been able to solve it. I have a go library c-archive library which I'm using in a iOS app and build were OK until Sonoma updated came last year. I updated all my go libraries and go runtime to latest version and still facing issues: my make script as follows: ios-arm64: CGO_ENABLED=1 GOOS=ios GOARCH=arm64 SDK=iphoneos SDK_PATH=xcrun --sdk iphoneos --show-sdk-path CARCH=arm64 CC=$(PWD)/clangwrap.sh CGO_CFLAGS=-fembed-bitcode go build -v -buildmode=c-archive -ldflags=-s -w -gcflags=all=-l -B -tags ios -o $(IOS_OUT)/btfs.a . If there is anything else you need I can share more details. Thanks!

I'm having a problem with a custom framework and iOS 12.5.1. XCode Version 12.4 iOS Version 12.5.1 - iPhone 5S The problem is, when i build the framework with Build for distribution = NO it builds and I can usee it on my app, everything works well, when I build the framework with Build for distribution = YES I have an error: Unknown class _exampleClass in Interface Builder file. Could not cast value of type 'UIViewController' (0x2736dd2b0) to 'mySDK.myCustomClass' (0x1026a5008). 2021-04-06 15:43:14.709001+0100 MyApp[822:200663] Could not cast value of type 'UIViewController' (0x2736dd2b0) to 'mySDK.myCustomClass' (0x1026a5008). Said problem only happens on ios 12.5.1 and with Build for Distribution = YES. On ios 13 or 14 it works great, and if I use Build for Distribution = NO it works on all devices with all ios versions. Any lights??? Thanks!!!!!!

Hello,We are making some framewroks for distribution, until now it was only static libraries, but we jumped the wagon to the hopefully more user-friendly Dynamic Frameworks.It seems there is a bug (or is it a feature?) preventing users from submitting their apps to the app store because they contain the Simulator Slice (which isn't stripped correctly in certain versions of Xcode, fixed in later 6 versions and back in the 7th again).Our users vary from large firms developers to small beginners, so we can't expect them to handle stripping these slices, and it negates any user-friendliness to provide them with two frameworks (one for simulators and one for devices).Is there any easier way to deploy dynamic frameworks?I've seen some bigger companies (Twitter, Facebook, etc) seemingly having perfectly functionning dynamic frameworks, what would be the secret?Thank you.Ein

Using Xcode 12.2, the specific error is building for iOS Simulator, but linking in object file built for iOS, file '.../FIRAnalyticsConnector' for architecture arm64. I've seen reports of this as an Xcode 12/Cocoapods issue that my project didn't have with 12.1 or 12.0. It only popped up when trying to build on my new M1 MacBook Air and Xcode 12. I've tried everything that's been reported to fix it, no dice. 1) I've tried pod install & pod update with a Rosetta2 version of Terminal. Both complete without error, but Xcode still can't build. 2) I've set excluded architectures to Arm64 on the project, target and pod project. 3) I've added x8664 and i386 to Architectures for project, target and pod project. 4) I've set all configurations to Build Active Architecture Only to Yes. 5) I've even created (and deleted) a VALIDARCHS user defined setting with the proper architectures to all three projects. 6) I've cleaned build