Search results for

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

186,333 results found

Post

Replies

Boosts

Views

Activity

Universal Links are not working in the Xcode 26 simulators
After updating the Xcode 26, defined universal links are not working in the iOS simulator. In the configuration, we have verified all the things including AASA file hosting and domain configuration. It is working properly in the real devices. Issue occurring only for Simulators. How can I debug it in the simulators to validate this ? Xcode Version: 26.1 Simulator iOS: 26.1
5
0
552
Jan ’26
Firebase crash reporting in an embedded framework
I'm developing an application, MainProject, that has an embedded framework, EmbeddedFramework (also developed by my team), and I'm incorporating Firebase Crashlytics in order to get crash reports.The crash reporting is working just fine in the base application, I'm getting deofuscated reports that point to the exact line where the crash happened.In the other hand, the crash reporting fails when a crash occurs inside of the embeddedframework. When that happens, all I get is a <compiler generated> or a <specialized> line of code, making it really hard to identify and/or debug.For example, for this instance of a crash report in Firebase: [1]: https://i.stack.imgur.com/ulmPS.pngCrashed: com.apple.main-thread 0 EmbeddedFramework 0x101b38628 $s6EmbeddedFramework0A14AuthenticationC6isIdleSbvg + 114 1 MainProject 0x100d07a94 specialized EntryViewController.clickLogin(sender:) + 884 (:884) 2 MainProject 0x100d035c4 @objc EntryViewController.clickLogin(sender:) + 48 (:48) 3
3
0
2.4k
Feb ’20
One embedded framework takes forever to sign when uploading
Hello, I have an iOS app with a lot of embedded frameworks. It works well when I start it from Xcode, it works well once it is on the AppStore or in TestFlight. My only problem is when uploading it using Xcode 13. At the Processing symbols for ....framework stage, when reaching a specific framework, it keeps going forever (I've tried letting it run for a night, and it did not move). I can upload with Xcode 12 without problems, but not with any version of Xcode 13 or 14. Since it keeps going forever, I do not have an error message that could help me in identifying the issue. The issue seems to be with a specific framework, but I cannot identify anything that this framework has that is different from the other frameworks (they've all been compiled from C code, using a Makefile and the same CFLAGS and LDFLAGS options). I couldn't find any similar issues on the forum. Do any of you guys have a suggestion on how to fix the issue?
2
0
1.3k
Jul ’22
Embed Framework vs. Link to Framework
I have a workspace with my main project. I have some other projects that create static libraries. Converting them to frameworks.Question:If I Link to a Framework do I have to Embed Framework? This is my own framework, which I have the source code to. Do I have to specficially embed the binary, or is that handled?The embed framework doesn't seem to work in my case. Is this only for thrid party applications?Question 2:If I make my framework headers public, but only use the framework in my own applications, are the headers private and encrypted or are they public? Seems obvious, but I feel like I should double check.Thanks
1
0
6.6k
Sep ’15
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
Okay...this works... before my configuration was this:I have my own framework which links to this third party framework (but does not embed). My main app links and embeds my framework and links and embeds the third party framework.So, this apparently doesn't work anymore? If I remember correctly, I did this because I had a hard time embedding a third party framework within one of my own frameworks in a previous version of Xcode.New configuration:In Xcode I changed my framework to link & embed the third party framework. Now my main app only links and embeds my framework and does not link or embed the third party framework anymore. And the app compiles and runs....no info.plist required.
Dec ’19
Reply to M1 Xcode 13.3 without Rosetta, PO in debug doesn't work
When adding manually -add_ast_path and using -Wl on app target, I have an explicit message: building for iOS Simulator-arm64 but attempting to link with file built for unknown-unsupported file format ( 0xE2 0x9C 0xA8 0x0E 0x01 0x08 0x00 0x00 0x5D 0x0B 0x00 0x00 0x07 0x01 0xB2 0xC0 ) But it works fine without this on Xcode 13.2.1 and Xcode 14.0 beta. It fails only with Xcode 13.3.1 and Xcode 13.4.1. (not tested with Xcode 13.3.0 or Xcode 13.4.0)
Jul ’22
Reply to dyld: Symbol not found: swift34swift50override_conformsToProtocol
Hi, I'm having the same problem here with Xcode 16. I've made an example project to try replicate the issue. In this example, when a build the sample app with Xcode 16 I get this same crash in launch time. The app structure is the following: App target > Depends on Dynamic Framework (pre-built) > Depends on Dynamic Framework (target created with Cocoapods) The dynamic framework was pre-built with this transitive dependency using Cocoapods but with Xcode 15, using vtool I can see this info like: ➜ vtool -arch arm64 -show DynamicFrameworkSample.framework/DynamicFrameworkSample DynamicFrameworkSample.framework/DynamicFrameworkSample (architecture arm64): Load command 8 cmd LC_BUILD_VERSION cmdsize 32 platform IOS minos 12.0 sdk 17.5 ntools 1 tool LD version 1053.12 Load command 9 cmd LC_SOURCE_VERSION cmdsize 16 version 0.0 If I recompile the framework with Xcode 16 it runs fine. I only get this crash in a real iOS device, not
Jan ’25
Archive error , building for iOS, but linking in dylib file for architecture arm64
Hello i dont know why i am getting this error. Everything is working good , but when i install Plaid library it fails I have done all of its instructions. But i am getting the following error. building for iOS, but linking in dylib file (/Users/xxxx/Library/Developer/Xcode/DerivedData/xxxx-craevlhuabfnpudjvspcrbdoorut/Build/Intermediates.noindex/ArchiveIntermediates/xxxx/BuildProductsPath/Release-iphoneos/LinkKit.framework/LinkKit) built for iOS Simulator, file '/Users/xxxx/Library/Developer/Xcode/DerivedData/Tenth-craevlhuabfnpudjvspcrbdoorut/Build/Intermediates.noindex/ArchiveIntermediates/xxxxx/BuildProductsPath/Release-iphoneos/LinkKit.framework/LinkKit' for architecture arm64 I tried on xcode12 and xcode11. Does any body have an idea , of what its going on , Thanks Everybody
1
0
2.1k
Nov ’20
Framework built on Xcode9 are not working on Xcode8
I get the error message below, when linking a static framework built on Xcode9 beta on Xcode8.I know FileProvider comes from iOS11, but I do not use it in my framework.Early I think this is a bug of Xcode9 beta, but today this still happened with Xcode9 GMframework not found FileProvider for architecture arm64Have also committed this to the bug reporter.
4
0
4.1k
Sep ’17
iOS app runs in simulator but won't build/archive
Hello! I've been having a problem wherein my app runs on the iOS simulator but won't build to the generic device. When I check the report navigator it always shows the same arrow next to the same file. (FirstViewController.swift)Here's the XCode report navigator (it's been like this for about half an hour)If anyone has had the same problem or knows a way to fix this, you'd be a complete livesaver!Also, here is my Podfile (the problem doesn't seem to be coming from Cocoapods though - and I do use the .xcworkspace file)# Uncomment this line to define a global platform for your project # platform :ios, '8.0' # Uncomment this line if you're using Swift use_frameworks! target 'Channel 2' do pod 'PopupDialog', '~> 0.3' pod 'Socket.IO-Client-Swift', '~> 6.1.6' # Or latest version pod 'YouTubePlayer' pod 'SwiftyJSON' end target 'Channel 2Tests' do pod 'PopupDialog', '~> 0.3' pod 'Socket.IO-Client-Swift', '~> 6.1.6' # Or latest version pod 'YouTubePlayer' pod 'SwiftyJSON
1
0
1.1k
Aug ’16
Reply to Xcode 12 beta 4 - error compiling for Simulator
For a general short term solution to this issue, the exclusion of arm64 arch needs to be specifically tied to iOS Simulator platform build. If solution is not tied to iOS Simulator platform, you are telling Xcode to never build for the arm64 arch. This solution doesn't work for me since I need to distribute FAT framework with all the iOS archs and all the iOS Simulator archs. The newer Xcode 12 is treating arm64 as an iOS Simulator architecture as well as a legacy iOS architecture probably because MacOS Big Sur 11 running on an Arm64 based Mac will be running the iOS Simulator on arm64... But the Xcode folks didn't appear to think thru the affects. Xcode 12 UX needs to be able to differentiate arm64 iOS Simulator from arm64 iOS in a better way. The generated binary need to include extra metadata so linker can tell choose the correct arch within a FAT
Sep ’20
Contacts framework crashing in simulator?
I am trying to run a very basic app on iOS10 with Xcode8 in the simulator. Everytime I make the call to authorize access to Contacts, it crashes the app immediately, and without stopping in the debugger. I dont see my app listed in the privacy permissions after this. Here is the code I use to request access to Contacts:CNContactStore *store = [[CNContactStore alloc] init]; [store requestAccessForEntityType:CNEntityTypeContacts completionHandler:^(BOOL granted, NSError * __nullable error) {Pretty basic. Is this a known issue? Has anyone else run into this?
Topic: UI Frameworks SubTopic: UIKit Tags:
4
0
3.0k
Jun ’16