MacOS 15.0 beta (24A5320a) + BlockBlock 2.2.2 + ScreenMirror to VisionPro == EXC_CRASH

[achaseturner]

BlockBlock 2.2.2 has an EXC_CRASH on MacOS 15.0 beta (24A5320a) while I attempt to ScreenMirror from macOS to VisionPro 2.0 (22N5308b).

2024-08-18T10.58 - Crash Report - BlockBlock.txt

[objective-see]

Thanks for the bug report ...I've just released a new version that hopefully address this.

Can you give it a whirl and let me know if the issue persists? Thanks! 🙏🏽

[achaseturner]

Thanks for the quick turnaround. Installing and turning on BlockBlock v2.2.3, I am no longer replicating the crash so your fix appears to work! …chase PS. Concerning LuLu, the following Apple Feedback FB15074003 I submitted to Apple recently might be of interest — # FB15074003 This concerns macOS Sequoia 15.0 (24A5331b) configured for “LockDown” mode and Firewall turned on. To replicate this issue, look to Firewall -> Options and verify that SidecarRelay is not in the list. If it is in the list, remove the entry so as to replicate the issue as follows: # TO REPLICATE 1. Log into visionOS and macOS. Ensure both systems are on same WiFi and in proximity. 2. Verify macOS is in Lockdown mode with Firewall enabled. Confirm SidecarRelay is not in the list under Firewall -> Options. 3. In VisionPro, click on “Connect”. Or if on macOS, click on “ScreenMirroring” and select visionPro device. 4. In a moment, you will see modal alert in VisionPro indicating the “MacVirtualDisplay connection lost: The operation could not be completed (RPErrorDomain -6745)”. 5. Now look to Firewall -> Options. Confirm “Sidecar Relay” is in the list with an incorrect setting of “Block incoming connections” # WORKAROUND(s) Option 1 : on macOS, disable Firewall Option 2 : on macOS, open Firewall -> Options. Toggle SidecarRelay to “Allow incoming connections” # ADDITIONAL When upgrading from macOS Ventura to Sequoia on a host with Lockdown enabled, the Firewall blocked previously installed third party applications that had been installed. Per the attached screenshot “2024-08-19T1718 ScreenShot.png”, notice there is no option to change Wolfram from “Block incoming connections” to “Allow incoming connections”. Additionally, there was no possibility of deleting the entries. The only workaround for this issue was to rebuild the macOS host from scratch.

…

On Sep 11, 2024 at 4:42:00 PM, Objective-See Foundation < ***@***.***> wrote: Thanks for the bug report ...I've just released a new version <https://github.com/objective-see/BlockBlock/releases/tag/v2.2.3> that hopefully address this. Can you give it a whirl and let me know if the issue persists? Thanks! 🙏🏽 — Reply to this email directly, view it on GitHub <#79 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAIII3PBBCI273UNO6MXQBLZWC2KRAVCNFSM6AAAAABMWPSF6WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNBUG42TGMRZGY> . You are receiving this because you authored the thread.Message ID: ***@***.***>