I have spent quite a while on this issue. I haven't found a proper answer.
I upgraded my Xcode to 4.0.2 and sdk to 4.3. When I run my application on Device, 2 warnings appeared:
warning: Unable to read symbols for /Developer/Platforms/iPhoneOS.platform/DeviceSupport/4.3.3 (8J2)/Symbols/System/Library/Frameworks/IOKit.framework/IOKit (file not found).
warning: Tried to remove a non-existent library: /Developer/Platforms/iPhoneOS.platform/DeviceSupport/4.3.3 (8J2)/Symbols/System/Library/Frameworks/IOKit.framework/IOKit
I have tried to remove the entire directory of 4.3.3 (8j2) and re-fetched again in Organizer. However it didn't help at all.
I have IOKit file under /Developer/Platforms/iPhoneOS.platform/DeviceSupport/4.3.3 (8J2)/Symbols/System/Library/Frameworks/IOKit.framework/Versions/A, after I copied the IOKit from directory "A" to IOKit.framework , the first warning gone, but the 2nd one still remained, and i do not think it is the proper way to solve this issue.
Anyone got any clue?
Thanks a lot!
It's just the debugger complaining, and unlikely to affect your debugging unless you're working with IOKit directly.
This won't stop the code from working, but I would report a bug to Apple.
Related
So since a few days I have this issue: I create an empty command line project and set up Cocoapods, but then I always get this runtime error:
dyld: Library not loaded: #rpath/Alamofire.framework/Versions/A/Alamofire
Referenced from: /Users/...
Reason: image not found
Program ended with exit code: 9
This happens regardless of the pod I want to use and also in already existing projects. Windowed Cocoa applications and iOS apps are not affected. I tried setting the pods.framework to Optional as suggested elsewhere, but this doesn't help. I tried it with the newest Cocoapods beta and the stable release and reinstalled Xcode, but without success. I noticed under Build Phases there is no 'Embed Cocoapods framework' as usual, so I tried adding that manually; didn't work either.
I've run out of ideas, so does anybody have any idea what might cause this? Otherwise I'll file a bug report. Thanks.
As it turns out, this behaviour is expected, as there is no easy way (for CP) to link libraries to a command line tool.
I've run this app on my iPhone before, and I have no idea how it randomly started not working, but I'm getting the following error:
Unable to read symbols for /Developer/Platforms/iPhoneOS.platform/DeviceSupport/4.2.1 (8C148)/Symbols/Developer/usr/lib/libXcodeDebuggerSupport.dylib (file not found).
So, I cleaned all targets and then deleted the app on my device and reinstalled it and ran it, and now I'm getting this error:
warning: Unable to read symbols for /Developer/Platforms/iPhoneOS.platform/DeviceSupport/4.2.1 (8C148)/Symbols/usr/lib/info/dns.so (file not found).
What is this and how do I fix it?
Well, I have the same problem but it only disables debugging (doesn't find the debugger symbols of the version installed on the device). Except debugging, It installs the app normally.
I know few people who got rid of these warnings by doing any of the following two :
1) copy the 4.2.1 symbols folder from the /Developer/Platforms/iPhoneOS.platform/DeviceSupport/ path to the symbols fodler in 4.2.1 (8C148) folder
2) Look at this one
Universal fix is: 'Clean all' in your project, delete app from device. Rebuild.
Are you targeting the same version that you're running on the device? Check this, then clean, delete from app, and rebuild.
This is the first time I've used the newest xcode (3.2.5) and the new iOS (4.2.1) and I'm getting the following run time error as soon as I run my application on my device:
Unable to read symbols for /Developer/Platforms/iPhoneOS.platform/DeviceSupport/4.2.1 (8C148)/Symbols/Developer/usr/lib/libXcodeDebuggerSupport.dylib (file not found).
Does anyone have a cohesive answer to fix this? And yes I know there is another post on this topic, but it has not made any progress and there is not a clear cut answer.
Thanks!
What I just did to solve this problem was:
cd /Developer/Platforms/iPhoneOS.platform/DeviceSupport/4.2.1 (8C148)/Symbols
and created the symlink was missing:
ln -s ../../4.2\ \(8C134\)/Symbols/Developer/ Developer
It solves my problem.
I'll post it in the other question also.
I'm not sure what you've done to try to solve it, but here's what I'd do, retrying between each step:
If you have that path but don't have the file, get it from someone (I'll volunteer). I'm guessing it's not that easy, though. :)
Delete and reinstall Xcode.
Go to the Xcode Organizer and plug in your device, and let it authorize and download the 4.2.1 stuff.
Do you even have a directory like that? I don't have those subdirectories (I don't have a 4.2.1 (8C148) directory but I do have 4.2.1 (8C148a)) there. Under DeviceSupport/Latest/ I have those subdirectories and files.
Probably a silly question. When running my project on the Device in the debug mode I get a lot of warnings al having the following string:
warning: Unable to read symbols for
/Developer/Platforms/iPhoneOS.platform/DeviceSupport/4.2.1
(8C148a)/Symbols/System/Library/PrivateFrameworks/
I think its due to the space between "4.2.1" and "(8C148a)". How can i get rid of it? It must be a setting somewhere in Xcode.
I dont have these warnings on the simulator.
thanks in advance, Christian
I was getting:
warning: Unable to read symbols for /Developer/Platforms/iPhoneOS.platform/DeviceSupport/4.2.1 (8C148)/Symbols/usr/lib/info/dns.so (file not found).
Version 4.2.1 does not include 'info/dns.so'. At least that was the case for me. However, it does exist in the 4.2 directory and is pointed to by the /DeviceSupport/Latest shortcut. I simply copy-pasted 'info/dns.so' to where the debugger was looking for it and that seemed to fix the warning.
I had this issue with 4.2.1 (8C148a), which I believe is caused by differing DeviceSupport files on the phone and in XCode. I tried many things, but eventually resolved it by deleting this folder:
/Developer/Platforms/iPhoneOS.platform/DeviceSupport/4.2.1 (8C148a)/
After this I plugged in my iOS device and was asked to connect and restore the symbol files from the device, and it worked normally again.
When you plug an iOS device (iPad) with a slightly newer OS than the the ones in the SDK, a button to download new symbols should appear in the Organizer window of Xcode. Hit it and wait.
I've seen errors like that when my device wasn't on the same version as what I was building for. Are you sure you're not on a 4.2 beta?
I don't think 8C148a is "final"; final builds numbers never seem to end in a letter (my phone is reporting "4.2.1 (8C148)"). I haven't debugged apps on it yet (I got bored waiting for it to extract symbols and went home).
4.2 GM was 8C134, so you're certainly running newer software, but something somewhere is getting the build number wrong.
But I digress.
What directories are in /Developer/Platforms/iPhoneOS.platform/DeviceSupport? If "4.2.1 (8C148a)" doesn't exist but "4.2.1" does, you might have luck doing something like this in Terminal:
cd /Developer/Platforms/iPhoneOS.platform/DeviceSupport
ln -s "4.2.1" "4.2.1 (8C134a)"
Equivalently, if "4.2.1 (8C148)" exists, do something like this instead:
ln -s "4.2.1 (8C148)" "4.2.1 (8C148a)"
You can generally use this trick to get Xcode to talk to a beta device without installing a beta SDK; this is useful if your company has some people running the beta (for testing purposes) and other people on the latest "final" (for release purposes).
There's a mismatch at the moment, where the released version of 4.2.1 is ahead of the SDK version 4.2
#Khrob's comment fixed it for me though!
Until they provide a solid SDK, a cool workaround is to :
1 - select the Executable ( In 'Executables' in the project browser ),
2 - get info and turn off "Break on Debugger() and DebugStr()"*
Cheers, and best wishes for 2011.
T
This does not disable NSLog.
I have 4.2.1 on an iPhone 3G and Xcode 3.2.5 running on a MacBook Pro with 10.6.6. After a clean install of Xcode, I was getting the prompt to download symbols for 4.2.1 after plugging in my iPhone. After the transfer, I would no longer get the prompt when attaching the iPhone, but I was getting tons of "unable to read symbols" messages.
First, what did not work for me:
Creating symbolic link to '4.2 (8C134)' with the name '4.2.1 (8C148)'
Creating symbolic link inside directory '4.2.1 (8C148)' like there is in '4.2 (8C134)' to the ../../Developer/SDKs/iPhoneOS4.2.sdk
Both of the above caused the 'UUID mismatch' errors for several libraries. GDB would start but appear to hang.
Finally, what is currently working for me:
% cd /Developer/Platforms/iPhoneOS.platform/DeviceSupport
% mkdir '4.2.1 (8C148)' # if it does not exist
% cd '4.2.1 (8C148)'
% cp ../4.2\ \(8C134\)/DeveloperDiskImage.dmg* .
% cp -r ../../Developer/SDKs/iPhoneOS4.2.sdk Symbols
Attempt to run debug session for an application and watch the Console. For each warning about a UUID mismatch, remove the file indicated in the log message (I had AudioToolbox, CoreMedia, and some others)
Stop GDB and try again, hopefully with success
At least for my application under development, everything now works fine. Hopefully, Xcode 4.0 will clear this up.
In my app, I use a very large amount of code that I copied from Apple's SpeakHere example, and when I run the app on an iPhone device it spits out this error about a hundred times before loading the XIB:
unable to read unknown load command 0x80000022
It also prints these errors:
warning: Unable to read symbols for ""/Users/eamonford/Desktop/Sleep Blaster touch/build/Debug-iphoneos"/Sleep Blaster touch.app/Sleep Blaster touch" (file not found).
warning: Couldn't raise load state for requested shlib: "Sleep Blaster touch" for breakpoint 1.
However, when I run the app in the Simulator there are no errors at all. Also, I know the errors are coming from some part of the code that I got from SpeakHere, because Apple's own example produces the same errors, and my app didn't produce these errors before I added the SpeakHere code.
Does anyone have some idea of what these errors mean or how I can trace them? Thanks!
Regarding the first warning, this appears to be a known issue in SDK 3.1 (I'm assuming you're using 3.1, I'd never seen this error with other versions). If you try compiling with a 3.0 target, that should resolve it.
I saw this error after upgrading to Snow Leopard, but before upgrading the Developer tools.
If you haven't already, go download and install the new Xcode and SDKs.