4 ms·
For one, it needs to install the SDK's for the new deployment target you just installed (be it macOS or iOS), and update the toolchain so it can build for it.
by w0utert 7y ago
For one, it needs to install the SDK's for the new deployment target you just installed (be it macOS or iOS), and update the toolchain so it can build for it.
It's mildly annoying, but the alternative would be to let you continue using the old version pegged to an older deployment target, and let you figure out all the incompatibilities at once when you decide you want release your app to the app store. IMO this would be much more annoying than just getting a coffee once while you wait for the upgrade.
- vetinari 7y agoHe said reinstall, not upgrade. For example, Xcode 11, which has 10.15 SDK target, can be installed on Mojave. This has been the case for years, the new Xcode can run on the n-1 OS release. So why reinstall it, after the system is updated?
- daveFNbuck 7y agoAnother alternative would be to upgrade xcode as part of the OS upgrade so all of my apps continue to work without me having to figure out this extra undocumented step. I'm not even using xcode. I just need the latest command-line tools for everything else to work.