I think we have to keep using modifyRecordsCompletionBlock because modifyRecordsResultBlock doesn't error on server record changed, it erroneously reports success. As of Xcode 14b1 iOS 16b1. See this post for more info.

Use one session, according to Use Background Sessions Efficiently I noticed if you init a session with a config with the same identifier you will actually get the previous instance. I assume you have to set a taskDescription on the task to be able to identify it in .backgroundTask() on the Scene, where presumably you have to retrieve all the completed tasks from the session and deal with the results.

The problem is ForEach with id: \.self for a dynamic array of value types is a major mistake unfortunately made by many developers, anyone know why? The documentation states that id needs to be "The key path to the provided data’s identifier." E.g. id: \.uniqueIdentifier, or preferably conform your model struct to Identifiable and implement either let id = UUID() or var id: String { return a calculated id from other vars }

The ForEach View cannot not work with indicies for dynamic data, it requires identifiers which is why we supply it with an array of Identifiable data. This is so that it can calculate inserts, moves and deletions which obviously is impossible with an array of indicies which will in the case of moving 5 items around the indices will still be 0-4.

You could try this workaround: var cancelable: AGSCancelable? let onCancel = { cancelable?.cancel() } return try await withTaskCancellationHandler { onCancel() } operation: {

In SwiftUI we don't use view model objects. The View structs (or custom @State structs) hold the data that SwiftUI uses to diff and update the screen. View models are a UIKit pattern don't use it in SwiftUI, if you do then you'll add an unnecessary level of indirection and slow SwiftUI down and lose a lot of the magic behaviour.

isDetailLink(false) on the NavigationLink will fix this problem

To avoid this do: struct InsideView: View { let value: Int // … } @Binding is for when we want write access to the state.

There is a mistake. You need to move your NavigationView into Tab1. Also remove the ZStack. struct Tab1: View { @State var shownextPage = false var body: some View { NavigationView{ NavigationLink( destination: SecondView(), isActive: $shownextPage) { Text("Next Page") } } } }