Post

Replies

Boosts

Views

Activity

How to fix "Could not launch: xxxx Executable does not exist" error"
Hi i am currently using XCode 15 to build a Swift command line application. But when I try to build & debug my project, it throws an error saying that it could not launch the executable. It does build but as the error suggests, the Build dir does not have a executable in it. I have messed around with DerivedData & Build location settings for quite a bit with no luck. Currently both of them are at default settings as I cleared XCode caches from ~/Library/Caches & created a new project. I tried compiling the basic Hello World but that seems to "build" but with no executable. I have attached the report for the Could not launch error Error report Am i missing something with respect to build location / configuration? Thanks for any assistance.
2
0
2.6k
Sep ’24
My app's dylibs not getting recognized as Mach-o after migration. How to troubleshoot / prevent this from happening?
As the title says, I have an application that has a few dylibs right next to it. More often than not, when one of my users migrates from one Mac to another using the Migration Assistant, my app starts crashing since it is not able to recognize the dylibs as a Mach-O file. Both my app & the libraries are compiled for x86 and run on top of Rosetta. Does this maybe play a part in causing in this issue? Doing a file <dylib name> returns "data" as the file type. How to prevent this from happening?
1
0
209
Aug ’24