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

Hi, I tried to build the existing application with Xcode 12. It uses a oneDNN library which was built on macOS 10.15. But when we build the same application using Xcode12 we are seeing below error ld: warning: dylib (IntelMKLDNN/v14/maci64/lib/libdnnl.dylib) was built for newer macOS version (10.15) than being linked (10.14) Let me know how to resolve this issue. Thanks, Praveen.

I'm using Network framework for communication between devices. The first time I instantiate an NWBrowser, it will prompt the user with a popup that says: Allow <app name> to find devices on local networks? The problem is, once I upgraded from Xcode 15.4 to Xcode 16.4, the popup doesn't appear; it says in the debug window: nw_browser_fail_on_dns_error_locked [B1] nw_browser_dns_service_browse_callback failed: PolicyDenied(18,446,744,073,709,486,046) I do have the info.plist keys Privacy-Local Network Usage Description (NSLocalNetworkUsageDescription) and Bonjour Services (NSBonjourServices) so it's not that. Also, It still works on a real device. I think something changed with Xcode 16 that tightened the security on a simulator, or maybe disabled Network framework entirely. It's not the firewall on my computer because that is turned off. I'm using an M1 MacBook Pro.

I have an XCode project for a Mac App that's many years old. Recently, I decided to create a new XCode project and reimported all of the classes and assets to start fresh after constantly battling various compile errors. This worked great and I'm able to build and run without any of the previous issues. The one problem I have is linking my private framework. In Build Phases I added my framework to Link Binary With Libraries and to Copy Files. I also added the path to my framework in Build Settings > Search Paths > Framework Search Paths. This works but whereas in the previous project when I make a change to my framework project and build it, I can then switch to my app project and XCode recognizes my new method(s) etc. In my new project this is not the case, I am getting editor error - No visible @interface 'ClassName' declares the selector... I can change existing framework functions and see the

Hi everyone,I'm attempting to export my library as a .framework to be used in iOS apps. When I link the framework into a test app (simple app, one view controller that does nothing) and attempt to install the app on a device it fails to install on the device saying App installation failed. The application does not have a valid signature.. If I don't link the .framework it all installs fine.After looking around at these and other forums (primarily StackOverflow), I found that looking at the device logs provides a little bit more information about the error. Device logs:Dec 24 14:32:48 Indigos-iPhone installd[40] <Error>: 0x1005a4000 -[MICodeSigningVerifier performValidationWithError:]: 188: Failed to verify code signature of <MIExecutableBundle : path = /private/var/mobile/Library/Caches/com.apple.mobile.installd.staging/temp.pRDquy/extracted/LibraryTesting.app/Frameworks/Company.framework identifier = com.company.Company type = Framework

I wrote an iOS app that I've been able to run under Catalyst. It uses Bluetooth to communicate with devices (although this doesn't work in the Catalyst version for some reason; not what I'm asking about). On the Mac, I want to use serial communications through a USB-to-serial interface. I have a framework for Mac OS that does this. How would I link this framework into the Mac build created by Catalyst, but omit it from the iOS build? Thanks for any insight.

Sparkle.framework gets signed by an Archive pre-action script defined in my Release scheme: LOCATION=${BUILT_PRODUCTS_DIR}/${FRAMEWORKS_FOLDER_PATH} codesign --verbose --timestamp --force --deep -o runtime --sign ${CODE_SIGN_IDENTITY} $LOCATION/Contents/Frameworks/Sparkle.framework/Versions/A/Resources/AutoUpdate.app codesign --verbose --timestamp --force -o runtime --sign ${CODE_SIGN_IDENTITY} $LOCATION/Contents/Frameworks/Sparkle.framework/Versions/A xcodebuild however seems to ignore the signing results (ie none of Sparkle's files are signed in the resulting archive) when running xcodebuild with the following arguments: xcodebuild -scheme Release -configuration Release -archivePath App.xcarchive archive Notarizing my app therefore fails. What am I doing wrong here? I also tried signing using a Run Script phase during build, which resulted in No such file or directory errors.

For some reason, I can't seem to run the watchOS and the iOS app in parallel in their respective simulators.If I build the apps with the watchOS scheme, then the iOS simulator starts up, but the app does not. If I want to run the (watchOS-scheme-compiled) iOS-app manually, it closes immediately. The same (but vice versa) happens when I chose the iOS scheme. In that case the watchOS app hangs during startup in the watchOS simulator.How are we supposed to debug WatchConnectivity in that case? Or are my targets just messed up and it should work usually?

Every time I try to run with the iOS simulator it gives me an alert that says a build action is already running an asks me if I want to stop it, but when I push stop it does nothing and won't let me access it. If I click on iOS simulator without running it with the new code I created it has a window for a iPhone 5s but it also has another window thats not responding that is titled TV OUT- 640x480 and it won't let me close either window. Even when I quit iOS simulator and even force quit it they still both repapear when I open it again. I have been trying to reboot it and reset it but the windows just keep reappearing! I want to run my code but I can't if anybody has any suggestions to fix this problem that would be great. Thanks!

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

An iOS app running in simulator has complete access to the Mac's file system: // Files in protected directory like Desktop, Documents, Calendar, etc will need additional permissions. let filesInSystem = FileManager.default.enumerator(at: .currentDirectory(), includingPropertiesForKeys: nil)?.allObjects This isn't the case when running in device as the app is sandboxed. Is the same possible when running in simulator? More specifically, is there a way to restrict access to the Mac's file system when running an app in the Simulator? This is particularly useful when trying out binaries/frameworks that are not open sourced.

Hi! I have encountered the next problem during the creation of the .xcframework and building it for the simulator devices and couldn't find any solution for this problem. Could not find module ‘’ for target ‘x86_64-apple-ios-simulator’; Let's me describe the build process: First of all i build framework for the iOS simulator and for iOS device. xcodebuild BUILD_LIBRARY_FOR_DISTRIBUTION=YES t-scheme $(FRAMEWORK_NAME) t-derivedDataPath $(DERIVED_DATA) t-arch x86_64 t-sdk iphonesimulator t-mios-simulator-version-min='11.0' build xcodebuild BUILD_LIBRARY_FOR_DISTRIBUTION=YES t-scheme $(FRAMEWORK_NAME) t-derivedDataPath $(DERIVED_DATA) t-arch arm64 t-sdk iphoneos t-mios-version-min='11.0' build 2. Extract from derived data a build product and compose it in the xcframework xcodebuild -create-xcframework ttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttt

I try to build my code with Xcode 13 beta 1. But it shows the following message: Application extensions and any libraries they link to must be built with the APPLICATION_EXTENSION_API_ONLY build setting set to YES. I used to set this no NO so that my compiler won't give me the warnings of importing unsafe API for app extension. But I'm wondering is the new Xcode required to have the APPLICATION_EXTENSION_API_ONLY to true now?