When I 'Build and Go' on the device, the console shows:
warning: Unable to read symbols for ""/Users/Steve/Blue/build/Debug-iphoneos"/Blue.app/Blue" (file not found).
warning: Unable to read symbols for ""/Users/Steve/Blue/build/Debug-iphoneos"/Blue.app/Blue" (file not found).
Is this something I should worry about? If so, where should I look to find the root of the issue? The app works OK, but I'm just worried that this might be an AppStore approval issue.
This appears to be a complaint of a missing file. If you haven't tried already you will want to Clean the project (Shift-Command-K) and then build it again. Although I doubt the App store would reject your app for this reason, it is rarely a best practice to release an App with build warnings so you will want to resolve this prior to submission.
This isn't an answer per se, but it may provide more clues and additional ammo.
I'm getting this exact same warning - twice - as well, and only for "Device - 3.0 | Debug" builds. When using the Simulator, no such warnings occur.
In my case, the message reads like yours, in a way that suggests something is being placed in one too many sets of quotes:
warning: Unable to read symbols for ""/Users/jdandrea/path/to/MyApp/build/Debug-iphoneos"/MyApp.app/MyApp" (file not found).
warning: Unable to read symbols for ""/Users/jdandrea/path/to/MyApp/build/Debug-iphoneos"/MyApp.app/MyApp" (file not found).
It's as if, somewhere, "/Users/jdandrea/path/to/MyApp/build/Debug-iphoneos" exists with explicit quotes, but where?
Also, the debug target settings do have "Generate Debug Symbols" checked.
Also also, I have two global breakpoints: [NSException raise] and objc_exception_throw. If I disable these, I still get the above message. Then again, if I enable them, I (sometimes?) get this:
warning: Couldn't raise load state for requested shlib: "libobjc.A.dylib" for breakpoint 1.
warning: Couldn't raise load state for requested shlib: "CoreFoundation" for breakpoint 2.
This was all added to a stock Cocoa Touch app. I keep looking around the target settings and the codebase, but I'm not sure what's amiss. Even Instruments and other analyses aren't complaining about leaks.
(I mention this second part about the breakpoints on the off chance that it's related. If not, then that's a separate issue. Again, it only shows up when debugging on the device.)
In short, I'm stumped too. Hopefully this helps provide someone with more clues to help crack the case!