Unable to read characters error

Question

When I find "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 what I should worry about? If so, where should I look for the root of the problem? The app is working fine, but I'm just worried that this could be an AppStore approval issue.

Answer 1

This is not an answer as such, but it can provide additional clues and additional ammunition.

I get this same warning - twice - as well, and only for the assembly "Device - 3.0 | Debug". When using the simulator, such warnings do not occur.

In my case, the message reads like yours, so that something fits in too many sets of quotes:

warning: it is not possible to read the characters for "/ Users / jdandrea / path / to / MyApp / build / Debug-iphoneos" /MyApp.app/MyApp "(file not found).

warning: it is not possible to read the characters for "/ Users / jdandrea / path / to / MyApp / build / Debug-iphoneos" /MyApp.app/MyApp "(file not found).

As if somewhere "/ Users / jdandrea / path / to / MyApp / build / Debug-iphoneos" exists with explicit quotes, but where?

In addition, in the debugging settings there is an option "Create debugging symbols".

In addition, I have two global breakpoints: [NSException raise] and objc_exception_throw. If I turn them off, I still get the above message. Again, if I turn them on, I (sometimes?) Get the following:

warning: failed to raise load state for requested shlib: "libobjc.A.dylib" for breakpoint 1.

warning: failed to raise load state for requested shlib: "CoreFoundation" for breakpoint 2.

All of this has been added to the Cocoa Touch app. I keep looking back at the target settings and code base, but I'm not sure what happened. Even instruments and other analyzes do not complain about leaks.

(I mention this second part about breakpoints that it is connected. If not, then this is a separate problem. Again, it appears only when debugging on the device.)

In short, I am also at an impasse. Hope this helps provide someone more tips to help crack this case!

Answer 2

I know this topic is very old, but I would like to share what worked for me - I hope this helps someone read this in the future.

It is simply a matter of removing a space on the way to the application. The fact is that you cannot see where the space is in the console - it cuts it off in space. You will have to manually view your path for this rogue space!

The console might show you something like:

 users/yourname/desktop/my/myapp.app/ 

When your path looks like this:

 users/yourname/desktop/my app/myapp.app/ 

Remove the space (or add an underscore) and do this:

 users/yourname/desktop/my_app/myapp.app/ 

Worked for me!

Answer 3

This seems to be a complaint about the missing file. If you have not tried it yet, you need to clear the project (Shift-Command-K) and then create it again. Although I doubt that the App Store will reject your application for this reason, it is rarely better to publish an application with build warnings, so you will want to allow this before submitting.