Obscure Xcode Error: Executable Path is a Directory

[NyekoObote]

Body

My build succeeded but I immediately got the following pop-up error:

Executable Path is a Directory
Domain: DVTMachOErrorDomain
Code: 5
Recovery Suggestion: /Users/myname/Library/Developer/Xcode/DerivedData/Myapp-dwsmxozkmjfflagroxubgbfvahwq/Build/Products/Debug-iphonesimulator/Myapp.app is not a valid path to an executable file.
User Info: {DVTErrorCreationDateKey = "2025-04-17 11:54:27 +0000"}

Executable Path is a Directory
Domain: DVTMachOErrorDomain
Code: 5
Recovery Suggestion: /Users/myname/Library/Developer/Xcode/DerivedData/Myname-dwsmxozkmjfflagroxubgbfvahwq/Build/Products/Debug-iphonesimulator/Myname.app is not a valid path to an executable file.

System Information

macOS Version 15.5 (Build 24F5053f)
Xcode 16.3 (23785) (Build 16E140)

Applied and Failed Fixes:

• Upgrade to MacOS 15.5 Beta
• pod deintegrate/podinstall
• uninstall and reinstall Xcode
• Delete DerivedData folder
• Edit info.plist Executable File name

Guidelines

• I have read and understood this category's guidelines before making this post.

[jgschmitz]

means Xcode is trying to run a directory (Myapp.app) as if it were an executable binary. This can happen when your app bundle structure is corrupted, misnamed, or the binary inside is missing. -

1. Clean Build Folder
   In Xcode: Shift + Cmd + K

Then, go to Product > Clean Build Folder

Or manually:

rm -rf ~/Library/Developer/Xcode/DerivedData

2. Check App Target
3. Go to your scheme (click near the Run button)

Ensure the correct runnable target is selected (it should be your app target, not a framework or a test target).

4. Inspect the .app Bundle
   Manually check:

cd ~/Library/Developer/Xcode/DerivedData/Myapp-*/Build/Products/Debug-iphonesimulator/Myapp.app
ls -lh

Do you see an actual binary like Myapp in there? If not, the build didn't produce the executable.

[NyekoObote]

I followed all of these steps and Terminal cannot seem to find the app binary. Producing this result:

cd: no such file or directory. I am using Mac 15.5 Beta.

In addition, Myapp.app is also crossed off in my DerivedData folder and when I click on it I get the message: "You can’t use this version of the application “Myapp” with this version of macOS."

And when I double click (right click) Myapp.app to reveal its contents I see: bundle files, my storyboards, png. of my logo, Frameworks folder, and my Google and infor.plist files. Nothing else.

I've attached more photos to help visualize. There are also photos of my Build settings related to executable files.

[jgschmitz]

You’ve built… a folder.
Xcode created the .app structure:

Info.plist ✅
PNGs ✅
Storyboards ✅
Frameworks ✅
Executable binary ❌ (aka the heart of the app)

And now macOS sees this sad empty .app and goes:
“You can’t run this app because it’s from a different dimension.”

That “crossed out” icon means macOS considers this .app invalid — likely because the actual binary file is missing, corrupted, or failed code-signing.

🩺 Diagnosis Checklist
You already tried:

Cleaning build folder (Shift + Cmd + K)

Nuking DerivedData (rm -rf ~/Library/Developer/Xcode/DerivedData)

Checking the .app structure manually (and yep, the binary's MIA)

Let’s go deeper:

Next Steps

1. Check Build Settings > Architectures
   Navigate to Build Settings

Under Architectures, ensure it's not set to "Standard Architectures (64-bit Intel)" only if you're on Apple Silicon

Try switching to "arm64" or "arm64 and x86_64"

2. Check Build Phases > Compile Sources
   If zero files are listed under "Compile Sources", your app literally has nothing to build

Make sure main.swift, AppDelegate.swift, etc., are in there

3. Reset Simulator or Build for Device

The simulator can get weird in macOS betas. Try:

xcrun simctl erase all

Or: Plug in a physical device and run the build there instead

4. Check for Entitlements/Code Signing Issues
   Sometimes Xcode silently skips building the binary if:

Code signing fails

Team/provisioning profile is missing

Or entitlements don’t match the target type

Look in the Issue Navigator (⌘ + 4) for any non-fatal build warnings

Lemme know if any of that helps!

[NyekoObote]

You’ve built… a folder. Xcode created the .app structure:

Info.plist ✅ PNGs ✅ Storyboards ✅ Frameworks ✅ Executable binary ❌ (aka the heart of the app)

And now macOS sees this sad empty .app and goes: “You can’t run this app because it’s from a different dimension.”

That “crossed out” icon means macOS considers this .app invalid — likely because the actual binary file is missing, corrupted, or failed code-signing.

🩺 Diagnosis Checklist You already tried:

Cleaning build folder (Shift + Cmd + K)

Nuking DerivedData (rm -rf ~/Library/Developer/Xcode/DerivedData)

Checking the .app structure manually (and yep, the binary's MIA)

Let’s go deeper:

Next Steps

1. Check Build Settings > Architectures
   Navigate to Build Settings

Under Architectures, ensure it's not set to "Standard Architectures (64-bit Intel)" only if you're on Apple Silicon

Try switching to "arm64" or "arm64 and x86_64"

2. Check Build Phases > Compile Sources
   If zero files are listed under "Compile Sources", your app literally has nothing to build

Make sure main.swift, AppDelegate.swift, etc., are in there

3. Reset Simulator or Build for Device

The simulator can get weird in macOS betas. Try:

xcrun simctl erase all

Or: Plug in a physical device and run the build there instead

4. Check for Entitlements/Code Signing Issues
   Sometimes Xcode silently skips building the binary if:

Code signing fails

Team/provisioning profile is missing

Or entitlements don’t match the target type

Look in the Issue Navigator (⌘ + 4) for any non-fatal build warnings

Lemme know if any of that helps!

This helped! Thank you.

[ChandramaniPatel]

I have exactly the same issue on iOS Simulator (All versions of iOS, I mean iOS-17,iOS-18) when run the code Xcode-16 .
My App is hydrid based on Sencha CMD and Cordova, and its run fine till iOS-17(Xcode-15).
when I upgraded to Xcode-16 to make it compatible with iOS-18, its giving me error on iOS Simulators.
Though I am able to create a prod build (with prod cert and PP)and its installed successfully on real devices.