Trying to “Run” my Mac build target from Xcode. Xcode complains with:
error: executable doesn’t exist: ‘[…]/Binaries/Mac/Ze-Mac-Debug.app’
error: failed to launch ‘[…]/Binaries/Mac/Ze-Mac-Debug.app’
Looking at the schemes, I see that it’s referencing “Ze-Mac-Debug.app”, but when I look in my binaries I don’t see Ze-Mac-Debug.app, but I do see Ze-Mac-DebugGame.app.
I’ve built for Running, Testing, and Profiling. Is this just a mistake in the project configuration (and subsequently UE4 Xcode project generation), and the scheme should be pointing to Ze-Mac-DebugGame.app where I can actually run from Xcode?
I’ve just started working with UE4 and I have come across the exact same problem in UE 4.8. I renamed the binary and that worked but it’s obviously not a good solution. The real solution would be to rename the DebugGame configuration to just Debug to match the other configurations but it needs to be done in the script that creates the Xcode project. I’m not sure where that is though. Hopefully Epic will get this fixed at some point.
Me too, renaming the app solves the problem but after compiling a new *-Mac-DebugGame.app is created…
I think it’s a small configuration in xcode, but I don’t know where and about any side-effects though.
The best workaround I know of is to simply select the correct executable via the “Executable” popup menu in the Scheme settings. See the screenshot in the original post. This will work until you rebuild the project, then you need to go set the correct executable again.
Are you referring to opening the project in the editor is causing problems or is it an issue with opening a packaged product? If there is a simple way to reproduce your problem can you give me steps to I can test it on my end or include a sample project where the problem is occurring? Let me know if there’s any additional information you can provide.
Just create a C++ project from the UE4 template. I used the “Flying” template. Then build it in Xcode and try to run it from Xcode. As you can see in the screenshot in the original post, the executable in the Scheme is not the same as the executable that is actually built so it will complain that it can’t find it.
