I'm no expert, but I would try the following. NavigationSplitView { List(notes) { noteTitle in NavigationLink (noteTitle.name) { NoteEditing(noteModelClass: noteTitle) } .onDelete(perform: deleteNote) } .navigationTitle("Notes") .toolbar { Button ("", systemImage: "plus", action: { presentNewNoteAlert = true }) }

In my case, when I submitted my app recently, nothing bad happened when I submitted my MacCatalyst binary to App Store Connect. @SwampDog, you need to submit a separate binary for the MacCatalyst app, I believe.

It used to take a week or more to get a review. I've experienced my apps be in review for. a few days. My suggestion is to be patient.

I’m simply talking about using voice instead of text input in a search bar.

I am seeing this message while using the visionOS simulator, but not while using the iPhone simulator doing the same steps.

Are you using the default iCloud container or did you define one yourself? I don't see your ModelConfiguration init. Something like the folliowing. let modelConfig = ModelConfiguration(schema: schema, cloudKitDatabase: .private("iCloud.com.mycompany.name")) do { container = try ModelContainer(for: schema, configurations: [modelConfig]) } catch { fatalError("Could not create ModelContainer: \(error)") }

I'm getting the warnings too, but I was able to build with the warnings and I've submitted the binary to App Store Connect. There were also some other gotchas that I had to resolve. The Mac build was linking to my watch app where it never did so before. I had to go into the build settings and click off the Mac dependency.

You can force a save, modelContext.save(), instead of waiting for the auto save.

In Page, try this @Relationship(deleteRule: .cascade, inverse: \Line.page) var pages: [Page] In Line, simply try the following var page: Page No need for @Relationship here as SwiftData infers this.

I've decided to keep the Mac Catalyst destination as I can resize the view, whereas with the Designed for iPad destination, I cannot.

You might need to import VisionKit.

You problem know this, but SwiftData works fine now on visionOS.

You didn't save your model with insert. You only inserted the data into the context. You need to either save the context or wait for an auto save.

I just added the visionOS platform to one of my apps and got a message about not being able to mess with metadata or upload a binary at this time. Okay, I think I got my answer by clicking the little checkbox.

Thank you rmahnud28.