Hi.Since XCode 10 beta 3, I've got the error below in the ValidateEmbeddedBinary stage.It only happens when I try to build for simulator. This problem doesn't occur when I build on a device with iOS 12 beta 3.The target it complains about is the watch binary target vs. the main target. The watch binary (embedded) didn't get any sign stage thus got Software Signing.It did work on XCode 10 beta 1 and when using new build system on XCode 9.Please help. Thanks!The error is:error: Embedded binary is not signed with the same certificate as the parent app. Verify the embedded binary target's code sign settings match the parent app's.Embedded Binary Signing Certificate: Software SigningParent App Signing Certificate: - (Ad Hoc Code Signed)
Search results for
Building for iOS Simulator, but the linked and embedded framework ‘XX.framework‘ was built for
186,347 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
I am facing this problem inside an app I am building using WKWebView. So sharing the link would be very difficult. If needed, I can share a video of the effect happening in real-time with the iOS 17.0 simulator and Safari Devtools
Topic:
Safari & Web
SubTopic:
General
Tags:
How can this be done without having the framework project within the app project? In m case I have an Xcode iOS project with type framework. Then I create a .xcframework and include that into another project with type app. In both projects the debug information format is set to Dwarf with dSYM in release build. Within the app project, within the Frameworks, Libraries & Embedded content section the framework is set to Embed and Sign, and its within the Embed Frameworks section. Yet when an archive of the app is created there is no dSYM present from the framework.
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
linking in object file built for iOS Simulator, file '/Users/Desktop/[PROJECT NAME]/Pods/GoogleAnalytics/Libraries/libGoogleAnalytics.a' for architecture x86_64 It looks like this cocoa pod contains a static library that does not support Catalyst yet. You should contact the vendor/maintainer of the pod you are using to see if there is a version that supports Catalyst.
Topic:
Programming Languages
SubTopic:
Swift
Tags:
Hi all, I’m suddenly experiencing an old issue again and can no longer build my project to run on the local iOS simulator. I’m using a MacBook with an M1 (ARM64) processor and Xcode for development. Until recently, everything was working as expected. However, when I opened Xcode today, I noticed new build options such as ARM64 and ARM64 + x86_64, and I’m also seeing simulator entries running under Rosetta. I don’t recall seeing these options the last time I used Xcode. At the moment: Building for “Any iOS Device (arm64)” succeeds. Building for Rosetta-based simulators also succeeds (which I understand are intended for Intel-based processes). However, when I select an ARM64 simulator, the build fails with the error: “Framework Podd_App not found.” It appears that simulator builds targeting ARM64 are being restricted or misconfigured, possibly due to a corrupted setting or a recent updat
Topic:
Developer Tools & Services
SubTopic:
Xcode
It may be good to know that when I linked all used by MyFramework frameworks to MyApp which uses MyFramework app build successfully. It seems that frameworks in MyFramework aren't linked correctly, but only for the macOS project, in the iOS project, all work properly.
Topic:
App & System Services
SubTopic:
Core OS
Tags:
Delete all versions of all apps you've already built to the simulator, off of the simulator.Then for your project, use the Product menu/clean build folder, then build to the simulator again.Assumes latest Xcode 11.1
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
Is it possible to link with a lib statically in release builds and dynamically in debug builds? Is so how? Motivation: On one hand app startup time depends on the amount of dynamically loaded libs (dylibs). The more dylibs I have the slower the startup time, hence I'd like to link with all libs statically to improve user experience. On the other hand static linking increases the compilation time, which affects developer's experience & productivity. Hence in order to win in both cases I'd like to link statically with all libs in release and dynamically with the same libs in debug builds. Progress: During a WWDC lab I've been told to: Set the MACH_O_TYPE of the relevant target to staticlib on Release configuration and dylib for Debug configuration. Add custom script that embed and sign the relevant framework only for Debug configuration. In Debug build it seems to work, but it fails on Release with: LLVM ERROR: Function Import:
This happens with a clean project also, it works fine when I manually embed files in the Targets → Unity-Phone → General → Frameworks, Libraries, and Embedded Content, but I'm afraid that in that case there may be other issues. (not passing validation for example). Doe's apple embed Frameworks to correct target? Because frameworks were embedded to UnityFramework and the game still crashes, the game does not crash when they are embedded to Unity-iPhone target manually. Can anyone do a clean build with sample project to confirm? I'm using Unity 2021.3
Topic:
Graphics & Games
SubTopic:
GameKit
Tags:
Logs - https://developer.apple.com/forums/content/attachment/52a9c8e0-96b1-444d-8e05-3e8cee36c77d Hi I have update my xcode to 12.0.1 and appium desktop to 1.18.1. While executing the command []to setup the Webdriver agent on my iphone i got the following error. Build Failed Task failed with exit code 1: /usr/bin/xcrun lipo -create /Users/username/Library/Caches/org.carthage.CarthageKit/DerivedData/12.012A7209/CocoaAsyncSocket/72e0fa9e62d56e5bbb3f67e9cfd5aa85841735bc/Build/Intermediates.noindex/ArchiveIntermediates/iOS Framework/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/CocoaAsyncSocket.framework/CocoaAsyncSocket /Users/username/Library/Caches/org.carthage.CarthageKit/DerivedData/12.012A7209/CocoaAsyncSocket/72e0fa9e62d56e5bbb3f67e9cfd5aa85841735bc/Build/Products/Release-iphonesimulator/CocoaAsyncSocket.framework/CocoaAsyncSocket -output /Applications/Appium.app/Contents/Resources/app/nodemodules/appium/nodemodules/appium-webdriveragent/Carthage/Build
Ever since upgrading to 7.1 from 7.0.1, the iOS simulator constantly hangs for 10+ seconds. It makes developing on the simulator painfully slow. Building on an iOS device doesn't have this issue.
@bgeerdes Can you please give more details about what you did? When I try this I get A library with the identifier ios-arm64 already exists What I tried: Compile sources with clang++ Link static libraries with libtool (one for each arch) Create frameworks from libs with lipo Create XCFramework from frameworks I also tried to combine arch in different ways, but I never got it to run in the M1 simulator (except with Rosetta enabled)
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
iOS does not support third-party standalone dynamic libraries. What you’re trying to do will work if you have a framework, so you need to place you dynamic library in a framework wrapper. I'm a bit surprised as the exact same project was building just fine 1year ago... And the dynamic library is embedded into the application bundle, shouldn't it be ok ? Is this something that changed recently ?
Topic:
Code Signing
SubTopic:
General
Tags:
at least theoretically it shouldn't crash as it was build for arm64 This is a common misconception. There’s a difference between architecture (Arm, Intel, and so on) and platform (iOS, iOS Simulator, macOS, and so on). Code is built for both the architecture and the platform. You can’t run code built for one platform on a different platform. I talk about this more, include info on how you tell these things apart, in An Apple Library Primer. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic:
Programming Languages
SubTopic:
Swift
Tags:
Hi, I'm trying to run my Ionic 3 app on IOS simulator with iOS 14. I am using Xcode version 12.4 and then I get this error: in /Plugins/cordova-plugin-google-analytics/libGoogleAnalyticsServices.a(TAGDataProvider.o), building for iOS Simulator, but linking in object file built for iOS, file 'platforms/ios/ManyTutors/Plugins/cordova-plugin-google-analytics/libGoogleAnalyticsServices.a' for architecture arm64 clang: error: linker command failed with exit code 1 (use -v to see invocation). any suggestion/help will be appreciated. Jitendera K.