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.

I am trying to port my sandboxed macOS app completely over to iOS using a Catalyst target and SwiftUI. There appears to be an issue when trying to drag to the Finder in Catalyst (and in SwiftUI in General). For some reason, the Finder will not accept multiple file drops, only a single file. On my macOS (non-Catalyst AppKit target), I overcame this by dropping multiple files to a UTType of .folder, and the OS accepted the folder. This workaround is not available for iOS because .folder is a macOS-only option. I have a test app to illustrate the issue. Hopefully someone can help. Download Test App

I am trying to port my sandboxed macOS app completely over to iOS using a Catalyst target. In my macOS app, I use 'SwiftySandboxFileAccess' package to add a symlink to '~/Library/PDF Services' so that the 'share to my app' menuItem shows up in the macOS Print Panel (in the PDF menu). It is critical for the function of my app to have this work on macOS. In the Catalyst target, I am having problems gaining access to '~/Library'. I have tried having the user select the folder, but the picker always returns 'canceled'. I have a test app that illustrates this. The test app tries to coax the user into selecting the library folder and then it is supposed to bookmark the location, but I am unable to get this far. As an aside, macOS should probably automatically add an entry to the Print Panel when the app includes PDF as a document type in XCode; it would save a lot of hassle and avoid having to go outside of the sandbox. However, I cannot wait for that. Hopefully someone can help. Download Test App from iCloud (If you have problems downloading the file, it might be because of some iCloud share setting that I am not aware of. Just tell me and I'll figure something out.)

I am porting my app to SwiftUI and I am hitting a wall when using ScrollView. In my application, I have nested scrollViews to represent a scheduler. outer vertical scroll view inner horizontal scroll view that allows to horizontally scroll multiple columns in the scheduler each column in the inner scroll view is a view that needs to allow for a drag to initiate the creation of a new appointment on macOS, I do a mouse-down drag, so it does not affect the scroll view and works fine on iOS, if I add a drag gesture to the column, it short circuits the scroll view and scrolling becomes disabled. To initiate the drag, there is a long-press, and that gesture is fine, only the subsequent drag gesture is problematic. I have attached URL to a test app. The UI allows you to toggle the drag gesture. Hopefully, someone can help to get it to work since I would eventually like to port the macOS target to Catalyst. Download Test App