I would start by commenting out the call to EditButton() and see if that fixes the error. If that doesn't work, comment out the code to create the "hi" toolbar item. The only other thing I see that could cause a problem is the following line of code: Text("Item at \(item.timestamp, format: Date.FormatStyle(date: .numeric, time: .standard))") That string looks fishy. It looks like you're missing a parenthesis at the end of item.timeStamp. I would start with something like the following: Text("Item at \(item.timestamp)") And add the format argument to the item text after you get the basic text to appear in the list.

All the online courses i have found are pre recorded and use outdated version of xcode and swift. List the courses you found that you didn't like so people don't recommend those courses to you. A lot of people like the courses at Hacking with Swift. https://www.hackingwithswift.com

I doubt you are going to find a course that teaches you how to build Mac apps with Python using Xcode. If you all you want to do is add a GUI to an existing command-line app, take a look at the Process class. This class lets a Mac app run command-line apps as subprocesses. Create a Swift app project and use Process to run the Python app. The Process class used to be named NSTask, which may provide better search results as Process is a generic name. If you are looking for resources to learn Mac app development, take a look at the following article: https://www.swiftdevjournal.com/resources-for-learning-mac-development/

Are you asking if an app you created with Xcode 13 and the iOS 15 SDK will run on iOS 16? If so, the answer is Yes, the app will run on iOS 16. You can make apps that support iOS 15 with Xcode 14. Set the deployment target, the minimum OS the app will run on, to iOS 15, and the app will run on iOS 15+ as long as you don't use anything Apple added in iOS 16. The following article provides screenshots and other details on supporting older versions of iOS: https://www.swiftdevjournal.com/supporting-older-versions-of-ios-and-macos/

The following condition: if false Will never be true so the code inside the if block print("Will this line of code ever be reached") someMethod() Will never execute. I have not read the book you are following. But it looks like the point of that code is to quiz you on whether the code in the if block will ever be reached, and not to build without any warnings. If you want to remove the warning, provide a condition that could be true or false or remove the if statement and the braces. But I think removing the warning defeats the point of the exercise.

What appears in Xcode's editor instead of your source code? If you see a bunch of assembly language code in Xcode's editor, look for a function you wrote in the stack trace and click that function. Xcode should take you to that function in your code. If that does not help, you have to provide more details on what you are doing, such as the following: The version of Xcode you are using The type of Xcode project you created What kind of breakpoints you set: line, symbolic, or exception.

What type of project did you create? The multi-platform app projects use SwiftUI so there's no option to choose a storyboard for the user interface. If you create an iOS or Mac app project, there should be an Interface menu where you can choose to use a storyboard for the app's user interface.

You have to wrap calls to async functions in a Task block if the function or closure where you make the call does not support Swift's async await syntax. If you are getting build errors if you remove the Task block, it's a sign the function or closure does not support the async await syntax. See the following article for additional explanation: https://www.swiftdevjournal.com/fixing-the-async-call-in-a-function-that-doesnt-support-concurrency-error-in-swift/ SwiftUI has a .task modifier you can use to make an async call from a SwiftUI view. You may be able to use it to avoid having to wrap your button code in a Task block. See the following article for an introduction to the .task modifier: https://www.hackingwithswift.com/quick-start/concurrency/how-to-run-tasks-using-swiftuis-task-modifier

Removing the if block will remove the warning. But I do not know if that is what the book wants you to do. I am not sure what the code is supposed to do because I have not read the book.

I tried solution mentioned in support page. But it is not working out. What specifically is the solution you tried that did not work? Xcode's issue navigator will show the build errors in your project. Press Cmd-4 in Xcode to open the issue navigator. What are the build errors the issue navigator shows? If the only build error the issue navigator shows is Error: Failed with exit code exited with status 1, clean the build folder by choosing Product > Clean Build Folder in Xcode. After cleaning the build folder, build the project again. Are you using CocoaPods in your project? Using them can cause build errors where you would need to update the pods.

Reddit has a Swift Playgrounds group that you could ask questions about the app. https://www.reddit.com/r/SwiftPlaygroundsApps/ Hacking with Swift has a forum where beginners can ask questions on Swift. https://www.hackingwithswift.com/forums

Are you making an app for yourself or for other people to use? If you are making an app for other people and want to play an audio file, you should bundle the file with the app and load and play the file from the app bundle. Using the app bundle is better than relying on a file being in the Downloads folder. macOS has privacy preferences in the Security & Privacy section of its Settings/System Preferences app. You can give an app full disk access or give an app access to specific folders. If you are making an app for yourself, use these settings to give your app permission to access what you need on the file system. You can give a sandboxed app access to the Downloads folder from the File Access section of the App Sandbox settings in Xcode.

You have a code signing error. What are the code signing settings for your project? Select your project from the left side of the project window to open the project editor. Select your app target from the target list on the left side of the project editor. Click the Signing & Capabilities button at the top of the project editor. Does your app have automatic or manual code signing? Are the provisioning profile and signing certificates correct? Xcode also has code signing build settings. Click the Build Settings button at the top of the project editor to access the build settings. The code signing build settings are in the Signing section. Are the values for those build settings what you expect them to be?

To create an app you can copy to other Macs, create an archive of your project and export it. In Xcode choose Product > Archive to create the archive. After creating the archive you can access it from Xcode's Organizer window. Choose Window > Organizer in Xcode to open the Organizer window. Select Archives from the left side of the Organizer to show the archives. You may have to choose your project from a menu above the Archives item on the left side of the window. Select your archive from the list and click the Distribute App button. A sheet opens asking for a method of distribution. Select Copy App because you do not have a paid developer account. Click the Next button. Choose a location to save the archived app and click the Export button. Now you have an app file you can run like any other app on your Mac and copy to other Macs.

Place the binary files in the app target's Copy Bundle Resources build phase to add the files to the app bundle. Open the project editor by choosing the project from the left side of the project window. Select the app target from the target list on the left side of the project editor. Click the Build Phases button at the top of the project editor. Click the disclosure triangle next to the Copy Bundle Resources build phases to see the files that are in the build phase. Click the Add button below the file list to add the binary files to the build phase.