Search results for

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

186,320 results found

Post

Replies

Boosts

Views

Activity

Reply to Xcode 12.3 failed on some 3rd framework and librarys?
This framework isn't built with a supported configuration -- iOS and iOS Simulator code has never been supported in the same binary. The linker in Xcode 11 began identifying these incorrect configurations and issuing warnings, and Xcode 12 goes further in identifying these issues. The only correct way to resolve this is to rebuild the framework as an XCFramework. - https://developer.apple.com/videos/play/wwdc2019/416/ If this is your framework, or owned by another group in your company, follow the information in the video and the Xcode Help article. - https://help.apple.com/xcode/mac/current/#/dev544efab96 If this framework is from a vendor, then you need to work with the vendor to get an updated version of the framework built with supported configuration. In the discussion of this thread, there is a build script that attempts to resolve this error. Scripts like that -- anything that tries to manipulate the outp
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Dec ’20
Multiplatform project error on Xcode 14 beta: Your target is built for macOS but contains embedded content built for the iOS platform
When creating a new Multiplatform project on Xcode 14 beta and adding a Notification Service Extension Target, compilation fails with: error build: Your target is built for macOS but contains embedded content built for the iOS platform (Notification.appex), which is not allowed. This really limits the usefulness of the new multiplatform single target, especially if we cannot incorporate basic extensions. Is there any way to use single target multiplatform and still have the freedom to add necessary extensions to the app?
Topic: Developer Tools & Services SubTopic: Xcode Tags:
3
0
4k
Jun ’22
Embedded Frameworks in Swift 4.1
I have a swift framework called Extensions that I embed in my applications. As the name implies, this framework provides a lot of commonly used extensions to Swift.I have a 2nd swift framework called Utilities that I also embed in my applications. Again, commonly used Swift utilitiy classes, structs and methods.Currently I am declaring the specific extensions I need to use in Utilities as fileprivate in the appropriate places in Utilities but I really hate the duplication.All this works well but now I would prefer to have Utilities use these extensions directly from framework Extensions.Is this possible without embedding a 2nd copy of Extensions within Utilities?
Topic: Programming Languages SubTopic: Swift Tags:
1
0
621
May ’18
Reply to App Won't Compile with Embedded Third Party Framework: Could not install at this time. Failed to load Info.plist from bundle at path
Thanks a lot for the reply. My original configuration was exactly as described in the link:If your app has dependencies between frameworks, configure the dependency with these instructions:In the framework target's General settings, add the frameworks it depends on to the Linked Frameworks and Libraries section, as shown in Figure 2.In the app project, follow the instructions for Embedding a Framework. The app target is responsible for embedding all of the frameworks, including any frameworks that other frameworks depend on.---My framework references the 3rd party framework (as described in point number 1). And my main app embeds the third party framework (as described in point number 2).This has always worked for me (until now). The app build will succeed but it won't launch (get the error about the info.plist as mentioned in my original post).Now because I'm just trying to g
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Dec ’19
How to link an App project to a Framework project so that changes made to the Framework code are "seen" in the App code without explicitly building the Framework code in Terminal?
I have learned how to create my own framework for iOS and iOS Simulator and then creating a single xcframework that I can drop into any project that needs to use my xcframework. So if I am working on an app, I can go to the app's project navigator > General tab > Frameworks, Libraries, and Embedded Content section, and drag my xcframework from Finder into that section. It works just fine. But while working on the app, if I realize I need to make a change to the framework, I'd have to launch the project for the framework, make my changes, then in Terminal, run xcodebuild archive, run xcodebuild -create-xcframework, then go back to my app, run Cmd-B / Cmd-R to build/run it. And if there are still issues in the framework code, I'd have to keep executing these steps over and over again. Is there a way to somehow link my app project to the framework project such that I simply make changes to the framework
Topic: Programming Languages SubTopic: Swift Tags:
1
0
2.4k
Aug ’21
Reply to Using a Brew-installed library on visionOS?
[quote='760198021, JetForMe, /thread/760198, /profile/JetForMe'] Can I make an xcframework out of it? [/quote] Yes you can, and we have an article for that with a section of tips for build tools like make: Creating a multiplatform binary framework bundle However, as Quinn said, you still need to be willing to dig around this project's configuration to locate the commands it issues to the complier, and insert the correct tuple for the different platform variations. I see also that this is building a bare dylib, and not a framework, which means you should also look to build the library as a static library instead, because bare dylbs (those outside of a framework bundle) are not supported on visionOS (nor on iOS). But once you've done those items, you can feed the built static library into an XCFramework so that you can encapsulate visionOS, visionOS Simulator, and even iOS variants into that framework bundle for s
Topic: Developer Tools & Services SubTopic: General Tags:
Jul ’24
Reply to Embed/Do Not Embed & Mach-O type
Ah, I thought might be the case. The simulator works a bit like macOS, where Xcode sets things up so that your app can load a framework from the build products directory. That won’t work on a real device, where the framework must be embedded in the app’s bundle. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic: Developer Tools & Services SubTopic: General Tags:
Oct ’25
Reply to Code Sign on Copy does not work for nested frameworks in Xcode 8
Maybe I come too late but I was looking for the same answers and I found a sane recommendation in the Carthage wiki:If the embedded framework in your project has dependencies to other frameworks you must link them to application target (even if application target does not have dependency to that frameworks and never uses them).This actually makes some sense to avoid conflicts in case if the developer of the app decides to link to FC not knowing that FB already uses FC, and maybe even another version of it.And also I found an official note here:https://developer.apple.com/library/content/technotes/tn2435/_index.htmlsaying one important thing:The app target is responsible for embedding all of the frameworks, including any frameworks that other frameworks depend on.See the section Apps with Dependencies Between Frameworks for full instructions. This means, if your framework B depends on framework
Topic: Code Signing SubTopic: Certificates, Identifiers & Profiles Tags:
Jan ’17
Reply to Adding XCFramework creates swift support folder missing error.
Thanks for the test project! Your XCFramework has the following contents, edited down for clarity: SampleForDevSupport/TNoodleLibNative.xcframework ├── Info.plist ├── ios-arm64 │ └── lib-scrambles.dylib └── ios-x86_64-simulator └── lib-scrambles.dylib That bare dylib file is then going to be directly embedded in your app, at a path like Your.app/Frameworks/lib-scrambles.dylib. That runs afoul of the framework embedding rules that I describe in another thread, which in turn is the top reason people ask for help with these Invalid Swift Support errors. In case this is a point of confusion in your circumstance, an XCFramework is not the same as having a framework bundle, which is what is actually required here. An XCFramework is a container, into which multiple copies of a .framework (which is the part that matters) are included. There's multiple paths to resolution here. I'm outlining them all for the many people who may come acros
Topic: Developer Tools & Services SubTopic: General Tags:
Mar ’25
Reply to App crashes from Xcode 11
I had the same issue using Xcode 11.5. I was initially developping an iOS app with Catalyst enabled. I started then to add a watchOS app Extension. Xcode automatically linked the Watch.app for iOS and macOS.It looks like embedding framework can cause issue with Catalyst. To resolve the issue, I had to go to my iOS target > General > Frameworks, Libraries, and Embedded Content and select iOS for Watch.app only and not macOS + iOS.
Topic: Programming Languages SubTopic: Swift Tags:
May ’20
Change in Xcode 7 prevents framework from compiling "building for OSX, but linking in object file built for iOS, for architecture x86_64"
An OS X app I'm working on won't compile now in Xcode 7. Previously in Xcode 6 everything was fine. I have a framework I put together awhile ago that links against several third party libraries (already compile .a). Worked like a charm before. In the original project (where the .a files were retreieved) has x86_64 and i386 in the list of valid architectures.The thrid party library I got these .a files comes with the .a already compiled (no subprojects so I can't just create another target and recompile it). These are all open source, cross-platform libraries ...with forks all over the place on the net...tracking down the source code for a compatible version and recompiling under Xcode 7 to swap in could take some time... maybe even a few days.I'm fairly certain that these .a's will run just fine on 64 bit Macs...I'm at the tail end of the development of this app and I've tested it out plenty of times with Xcode 6.4. Is there a workaround to this?Thanks a lot.
Topic: Developer Tools & Services SubTopic: General Tags:
3
0
1.1k
Oct ’15
Reply to Xcode 12.5 "code signature version is no longer supported"
I had this issue and found the solution. It's not about Xcode 12.5, but running on a device with iOS 14.5+. My project was embedding 2 static frameworks (see @idelfonso answer) and the issue was fixed when I changed them to [Do Not Embed]. However, the correct answer here is not to [Do Not Embed] every framework you have, as you actually need to embed dynamic frameworks, your app will crash upon launch otherwise. Use 'file' command line to find out if the framework is dynamic or static. For example: bash file Frameworks/Flutter.framework/Flutter Frameworks/Flutter.framework/Flutter: Mach-O universal binary with 3 architectures: [x86_64:Mach-O 64-bit dynamically linked shared library x86_64] [arm_v7] [arm64] Frameworks/Flutter.framework/Flutter (for architecture x86_64): Mach-O 64-bit dynamically linked shared library x86_64 Frameworks/Flutter.framework/Flutter (for architecture armv7): Mach-O dynamicall
Topic: Developer Tools & Services SubTopic: Xcode Tags:
May ’21
Reply to Mac Catalyst and OpenSSL
The OpenSSL libraries librypto.a and libssl.a cannot be defined as conditionally being linked: Due to the same names Xcode is only reflecting one platform version in its build phases, and it is not possible to define them platform specific. The solution is to combine these libraries into an XCFramework, so the right architecture for a build target is used automatically. I've done this using <https://github.com/balthisar/openssl-xcframeworks/releases> ... actually I downloaded the binaries (although they could be built using the sources / scripts in the GitHub repo). I still had to add OpenSSL header files (and their header search path) as the dynamically generated Receigen file cannot include the frameworks headers. So my project runs on iOS simulator, iOS device and Mac Catalyst, and I only need to figure out the receipt validation thing... Greetings, Mattes
Topic: App & System Services SubTopic: StoreKit Tags:
Aug ’20