Executable Not Found. xxx.app is not a valid path to an executable file

Question

Details

Executable Not Found Domain: DVTMachOErrorDomain Code: 5 Recovery Suggestion: /Users/riber/Library/Developer/Xcode/DerivedData/digitalCurrency-hiyiyrokjaydkiagjimlwohehrtu/Build/Products/Debug-iphonesimulator/digitalCurrency.app is not a valid path to an executable file. Please rebuild the project to ensure that all required executables are created. Check your project settings to ensure that a valid executable will be built.

System Information

macOS Version 11.4 (Build 20F71) Xcode 12.5 (18205) (Build 12E262) Timestamp: 2021-06-11T16:34:20+08:00

solution worked for me. removed VALID_ARCHS from file not settings. — cagatay, Dec 06 '21 at 04:45

score 29 · Answer 1 · edited Jan 08 '22 at 23:07

29

Check if all files are available.

Targets -> Build Phases -> Compile Sources

If you see faint files, then they need to be removed or added.

View Screen

edited Jan 08 '22 at 23:07

glennsl

28,186
12
57
75

answered Jan 04 '22 at 11:03

Sosin Vitalii

339
3
4

3

This solved it for me on Xcode 13.2.1 in a SwiftUI app with iOS and macOS support. In my iOS target I had a "failt" file. Removing that file solved it! – Sajjon Feb 22 '22 at 08:48
2

This solved it for me as well, thank you – Natalia Terlecka Mar 04 '22 at 11:37
@Sajjon what is "failt" file? I do have the same issue but could not resolve it. – Manish Nahar Oct 19 '22 at 11:14
@ManishNahar I misspelled, I was supposed to write “faint” as in “greyed out”. – Sajjon Oct 19 '22 at 13:27

score 9 · Answer 2 · edited Aug 10 '21 at 18:54

9

Under "Build Settings" - "Architectures" check that you don't have "arm64" excluded under "Excluded architectures" for release, as all new iOS devices use this architecture.

edited Aug 10 '21 at 18:54

Dharman

30,962
25
85
135

answered Aug 10 '21 at 18:48

Manuel Castillo

371
4
4

Thanks. This is the only solution in this page that worked for me. – TomV Oct 22 '22 at 13:39
This is only if you are deploying it to a real device, right? – chitgoks Mar 06 '23 at 10:00

score 8 · Answer 3 · answered Feb 08 '22 at 02:38

I'm also get the same error. Let me share how I fix it.

I write cpp code on vscode.
I deleted a .cpp/.h file that I didn't need anymore a few days ago.
Everything nice and happy when I working on vscode.

".app is not a valid path" appeared when i switched back to the xcode to verification function.
I was confused.
(I don't immediately remember my delete operation a few days ago)

The key isn't the dialog showed "Executable Not Found",
Switch to "Issue Navigator" and drag to the bottom...
Now the ERROR shows up in front of U:

Finally the solution is :

TARGETS -> Select your ‘Target' -> Build Phases -> Compile Sources :

Select the ".cpp" file that had been delete, then "Remove Items" by click the second "-" button in the lower left corner.

score 4 · Answer 4 · answered Feb 03 '22 at 01:56

4

resolve it using pod install. as Frank said, I also use RN in my app.

I have tried clean derived data & even reboot, still happening

answered Feb 03 '22 at 01:56

ACE_xW

41
5

As it’s currently written, your answer is unclear. Please [edit] to add additional details that will help others understand how this addresses the question asked. You can find more information on how to write good answers [in the help center](/help/how-to-answer). – Community Feb 03 '22 at 09:55

score 3 · Answer 5 · answered Sep 23 '21 at 02:27

3

I fixed it by adding x86_64 to VALID_ARCHS. Build Setting search "VALID_ARCHS",check the x86_64 is there or not, add and run.It worked with me .

answered Sep 23 '21 at 02:27

闰土二爷

31
3

score 2 · Answer 6 · answered Aug 18 '21 at 11:09

2

Check the Executable File in the Info(.plist). It should be named the same as your Product in Products

answered Aug 18 '21 at 11:09

aqm

142
2
17

score 1 · Answer 7 · answered Jan 17 '22 at 23:42

1

I have this issue on a react native application and I can resolve it reinstalling cocoaPods.

pod install

Inside the ios folder on your react native project.

answered Jan 17 '22 at 23:42

Fran Hurtado

154
1
10

This happens in projects that aren't React Native too. – Mikael Grön Jul 01 '23 at 19:21

score 0 · Answer 8 · answered Nov 02 '21 at 15:29

Check if you have any other info.plist-s added to project. I had similar issue when I added some pod sources (MKStoreKit) to the project - it had several info plists for different platforms which interfered with original one. Deleting wrong info plists solved the issue.

score 0 · Answer 9 · answered Dec 06 '21 at 12:42

0

I have to delete the 'DerivedData' folder:

$ rm -Rf ~/Library/Developer/Xcode/DerivedData

answered Dec 06 '21 at 12:42

Bruno Carneiro

71
1
3

had absolutely no effect :( – EternalLight Jan 08 '22 at 16:28

DungeonDev · Answer 10 · 2022-02-04T14:08:44.883

EDIT: I've found a solution...

The problem in my case was because of project configurations and Pods. In the long life of my project the configuration files for the schemes changed and Xcode, using the new build system, did not like.

To fix it, just go to the Project -> Info tab. Under Configurations change the Based on Configuration value of the Targets and set them to None. Please note that I've changed only the Targets. Now close Xcode and launch pod install from the Terminal. reopen Xcode and launch your project.

Old answer:

I may have found a workaround to this issue... not a solution but a workaround.

I have to work on a not really recent project that was built using the Legacy System that, as you may know, is deprecated now. While I was using Xcode 12 everything was fine. Then I installed the Xcode 13 GM and I upgrated the project to the new building system and I started to experience this issue. I have the same problem with any Xcode 13.x version. With the betas I had not, as far as I can remember. The strange thing is that "sometimes" (I could not reproduce it sorry), the new build system worked... but just for a while. The building phase succeeds but then, then the app is installed on simulator OR on a real device, I have that annoying message that we know...

This morning I may have find a solution...

In Xcode go to File -> Workspace Settings, keep the Legacy Build System and check the box "Do not show a diagnostic issue about build system deprecation"

Now the app builds and can be installed.

Honestly I don't know it is an Xcode bug or not... maybe it is.

Usama Kabir · Answer 11 · 2022-11-27T10:43:49.773

0

Please make sure that your runner isn't missing AppDelegate.swift or Runner-Bridging-Header.h file. In my case, my AppDelegate.swift file and Runner-Bridging-Header.h files were deleted, so I copy and paste both the files in ios>Runner folder again from some other project (usually both of these files are same in all projects, just need to add the code lines for firebase configurations).

edited Nov 27 '22 at 10:43

answered Feb 22 '22 at 10:24

Usama Kabir

53
5

score 0 · Answer 12 · answered Mar 03 '22 at 12:19

if you are using git, there's huge chance there might be conflict in .pbxproj due to multiple people adding stuffs together. During the resolution xcode might try to recover those 'lost references' it got confused and unable to resolve the once there references. find those 'recovered references' in project explorer and remove them if they are invalid

score 0 · Answer 13 · answered May 06 '22 at 15:13

0

Had the same issue. I deleted the simulators and added them again.

answered May 06 '22 at 15:13

Matthew Korporaal

2,369
1
20
25

Pramodaya Jayalath · Answer 14 · 2023-02-27T07:00:17.003

0

I also had the same issue. These steps worked for me. I've done the following steps in XCode.

Goto 'Product -> Schema -> Edit Schema -> Select the correct Executable again.
'Close' and try again.

edited Feb 27 '23 at 07:00

answered Feb 26 '23 at 17:07

Pramodaya Jayalath

1
1

Executable Not Found. xxx.app is not a valid path to an executable file

14 Answers14

Linked