@DTS Engineer Would it be possible to revisit the swift API? I removed the explicit disallowal from the modulemap, and was able to get a swift installer plug-in building and working perfectly. I uploaded the code to this repo, based on the original authorization plugin sample code: https://github.com/SoCuul/SwiftInstallerPluginSample

Thanks for the confirmation! I discovered that my "nsmb.conf" file already contained soft=yes so unfortunately I think there's no proper resolution until a future macOS update.

Hi, thank you so much for the reply! However, I'm not manually setting up this mount with mount_smbfs. This is being done by (to my knowledge) backupd, when setting up a Time Machine backup to a network drive. I'm not exactly sure how I could tweak its "soft" behaviour, but I am likely guessing that it using a hard mount is what causes the kernel panics. This has been mentioned by other users as well, who have expressed that they use time machine over a network: https://discussions.apple.com/thread/255532638 https://discussions.apple.com/thread/255775553 https://discussions.apple.com/thread/255820364 https://discussions.apple.com/thread/255949982 It looks to have been introduced in macOS Sequoia, and that the issue was not present in macOS Sonoma. If the radar could possibly be referred internally to the correct CoreOS team, I would be extremely greatful.

I have been experiencing this as well on the macOS 27 Beta. My simple use-case was to try pinging a local IP in iTerm2, which resulted in sendto: No route to host, with no local network popup. The app is not listed in the local network privacy settings, and since its introduction it still has been missing the buttons to add/remove programs from the permissions list.

I can't believe that almost an entire year later this is actually still a problem.