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

Hi, I am developing a dynamic framework using xcode 6.4. I am able to generate the debug build for it which is available in debug-iPhones and debug-iPhonesimulators folders under Products Group. But I am not able to generate the release build for the same. I tried editing the scheme but it didn't work.Also I dont want to go with archive option as it works only in device. I want the release build to work for the simulators as well as for the devices. So, I want the release build to be generated in release-iPhones and release-iPhonesimulators folders, same as in case of debug build.What is the procedure to generate release build for framework?

Hi,So I've been trying to setup universal links and have gotten working on actual devices. However I'm unable to get them to work within the iOS simulator.I've seen conflicting comments about this through some searchs and am hoping I can get a definetive answer.It does say in the documentation that it works:https://developer.apple.com/library/ios/documentation/General/Conceptual/AppSearch/UniversalLinks.htmlThanks.

I have a Mac OS application that's linked against a few dynamic libraries. Previously I hadn't needed to configure anything in particular in XCode. When exporting the application the libraries were automatically copied into the archive in a folder called libs. When running otool on the version of the app created by XCode 11, I see this: @executable_path/../libs/libsqlite3.0.dylib (compatibility version 9.0.0, current version 9.6.0) @executable_path/../libs/libcrypto.1.0.0.dylib (compatibility version 1.0.0, current version 1.0.0) I'm now trying to export my app on Big Sur using Xcode 12. With no configuration changes on my behalf, the libraries were no longer exported at all, so the app wouldn't work on any other machine. To try to fix the issue I'm telling Xcode to embed them from the general settings. Xcode then adds them to the copy phase, and they are now exported (albeit in the Frameworks folder): The run path search option it set to: @loaderpath/../Frameworks @executablepath/.

Hello, I have a custom script that builds a library needed for integrating Rust code into a project. The script works just fine when I build for the simulator. But, when I switch the target to an actual device (connected via USB) the script does not run. Here is what I have for the Run Script section: # Type a script or drag a script file from your workspace to insert its path. echo Running script... bash ${PROJECT_DIR}/bin/compile-library.sh shipping-rust-ffi $BUILDVARIANT echo ...completed Here is the relevant portion of the log when building for the simulator showing the script running: Here is the relevant portion of the log when building for hardware showing that phase being skipped: I have looked through all the Build Settings, Build Phases, and Build Rules sections with no luck. What I am doing is just a simple test app based upon this article: https://blog.mozilla.org/data/2022/01/31/this-week-in-glean-building-a

I released an App say 1.0 . Now , I am shipping a huge update say 2.0. But in 2.0 , I want to ship a framework of 1.0 , so that end users can fallback in case of any catastrophic issue in 2.0. Now my 1.0 uses a dynamic framework(say version 1.5) and few static libs(say version 1.5) Now my 2.0 app uses same libs and frameworks but different versions of them i.e. dynamic framework(say version 1.8) and static libs(say version 1.8) So my app running is 2.0 , here is what I want When 2.0 is running and 1.0 framework is NOT running , it should use dynamic framework(version 1.8) and static libs(version 1.8) When 2.0 is running and 1.0 framework is running , it should use dynamic framework(version 1.5) and static libs(version 1.5) Here is what I have done so far: Dynamic Framework of 1.0 is compiled and dynamic framework(version 1.5) and static libs(1.5) are not embedded into the framework But when I integrate

Hi,we are using a QLPreviewController in our App to preview PDF documents.For some reason the Links embedded in the PDF document are not opened in safari, even though the AlertView Leave APPNAME and open this link? is shown and confirmed.In our logs I see the following+[LSApplicationProxy applicationProxyFor*] is not a supported method for getting the LSApplicationProxy for the current process, use +[LSBundleProxy bundleProxyForCurrentProcess] instead.I also added the QLPreviewControllerDelegate to handle the callback shouldOpenUrl - however this callback is never firedfunc previewController(_ controller: QLPreviewController, shouldOpen url: URL, for item: QLPreviewItem) -> Bool { return true; }

Hi,It seems that I cannot find Cocoa framework in the Linked Frameworks and Libraries area. I am using xcode version 10.1. Anyone knows the steps to add it? Thanks.Best regards,Zhi Chen

The framework layout doesn't meet Apple's Bundle Guidelines. Everything is in the root of the bundle, with no Versions folder. I suspect it works because the main executable and the Resources folder are in the root. However Code sign doesn't complain about it either, unlike some other incorrectly formatted bundles. I ask because the documentation for bundle structures hasn't been updated since 2017 (https://developer.apple.com/library/archive/documentation/CoreFoundation/Conceptual/CFBundles/BundleTypes/BundleTypes.html#//apple_ref/doc/uid/10000123i-CH101-SW1) and I am wondering if there is newer documentation or perhaps Framework bundles no longer need to organized according to that documentation.