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
Check if all files are available.
Targets -> Build Phases -> Compile Sources
If you see faint files, then they need to be removed or added.
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.
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.
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 .
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
Check the Executable File in the Info(.plist). It should be named the same as your Product in Products
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.
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.
I have to delete the 'DerivedData' folder:
$ rm -Rf ~/Library/Developer/Xcode/DerivedData
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.
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
Had the same issue. I deleted the simulators and added them again.
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).
I just updated my xcode to Version 10.1 (10B61). After doing so, my pods don't work. See below error messages. Aside from PKHUD, the error messages don't provide suggestions as to how to fix this issue. Per online sources, I've updated my OS to High Sierra 10.13.6. Any suggestions on how to get the app to compile? It was working before the update.
On Xcode, select the Pods project and on the left panel select the frameworks that are causing the issue. On Build Settings, browse for Swift and make sure you have correctly set the version you have installed of those frameworks.
You can check that framework is fine after you tweak that value by compiling the framework after selecting it.
Just run cmd+B to compile and check if it build successfully. If you don't see the framework on the list just go to manage schemes and add it.
I'm trying Firebase for the first time, and after adding pod 'Firebase/Firestore', Xcode 9.0.1 produces many warnings in the various cocoa pod installed libraries.
Possible misuse of comma operator (in leveldb-library)
Multiple build commands (for a file in BoringSSL (there are like 15 copies of internal.h)
In gRPC-Core there are 51 issues, some "multiple build commands" and several that I've read about elsewhere relating to syntax, like "This function declaration is not a prototype".
I'm new to Firebase and Cocoapods, and I'm just starting a project that I would not need to ship for weeks. What should my strategy be:
a) These warnings are due to the Firebase pods not catching up with new language rules. I should just wait for some time and reinstall and they will go away.
OR
b) I goofed up installation (even though I've tried several times), and there's a step I missed, or a step I shouldn't have taken. Here's what I did:
platform :ios, '10.0'
pod 'Firebase/Core'
pod 'Firebase/Auth'
pod 'GoogleSignIn' // all this worked fine up to here
pod 'Firebase/Firestore'
added no new code to the boiler plate stuff I copied in to test auth
closed xcode
$pod install
open xcode, clean, rebuild, see 107 warnings
I can live with the warnings and carry on developing, should I? It will be hard to see legit warnings my code generates, and if (when) my newbie code hits an error, I'll be stuck wondering if it's me or one of these warnings manifesting itself.
Can someone share experience? Is it some bad install thing I did or is it just that I'm using stuff that's too new? More importantly, how to proceed?
The answer is (a).
Xcode 9 introduced several new default warnings and the Firebase team is working with its dependency pod providers to address them.
You can expect the warnings to go away in upcoming Firebase, leveldb, and gRPC releases.
Recently I installed cocoapods and wanted to add Firebase analytics to my app. The first time a published the app worked, but now it started showing me that: Library not found for -lGoogleToolboxForMac.
I install again pods but still the same.
What should I do in this case? I mention that I use VirtualBox.
Please ensure successful installation of pods.
Also, after installation close current project .xcodeproj and open up .xcworkspace.
We have discovered one or more issues with your recent delivery for "AppName". To process your delivery, the following issues must be corrected:
Invalid Bundle - One or more dynamic libraries that are referenced by your app are not present in the dylib search path.
Once these issues have been corrected, you can then redeliver the corrected binary.
Regards,
The App Store team
For me the following worked:
i updated cocoapods if You have troubles doing so this link may help
deleted MyProjectTests (that i wasn't using)
deleted my Pods/ folder and Podfile.lock
made pod install
rebooted my mac
and the problem is gone
I have just seen the problem after install the app in a real device, but crashed (in the simulator works). My app missing a library installed with Cocoapods.