Why does Xcode keep modifying its executable?
Something really strange is happening with Xcode and the iPhone project I am working on, when I create a simulator, the project has 2 active executables (MyApp - iPhone Simulator (2.0) and MyApp - iPhone Simulator (2.1)) Almost all the time I want to use active 2.1 executable but Xcode will quietly change to 2.0 sometimes.
There seems to be no pattern for this or any trigger that I can notice. Googling found a couple of people who have the same problem but no solutions.
Help me do stackoverflow-kenobi! You are my only hope!
source to share
It's weird - I've been doing iPhone / Xcode development for a while now and have never seen anything like it.
Are you absolutely sure you're not going to dig up some place that is causing the change?
Perhaps you have a corrupted Xcode or .xcodeproj? If it persists, I'll try to rebuild my project, and if that doesn't work, reinstall Xcode.
Very strange, really ...!
source to share
I have the same problem. I need to install an active 2.1 executable for openAL to work. I watched it switch every time I switch to export to device. Isn't that what is happening to you?
I saw the issue commented several times on the official iphone dev forum but no solutions. Looks like a bug.
source to share
So why are you actually doing this? It is probably better, given the nature of the iPhone (with multiple frameworks for multiple architectures), to set up different targets for your different projects. The generated executable will be the result of the build phases for your purposes.
source to share