The released date of macOS 12 is expected to be announced in days, and the new version of Xcode including macOS 12 SDK will be published a few days before then. Or you can try with Xcode 13 beta 5, which includes macOS 12 SDK beta.

Sorry, but I do not know what would be the best. In fact, I have never watched SpriteKit/SwiftUI apps tracking the paused state. But, if your code is working as expected, I cannot think of anything bad.

In this way it's impossible to use inside mac apps. Xcode 13 does not include macOS 12 SDK. You may need to wait the next Xcode which contains macOS 12 SDK.

Can you show what you have tried? The answer of uocram would work for kUTTypeData with a similar manner.

@skattan, you should better start your own thread. Please do not forget to include all your current codes or any other context possible. Even when you are seeing the same error message Cannot find 'landmarks' in scope, it may be caused by many sort of mistakes.

@DidStory, Is the lack of capacity irreplaceable with iCloud? No, iCloud will not make it. Many of the files required for developing, building and testing apps need to be placed on a start up disk. You can start with a 256GB Mac, and when you feel it too small, one alternative is buying an external storage device with larger space and install macOS and Xcode into it. When you start up your Mac from the external drive, you will be able to continue developing. If you do not prefer to work with external storage, I recommend you get a Mac with 1TB (or more if you can). And I have never heard of apps as _ a "connector"_, so I cannot say any more. But in case I use the term "not simple" app, I have in mind huge game apps consuming tens of GB of storage space each published by famous game studios.

Thanks for trying to explain in details. But with my lacking enough ability to understand all the descriptions and nuances (I guess Google is doing well, but I cannot be sure), my recommendation would not change: Start now.

Generally, when you show some code, you should show all the code as text. Adding an image would be helpful as an additional info, but it cannot be a primary info because readers cannot pick up the parts included in the image. Usually, in this sort of errors, you should better show all the headers of ObjectiveC classes and the bridging header. But reading the strange thing, there may be a possibility that your Xcode is malfunctioning and just recalling the old errors when you had not set the bridging header correctly. Have you tried restarting Xcode, or restarting your Mac?

Apple prefers innovation rather than compatibility, that might show some bad aspects for beginners. But Apple has the dev forums. If you find difficulties developing on the Apple's platforms and tools, you will get answers here. Hope you will make great apps. Good luck.

@ArjunDureja, as I have already written, I cannot find any descriptions about the API in shazam.com . You may need to be responsible for all the things when you want to use the API, including payment.

When you show your code, you should better show it as text, using Code Block. With easily triable code, more readers would spend time for your issue. Screen shots are sometimes useful, but we cannot copy the lines in images into our Xcode. And thanks for showing the image Here is what I made so far, but can you show what is the expected result? If any of the images in your opening post is representing the expected result, you should write so.

Then you should have included the body in the opening post. Learning how to write a good question will help you learning programming.

Please share your solution.

@H957169, Please do not put SOLVED on a post that says just the issue is solved. When you solved the issue, please post and share the solution and mark it SOLVED. If any of the answers helped solving the issue, choose the most valuable answer and mark it SOLVED.

Didn't you read my answer? When you show your code, please show it as text using Code Block. Ignoring some answers would not be considered to be a good manner when communicating on the web. And I believe my answer solved the issue Cannot assign value of type'Int' to type 'UILabel'. If it does not solve the issue, you can write a comment to my answer, if you find other issues as I described, you can start new threads asking the issues. Please do not forget to include your code as text when starting a new thread.