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