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

Hello, I'm trying to port my framework CI to xCode Cloud and i have to create the release build that contains iOS ios-arm64 and ios-arm64_x86_64-simulator architectures for being able to build the XCFramework on iOS devices and Simulators. I looked in the Archive Action in the Xcode Cloud options but the Platform selector has iOS but not not Simulator. Currently i achieved the results that i needed by adding a ci_scripts/ ci_pre_xcodebuild and working with old fashion xcodebuild archive command and works fine . Can i achieve what i want without the sh script by using predefined actions from Xcode Cloud ? Thanks, Florin

I have a third party framework 'serviceCommon' built using Xcode 12.5.1 (12E507). When I try to build my app which links to this framework, Xcode 13 beta 4(13A5201i) fails with the following error (FYI. Xcode 12.5.1 is able to build this app fine). Failed to build module 'serviceCommon'; this SDK is not supported by the compiler (the SDK is built with 'Apple Swift version 5.4.2 (swiftlang-1205.0.28.2 clang-1205.0.19.57)', while this compiler is 'Apple Swift version 5.5 (swiftlang-1300.0.27.6 clang-1300.0.27.2)'). Please select a toolchain which matches the SDK.

When trying to build and run our iOS app on the simulator we're hitting the following error: Could not attach to pid: XXXXX failed to get reply to handshake packet within timeout of 6.0 seconds I've included some more details on our project/setup below: We're working on a large project with multiple schemes / app targets. The error only affects one of our targets - however the dependencies between the problematic target and the others are very similar. The issue only affects building to the simulator; building to a physical device works fine. Scheme configuration is the same across all targets. We've faced this issue on multiple versions of Xcode, from 15.x through to the latest 16.3 RC. We've tried a number of workarounds, some of which work intermittently for some colleagues - but none of which have provided a durable solution. These include varying combinations of: Setting the IDEPreferLogStreaming=YES environment variable Unchecking Debug Executable un

Hello!I'm trying to use dlib on iOS. So, I found a tutorial which describes how I can do this. I did everything exactly with this recommendation, including adding in the Xcode Other Linker Flags these items:/usr/lib/liblapack.dylib /usr/local/lib/libjpeg.dylib /usr/local/lib/libpng.dylib /usr/lib/libcblas.dylibBut after my try of building I get Xcode linker error which says:ld: building for iOS simulator, but linking against dylib built for OSX, file X for architecture x86_64Where X - every library which listed above.So, is this a correct building and using of dlib for iOS? And how can I use(or build) these libraries on iOS?Any help will be very useful!

I am trying to run the Application with our custom framework. Framewok itself contains other frameworks.When trying to launch the Application I am geting a following error:dyld: Library not loaded: @rpathX.framework/X Referenced from: /private/var/mobile/Containers/Bundle/Application/.../FrameworksY.framework/Y Reason: no suitable image found. Did find: /private/var/mobile/Containers/Bundle/Application/.../Frameworks/Y.framework/Frameworks/X.framework/X: mmap() error 1 at address=0x101270000, size=0x00044000 segment=__TEXT in Segment::map() mapping /private/var/mobile/Containers/Bundle/Application/.../Frameworks/Y.framework/Frameworks/X.framework/XWith Xcode 7 beta 3 everything was ok.May be someone have similar issue?

When you build your project, what makes a framework usable is a two-stage process. You first import the framework's header in order to compile and it must link to the framework's binary so that they can interact with each other during runtime. But, how am I allowed to use the Apple's frameworks by only importing them and not linking them in to your target in the Build Phase ? For example, I've seen some people manually add MapKit to the Link Binary With Libraries section of Build Phase , but it works perfectly fine without doing so. What is the rule of thumb? Do I ever have to do this process manually? Do I have to make sure to do this for the 3rd party frameworks?

I would like to build a simulator build using Terminal and xcodebuild. Up until now passing something similar like -sdk iphonesimulator9.0 worked. Now that the watch extension is running on the watch I receive this error :=== BUILD TARGET appName WatchKit Extension OF PROJECT appName WITH CONFIGURATION Debug === Check dependencies target specifies product type 'com.apple.product-type.watchkit2-extension', but there's no such product type for the 'iphonesimulator' platformDo you know how can someone build simulator version of their app which has watchOS2 support?Thanks!

I have a custom framework built and when an end developer uses my custom framework and if the app crashes it shows the the framework build path (The local machine path from which the framework was built).Please help me with this as it's not correct to show the local path of the farmework in the end users console.It happens in Xcode 11 only and it wasn't happening in the previous version of xcode.