Module file's minimum deployment target is watchos2.1 v2.1Our setup is basically like so:Workspace: - App - Main Target - Today Extension Target - Watch Extension Target - AppCoreLogicFramework - iOS app target - iOS extension safe API target - watchOS targetEach of their core framework's targets are named the same as per instructions from Apple about how to properly get this set up, but each target links against the appropriate version. This was working fine until Xcode 7.2 and now I get the error above.Both the Watch Extension Target and the core framework's watchOS target are using Latest watchOS 2.1.Has anyone found a work-around yet? Thanks!
Search results for
Building for iOS Simulator, but the linked and embedded framework ‘XX.framework‘ was built for
186,312 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
I'm trying to simulate GPS in the iOS Simulator, but Debug → Simulate Location is greyed out even though I'm: Running the iOS scheme On an iPhone simulator only (no watch paired) Build configuration = Debug allowLocationSimulation=YES in the scheme
Topic:
App & System Services
SubTopic:
Maps & Location
I met this problem also.I can rebuilt the third party framework to 2 frameworks with ios and ios simulator architecture respectively.So, now my problem is how to add framework for ios and ios simulator building separately?
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
@Noitham not work.. xcodebuild test -workspace OmniSDK.xcworkspace -scheme OmniAPITests -destination 'platform=iOS Simulator,name=iPhone 14,arch=x86_64' --- xcodebuild: WARNING: Using the first of multiple matching destinations: { platform:macOS, arch:x86_64, variant:Mac Catalyst, id:00008103-001D69941A79001E } Error: building for Mac Catalyst, but linking in object file built for iOS Simulator...
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
I have a similar problem. With another symbol from CoreGraphics library. I'm building an iOS app and it crashes in iOS 15.5 Simulator when built with Xcode 14. Working fine on iOS 16 Simulator or when built with Xcode 13.4.1.
Topic:
Programming Languages
SubTopic:
Swift
Tags:
I've built a Framework which I would like to use it in other applications.I know the basics on including and using frameworks.The problem is I really have TWO Frameworks the Device Framework and the Simulator Framework.Is there a way to tell XCode to use the right Framework?
When embedding a framework in an iOS application I noticed some differing behavior when running on an actual device and simulator which I couldn't find an explanation for anywhere in the documentation. The embedded frameworks are loaded from outside (adjacent) to the app package when running on simulator whereas they are loaded from within the app package, within the Frameworks directory when running on an actual device. Here's a link to an example project which logs the path at which the dylib within the framework is loaded: https://github.com/R4N/simulatorLoadFrameworkExample The sample outputs are as follows: On simulator: /Users/username/Library/Developer/Xcode/DerivedData/simulatorLoadFrameworkExample-gmxyfcrvpmdfgqepjbbysebvysmh/Build/Products/Debug-iphonesimulator/libsimple.dylib On device: /private/var/containers/Bundle/Application/9D22C144-848A-4E40-B5B3-707B1CFD3151/simulatorLoadFrameworkExamp
I'm also getting the same error, when linking to a framework that I've built with xcodebuild. This framework contains only arm64 libraries, one that targets the simulator and the other device. This warning goes away when I set DEBUG_INFORMATION_FORMAT to DWARF, but I don't consider that a full fix, since Firebase expects dSYM files.
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
Figured it out. If you build on an iOS simulator that is the same as your built target you won't run into issues. If you build on an iOS simulator less than your xcframework target you may run into issues. Thx
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
Today I Update XCode 7.1 ,And got a very similar error:ld: in XXXX.a, building for iOS simulator, but linking in object file built for OSX, for architecture x86_64clang: error: linker command failed with exit code 1 (use -v to see invocation)Still looking around for the cause and/or a fix...
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
As an update to @eskimo 's response, There's a few cases here: Case #1: Building for the simulator. Case #2: Building for a real device, but running on a device where the framework isn't present (eg: iPad, Mac) Case #3: Building for an iOS version before iOS 17.2 where the framework isn't available For case #1: use #if canImport(JournalingSuggestions) like this: #if canImport(JournalingSuggestions) import JournalingSuggestions #endif Then, in your code where you use JournalingSuggestionsPicker, check if you can import it first. This way, if you're not building for a real device, the framework will not be imported. For case #2: Since you're building for a real device, the framework can be imported. Since it's not an iPhone, your app will crash when run. Protect against this by first checking if you can import UIKit, then setting isJournalingSuggestionsAvailable to be true if you're on an iPhone. If you'r
Topic:
App & System Services
SubTopic:
Core OS
Tags:
It sounds like you are linking against the framework but not including the actual framework in your app bundle. These are (unfortunately) separate configuration steps in Xcode. Select your build target in Xcode and look at the General tab. Make sure the framework is included in the Embedded Binaries section.
Topic:
Programming Languages
SubTopic:
Swift
Tags:
The problem here is that there are now multiple platforms that use arm64, macOS, iOS, and the iOS Simulator. The file you’re linking was built for one platform (iOS Simulator) and you’re trying to use it another (iOS). This won’t work because arm64 code build for iOS is different from arm64 code build for the simulator. As to how you fix that, it depends. Based on the build transcript it looks like you’re using CocoaPods. If so, you should escalate this via their support channel. They should be able to tell you whether this is a CocoaPods issue or an issue with the actual pod. And if it’s the latter then you’ll need to escalate that wit the pod’s author. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @apple.com
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
Hi mlchild,We haven't submitted to TestFlight yet. Still in developement and am hoping for a solution to this problem so I don't have to also develop a main iOS app as well.To get the message extension to run on the device with linked frameworks is the frameworks must be Embedded in the main host app. Look under the General setting for the main host app target and add your frameworks to the Embedded Binaries list as well as the Linked Frameworks and Libraries list as well. Wes
Topic:
App & System Services
SubTopic:
General
Tags:
Our app uses CoreNFC to scan NFC tags or you can use QR if NFC is not supported. This worked pretty well and we were able to run the app in the simulator for (ui) testing purposes. Until Xcode12 / iOS14 GM builds. In iOS13 (or lower) we wouldn't have any issues running it on a simulator. But in Xcode12 running it on a iOS14 simulator iPhone11 we would get the following: dyld: launch, loading dependent libraries DYLD_SHARED_CACHE_DIR=/Users/xxx/Library/Developer/CoreSimulator/Caches/dyld/19G73/com.apple.CoreSimulator.SimRuntime.iOS-14-0.18A372 DYLD_ROOT_PATH=/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS.simruntime/Contents/Resources/RuntimeRoot DYLD_LIBRARY_PATH=/Users/xxx/Library/Developer/Xcode/DerivedData/BeeSafe-awnlestrbvesqqbynrhmluzhbcsc/Build/Products/Debug-iphonesimulator:/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Library/Developer/CoreSimulator/Profil