Very Concerned About Recent Update Issue on Apple Macs-Driver Install?

[CommanderJoy]

I am becoming concerned that the Aha Halo IT team is too steeped in developing for Windows that whatever recent issue occurred with OS updates is disrupting the pristine manner in which Apple operates. I am running Tahoe v. 26.3.1 and have not yet downloaded the recent OS update to 26.4. I have not had an issue with the Halo not being recognized.

When booting up the SW, I received the update message that (supposedly) Apple has stripped out a driver that the Aha Halo SW needs to see the attached device. Really? I downloaded the new Halo SW and the message is “Virtual Com Port Driver Missing”. Well it wasn’t missing before and I have been running the same version of Tahoe and Halo SW.

So OK, I downloaded the new Halo SW and am VERY concerned that an independent CP210x Mac OS Driver - by Silicon Labs now needs to be installed. This is not the way Apple operates and should not be the way the Aha Halo SW is coded for Macs. Coggling together drivers, code and bits and pieces is a Windows thing, and should not be necessary when competently coded Mac software is created. You state that “Apple stripped out a driver”. I haven’t even downloaded Tahoe 26.4 and the software was working fine.

I am receiving a message from Mac OS Privacy and Security saying that “Aha Halo” was prevented from modifying apps on your Mac.” after downloading and attempting to install the latest Halo SW. I do not want to compromise the security of my computer this way, and now have a dilemma that frankly I think your IT people should have avoided. It smacks of Windows programming really not understanding proper Mac coding and approaching it from a Windows training and perspective.

I would like to see a thorough evaluation of your Mac updates. We should NOT need to download and install a 3rd party driver just to run your software on a Mac. You need to do a better job.

UPDATE: When booting up the Halo SW and the message that comes up says “The driver for the virtual com port is missing or outdated.” just hit CANCEL. The SW opens just fine. Didn’t the IT team test this? Why weren’t they aware that the driver was not needed? What evidence exists the “Apple stripped out a com driver?” So my advice to Mac users is avoid installing the driver as it is not needed.

[ahaharmonyofficial]

Thank you, CommanderJoy, for your valuable input! We appreciate you taking the time to share your thoughts with us.

We completely agree that the ideal installation experience is one that doesn’t require any additions to your system. However, when specific hardware needs to communicate with your Mac, sometimes a few modifications are necessary to keep everything running smoothly.

You’re absolutely right that up until macOS Tahoe, there was rarely a need to install a driver, as Virtual Com Port communication was handled natively by the system. Recently, though, we noticed more bug reports from Apple users whose Halo devices weren’t appearing, neither inside the app nor in the system list. After digging into Apple forums and Reddit, we discovered that Tahoe introduced some instability with these USB device connections. In some cases, users couldn’t even find their mouse or keyboard anymore.

There are a few ways to work around this, including changing Mac security settings, but we agree that approach can raise security concerns. The most reliable fix is making sure the Silicon Labs VCP driver is installed in its most recent version. This update also includes fixes for rare bugs that could cause Halo to disconnect while reading its installed programs list.

We currently include the installer as an optional item on the Halo DMG, but we noticed our FAQ instructions were often overlooked. While we could bundle the driver directly into the main installer, that wouldn’t help users who update via the internal installer.

We understand your concern about the security warning that appears when the app writes the installer to run it. Based on your feedback, we plan to add a “Don’t warn me again” checkbox. This way, the warning will typically appear only once, and users like yourself, whose devices are still accessible on Tahoe, can skip the forced installation. Just a gentle note: skipping the installation means using an outdated driver, which may lead to connectivity issues that a driver update would otherwise fix.

Thanks again for helping us improve! If you have any other questions or thoughts, we’re always here to listen.