So, yeah, I'm also getting this, here in Ireland. I filed FB13706261 about it, because it does seem to be some rather bad behaviour on the part of codesign.
kithrup
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
From
Beaverton, OR, United States
Post
Replies
Boosts
Views
Activity
I'll let it run for a while, but it does seems like a good thing.
Wow, that's very detailed, and helpful.
There is a NavigationStack in the view -- but it has to be wrapped inside of another one?. The onChange should be within the NavigationStack?
Then how do we contact DTS to request it?
Except you cannot use either @available or #available in a #if.
The crash is in self.selectedItem.first!.name because selectedItem has no entries at that point, in the sheet. It does in the Button action, which is why I am deeply confused.
I think @unvavailable would do the trick, but #unavailable does not -- as I said above, it's for a declaration not in-function code. However, that proposal doesn't actually discuss @unavailable.
I don't think being at my wit's end is cool. 😄
FB13319168; it is not resolved, which is why I filed the FB.
The machine that works is 12, and the ones that don't are 11.
I am kinda disappointed there was no Apple-provided class interface, since all those events are so clearly perfect for them. 😄
Although I haven't tried on iOS -- this was for macOS.
I haven't tried it yet, but NWPathMonitor / nw_path_monitor_t look promising.