You mentioned cross platform, and this is very late, but on macOS I couldn't get Link or @Environemnt(,openURL) to open a log file. BUT NSWorkspace.shared.openURL works for me. I don't think it is available on iOS though. I mainly posted in case some else finds this it will help. NSWorkspace seems obscure and I might not have found it save I had worked with it a lot some years ago. And to say hi to the eskimo ive seen here for years :) maybe ill see KMT again too.

Beta 8 and I have 96 gigs free with SystemData eating 65 and CoreSimulator says its almost full. It's definitely not but hey it must work on Craig's machine and his paycheck is safe. It said my disk was full even after a fresh install. Sure feels like a major bug and its obviously happening to re than one person. Im screwed until they fix this. Could cost me a job.

Unusable for me in swift but for totally different reasons: constant beach balling and stuttering UI. Worked fine in 14.0.1 Not surprising at all to me, I've used Xcode since 3.2. Apple can't compete with the expectations in developer tools Microsoft created with theirs.

I am having this issue merely using Map(...anotiationItems:,annotationView:...) If there are ANY annotationItems returned , then multiple times per second that error is spat out with the most useless call stack from LLDB I've seen since Xcode 5. It has nothing to do for me, with whether map bindings are @State local to the view or in a view model. I can see from searching online the problem isn't even acknowledged. Only option I have now is dumping apple maps I suppose. If anyone else has any ideas....

Yep.4 years later, tneyears later, doesn't matter with Apple. I just get build failed, Command SwiftCompile failed with nonzero exit code, or just nothing but build failed. Restarted Xcode twice, deleted deprived data once. Googling this shows it has happened since 2013. I guess they just don't have enough money to have tools on par with the industry. I have to just create a new project and do a ton of extra work because of the poor tooling. JS sucks, but god its tools actually work. I'll reboot my Mac and pretend I'm a PC. Its not like Apple ever acknowledges these problems anyway and will never fix them. I'm tired of losing work to the tooling.