I’m trying to use NWPathMonitor in my watchOS 6 app. The weird thing is that it works fine in Simulator, but is never ‘satisfied’ on a real device. Is there a reason why this is so? If it is a limitation of a real device, then perhaps Simulator should reflect that limitation. If it’s not a limitation, then how can I coax the device to return ‘satisfied’?

I am using SwiftUI Table View in my macOS application The app uses a server-client paradigm where the client queries the server database and presents the fetch in a table. I had used List earlier on, but I found it was not performant on macOS so I switched to using Table view. the Table view on macOS was better than List but it suffers from a 'forever hang' where a beachball can last for minutes. this occurs each time in this way: launch the app and the Table with 5000 rows load fine on update of the data, it hangs forever interestingly, this does not occur on iOS. I have a very simple test app that shows this issue but I cannot figure why the data update causes a hang and how to remedy this. I have tried applying an .id() to the Table but this did not help. Clearly, since the initial loading of the data is easily handled by the framework means that there is no inherent limit to the number of rows. There is something going on when applying an update to the table data.