Iam able to run my project in iPad and iphone but when i tried to run it in iPad simulators
but then i got this error .
ld: building for iOS Simulator, but linking against dylib built for MacOSX file '/Users/apple/Documents/releaseAPICON2015/SenTestingKit.framework/SenTestingKit' for architecture i386
clang: error: linker command failed with exit code 1 (use -v to see invocation)
please check this link for screenshot
Error
Please tell me how to get back all simulators in xcode 6.1.1
You are trying to link SenTestingKit.framework in you iOS project. You cannot use OS X binaries in iOS Simulator apps as they are not compatible.
On older versions of iOS, you would encounter runtime errors (incorrect values or crashes). On iOS 8.0, this became a link-time error.
You need to build a version of SenTestingKit.framework for iOS. Hope this helps.. :)
Related
I'm fairly new to Xcode and have no idea why my build failed. The following is a part of the output, the parts that I omitted are just warnings about deprecations.
ld: building for iOS Simulator, but linking in object file built for iOS, file '/Users/user/Documents/GitHub/bus/ios/Pods/GoogleMaps/Maps/Frameworks/GoogleMapsCore.framework/GoogleMapsCore' for architecture arm64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
note: Using new build system
note: Planning
note: Build preparation complete
note: Building targets in parallel
Could not build the application for the simulator.
Error launching application on iPhone 13.
Exited (sigterm)
What can I do to fix this issue? I have no issues building my app in android.
It works against an iOS 14.4 simulator and Google Maps appear on the app correctly.(M1 machine)
I'm getting error while running an application on simulator using Xcode 9.2. Can not run project on simulator devices.
Error:
clang: error: linker command failed with exit code 1 (use -v to see invocation)
And in my CoreSimulator.log file I have seen:
Spawning processes in an unbooted state without setting kSimDeviceSpawnStandalone is deprecated.
I tried to remove derived data, quit Xcode and reopen does not solve my issue. Could you please help to solve this bad situation?
My mac OS version: 10.13.2(High Sierra)
Xcode version: 9.2
I found solution;
In my target -> build phases -> link binary with libraries section
lib386.a
multiplexed. Because of my third party's "xxx.a" library which contains "lib386.a".
Deleted "lib386.a" in link binary section and then simulator runs.
Thanks all.
I have made react-native integrated with my existing app. But it can only run on iOS 8.0 or later. As many programmers said, react-native can run on iOS 7.0, but I didn't make it work. And there are the compiling error messages from xcode:
ld: embedded dylibs/frameworks are only supported on iOS 8.0 and later (#rpath/React.framework/React) for architecture arm64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
Anyone can tell me how could I solve this problem to make react-native to run on iOS 7.0?
I have searched http://sourceforge.net/projects/xlslib/files here and download the library. I added the library into my xcode project like this
My xcode version is 6.4 and my project iOS Deployment Target is 8.0.
After I added it into the project without typing any code, I just built to see if it works.
But I failed and get these information:
ld: building for iOS Simulator, but linking against dylib built for MacOSX file '(MyProject Directory)/xlslib/libxls.3.dylib' for architecture x86_64
clang: error:
linker command failed with exit code 1 (use -v to see invocation)
When I changed iOS Deployment Target to 7.0, build the project by using iOS simulator with iOS version 7.1, it works. Is the library doesn't support iOS 8.0 and later ?
BTW, other link flag is already be empty, what should I do to solve this problem?
Any help would be appreciated.
I finally realised why the 'Archive' option was gray. I needed to select an iOS device.
The only device that I currently have with me has iOS6 installed on it.
It says the following when trying to Archive the app:
ld: warning: ignoring file
/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS6.0.sdk/usr/lib/crt1.3.1.o,
file was built for armv7 which is not the architecture being linked
(armv6):
/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS6.0.sdk/usr/lib/crt1.3.1.o
ld: entry point (start) undefined. Usually in crt1.o for architecture
armv6 clang: error: linker command failed with exit code 1 (use -v to
see invocation)
But I want to support armv6. What should I do?
EDIT: I tried changing the target from iOS4.0 to iOS 4.2 and said the following:
/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/usr/bin/lipo:
/Users/airrider3/Library/Developer/Xcode/DerivedData/TRGame-fvkoniflczyexwhcnmjvozqbuozd/Build/Intermediates/ArchiveIntermediates/AppStore/IntermediateBuildFilesPath/TRGame.build/Release-iphoneos/iOSGame.build/Objects-normal/armv7/Kipos
and
/Users/airrider3/Library/Developer/Xcode/DerivedData/TRGame-fvkoniflczyexwhcnmjvozqbuozd/Build/Intermediates/ArchiveIntermediates/AppStore/IntermediateBuildFilesPath/TRGame.build/Release-iphoneos/iOSGame.build/Objects-normal/armv7/Kipos
have the same architectures (armv7) and can't be in the same fat
output file Command
/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/usr/bin/lipo
failed with exit code 1
EDIT: I now managed to archive with just armv7 to iOS 4.0. Is it going to work?
You can't archive an file with IOS6, you need to downgrade to the latest official version to archive.
Edit:
Devices updated to iOS 6 beta can not be restored to earlier versions
of iOS. Registered development devices will be able to upgrade to
future beta releases and the final iOS 6 software.
https://developer.apple.com/devcenter/ios/index.action#
I figured it out. Instead of adding the 'armv6 armv7', I just needed to add 'armv6', as the code for 'armv7' was already written with that other default bizarre code.
That's why it was telling that two armv7 was being built.
Thanks everyone for the help, either way!