I have read the other most relevant posts on this topic here and here. However, the situations described in these posts are different. My app is just a regular Mach-O bundle with a single executable that is launched by the user from the Finder. I've read the Local Network Privacy FAQ and TN3179 carefully and these also doesn't cover the problem described below, which is being reported to me by several of my users. The problem is that some days after giving Local Network permission to my app, without having changed anything, local network connections will spontaneously start failing with EHOSTUNREACH, indicating that it is being blocked by macOS. This typically happens after a Mac reboot. Toggling off/on the Local Network permission for my app will get it working again, until the next time it fails. My users who are reporting this have stated that they are running macOS Sonoma 15.2, with only a single version/copy of my app installed. I've tried, and failed, to reproduce this in a VM with a clean 15.2 system, but maybe this is due to the relatively short duration of my testing (days rather than weeks). I know there isn't much to go on here, and it may be tempting to put this down to misreporting. After all, the vast majority of my users aren't reporting this, and I can't reproduce it. But, I have received enough similar reports at this point that it's starting to feel like a macOS bug. Is anyone else seeing this? If there is anything that anyone can suggest - either modifications in my app, or anything that my users can do on their side - this would be very much appreciated! Many thanks, Ben

Hi All, I have an established macOS app that I would really like to add HomeKit features to, but I have been prevented from doing so by the lack of a macOS HomeKit API. However, now with the ability in Big Sur to create Mac Catalyst apps that can use HomeKit, my idea is to use this functionality to create a small Mac Catalyst app to serve as an intermediary between HomeKit and my macOS app. Technically it would work, however it's unclear whether this would be against Apple's rules. Any Mac Catalyst app that uses HomeKit apparently needs to go through the Mac App store (please correct me if I'm wrong, but as far as I can tell, it can't be Notarized and distributed directly to customers), hence it would need to comply with the App Store Review Guidelines. I can't see anything in the guidelines prohibiting this, so it would seem to be allowed, however before spending significant time on this project, I would like to find out for sure. Any input would be much appreciated. Many thanks! Ben

Hello all, My app invokes a bash script via NSTask, which creates an invisible folder in the user's Home folder, and then creates a file in that invisible folder (i.e. ~/.dirname/filename). Subsequently, I am attempting to read this file via POSIX functions, and the read() call provokes the following crash on the latest macOS 11 beta: OS Version:						Mac OS X 10.16 (20A5354i) Report Version:				12 System Integrity Protection: enabled Crashed Thread:				0	Dispatch queue: com.apple.main-thread Exception Type:				EXC_BAD_ACCESS (Code Signature Invalid) Exception Codes:			 0x0000000000000032, 0x00007fff6a0e098e Exception Note:				EXC_CORPSE_NOTIFY Termination Reason:		Namespace CODESIGNING, Code 0x2 Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0	 libsystem_kernel.dylib				 0x00007fff6a0e098e read + 10 I have seen this on a few different Macs, but on others (with the same OS) it seems to work just fine without crashing. No problems under macOS 10.13-10.15. My app is hardened, codesigned and notarized. I've checked the entitlements options and none seems appropriate to this. I should be able to read files within the non-protected areas of the user folder (i.e. not Documents, Downloads, Trash etc.), shouldn't I? Is this a macOS bug? Any help that anyone can provide would be much appreciated! Many thanks, Ben