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

We have a custom static library CMFLibrary which utilized Firebase pods. The library builds successfully however, embedding CMFLibrary in our test app produces the following build error e.g. ViewController class -> import CMFLibrary (build error: Missing required module 'Firebase'. I have tried different build settings etc per suggestions on SO and other web sites. Same error each time. This is a critical issue. Help would be appreciated. D

I’m running into an issue while implementing JournalingSuggestions with Xcode 16.2 and the iOS 18 simulator. My code builds and runs fine on a physical device, but it consistently crashes on the simulator and in Xcode previews. I’ve tried several workarounds, including weak linking and solutions from this post (746843), but I’m still hitting a wall. Here’s what’s happening: I get a warning: JournalingSuggestions is not available when building for iOS Simulator. This is followed by a build error: Linker command failed with exit code 1 (use -v to see invocation). What I’ve Tried: Weak linking the JournalingSuggestions framework. Applying fixes from this post (746843), such as cleaning the build folder and using weak link. Deleting Derived Data and rebuilding. Testing on a physical device (works fine). My Setup: Xcode Version: 16.2 Simulator: iOS 18 Build Success: Works

I have built an .app for use on iOS simulator on appium. My tests fail because they are unable to locate specific xcuitest elements which are missing from a collection view. If i build an .ipa for real device, then the collection view loads these xcuitest elementsI have logged this with the Appium project but they tell me its a third party issueI have done a comparison of the app source code on the simulator app vs the .ipa real device app and found that there are collection views missing see https://www.diffchecker.com/PF4y3OhUI have built the simulator app via the following command: e.g.xcodebuild -workspace '/Users/.../apps_ios/<app>.xcworkspace' -scheme 'dev' -arch x86_64 -sdk iphonesimulator10.3I am trying to locate the ‘Sort’ and ‘Filter’ buttons as per screenshots attached Simulator build:https://user-images.githubusercontent.com/1721580/27862852-a6dce43e-6187-11e7-8874-b36d00152b9b.pngReal device build:Here I am able to insp

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'm running into a problem that I'm not quite sure how to solve.I have a stand alone message app that has a few embedded frameworks that I have written. In a normal app, those frameworks can live within the container app, and the extensions can reference them. With a message app, the dummy container app has no way to manage frameworks/linked libraries, so the message extension needs to manage them. This means the .appex now contains a framework folder within it.When attempting to upload the binary, TestFlight returns the following error:ERROR ITMS-90205: Invalid Bundle. The bundle at 'XXXXXX.app/PlugIns/XXXXXXX.appex' contains disallowed nested bundles. I'm not exactly sure how to manage the frameworks in this particular heirarchy to please the TestFlight Gods and get the app processed.Has anyone successfully submitted a standalone message app with embedded frameworks? Should I file a rdar?

Hi. We're attempting to submit an app to the app store but is being rejected due to ERROR ITMS-90205: Invalid Bundle. The bundle at [...] contains disallowed nested bundles. There is indeed an app and a framework bundled together. I'm not sure if I've set it up incorrectly or if there's some sort of trick you need to do to get it accepted if you have an app that depends on a custom framework.Both app and framework are written purely in Objective-C.The app compiles without warnings and installs and runs correctly on devices in both Debug and Release configurations. The Archive is also created without issue. It's only when we submit to the App Store that it complains about nested bundles. The workspace setup is as follows:ourApp Target -> General -> Embedded Binaries -> ourFramework.framework -> Linked Frameworks and Libraries -> ourFramework.framework, Status = Required -> Build Phases -> Link Binary with Libraries -> ourFra

Hi,I have application, where the deployment target is 7.0. And using 1 third party lib, which is built based on 8.0. And then I am getting following linker warning:ld: warning: object file (/Users/xxxxxxx/Build/Products/Debug-iphoneos/xxxxxFramework.a(polymorphic_oarchive.o)) was built for newer iOS version (8.0) than being linked (7.0)But my application continues to work good. So let me know does this warning have any significance to apple certification process?Thanks.RahulG

I installed the latest version of Xcode and its Simulators. It takes about an hour for the simulator to load and launch. And when it does run, the entire computer's response to any click or keyboard input is very slow. Is anyone else having this problem? I am running on a late 2013, 21.5 8GB iMac. The simulator is running as iOS 14.

Hello!Last month I bought a new MacBook Pro 13 (early 2015, Core i5 2.7 GHz, 8 Gb RAM, 256 Gb SSD). After clean installation of Xcode 7.3.1 I get simulator that is working slowly. I can see it even in built-in applications like Calendar or Settings. When I'm trying to scroll lists in these applications, they freeze and scroll jerky.I've tried to toggle on/off slow animation mode, but it has no effect.Have anybody this problem? Or may be my MacBook Pro is not enough powerfull for iOS developing?

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

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