I cannot reproduce your issue. I do not get the error message on Xcode 12.5 on macOS 11.4 when I create a new iOS game project that uses SpriteKit and run the project on an iOS simulator. The project runs and the spinning nodes appear when tapping/clicking in the simulator.

@testable import is for importing Swift modules, such as your app, not individual classes. Replace the class name with the name of your app (or framework) target, and you should be able to access your app's classes in the unit tests.

Looking at the Xcode 12.5.1 release notes, I see no reason why you would need to update your app. If Xcode 12.5 is working for you, keep using it to develop your app.

When you say "I never see the window", do you mean you do not see the Welcome to Xcode window? If this is the case, Xcode has launched. There happen to be no windows open. You can open the Welcome to Xcode window by choosing Window > Welcome to Xcode or pressing Cmd-Shift-1.

You need to use Xcode 13 to run/debug your project on an iPhone running iOS 15. To use Xcode 12 the phone has to be running iOS 14 or earlier.

New Xcode projects default to using SwiftUI with the SwiftUI app life cycle. The SwiftUI app life cycle does not include an app delegate file. There are multiple ways to get an app delegate file. The first way to get an app delegate is to choose Storyboard from the Interface menu when creating the project. Choosing Storyboard tells Xcode to use UIKIt for the project. UIKIt uses the app delegate file. The second way applies only to Xcode 12. For iOS and Mac SwiftUI projects, there is a Life Cycle menu. Choose either UIKit App Delegate or AppKit App Delegate to get an app delegate file. Xcode 13 does not have a Life Cycle menu. New projects use the SwiftUI app life cycle. To use the app delegate life cycle you will have to add a new file to the project for the app delegate and remove the App file that Xcode creates when building the project.

You need a paid developer account to publish your app on the App Store. You need a paid developer account to have other people use your app. With a free developer account you can put an app you develop on your own device. But you have to reinstall the app every 7 days.

No, UIKit is not dead. Apple has the following video from the most recent WWDC about UIKit What's New in UIKit The choice to use UIKit or SwiftUI for a new project depends on the project and you. Use UIKit if you are comfortable with it or if you need to support iOS 13 and earlier versions of iOS. Use SwiftUI if you are interested in learning it or if you want to make an app that runs on iOS and Mac.

Xcode 12.4 is the latest version that runs on Catalina. You can download it at the following URL: https://developer.apple.com/xcode/resources/ The site Xcode Releases (xcodereleases.com) also has direct download links for every Xcode version Apple has ever released.

Is there a reason you cannot use a tutorial that uses Swift? Most of the Objective-C material is going to be 5+ years old. You are going to have to use Swift if you want to use learning material that is up to date. I recommend going through the Hacking with Swift 100 day course that uses UIKit to learn iOS development. After going through the course, recreate the projects in Objective-C to learn how to make iOS apps in Objective-C.

What version of macOS are you running? What part of the message in the alert are you having trouble understanding? Xcode 12.5, the current release version, requires macOS 11 or later to run. If you are unable to update your Mac to macOS 11, go to the Xcode Releases site (xcodereleases.com) to find direct download links for every version of Xcode Apple has ever released along with the minimum version of macOS you need to run that version. Xcode 12.4 is the latest version that runs on macOS 10.15. Xcode 11.3.1 is the latest version that runs on macOS 10.14. Xcode10.1 is the latest version that run on macOS 10.13.

Xcode 12.0 does not support running and debugging iOS apps running anything newer than iOS 14.0. It is an annoying part of Xcode, as installing a minor iOS update forces you to update Xcode too. There are two ways to fix this issue. The first way, which is the Apple-approved way, is to install the most recent version of Xcode from the Mac App Store. The second way is to download the iOS 14.6 support files and them to your Xcode 12.0 app bundle. Read the last question in the following FAQ for more detailed information, including a link to the support files: swiftdevjournal.github.io/StartingiOSDevelopmentFAQ/Xcode

If you search for put Xcode project on GitHub in a search engine, you will find many articles on setting up git with Xcode, including the following: swiftdevjournal.com/putting-your-xcode-project-on-github-bitbucket-or-gitlab/

If you want someone to help you, you need to be much more specific about what you are doing, what you expect to happen, and what happens. Does the class of the view controller in the storyboard match the name of the class in the source code file where you are trying to create the outlet? Forgetting to set the view controller's class in the storyboard is a common reason for being unable to connect and create outlets and actions.

The following article has a collection of resources for learning Mac development: swiftdevjournal.com/resources-for-learning-mac-development/ Regarding learning SwiftUI or AppKit, you're going to find many more recent articles and tutorials on SwiftUI. Most of these articles are focused on iOS, but most of the material will apply to Mac too. Lists are the one view where you'll run into issues because lists(table views) have much different behavior on Mac than on iOS.