tdesktop build v6.7.6 could not start as damaged on macOS 26.4.1, M2 Max

[iamwavecut]

Steps to reproduce

1. Download mac build from releases tab
2. Unpack
3. Drag & drop into Applications
4. Launch and accept unknown source warning

Expected behaviour

I expect it to start and work as normally as it did after the previous updates for along time.

Actual behaviour

Operating system

macOS 26.4.1

Version of Telegram Desktop

6.7.6

Installation source

Static binary from official website

Crash ID

No response

Logs

[23rd]

Hello.
Can you tell me is this your first time you are using (installing) Forkgram?

[iamwavecut]

Hello. Can you tell me is this your first time you are using (installing) Forkgram?

No, I have it installed, and right now I have a copy of functioning version 6.6.2, but the new one is coming with new bundle name so it looks like a separate app.

[23rd]

but the new one is coming with new bundle name so it looks like a separate app.

Yes, it really is.
Recently I had renamed it. To be honest it always was inconvinient to have a conflict with "Telegram.app" as Forkgram, "Telegram.app" as Telegram C++ and "Telegram.app" as Telegram Swift.

So, I made a decision to change the name of my fork to proper "Forkgram.app".

What about the "damaged" message — unfortunately I have no resources to sign my app with the Apple Developer certificate, so yeah, macOS will always warn you on each new version of Forkgram, sorry.

[iamwavecut]

No, it's not about the signature or something. It just doesn't start at all. Like, the app binary is corrupted. There is no option to override this behavior. Recent 6.7.7 release affected, too.