Apple could not verify the Software // TeamSpeak 6 MacOS missing Certificate

TeamSpeak 6 Client
, , , ,
1

When I try to open TS5, I get this:

“TeamSpeak.app” Not Opened
Apple could not verify “TeamSpeak.app” is free of malware that may harm your Mac or compromise your privacy.

Screenshot 2024-11-15 at 11.45.29 AM
Screenshot 2024-11-15 at 11.45.29 AM656×600 82.6 KB

Is there a signed version of TS5 client available?

PS: I’m on macOS Sequoia 15.1

2

Hello @corychu and welcome to the TeamSpeak Forum.

After you’ve tried to open the app, follow these steps:

  1. Open System Settings.
  2. Click Privacy & Security, scroll down, and click the Open Anyway button to confirm your intent to open or install the app.
    In System Settings, choose to open an app despite the security warning if you're certain the app is from a trustworthy source.
    In System Settings, choose to open an app despite the security warning if you're certain the app is from a trustworthy source.1430×1226 77.4 KB
  3. The warning prompt reappears and, if you’re absolutely sure that you want to open the app anyway, you can click Open.

The app is now saved as an exception to your security settings, and you can open it in the future by double-clicking it, just as you can any authorized app.

1 Like
3

I know how to bypass this. I just want to know why there is no signed version of the TS5 client while the TS3 client is properly signed.

4

No there is not a signed version.

1 Like
5

Hi, I found a “solution” for this Problem: run the following command in the Terminal:

xattr -rd com.apple.quarantine /path/to/TeamSpeak.app

The binary has (for some reason) the “com.apple.quarantine” Attribute attached to it. The Teamspeak Team has to fix this before packing the .dmg and then it will be fixed for all users (because the binary is already signed and valid).

FYI: For me the binary is located at /Applications/TeamSpeak.app.

6

Sometimes, it’s hard to understand the reasoning behind certain decisions, especially when they seem to focus on small details. As a fellow developer, I often wonder why certain issues are simply ignored. For example, signing a macOS application is essential for gaining user trust and encouraging adoption. While the notarization process may seem cumbersome, especially with Apple’s tight control, it is crucial for reaching non-technical Mac users. Without it, you risk driving them away.

Similarly, when it comes to ARM builds, I believe compiling your existing client codebase for ARM should be a relatively minor task—assuming there are no legacy dependencies that aren’t supported (which, ideally, would have already been addressed in the development of TS5). The effort required is small compared to the potential benefit of expanding your user base.

In many cases, it feels like a lot of decisions are driven by personal preferences or feelings within the team. While this approach has its merits, it might sometimes be more effective to adopt a pragmatic perspective, focusing on the bigger picture.

1 Like