[orbitur]

Can you still submit apps with Xcode 7?

In response to your problem, having done the Xcode Old/Xcode New dance every year since 2012, I got into the habit of making sure they are never running concurrently. Things get even worse if you run xcodebuild on the command line while a different UI version is running.

[xenadu02]

You can't run multiple versions of Xcode concurrently due to CoreSimulator fighting over which version gets to run. This is a limitation we are aware of. We are also very aware of the problems it causes.

As for other problems, please file radars and respond to requests for additional information. I have been on the external side of radar, I know it can be frustrating, but we do read them and we do take direct action based on them. Even duplicates are very useful.

[megablast]

What? I have very little problem running Xcode 7 and Xcode 8 along side each other. As long as you close the simulator before running from the other version.

[xenadu02]

Only one CoreSimulator service can be running at a time because only one can be in control of the devices and the database. If you try to keep two versions of the tools open they'll keep killing each other's CoreSimulator or one will get stuck with the wrong incompatible version.

CoreSimulator is used during builds and for IB's accurate rendering feature. Instruments and Console open connections to CoreSimulator for various purposes. A lot of things can break.

[orbitur]

I've found having IB open in both versions will eventually lead to errors in IB, if not outright crashes.

[wool_gather]

> Can you still submit apps with Xcode 7?

...yes. You can. 6 is the minimum.

> having done the Xcode Old/Xcode New dance every year

There didn't used to be this hard division between Xcode versions because of the compiler. If you were willing to do some reconfiguring, you could use newer GCC or "Apple LLVM" with the older Xcode.

[LeoNatan25]

Why are you not using the Swift 2.3 option in Xcode 8? It is going away in Xcode 8.3, but still, you can use more modern and stable dev tools.

[wool_gather]

I'm not sure why it hasn't been done yet; I've only been on the team for two months now. That would indeed be lovely. But the plan is to have one of our contractors move the entire project up to Swift 3. I don't know exactly when, though...

[wahnfrieden]

The OP mentioned Swift 2, not Swift 2.2 - even that upgrade can be non-trivial (2->2.2).

[wool_gather]

Eh, it is indeed 2.2, sorry for the imprecision. But yes, the concern is the time for the transition. Planned. We just have to fit it in.