Post not yet marked as solved
I had 2 "Apple Worldwide Developer Relations Certification Authority" certificates. After deleting the older (expired) one in Keychain Access, the error went away in Xcode 13.1.
Post not yet marked as solved
I'm got the same problem trying to download Xcode 13 RC. I'm in the US, have a developer account, and just downloaded Xcode 13 beta 5 last week and have been using it fine. But I get the same cryptic web page when clicking on the Xcode 13 RC download link. I think this is a mistake and should be telling you that you need to be running macOS 12.X, but it doesn't say that. Here's what the description says:
To continue developing apps for macOS Monterey, use Xcode 13 beta 5.
But this seems wrong. I believe it should read "To continue developing apps for macOS Big Sur, use Xcode 13 beta 5." Even though the text looks wrong, it's a clue that the requirements have changed. The release notes say "Xcode 13 RC requires a Mac running macOS 11.3 or later." but I believe this is also wrong (likely a copy-paste error that didn't get changed from he previous release notes).
IIRC, the final version of an Xcode beta release schedule ("RC") does typically require the new, soon-to-be-released version, so it would make sense for a RC to require macOS 12.X.
Xcode 13 Beta-5 has actually been stable for me though, so I'll just continue using it for now.
Post not yet marked as solved
I agree with @ppix, it's a shame that SceneKit and SpriteKit look to be abandoned (not officially, but it's pretty clear they're not getting much love going forward). With a little more building out and some more comprehensive documentation, these could have been a prefect balance of ease of use and performance. Being able to use them in Swift was wonderful (although I started using them in Obj-C).
But yeah, thanks for these APIs, as imperfect as they were, they were great for a while. I found them very useful for writing utility apps, such as for touchscreens used in broadcast.
This is STILL happening in Xcode 12 beta-3. Unbelievable.
For reference, here is my bug report to Apple. To be fair, they did get back to me requesting further information (the build log), which I provided. But that was over a month ago (not only is Xcode 11 out of beta now, but 11.1 is released and still exhibiting the same issue).Please provide a descriptive title for your feedback:Xcode 11 beta-5 with SPM dependencies produces errors with Archive buildWhich area are you seeing an issue with?Swift CompilerWhat type of feedback are you reporting?Incorrect/Unexpected BehaviorPlease describe the issue:I have a Swift 5 project using Swift Package Manager dependencies in Xcode beta-5. This project could Archive build without errors in Xcode 10.X, but in Xcode 11, I get compilation or linking errors and the archive is not built. Specifically, each dependency generates one of 2 errors: "No such module" or "Command CompileSwift failed with a nonzero exit code".These errors are NOT generated using Run (Debug build), they only appear when attempting a non-Debug build, such as Archive or Profile. Again, this same project compiled, linked, and exported fine in Xcode 10.Please list the steps you took to reproduce the issue:1. Cleaned project (Option-Clean Build Folder).2. Delete all in DerivedData folder.3. Restart Xcode.4. Restart computer.5. Try same project on different computers also running Xcode 11 beta-5 (same result seen both with macOS 10.14.4 and macOS 10.15 beta-5).6. Select File > Swift Packages > Reset Package Caches.7. Delete project and workspace files, re-create those files fresh using Xcode 11 beta-5, re-add source files and dependencies.What did you expect to happen?Expected Archive command to produce an archive build.What actually happened?Build fails with error listed above.
I wouldn't close this thread, because the problem is not solved. By closing it, you may give people (even Apple) the impression that it is no longer an issue. We're on Xcode 11.1 release and this is still a problem for me.
You're right, these kinds of bugs will sour people on adopting SPM for sure, it already is for me. I was really excited to finally have SPM integrated, hoping I could move away from Carthage and Cocoapods, but with the SPM system behaving this way it's a serious impediment and will make me skittish about using it for a long time. I can't afford the time loss trying to figure out what's going on in Apple's inscrutable build system. A "nonzero exit code"? Uh, thanks for that helpful description, Apple, what am I supposed to do with that?
I'm having the same or a similar problem, but in my case re-creating the project and workspace files in Xcode 11 beta-5 still results in those "no such module" errors when compiling/linking my SPM dependencies. In addition to "no such module" errors, some dependencies generate "Command CompileSwift failed with nonzero exit code" errors. Like you, I can run it fine in Debug mode, but cannot export using Archive. This seems like a bug (I hope?), hopefully one that will be fixed soon. This project was fine compiling non-Debug builds in Xcode 10.X. I'm using macOS 10.14.4, but I also tried it in macOS 10.15 beta-5, but it didn't fix anything.Submitted Feedback Assistant bug report #FB7031121 "Xcode 11 beta-5 with SPM dependencies produces errors with Archive build."EDIT: problem is still present in Xcode 11.1 (release). I'm pretty sure this is some setting from Xcode 10 that got stuck and is messing up the linking, because I created a few new projects with the same dependencies and they're OK, but I can't find exactly what causes it.
