Mac VESC Tool Crashes upon BLE Connect

[gamer736413]

On Mac, I'm having a new issue I didn't have before. When I scan BLE and select a device to connect to, VESC tool crashes. I have tried this on multiple devices that previously I could connect to fine for the past 1-2 years.

I did try to uninstall and reinstall the latest build, but no change.

MacBook Air M1 / Sonoma 14.3 (23D56)

[blundey]

Also having the same issue on a macbook pro m2. Latest mac tool crashes upon BLE connect. It shows the device fine.

Produces a signal 11 crash and mentions about a out of bounds address on the stack. So its a propper crash.

[yoodog]

Version 6.05 stable for MACOS intel version - MacBook Pro 2019 i9, Also crashes every time after you select your BT VESC as soon as you press "connect" button... Has been doing it even on 6.02 VESC tool

I have even installed it on COMPLETELY fresh, as new, MacBook Pro i9 2019 (another one with similar specs) - same behaviour.

Windows VESC tool, if I switch to windows 10, connects via BT no issue.

Looks like MAC version has some bug that escaped DEVs

[yoodog]

Can we please have it addressed? iPhone app connect perfectly fine

[TheZeroBeast]

This is also happening for my MacBook Pro M3 2023. Is there anyone progress on this?

[mwinterm]

I can confirm the same behavior as well on a MacBook M1.

[etalot]

Same issue, I have two Macbook Air M1(actually three, but tried on two).

`
Translated Report (Full Report Below)

Process: VESC Tool [1080]
Path: /Volumes/*/VESC Tool.app/Contents/MacOS/VESC Tool
Identifier: com.vesc.vesc-tool-3.01
Version: ???
Code Type: X86-64 (Translated)
Parent Process: launchd [1]
User ID: 501

Date/Time: 2025-09-18 22:13:14.5262 +0700
OS Version: macOS 13.7 (22H123)
Report Version: 12
Anonymous UUID: DC5B8CD1-~~~~~~-4859-3EB2-~~~~~~~~~~~~

Time Awake Since Boot: 440 seconds

System Integrity Protection: enabled

Crashed Thread: 3 Dispatch queue: com.apple.bluetooth.iobluetooth.coordinatorQueue

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x000000000000080b
Exception Codes: 0x0000000000000001, 0x000000000000080b

Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11
Terminating Process: exc handler [1080]

VM Region Info: 0x80b is not in any region. Bytes before following region: 140722811336693
REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL
UNUSED SPACE AT START
--->
mapped file 7ffc952e8000-7ffca8880000 [309.6M] r-x/r-x SM=COW ...t_id=d3efa6e1

Thread 0:: Dispatch queue: com.apple.main-thread`

The issue is mass and old:

https://vesc-project.com/node/4006
https://vesc-project.com/node/4822
https://pev.dev/t/vesc-tool-on-mac-keeps-crashing-on-bluetooth-connect/669

F**K x86, Apple silicon(ARM) is great!

I definitely will not buy paid versions of Vesc Tool till this bug exist. Please fix.