3 ms·

Yeah, bit of a shame. I took some time to go through Apple's tutorial, just to get a taste of SwiftUI, but I ran into Xcode crapping the bed every few minutes;

Yeah, bit of a shame. I took some time to go through Apple's tutorial, just to get a taste of SwiftUI, but I ran into Xcode crapping the bed every few minutes; having to clean the build folder every time a new source file was added; compiler bugs; and to top it all off there were a couple of places that the tutorial was outdated already. And of course you need to be on the bug riddled Catalina to get any real SwiftUI development done (live previews). UI development in the Apple ecosystem has always been a bit rough, but I've never run into _this_ many problems in such a short amount of time, all while following their official tutorial.

justAnotherNET 7y ago
It’s worse than you think. They recently shipped Xcode 11.2, which is required to build on iOS 13.2. By default, ALL builds built with Xcode 11.2 that use (common basic feature) runtime crash on iOS < 13.2. Yep. Every very soon. So if you happened to update your test device and ship with ios 13.2/11.2 Xcode ~40% of your users will crash on launch. Oh and it also broke all 3rd party lib loading, dead code stripping strips ALL 3rd party lib code... so you will bad_access on launch if you use SPM and leave dead code stripping on (default) So you need to reinstall a parallel Xcode 11.1 to ship today. But 11.1 can’t install to iOS 13.2, so god help you if you updated your only test device to 13.2. Oh, and this persisted to live despite the initial bug report on oct 3rd. In 5 years this is the worst I’ve ever seen
ta0xdeadbeef 7y ago
I mean XCode has been a terrible experience for a lot of devs (C++ in particular) for years. I completely avoid it, when you need it for a build just invoke it from the command line. Some of the other stuff is tricky to set up outside the UI so you need it, but other than that, XCode is not worth the hassle imo. Real shame too. I've talked about this with some of their tools team I went to school with. I don't know what's in the water in Cupertino but I don't think Apple devs are getting the same experience out of XCode as their actual users.

justAnotherNET 7y ago

It’s worse than you think. They recently shipped Xcode 11.2, which is required to build on iOS 13.2. By default, ALL builds built with Xcode 11.2 that use (common basic feature) runtime crash on iOS < 13.2. Yep. Every very soon. So if you happened to update your test device and ship with ios 13.2/11.2 Xcode ~40% of your users will crash on launch. Oh and it also broke all 3rd party lib loading, dead code stripping strips ALL 3rd party lib code... so you will bad_access on launch if you use SPM and leave dead code stripping on (default) So you need to reinstall a parallel Xcode 11.1 to ship today. But 11.1 can’t install to iOS 13.2, so god help you if you updated your only test device to 13.2. Oh, and this persisted to live despite the initial bug report on oct 3rd. In 5 years this is the worst I’ve ever seen

ta0xdeadbeef 7y ago

I mean XCode has been a terrible experience for a lot of devs (C++ in particular) for years. I completely avoid it, when you need it for a build just invoke it from the command line. Some of the other stuff is tricky to set up outside the UI so you need it, but other than that, XCode is not worth the hassle imo. Real shame too. I've talked about this with some of their tools team I went to school with. I don't know what's in the water in Cupertino but I don't think Apple devs are getting the same experience out of XCode as their actual users.