Apple Silicon support status

[Kari Lempiäinen]

Hi,

I’ve started to get reminders when starting GoldenCheetah that it won't start in the next version of OSX. Are there any plans to support macOS 27?

Cheers,

Kari

[Ale Martinez]

El sábado, 25 de abril de 2026 a la(s) 7:48:27 a.m. UTC-3, kari.le...@summerday.net escribió:

Hi,

I’ve started to get reminders when starting GoldenCheetah that it won't start in the next version of OSX. Are there any plans to support macOS 27?

For the moment there is no plan, we have an open issue for this (https://github.com/GoldenCheetah/GoldenCheetah/issues/4682) and the limitation to build using Python 3.7 was removed but I don't know if anyone is actively working on this, the main issue seems to be code signing necessary to be able to run the generated binaries standalone. Contributions are welcome.

Currently it is possible to generate Apple Silicon binaries building from source as explained in https://github.com/GoldenCheetah/GoldenCheetah/blob/master/INSTALL-MAC

Cheers, Ale.

[Ale Martinez]

El sábado, 25 de abril de 2026 a la(s) 11:54:58 a.m. UTC-3, Ale Martinez escribió:

El sábado, 25 de abril de 2026 a la(s) 7:48:27 a.m. UTC-3, kari.le...@summerday.net escribió:

Hi,

I’ve started to get reminders when starting GoldenCheetah that it won't start in the next version of OSX. Are there any plans to support macOS 27?

For the moment there is no plan, we have an open issue for this (https://github.com/GoldenCheetah/GoldenCheetah/issues/4682) and the limitation to build using Python 3.7 was removed but I don't know if anyone is actively working on this, the main issue seems to be code signing necessary to be able to run the generated binaries standalone. Contributions are welcome.

Update: Nathan has made good progress on the issue above based on Magnus previous work modernizing macOS builds, there is a proof of concept ARM64 binary available there if anyone wants to collaborate with testing and provide feedback.

[Kari Lempiäinen]

Great! I managed to compile my own version but the provided ARM64 binary from the GitHub is working fine. I’d much rather use those than compiling my own version. Hopefully this will included in the normal way of distributing binaries, as well as with development builds.

Thanks! 

Kari

[Ale Martinez]

Hi Kari, thanks for testing!

Nathan work is merged and an Apple Silicon binary is included in latest snapshot builds: https://github.com/GoldenCheetah/GoldenCheetah/releases/tag/snapshot 

Cheers, Ale.

[Kari Lempiäinen]

Thank you Ale and Nathan!!

Cheers,

Kari

[Ale Martinez]

Apple Silicon (arm64) build now is complete including the secrets for Cloud Services access:  https://github.com/GoldenCheetah/GoldenCheetah/releases/tag/snapshot

Feedback is welcome.

Cheers, Ale.

[Kari Lempiäinen]

Opens fine, still need to allow app from Security settings on the first launch.

Cheers,

Kari

--
_______________________________________________
Golden-Cheetah-Users mailing list
golden-che...@googlegroups.com
http://groups.google.com/group/golden-cheetah-users?hl=en
---
You received this message because you are subscribed to the Google Groups "golden-cheetah-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to golden-cheetah-u...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/golden-cheetah-users/b6fed05b-d598-4ef5-9765-975b29f5d88dn%40googlegroups.com.

[Ale Martinez]

El miércoles, 27 de mayo de 2026 a la(s) 12:06:08 p.m. UTC-3, kari.le...@summerday.net escribió:

Opens fine, still need to allow app from Security settings on the first launch.

Yep, that is not likely to change any time soon:  https://github.com/GoldenCheetah/GoldenCheetah/wiki/Developer-cannot-be-verified-on-MacOS

[Chris Cleeland]

On Saturday, April 25, 2026 at 9:54:58 AM UTC-5 Ale Martinez wrote:

the main issue seems to be code signing necessary to be able to run the generated binaries standalone. Contributions are welcome.

Is "the code signing" issue something that has to be solved technically, or is it a process (money, ownership, etc.) problem?

My assumption is that this is a scenario where apple wants a developer to sign a binary using credentials obtained from apple, and that means that somebody must "own" (and probably pay for) those credentials, so the issue is mostly "process"?

[Ale Martinez]

It is not a technical issue but an economic/political decision, AFAIK.

[Chris Cleeland]

On May 28, 2026, at 10:13 AM, Ale Martinez <amtri...@gmail.com> wrote:

It is not a technical issue but an economic/political decision, AFAIK.

Are the issues captured anywhere concisely?

[Ale Martinez]

As I commented before, this is not an issue for me but a decision taken by the project owner documented in the wiki link I posted.

OTOH I think my english language is not good enough to state I couldn't care less about this "issue".

[Ale Martinez]

I mean, our Windows binaries are not signed either and users seem able to take their own decision without issues, why we would need to make an exception for macOS users? 

[Ale Martinez]

See https://groups.google.com/g/golden-cheetah-users/c/_n9-ebzpD3c/m/X6u-mIZGAgAJ

[Graham White]

I can confirm that the ARM build runs on my M1 Macbook Air running the latest release of OSX. It feels a snappier but that might be optimism bias.

My thanks to the developers who made this work.

Graham

On Friday, 29 May 2026 at 14:52:03 UTC+1 Ale Martinez wrote:

See https://groups.google.com/g/golden-cheetah-users/c/_n9-ebzpD3c/m/X6u-mIZGAgAJ

[Chris Cleeland]

> On May 29, 2026, at 3:01 PM, Graham White <gwhi...@gmail.com> wrote:
>
> I can confirm that the ARM build runs on my M1 Macbook Air running the latest release of OSX. It feels a snappier but that might be optimism bias.

I confirm that it’s definitely faster on my M4 running Tahoe 26.4.1 than running on my 2019 i9 on Ventura.

I’m getting a consistent crash on ARM during the auto-import of FIT files at startup. It’s after they’ve all been validated, and during the actual import action. The crash stack is related to drawing an overlay.

I’ll try to dig in over the weekend and, most importantly, compare to the same build running on intel macos to see if it’s an ARM issue. Hopefully I can isolate it to a particular FIT file.

[Graham White]

I don't use auto import on startup. If it helps to narrow things down, I've checked reading in files and syncing to a cloud service since my previous email. I didn't try a synch where a file would be imported.

I do a mixture of running, gym work and cycling. Running and gym is imported  from TCX file exported from Polar Flow and cycling from a FIT file exported from Hammerhead. Both worked fine. L/R power balance wasn't imported as usual but that's an issue with Hammerhead not sticking to the FIT standard as Ale has previously pointed out.