True, the abandoned 2.3.1 libLeap.dylib isn't built for arm64. But there's always Rosetta... In a funny cluster of circumstances, under macOS 12.6 it's actually only M1 machines that can connect with the Leap controller. The OS doesn't recognize it, but M1 users have a hacky option: go to "Recalibrate Device" in Leap settings then restart the machine. Upon restart, the device is recognized. This doesn't work for Intel macs, so we've got a situation where the only Leap library build option is for the architecture that can't recognize the device: great. I have no idea of the behavior under macOS 13. It may be that Leap hardware is a complete no-go there.