Filipe Mota
Filipe Mota

Reputation: 350

Unable to open executable - xcode

I'm getting this error...any idea how to solve it?

GenerateDSYMFile /Users/fmota/Library/Developer/Xcode/DerivedData/PBTest-gvudadeakgzklbekugyiqyfyprlt/Build/Products/Debug-iphonesimulator/PBTest.app.dSYM /Users/fmota/Library/Developer/Xcode/DerivedData/PBTest-gvudadeakgzklbekugyiqyfyprlt/Build/Products/Debug-iphonesimulator/PBTest.app/PBTest
    cd /Users/fmota/Documents/Developer/Protobuf/PBTest
    setenv PATH "/Developer/Platforms/iPhoneSimulator.platform/Developer/usr/bin:/Developer/usr/bin:/usr/bin:/bin:/usr/sbin:/sbin"
    /Developer/usr/bin/dsymutil /Users/fmota/Library/Developer/Xcode/DerivedData/PBTest-gvudadeakgzklbekugyiqyfyprlt/Build/Products/Debug-iphonesimulator/PBTest.app/PBTest -o /Users/fmota/Library/Developer/Xcode/DerivedData/PBTest-gvudadeakgzklbekugyiqyfyprlt/Build/Products/Debug-iphonesimulator/PBTest.app.dSYM

error: unable to open executable '/Users/fmota/Library/Developer/Xcode/DerivedData/PBTest-gvudadeakgzklbekugyiqyfyprlt/Build/Products/Debug-iphonesimulator/PBTest.app/PBTest'

Upvotes: 13

Views: 18215

Answers (9)

software evolved
software evolved

Reputation: 4352

Another thing to check -- if you have "Continue build after errors" set to YES, then a compile error (which you may have missed in the issue pane) can eventually lead to this error. Fix the compile error to resolve it.

Upvotes: 0

puzzl
puzzl

Reputation: 831

And here's yet another cause: repeated use of [unowned self] inside of nested blocks.

Upvotes: 0

JackyJohnson
JackyJohnson

Reputation: 3126

I might be a lil' late to this party, but same problem, solved it by going to Product > Scheme > Manage Schemes... Then simply delete current scheme and recreate a new one then try building again.

This is a good way of resetting any compilation settings you might have inadvertently changed.

Upvotes: 4

Craig Conover
Craig Conover

Reputation: 4738

I had accidentally added the same source files to my Project in Xcode twice (a header and an implementation file. Look for clues in the error message as to which files might be duplicates.

Deleting the duplicate copy (Remove References, not Move to Trash) solved my issue.

Upvotes: 0

Josh Liptzin
Josh Liptzin

Reputation: 796

In my case I had accidentally #imported the implementation file of a class instead of the header file (#import "MyClass.m" instead of #import "MyClass.h"). Unfortunately the error message for this innocent mistake is the opposite of helpful.

Upvotes: 4

Enthusiastic Techy
Enthusiastic Techy

Reputation: 908

In my case, I was trying to compile external library into my code and some of test c files in this library was added on "Compile Sources" on "Build Phases" tab. These files also had main() function which was causing it show "duplicate symbol" message. Once I removed these files from Compile Sources, project compiled successfully.

Upvotes: 3

puzzl
puzzl

Reputation: 831

I was getting the same error dialog. It turns out I had two consts of the same name declared in different files and the compile was failing with no meaningful error output, only this problem. After doing the DWARF thing discussed here I was able to get better error output that helped me find the problem

Upvotes: 0

Jeanne
Jeanne

Reputation: 85

I solved this by deleting the path specified in both Header Search Paths and Library Search Paths, found under Targets - Build Settings - Search Paths. The application now builds and runs cleanly on the iOS simulator.

I do not yet have real-device testing capability, so we'll see what happens when I get to that point.

Upvotes: 0

Manobala
Manobala

Reputation: 294

I have also faced that problem. I have closed, restarted Xcode; deleted the application from device and reinstalled it again, then the problem has gone.
Make sure the library and project files is truly included if it is not include it shows in red color in this type of case some time it is in original folder and not in project so delete it and add it again.

Upvotes: 7

Related Questions