Search results for

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

186,340 results found

Post

Replies

Boosts

Views

Activity

Reply to Build failed on Xcode 15
how long is it since you last built or linked your project? Is it an app, a library or a framework? What version of Xcode and did it last succeed on? It sounds like a tool has changed, and what used to look like a flag now looks like a file name to the build tools.
Dec ’23
Reply to Builduing IOS apps
can I connect an iPhone to windows 10 and build ios apps? NO. Some development frameworks provides some ways to develop and test an app on simulators on Windows, but you need Mac to run such apps on your actual iPhone.
Topic: App & System Services SubTopic: Core OS Tags:
Jan ’21
Crash on iOS 12.5.7 (release build only) when built with Xcode 15.1
I'm testing my app built with Xcode 15.1 on 3 devices: iPhone 14 Pro (iOS 17.2) - no problem with both debug and release builds iPhone 6S (iOS 15.7.9) - no problem with both debug and release builds iPhone 5S (iOS 12.5.7) - no problem with debug build but immediate crash on the splash screen when running release build. The message is: dyld: Library not loaded: /System/Library/Frameworks/SwiftUI.framework/SwiftUI Referenced from: /var/containers/Bundle/Application/MyApp.app/MyApp Reason: image not found Googled about this error and it seems to be an old and known issue: Apps containing SwiftUI inside a Swift package might not run on versions of iOS earlier than iOS 13. (53706729). Adding -weak_framework SwiftUI to Other Linker Flags fixed my issue. However I'm curious why this old issue reappeared in the most recent Xcode 15 while I haven't such problems with Xcode 14 and 13.
1
0
1.3k
Dec ’23
Black Screen while Building App on iOS Simulator Xcode 14.3.1
Hello. I am trying to build my app on Xcode but everytime I get a black screen. It should show a table with images but it won't. I already reviewed the ViewController, App Delegate and DetailViewController, each of these files seem to be correct. I also tried building my app with an older version of iOS being iOS 15.5 but this process was not successful and finally just to make sure everything was correct in my code also tried removing certain parts (the newest code added) of my ViewController but it wouldn't build the app still. Has this happened to anyone of you? I am using Xcode 14.3.1, MacOS 14.3 This is from Hacking with Swift by Paul Hudson. I am new to this entire ecosystem and has been a bit difficult to go step by step, 1 hour per day. I have never used Xcode nor MacOS before but I am always eager to learn more everyday.
Topic: UI Frameworks SubTopic: UIKit Tags:
1
0
783
Jul ’23
Reply to Xcode 7.1: Archive Only Error - All frameworks and dylibs for bitcode must be generated from Xcode Archive or Install build
Hi All,I am not using Carthage but i am using my workspace to build embeded framework , i have enabled enable bitcode flag to YES, then i integrate it with a sample application and trying to archive but i am getting the same errorld: bitcode bundle could not be generated because '/Users/user/Downloads/sampleapp-3/testFramework.framework/testFramework' was built without full bitcode. All frameworks and dylibs for bitcode must be generated from Xcode Archive or Install build for architecture armv7clang: error: linker command failed with exit code 1 (use -v to see invocation)It would be great if someone have solution on this.Thanks
Nov ’15
Journaling Suggestions is not available on iOS Simulator
Hey, when I try to run my project on an iOS Simulator, I get the following message: JournalingSuggestions is not available when building for iOS Simulator. and Linker command failed with exit code 1 (use -v to see invocation) Steps to reproduce this behavior: Create a new Xcode project Add the Journaling Suggestions Capability Add the Journaling Suggestions Framework Under Target > Build Phases > Link Binary with Libraries, select “optional“ for JournalingSuggestions.framework Under Target > Build Settings > Other Linker Flags > Debug select „Plus“ and add „iOS or iOS Simulator“ and paste this -Xlinker -weak_framework -Xlinker JournalingSuggestions into the editable field. Do the same for Target > Build Settings > Other Linker Flags > Release This tread is about the same problem, but is already checked as answered. That's why I'm creating this new tread. The last two bul
3
0
639
Oct ’24
Reply to Install application os Simulator
The alternative is to use the iOS simulator on a Mac computer. But, the big question is, how do you install the App to your simulator without building it using Xcode and allowing Xcode to install the App for you? Well, as it turns out, the solution is relatively easy.You just simply need to manually install the App to your Simulator but the App also needs to be built targeting the iOS simulator. You might be having some problems with installation. Certainly, there are different iOS emulator for MAC which can run any of the apps or games on MAC PC.
Feb ’20
Framework Linking to AppDelegate or ViewController
My goal: Create a Cocoa Touch Framework that is a syncing framework for different Cloud API Storage Services (Azure, AWS, Filemaker API*)Currently, I use FileMaker Pro with FileMaker Go IOS APP SDK the most. FileMaker Inc. has created a Cocoa Touch Framework bundle that is basically an entire application within it, I assume the AppDelegate and ViewController classes are within it, but I can't tell because they are compiled. I would like to create a second Framework with Coca Touch that can run background tasks / downloads triggered by my custom framework.I have been sucessfull at embedding my framework along side FileMaker Go's iOS App SDK and running commands, I can push JSON, get JSON, and download files but only in the main thread, once the app goes to sleep the download triggered from my framework stops. I am using NSURLSession to do all of this. But as soon as I try to attach a NSURLSession Background Config everything stops
1
0
2k
Apr ’17
Reply to AV PlayerView + Interface Builder + Archive Build Error
The error is reporting that the class does not exist because AVKit.framework is not loaded. You can either explicitly included as described in another post: Add AVKit.framework to Targets -> App -> General -> Frameworks, Libraries, and Embedded Content Or you ensure Build Settings->Apple Clang - Language - Models -> Links Frameworks Automatically == YES and add a direct code reference to a symbol in AVKit to trigger the loading along along with the AVKit import.
Jun ’20
Reply to iOS 13.6, DYLD, symbol not found,expected in '/usr/lib/libc++.1.dylib',
the problem is solved by checking build warning, one of the warning: ld: warning: object file (XXX.o)) was built for newer iOS version (18.0) than being linked (12.0); it indicates that a library written with c++ linked to the app is built for iOS 18.0; after rebuilding the library for iOS 12.0, everything is ok. one final confusion: the crash report seems not relevant to the cause of the problem.
Topic: App & System Services SubTopic: Core OS Tags:
Dec ’24
I am having trouble running a Xamarin iOS Application in an iOS Simulator on my Mac
Whenever I attempt to build and run my Xamarin iOS app from within Visual Studio for Mac, I get this error message after a failed build: /Library/Frameworks/Mono.framework/External/xbuild/Xamarin/iOS/Xamarin.Shared.targets(3,3): Error: Could not find any available provisioning profiles for MyProject on iOS. I understand that provisioning profiles ought to be required only when I am trying to run my application on a real iOS device. I am not trying to run the application on a real iOS device, I am trying to run this on an iOS simulator. I do setup my publishing profile in both Visual Studio and Xcode with my Apple Developer account - which is linked to my company's team account. But this does not resolve the issue. Is anyone else experiencing something like this? I'd appreciate any help on this issue.
1
0
1.3k
Jan ’22
Reply to The app links to non-public libraries when validating on xcode 15.0 beta
The immediate cause of this issue is that your app contains a framework, image_picker_ios, that links to private frameworks, namely AVFCapture and AVFCore. It shouldn’t be doing that. As to how it got that way, it’s hard to say based on the info presented so far. Are you building the image_picker_ios framework from source? Or using a copy built by someone else? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Jun ’23