Deeplink on MacOS results in a crash when the application is not opened

AppInfo: 6.0.0-beta2 (1737468425)
OS Info: macOS 15.6
Device Info: MacBook Pro, 13-inch, M1, 2020
–––––––––––––––––––––––––––––––––––––––

Application crashes when i trying to open it with teamspeak:// scheme.
ex.: teamspeak://ts.myserver.ru

  • If the application is closed, it crashes when opening the scheme
  • If the application is already running, it opens the server from the link
Crash log
-------------------------------------
Translated Report (Full Report Below)
-------------------------------------
Process:             TeamSpeak [98560]
Path:                /Applications/TeamSpeak.app/Contents/MacOS/TeamSpeak
Identifier:          com.teamspeak.5.client
Version:             1.0 (1)
Code Type:           ARM-64 (Native)
Role:                Background
Parent Process:      launchd [1]
Coalition:           com.teamspeak.5.client [26854]
User ID:             501

Date/Time:           2025-10-20 09:51:37.5682 +0400
Launch Time:         2025-10-20 09:51:36.4554 +0400
Hardware Model:      MacBookPro17,1
OS Version:          macOS 26.0.1 (25A362)
Release Type:        User

Crash Reporter Key:  CAFF9BC3-0260-4901-0D9C-6A0E48848E93
Incident Identifier: 7D4184C7-40E2-4B8F-B572-32534A1CE23D

Sleep/Wake UUID:       1E436A28-CF5F-45FD-806D-AB7892F9FAEB

Time Awake Since Boot: 280000 seconds
Time Since Wake:       5731 seconds

System Integrity Protection: enabled

Triggered by Thread: 0  CrBrowserMain

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

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


VM Region Info: 0 is not in any region.  Bytes before following region: 4344692736
      REGION TYPE                    START - END         [ VSIZE] PRT/MAX SHRMOD  REGION DETAIL
      UNUSED SPACE AT START
--->  
      __TEXT                      102f6c000-10507c000    [ 33.1M] r-x/r-x SM=COW  /Applications/TeamSpeak.app/Contents/MacOS/TeamSpeak

Thread 0 Crashed:: CrBrowserMain
0   TeamSpeak                     	       0x1034c2f04 0x102f6c000 + 5598980
1   TeamSpeak                     	       0x1034c2e48 0x102f6c000 + 5598792
2   TeamSpeak                     	       0x1036aa9bc 0x102f6c000 + 7596476
3   Foundation                    	       0x18a2582d4 -[NSAppleEventManager dispatchRawAppleEvent:withRawReply:handlerRefCon:] + 316
4   Foundation                    	       0x18992a638 _NSAppleEventManagerGenericHandler + 80
5   AE                            	       0x1902f3108 0x1902e8000 + 45320
6   AE                            	       0x1902f2a3c 0x1902e8000 + 43580
7   AE                            	       0x1902ec0e8 aeProcessAppleEvent + 484
8   HIToolbox                     	       0x194a7c7b8 AEProcessAppleEvent + 68
9   AppKit                        	       0x18c5191a0 _DPSNextEvent + 1296
10  AppKit                        	       0x18cf6b958 -[NSApplication(NSEventRouting) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 688
11  AppKit                        	       0x18cf6b664 -[NSApplication(NSEventRouting) nextEventMatchingMask:untilDate:inMode:dequeue:] + 72
12  AppKit                        	       0x18c511720 -[NSApplication run] + 368
13  Chromium Embedded Framework   	       0x1715f179c ChromeWebAppShortcutCopierMain + 5355908
14  Chromium Embedded Framework   	       0x1715efa18 ChromeWebAppShortcutCopierMain + 5348352
15  Chromium Embedded Framework   	       0x1715a4858 ChromeWebAppShortcutCopierMain + 5040704
16  Chromium Embedded Framework   	       0x171567048 ChromeWebAppShortcutCopierMain + 4788784
17  Chromium Embedded Framework   	       0x16d7295e4 temporal_rs_Duration_hours + 114396
18  TeamSpeak                     	       0x102f78808 0x102f6c000 + 51208
19  TeamSpeak                     	       0x1036ab734 0x102f6c000 + 7599924
20  dyld                          	       0x187ccdd54 start + 7184

Thanks for reporting this crash.

I will forward this issue to our QA / Dev Team to further investigate.

2 Likes