Getting an Issue with Upgrade to Xcode 10.2

Can't build macOS project after updating to Xcode 10.2/Swift 5

I had problems with some of my code involving extending the ClosedRange type to Encodable and Decodable in a custom way. In Swift 5, ClosedRange already conforms to Encodable and Decodable when its Bound is Encodable and Decodable, but the compiler wasn't giving me an error about the redundant conformance, instead just hanging on compilation.

After I modified my code to use the new Swift 5 protocol conformance, it compiled fine. It took a long time to narrow down the problem to this, however. It seems to me to be a bug in the Swift Compiler because the compiler hangs in a Playground or from the command line as well, even on a different Mac.

Update Xcode 10.1 to 10.2 on High Sierra 10.13.6

The difference between the two versions is not that huge for example Swift 5.0 allows to build projects without the embedded Swift Libraries.

Xcode 10.2 doesn't run in High Sierra. It requires macOS 10.14.3

Xcode 10.2 Update issue Build system error -1: Unable to load contents of file list: input/output xcfilelist

I struggled with this for several hours today and this is what finally worked for me:

1. sudo gem update cocoapods --pre
2. pod update
3. clean
4. build

From what I've read, this is an issue with the new build process that is enabled by default in Xcode 10.2 though I've not found the workaround clearly documented anywhere yet. There may be a more elegant solution than what I described.

hundred of warnings after update to Xcode 10.2.1. is it still OK to be published to App store?

Regarding the decision to update Xcode so you could run this on your device, it turns out that this may have been unnecessary. Largely regardless of Xcode version you use, you generally can manually install an app on an device running a more contemporary iOS version. You just won’t be able to run it via the debugger from an older version of Xcode. See https://stackoverflow.com/a/35044362/1271826, whose basic concepts about installing still apply today.

All of that having been said, the choice of minimum Xcode version is dictated by Apple’s App Store guidelines. See this March 2019 guideline which says that apps must use iOS 12.1 SDK or later. And watch the Apple Developer News feed as these minimum SDK requirements change over time.

Regarding the warnings, they will not be a problem for submission. Apple doesn’t have your source code and has no exposure to what compile-time warnings you got. The thing is that these warnings really are telling you important and helpful stuff about “such and such might be a problem”, which is why it’s good to resolve all of them. We can’t comment about which warnings are really important and what’s not without seeing which warnings you received.

But I’d suggest that you:

• Make sure you install a version of Xcode that supports the minimum SDK version outlined in the Apple Developer News feed; and
• Make a good faith effort to address as many of the warnings as time permits.

At the time of writing, the minimum SDK version is 12.1. But keep an eye on that feed, as the minimum requirements are periodically updated, but generally with some advance warning.

Xcode 10.2.1 xcode simulators are not working

I was having the same issue after upgrading to macOS 10.15.3 Catalina with Xcode 11.3.1.

TL;DR

I had to reinstall macOS over the installation using recovery - but please try all the other steps prior to that though, and here's why:

My update procedure was rather unusual:

• installing 10.15 externally to a fast SSD
• building up the installation with all cloud storages and software that I needed gradually when I had the time
• keep on working with my proven 10.14 installation during day to day work
• once I had a certain installation level on the new installation, cloning the internal 10.14 installation to another external drive with Carbon Copy Cloner (CCC) (and confirming that it did boot and work)
• erasing the internal storage and cloning from the new installation of the external drive to the internal storage

Phew – I know, that's involving a lot, but that's just the way I did it... And I like to do this every once in a while just to get rid of software I once installed for reasons but that I am not using any more (and probably forgot about...).

Anyway, when cloning to the internal flash, CCC through a warning at me, that a file had not been cloned as it should have:

So I thought that maybe missing this com.apple.TCC file wouldn't be a big deal cause it might get rebuilt upon boot or whatever – so I gave it a try anyways and booted from the internal storage.

Everything seemed to be working as expected – expect not being able to run any of my projects in a Simulator from Xcode. So I researched and tried a view things that did not work.

When I was at the point where I almost broke in and considered reinstalling internally from scratch again (Ofer having deleted and reinstalled Xcode I have to add), I thought, maybe I could try and just install macOS over it through Recovery.

All that is to say that: after having installed macOS over the cloned installation, my projects attach just fine to the Simulator again.

I am not quite sure whether com.apple.TCC really had anything to do with it, but I can at least say that reinstalling save my bacon...

(Perhaps installing the latest Xcode Beta 11.4 or waiting for that to get out of Beta would have helped also, but neither of those two where an option for me at this stage)

Hope this might help anyone running into this issue...

---

Related Topics