Driver not installing - NEW issue - partly solved (MBP M1/CalDigit TS3+)

[kaz911]

I had the same issues as others where the DEXT extension would not install - and never got the "settings" opportunity to allow installation.

I tried EVERYTHING listed here - and nothing helped. DEXT did not get installed ( check in terminal with "systemextensionsctl list"

Well that is right until I unplugged my CalDigit TS3+ docking station while installing - then SUDDENLY the DEXT could be installed and I got the notification.

~ so now drivers are installed - but then on to another problem.

So if you have issues - check if you use CalDigit d*ck stations.. (interpret * as you want)

My SpaceMouse Wireless works PERFECT in Windows 10 on a ThinkPad! All functions work. USB "graphics" show up for the adaptor - and it shows SpaceMouse Wireless battery capacity etc.

But on my MBP M1 - it only acts like it is a normal mouse. The driver does NOT see it as a SpaceMouse Wireless. None of the demo's work. I can move mouse curser with tilt up down and sideways - and scroll with wheel turn left / right. But none of the SpaceMouse apps work.

In Settings/3DConnexion Tools tab - it says "No Device Found"

Is this a firmware issue?

/k
(Posting this to support as well - but someone might know the answer)

[kaz911]

Well got initially very fast responses from Support.

But turns out it is a know problem (As in SpaceMouse only works as a mouse and is not recognised by "Settings/3DConnexion / Tools tab"

I've sent crashlogs to 3DConnexion.

No idea about turn around time - but looks like other people in this forum have had same issue going back to January of '24. So it does not look great.

The process "3DconnexionHelper" is supposed to be running (check Activity Monitor - search for 3D if you have a lot of processes)

If it is NOT running - check the App "Console" on the Mac and go to Crash Reports. If you see crash reports from Process Name "3DconnexionHelper" - and it is NOT running in Activity Monitor - then you have the same issue.

Support said the problem is filed internally under "TS-511" - so if you have the same issue - point to TS-511 when you contact support.

/k

[AmroSalih]

Well got initially very fast responses from Support.

But turns out it is a know problem (As in SpaceMouse only works as a mouse and is not recognised by "Settings/3DConnexion / Tools tab"

I've sent crashlogs to 3DConnexion.

No idea about turn around time - but looks like other people in this forum have had same issue going back to January of '24. So it does not look great.

The process "3DconnexionHelper" is supposed to be running (check Activity Monitor - search for 3D if you have a lot of processes)

If it is NOT running - check the App "Console" on the Mac and go to Crash Reports. If you see crash reports from Process Name "3DconnexionHelper" - and it is NOT running in Activity Monitor - then you have the same issue.

Support said the problem is filed internally under "TS-511" - so if you have the same issue - point to TS-511 when you contact support.

/k

https://forum.3dconnexion.com/viewtopic ... 5&start=15

[kaz911]

As I have issues with 3DconnexionHelper "breaking down" here is a dump from terminal of what goes wrong. I have sent it to 3Dconnexion Support but they have not responded since (Sent July 5th 2024)

It is clear there is an issue between 3DconnexionHelper and the DEXT... "uncaught exception" + nil argument in NSCFString - should make finding the bug reasonably easy...

2024-07-05 18:30:49.606 3DconnexionHelper[3249:179815] -[TDxDEXTManager connectDEXT]
*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '*** -[__NSCFString rangeOfString:options:range:locale:]: nil argument'
*** First throw call stack:
(
0 CoreFoundation 0x0000000195ef72ec __exceptionPreprocess + 176
1 libobjc.A.dylib 0x00000001959de788 objc_exception_throw + 60
2 Foundation 0x0000000196f5fbf8 -[NSPathStore2 copy] + 0
3 Foundation 0x0000000196f7c3f8 -[NSString containsString:] + 56
4 3DconnexionHelper 0x00000001047d00b8 3DconnexionHelper + 82104
5 3DconnexionHelper 0x00000001047d08d0 3DconnexionHelper + 84176
6 3DconnexionHelper 0x00000001047d04c0 3DconnexionHelper + 83136
7 3DconnexionHelper 0x00000001047d8714 3DconnexionHelper + 116500
8 IOKit 0x00000001995a56a0 __IOHIDManagerDeviceApplier + 592
9 CoreFoundation 0x0000000195e48db4 __CFSetApplyFunction_block_invoke + 28
10 CoreFoundation 0x0000000195e48bd0 CFBasicHashApply + 148
11 CoreFoundation 0x0000000195e48b0c CFSetApplyFunction + 224
12 IOKit 0x00000001995a5a70 __IOHIDManagerInitialEnumCallback + 120
13 CoreFoundation 0x0000000195e824d8 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 28
14 CoreFoundation 0x0000000195e8246c __CFRunLoopDoSource0 + 176
15 CoreFoundation 0x0000000195e821dc __CFRunLoopDoSources0 + 244
16 CoreFoundation 0x0000000195e80dc8 __CFRunLoopRun + 828
17 CoreFoundation 0x0000000195e80434 CFRunLoopRunSpecific + 608
18 CoreFoundation 0x0000000195efe45c CFRunLoopRun + 64
19 3DconnexionHelper 0x00000001047c7800 3DconnexionHelper + 47104
20 Foundation 0x0000000196fadf80 __NSThread__start__ + 716
21 libsystem_pthread.dylib 0x0000000195da2f94 _pthread_start + 136
22 libsystem_pthread.dylib 0x0000000195d9dd34 thread_start + 8
)
libc++abi: terminating due to uncaught exception of type NSException
- consolezsh: abort

If anybody else has issues with 3DconnexionHelper dying (not visible in Activity Monitor) - then try the below to get better debug data.

1. Unplug your 3D Mouse..
2. open Activity Monitor - and kill the 3DconnexionHelper if it is running
3. Open MacOS "Terminal"
4. execute the command at the prompt "/Applications/3Dconnexion/3Dconnexionhelper.app/Contents/MacOS/3DconnexionHelper" [press enter]
5. Insert your 3D Mouse dongle or direct via USB
6. Watch for errors in the Terminal window like mine in the quote above.
7. Send errors / messages to 3Dconnexion support

[kaz911]

We now have gone from July 5 until August 5th with no resolution and no further responses from 3Dconnexion..

[cremin2]

Have you tried any specific troubleshooting steps beyond what you've shared, such as reinstalling the 3Dconnexion software or checking for macOS updates that might resolve compatibility issues with the 3DconnexionHelper?

[kaz911]

Have you tried any specific troubleshooting steps beyond what you've shared, such as reinstalling the 3Dconnexion software or checking for macOS updates that might resolve compatibility issues with the 3DconnexionHelper?

yes - all of them - complete driver removal and reinstall - remove security and reinstall etc. etc. I have spent a good 20 hours on it - nothing has solved the issue.

It IS a bug in their own SW interface between 2 of their components. But they just stopped responding when I documented it. (I'm have an electronics engineering background with about 40 years experience in PC HW/SW development all the way from CPM and PC Dos 2.0'ish to Win 11/Macos and Linux.

I have not had any response since. What causes the problem - is not visible unless you have access to the source code.

3DConnexionHelper calls the connectDEXT (extension) - and part of the call the DEXT is called with a parameter which the DEXT function does not understand. BOTH parts are "3DConnexion" controlled software. The result is the DEXT submits an "Exception" (kind of a big stop sign) - the exception is not caught (like a good developer would do) by 3DConnexionHelper - so 3DConnexionHelper breaks down due to the unhandled exception.

If the software was well written - it would have a function to catch an exception and as a MINIMUM log what happened - and then shut down the process gracefully. Then you would have an extended debug log to send to the developers including the part of the "offending" data the processes are trying to send each-other.

The way the current ConnexionHelper handles it - is by saying "f*u - i'm out of here" and just "terminate / die".

A good sign of careless/badly developed software - is a lack of exception (error) handling. When-ever you meed an "Exception" error - you know the SW developer took a shortcut - and assumed no errors would ever pop up in a call to that function.

I have 4 "on mac" unusable 3DConnexion products now - 2 x SpaceMouse wireless and 1x SpaceMouse Enterprise and 1x SpaceMouse Pro. They all work fine on Windows - just not on MacOS - now including MacOS Sequoia V15 - and 3DConnexion does not care.

[AmroSalih]

If your system blocks the system extension of 3Dconnexion you might want to temporarily disable the security integrity policies. I'm interested in which exact steps have been taken from your side to reinstall the 3DxWare driver on macOS 15.

We documented the issues such as a settings error prompt in 3Dconnexion prefPane internally for our development in report TS-468. Other customers contacted the 3Dconnexion Technical Support. Our developers reviewed this issue. I'm happy that you shared your feedback in the forum, but in my opinion 3Dconnexion does care. The affected clients confirmed the solution that our developers suggested.
Further, the description for this thread is related to 3DxWare not installing:

1. Has the 3DxWare driver installation finished or was there an issue?
a. Is there an issue with "3DconnexionHelper' after the installation?

2. For macOS 15 Are you able to reproduce the issue after activating “3DconnexionHelper"?
a. Open macOS System Settings > “General” > “Login Items & Extensions”.
b. Click on “Driver Extensions com.3Dconnexion.dext”.
c. Activate “3DconnexionHelper” .
d. Verify the change by entering the password of your macOS account.
e. Click on “Done” to apply changes.

I strongly recommend to get in touch with our Technical Support Team if you haven't already done so. Please visit https://3dconnexion.com/support/