Search results for

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

186,355 results found

Post

Replies

Boosts

Views

Activity

Reply to Static library inside iOS Framework error
I cross verified Library C is a lipo file (simulator and device). Framework B is a simulator file and i am building in App Project A with simulator. Is there anything to do with modulemap? I tried App project A as a Objective C project. Still seeing the same error. If i remove Library C from Framework B then A is working fine.
Topic: UI Frameworks SubTopic: UIKit Tags:
Mar ’17
Reply to copy on code sign, where does version come from?
This is a cross platform library built as framework for OSX and iOS, and the version tag is what it is to cover all platforms.Yeah, I thought you might be heading in that direction. What’s your deployment target for this framework? These days most macOS products (and all products on iOS-based platforms) are self contained. As such, there’s no point have multiple versions of the code nested within your framework, because the framework is embedded within an app that contains all of its client code.Moreover doing this is actively harmful:It makes the framework bigger than necessary.It puts you well off the beaten path, as you’ve discovered here.Regardless, if you want to keep going down with path you should check out the --bundle-version option to codesign. Share and Enjoy — Quinn “The Eskimo!” Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com
Topic: Code Signing SubTopic: General Tags:
Oct ’16
Framework fails to link in Xcode 10
My App uses a static framework A (built as a dependency) which itself uses a static framework B. In Xcode 9 this built and worked fine. In Xcode 10 I get Undefined symbols for architecture x86_64 followed by a list of symbols used in A defined in B. However, nm shows the symbols are present in A:nm -m -arch x86_64 A | grep <missing symbol> (undefined) external <missing symbol>Why is this only failing in Xcode 10?
1
0
2.5k
Sep ’18
Xcode 7 does not build ios swift project with c++ framework
I can't build project with a new version of the opencv 3.0.0 framework (version 2 DID NOT have this problem).Xcode 7 does not compile c++ sources as c++.Here's the simplest setup that is not building:1. Download the 3.0.0 framework from here http://netix.dl.sourceforge.net/project/opencvlibrary/opencv-ios/3.0.0/opencv2.framework.zip2. Create the simplest ios project with Swift language.3. Drag-and-drop the framework to the project.4. Create the `Objective-C++` source and headers and add them to the project.5. Create the bridging header.Here's the setup:http://i.stack.imgur.com/vWp0X.pnghttp://i.stack.imgur.com/nQi8C.png6. Build.And here's what the compiler says:opencv2.framework/Headers/core/base.hpp:49:4: error: base.hpp header must be compiled as C++http://i.stack.imgur.com/Ak69F.pngWhy is that? I've got the `.mm` file and it is supposed to compile as the Objective-C++ source.
2
0
3.6k
Sep ’15
Unable to boot the iOS simulator
After upgrading to El Capitan, I now get this error when running my simulator for 7.1 using Xcode 6.3.2 (8.3 simulators are fine)1) I checked for /etc/launchd.conf and there is none2) I tried deleting the 7.1 runtime and reinstalling it from xcode / preferences / components3) I tried deleting and readding the simulator for the devices (4s, 5, etc)3) I tried Xcode 7 BetaHere are some logs from https://forums.developer.apple.com/message/5474#5474-Jun 16 11:55:30 com.apple.iphonesimulator[18024] <Error>: Error Domain=NSPOSIXErrorDomain Code=60 Unable to boot the iOS Simulator. UserInfo=0x7ffa9285bb30 {NSLocalizedDescription=Unable to boot the iOS Simulator., NSLocalizedFailureReason=launchd failed to respond.}-Process: launchd_sim [2066]Path: /Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 7.1.simruntime/Contents/Resources/RuntimeRoot/usr/libexec/launchd_simIdentifier: launchd_simVersion: ???Code Type: X86-64 (Native)Parent Proc
12
0
27k
Jun ’15
Reply to UITextView crashes with 100000+ characters
I have the problem with both Simulators (iPad, iPhone) and real Devices (iPad, iPhone).I tried with many iOS versions (older and newer), including several 13.0 betas on Simulator.Below I have added a link to a DemoApp that can be built and replicate the crash:- build and launch the app- a UiTextView layout gets displayed (it has 100001 characters in it)- you can scroll up/down the text but as soon as you CLICK or TAP on it, the app will CRASHI reported the issue to Apple Tech Support, they asked me to contact Apple Developer Feedback Assistant, they asked me for a demo, I sent them the same DemoApp, but haven't heard from them since! Perhaps they have other priorities with iOS 13, Catalina, Catalyst, etc.ThanksLink to DemoApp source (Objective-C):https://www.dropbox.com/s/hblpmqiqv9d8nil/DemoApp.zip?dl=0
Topic: UI Frameworks SubTopic: UIKit Tags:
Sep ’19
Reply to dyld Symbol not found
I have decided to not go the route of using a nested framework.Instead, in my Framework, I import the 3rd Party Framework to the project, use its functionality, but dont add it to the 'Linked Libraries and Frameworks' section. This builds fine, but doesnt include the 3rd Party Framework in the framework directory / bundle. In the app project, I then add the Framework, and the 3rd Party Framework directly to the app project via 'Embedded Binaries'. This builds and deploys to device with no errors.In Framework -Always Embed Swift Standard Libraries:NoFramework Search Paths:$(inherited)$(PROJECT_DIR)$(PROJECT_DIR)/<MyFramework>Runpath Search Paths:$(inherited)@executable_path@loader_path/Frameworks@executable_path/FrameworksInstallation Directory:$(LOCAL_LIBRARY_DIR)/FrameworksDynamic Library Install Name:$(DYLIB_INSTALL_NAME_BASE:standardizepath)/$(EXECUTABLE_PATH)Dynamic Library Install Na
Topic: Programming Languages SubTopic: Swift Tags:
May ’17
Reply to Xcode 13 beta | Failed to build module 'Network' for importation due to the errors above; the textual interface may be broken by project issues or a compiler bug
I’m not seeing this problem in Xcode 14.3. Now, the original problem was reported as being when you build for iOS 10 and the minimum supported deployment target for Xcode 14.3 is iOS 11, so I can’t test it exactly as above. However, I was able to do the following: Create a new project from the iOS > App template. Add an import of Network framework. Set the simulator run destination. Build it. Set the deployment target back to iOS 11. Build it. Set an actual device deployment target. Build it. Can you post more details about how your reproducing it? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Apr ’23
iOS 17.0 features not working when I have an iOS 17 simulator installed
I am on macOS 14.3 Release Candidate with Xcode 15.2 and iOS 17.2 simulators installed. If I attempt to use iOS 17 features such as the SwiftData framework, it throws an error despite running my project on an iOS 17 simulator with an error such as 'model context' is only available in iOS 17.0 or newer. I am in an iOS App Playground but I don't believe that this will change much (correct me if I'm wrong). How could I fix this issue so I can use these features in my application? Thanks
1
0
1.4k
Jan ’24
Embedded Framework - Swift Classes not in Interface Builder
I was recently running into an issue where I have a compiled framework that I embed into another application. This framework has both Objective-C and Swift code in it. The problem I was having was that none of my swift subclasses of UIKit based objects, such as UIViewController or UICollectionViewCell, were showing up for usage inside interface builder in my main project. All of the classes were available through use direclty in code though.After several days I finally discovered that the issue was if ANY of my swift UIKit classes used extensions, custom or things like UICollectionViewDelegate, then none of my siwft classes would be available in interface builder. However, if I moved the protocol implementations inside the class itself rather than an extension everything becomes available.I am assuming this has something to do with the compilation process of the code that it is generating something that makes interface builder unable to detect any of the swift UIKit classes.I was curious if
2
0
992
Apr ’18
Xcode Build Target Failure Because Of Simulator
I am unable to run my app out of Xcode. I have been able to run my app off of my iPhone and simulators in the past so I am not sure what is happening. I continue to get this error: rsync: [sender] link_stat /Users/myusername/Desktop/ProjectName/GitHub Repo/packageName/node_modules/expo-structured-headers/ios/EXStructuredHeaders.xcframework/ios-arm64/* failed: No such file or directory (2) but i can see that the file does exist I also have updated my rsync and have done the usual delete pod.lock file and then do pod update, pod install, I have also tried pod deintegrate and pod install. I have tried my physical phone as well as a phone simulator. I have tried clearing the simulator cache, creating a brand new simulator, changing the directory name, upgrading the expo package, upgrading all of the outdated packages....not sure what else to do. Any help would be appreciated.
0
0
1.3k
Apr ’22
Weird linker error: "building for macOS-x86_64 but attempting to link with file built for macOS-x86_64"
I've got a makefile that creates a library of object files using ar r mylib.a myobj1.o myobj2.o etc. Then I link with gcc main.o mylib.a -o myexe and I get the error above. Clear the error is complete garbage - it's complaining that I'm attempting to link with the architecture I've built for which is what you're supposed to do this isn't an error anyway! If I link directly with the object files it all works fine, so those objects are OK as is everything else. Something about putting them in a static library seems to hit a bug in ld therefore - evidenced by the garbage error message. The only other example I've found of this on google was 'fixed' by the poster using a more up-to-date version of the application he was compiling, so no help in what was the cause nor fix for the error. Anyone else come across this? Any thoughts on how to debug it further? Thanks.
3
0
6.9k
Nov ’21
App targeting iOS 8 with an intent extension crashes in the simulator
- I have an iOS app that targets iOS 8.- It includes an Intent Extension (for Siri Shortcuts).- It runs perfectly fine on iOS 12 (device + simulator) and 10 (simulator).- It crashes immediately in the iOS 8 simulator and outputs the following: dyld: Library not loaded: /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices Referenced from: /System/Library/Frameworks/Intents.framework/Intents Reason: no suitable image found. Did find: /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices: mach-o, but not built for iOS simulatorI realize that I won't be able to use the Intents Extension on older versions of iOS, but I still want my main app to work. From what I've read online, I should still be able to target 8 even though I use SiriKit. Any Intent related code has been guarded against when iOS < 12.My project is configured like this:- Project De
13
0
7.1k
Sep ’18