3 ms·

I started developing an iOS client for an API we use at work recently. Downloaded Xcode again, built a small POC Mac app and ran it. It wouldn't run because I a

I started developing an iOS client for an API we use at work recently. Downloaded Xcode again, built a small POC Mac app and ran it. It wouldn't run because I am still on Mojave and the default settings are to build for 10.15. I was a little shocked/not surprised to get a "This application is not compatible with your software" type dialog from my own brand new code! I really like a lot of the ideas that Apple implements, but the upgrade treadmill is notorious and not one of them.

eschaton 6y ago
You can write applications that run all the way back to Mac OS X 10.6 using the latest Xcode. However, our of the box a new project is going to be configured to build for the latest macOS supported by the version of Xcode you’re using. It’s very easy to set your deployment target to an older operating system though.
- ultrarunner 6y ago
  Yes, you're absolutely right and this is not generally a problem (although obviously APIs get deprecated, etc). All my projects have a cycle, though, where I open them back up and have to turn several knobs in the build settings to get them to build. It's not often an issue with the code aging out, but the Xcode configuration. I got a pretty good chuckle when that happened to a brand new project right off the bat.