I had a similar issue, which you can see in the following post: https://developer.apple.com/forums/thread/740539 It turns out I had to add a Mac build to my app in TestFlight and get the build approved for external testing to get the products to fetch properly.

According to the following article: https://serialcoder.dev/text-tutorials/swiftui/navigation-view-style-in-swiftui/ Use the columns navigation view style to have two panels side by side on iPhones with screens big enough to show two panels. NavigationView { … } .navigationViewStyle(.columns)

I don't have any simplified approach for you. I can tell you two things. First, to pass a view model to a SwiftUI view, do the following: Have the view model conform to ObservableObject. Add @Published properties in the view model for any properties where you want the view to update when the property's value changes. Use @StateObject in the view that owns the view model. Use @ObservedObject in the other views where you want to use the view model. Second, avoid nesting observable objects. SwiftUI views may not update properly when a property in a nested observable object has its value change. If you are unfamiliar with nested observable objects, read the following article: https://holyswift.app/how-to-solve-observable-object-problem/

I don't see anything obviously wrong in your code. The only possible problem I see is a coordinate system problem where the values of the touch location may not be what you expect because the view and the scene have different coordinates. Set a breakpoint at the following line of code: let node:SKNode = ourScene.atPoint(location) Check if location is where you expect it to be.

I made a mistake in my answer. The @ObservedObject property wrapper is for SwiftUI views. You can't use it in a view model. The following declaration: @ObservedObject var dataManager = DataManager() Should be something like @Published var dataManager = DataManager() I am not sure what you are asking in your second response. You described what you are trying to do but didn't ask a question.

Bindings are for SwiftUI views. Using @Binding in a view model isn't going to work. Creating a binding like Binding<Bool> in a view model isn't going to work either. For passing data from a view model to a SwiftUI view, you are on the right track with the following code in ContentViewModel: class ContentViewModel: ObservableObject { @ObservedObject var dataManager = DataManager() @Published var isOn: Bool = false } Have the view model conform to ObservableObject. Use @Published for any properties where you want the view to update when the property's value changes. The view that owns the view model uses the @StateObject property wrapper, like you have in your content view. @StateObject var viewModel = ContentViewModel() Use the @ObservedObject property wrapper to pass the view model from the content view to other views. I am not sure why the content view model needs its own isOn property. Can't it use the data manager's isOn property?

For the Swift Student Challenge, either create an App playground in the Swift Playgrounds app or create a Swift Playgrounds App project in Xcode. That will give you a playground or project that meets the challenge's eligibility requirements. https://developer.apple.com/swift-student-challenge/eligibility/

Starting April 29 Apple is going to require Xcode 15 for App Store submissions. Xcode 15 requires macOS 13+. https://developer.apple.com/news/?id=fxu2qp7b The chances are high you won't be able to submit apps with that MacBook Air. I recommend buying a Mac with an ARM processor. ARM Macs are going to be supported longer than Intel Macs.

The .fileImporter modifier isn't for opening your SwiftUI app's documents. It's for opening other types of files in your app. The document struct's init that takes a ReadConfiguration is for opening your app's documents, either from a document picker (iOS) or by choosing File > Open (Mac). Instead of using your document struct's init that takes a ReadConfiguration, write a function to process the JSON that takes a URL as an argument. Pass the URL the file importer gives you to the JSON processing function.

I am not sure if the Swift Playgrounds app has been updated to support SwiftData, but the following article shows how to use Core Data in a Swift Playgrounds app: https://www.cephalopod.studio/blog/build-an-app-on-ipad-with-swift-playgrounds-and-core-data

I have never had a problem with my projects when moving to a new version of Xcode. Create backups of your projects before updating so you have a copy you can go back to if you do encounter a problem when updating to Xcode 15.

Choose Help > Report an Issue in Xcode to file feedback for this request. Posting about it on these forums isn't going to do anything.

I'm trying to follow STORMVIEWS tutorial which was made with an old version of swift were viewed load was still available The viewDidLoad method is still available. Your problem is that you are using SwiftUI to follow a tutorial that uses UIKit. Start over by creating a UIKit project. Take the following steps to create a UIKit project in Xcode: In Xcode choose File > New > Project. Select iOS from the platforms at the top of the New Project Assistant. Select the App template from the list of iOS app templates. Click the Next button. Choose Storyboard from the Interface menu. Read the following article for more details and a screenshot: https://www.swiftdevjournal.com/xcode-11-missing-view-controllers/

Not many people on this forum use SDL. You have a better chance of solving your problem by asking on SDL's forums: https://discourse.libsdl.org You may also want to search GitHub for SDL Xcode project templates. Using a project template can make working with SDL in Xcode easier.

If the solutions in the following article don't work: https://www.swiftdevjournal.com/dealing-with-failed-to-prepare-device-for-development-error-message-in-xcode/ You won't be able to run and debug the project on your iPhone running iOS 17.3. You have the following options: Buy a new Mac. Use Open Core Legacy Patcher to update your current Mac to the latest version of macOS so you can use Xcode 15. Use an iOS device running iOS 16 or earlier to run your project.