In our application, we have over 189 pods based on the Podfile.lock with the release of Xcode13.3 we are getting linker error: dyld[19610]: Symbol not found.
The same exact project used to work in the previous Xcode release 13.2.1.
When working with Apple DTS we came to learn that the issue is related to the sheer volume of LC_RPATH results. Overrunning the 32 KB buffer size that dyld allocates to hold all of these references and their file paths. We believe the overrunning buffer size is to the sheer volume of dependencies in our project.
Any suggestion or workaround to resolve this issue?
Related
Upon updating to Xcode 6, I can no longer build my app. Xcode is throwing errors and warnings like the following:
Error:
/Applications/Xcode-6.0.1.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS.sdk/System/Library/Frameworks/CoreData.framework/Headers/NSManagedObjectContext.h:121:5:
Pointer to non-const type 'id' with no explicit ownership
Warning:
/Applications/Xcode-6.0.1.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS.sdk/System/Library/Frameworks/Foundation.framework/Headers/NSString.h:206:4:
warning: '__strong' only applies to Objective-C object or block
pointer types; type here is 'const char *' [-Wignored-attributes]
The error is in CoreData.framework, the warning is in Foundation.framework.
Here's a link to my build log: http://pastebin.com/RCgV8Pj1
I've tried deleting and re-adding my frameworks using both drag and drop from the Frameworks directory, and the add button in Project->Build Phases. Neither fixes the error. I also tried deleting the SharedPrecompiledHeaders directory. I also saw this, but his fix doesn't work for me. I have no "Frameworks" directory in my project. I even went as far as re-installing Xcode 6.
I assume this is an error with a build setting someplace, but I don't know what would have changed or what I should update. Initially after using Xcode 6 I couldn't build in Xcode 5 either, but I reverted my xcodeproj and it works fine in the older version.
Make sure you don't have a Frameworks path in your FRAMEWORK_SEARCH_PATHS in project settings or target settings, as it can cause headers to be read from both iPhoneOS.platform and iPhoneSimulator.platform, causing warnings during compilation and errors during linking.
The problem can arise spontaneously if you add/change frameworks in your project and once Xcode's caches have been rebuilt, you also lose the ability to compile backups of your project because the bug is at the Xcode level.
See:
My answer in '__strong' only applies to objective-c object or block pointer types; type here is XXX" warning
This appears to have been fixed by upgrading to OS X 10.10 GM and reinstalling Xcode 6. Not sure which one actually allowed the project to build.
[UPDATE]This didn't permanently fix the issue. It came back after about 5 days.
Suddenly began getting this error when running my app on iOS 7 Simulator.
ld: library not found for -lacmobileshim
clang: error: linker command failed with exit code 1 (use -v to see
invocation)
On Device this problem doesn't happen and the app runs OK.
Have already searched for this library inside SDK but couldn't find it. Have no idea what's going on cause it was running OK both on Simulator and Devices before and haven't added any additional library to my project.
Is there a way to set Library Search Path in Build Settings just for this library?
Should reinstall SDK be a workaround?
These are the libraries i'm including in my project:
After get the same headache as updated to Xcode 6/iOS 8 sdk, just found a simple way to solve this issue with libacmobileshim.dylib and also other dynamic libraries that were causing the same problem when building the app on simulator. Just delete the dynamic libraries from Build Phases settings and the app is running perfectly again on simulator. Hope it may help someone with the same problem.
libacmobileshim.dylib is in the iOS Device SDK, but it is not in the simulator SDK. External developers should have no need for this library, so I'm confused as to why you're linking against it.
Looking at that list of libraries that you're linking against, I suspect a bunch of them aren't even needed by your project. You should audit that list and eliminate unnecessary linkage.
Totally stumped here, need help please...
Open Xcode
Project > Archive
Build Failed with 15 errors
ViewController.mm error: No matching constructor for initialization of 'OFDelegate'
LinkedList.m error: Subscript requires size of interface node which is not constant in non-fragile ABI
This would build successfully in previous versions of Xcode
I expect to see build successful and instead I see failed build with 15 errors
I am using Xcode v4.2 on Mac OS X 10.7.2 Lion.
Build errors:
Screenshot #1: http://cl.ly/CYo2/o
Screenshot #2: http://cl.ly/CY60/o
This error (the ABI message) comes up sometimes when trying to build against code originally compiled for the old runtime. The modern runtime (the 'non-fragile ABI') now available is a lot more stable but prevents certain memory-based tricks which depend on how the compiler lays out instance variables. You use one of those tricks in your linked list - calling sizeof(Node).
Basically, you can't call sizeof(ivar) anymore. See here: "Invalid application of 'sizeof' to interface 'Fraction' in non-fragile ABI" in Objective-C. You'll need to re-write that linked list class if you're building for iOS, or revert to the old, fragile runtime if you're on 32 bit OS X.
I've already spent countless hours puzzling over this, utilizing Google searches and other Stack Overflow questions to no avail.
I have an iPhone/iPad universal application, which seems to compile fine when the target is armv6. However, when the device is iPad, I get this warning:
warning: building for SDK 'Device - iPhone OS 3.2' requires an armv7 architecture.
Oddly enough, the app still runs great on iPad in spite of this warning. However, I do want to do things the "right way" what ever that means in this case. When I switch the target architecture to armv7, I get linking errors:
"___restore_vfp_d8_d15_regs", referenced from:
*redacted*
"___save_vfp_d8_d15_regs", referenced from:
*redacted*
ld: symbol(s) not found
collect2: ld returned 1 exit status
The "redacted" portions of the errors are references to the static library to which I'm trying to link.
Here's what I've tried from the many suggestions online. Each of these were suggested more than once without any explanation, which leads me to believe nobody quite understands this problem:
"Never use the drop down menu in the upper left of the XCode window to choose the target. Instead, set this to Base SDK and then the Base SDK to iPhone OS 3.0 in the target configuration. Set the target device to your preferred target (iPad, iPhone OS 3.2 in my situation.)"
This yields the error "Library not found for -lcrt1.3.1.o"
"Make sure that GCC isn't linking against the wrong version of the standard library. (You'll have to make sure the LIBRARY_SEARCH_PATH doesn't have the wrong path in it.)"
My LIBRARY_SEARCH_PATH is already empty, so this doesn't seem relevant.
"Try compiling with GCC 4.0 rather than GCC 4.2."
I get a syntax error inside a UIKit header file. The error is "Syntax error before 'AT_NAME' token." The line is "UIKIT_EXTERN #interface UILocalizedIndexedCollation : NSObject."
Another project compiles just fine with the same target settings, which is really making me question my sanity. Could I be dealing with a corrupt XCode project?
If anyone knows what's actually happening and has a reference or doesn't mind explaining it, I would be so very grateful.
Cheers!
VFP between ARMv7 and ARMv6 differs in various ways. In ARMv7 its usually preferable to use NEON. The problem is your static library depends on VFP in ARMv6 - you either need to compile the library at ARMv7 or keep the whole application at ARMv6.
Reverting back to GCC 4.0 is silly - ARMv7 support was basically nonexistent back then unless Apple backported it.
I had the same errors except it was for armv6. I fixed them by unchecking "Compile for Thumb" in the project settings for the static library and the main project.
try do like this http://groups.google.com/group/three20/browse_thread/thread/31ddbc047aa1b9ae/c4c5827ab0c7a76f
As far as AT_NAME error is concerned one of the possiblity is
Check if you miss the #end in a class.
To know more about AT_NAME error visit the following link
http://iosdevelopertips.com/xcode/error-syntax-error-before-at_name-token.html
I am trying to debug a crash minidump.
have the release debug symbols and release binaries same as crash.
While debugging that crash and pointing to symbols still I am getting "No matching binary found" error .
I am using the right symbols, binaries and pointing to right location.
So why this can happen? I can see a slight difference in timestamp of dll loaded in VS(9:03AM) and the release binary(9:04AM)
Can this be the reason for the error?
Any solutions for this , I need to fix the crash and since this crash occuring on client machine , I cannt repro it.
You may try to debug the dump using the windbg/ntsd (from the 'Debugging tools for Windows' package that comes with Windows SDK ). There you may try to load the symbols while ignoring a mismatch in the .pdb file versions '.reload /i' command.