macOS 5.1.0 build not available on FOSSHUB #16949

https://www.qbittorrent.org/news#sun-apr-27th-2025---qbittorrent-v5.1.0-release

Author

Owner

@xavier2k6 commented on GitHub (Jun 12, 2025):

There nearly has always been some delay in providing macOS builds, it's expected at this stage.........(not well supported & even a few of us @qbittorrent/bug-handlers have suggested to stop releasing builds for macOS.)

macOS builds will be available on a later date.

NOTICE: macOS builds will be available later.

https://www.qbittorrent.org/news#tue-dec-17th-2024---qbittorrent-v5.0.3-and-v5.1.0beta1-releases

The macOS version is not well supported, because we don't have active macOS developers/contributors. The project is in need of macOS developers.

https://www.qbittorrent.org/news#tuesday-aug-30th-2022---qbittorrent-v4.4.5-release
https://www.qbittorrent.org/news#monday-aug-22nd-2022---qbittorrent-v4.4.4-release

MACOS: Builds will take a few days to be uploaded.

https://www.qbittorrent.org/news#tuesday-february-15th-2022---qbittorrent-v4.4.1-release

MACOS: Builds will be uploaded in the next days.

https://www.qbittorrent.org/news#thursday-january-06th-2022---qbittorrent-v4.4.0-release

The macOS build will follow.

https://www.qbittorrent.org/news#thursday-november-21st-2019---qbittorrent-v4.2.0rc_20191121_9c1617b9778-release

The macOS builds will follow in a couple of days.

https://www.qbittorrent.org/news#monday-november-19th-2018---qbittorrent-v4.1.4-release

macOS builds will follow.

https://www.qbittorrent.org/news#friday-december-1st-2017---qbittorrent-v4.0.2-release

macOS packages might follow.

https://www.qbittorrent.org/news#monday-august-7th-2017---qbittorrent-v3.4.0beta_20170807_0320f9d5b5e-release

@xavier2k6 commented on GitHub (Jun 12, 2025): There nearly has always been some delay in providing macOS builds, it's expected at this stage.........(not well supported & even a few of us @qbittorrent/bug-handlers have suggested to stop releasing builds for macOS.) ____ >macOS builds will be available on a later date. https://www.qbittorrent.org/news#sun-apr-27th-2025---qbittorrent-v5.1.0-release >NOTICE: macOS builds will be available later. https://www.qbittorrent.org/news#tue-dec-17th-2024---qbittorrent-v5.0.3-and-v5.1.0beta1-releases >The macOS version is not well supported, because we don't have active macOS developers/contributors. The project is in need of macOS developers. https://www.qbittorrent.org/news#tuesday-aug-30th-2022---qbittorrent-v4.4.5-release https://www.qbittorrent.org/news#monday-aug-22nd-2022---qbittorrent-v4.4.4-release >MACOS: Builds will take a few days to be uploaded. https://www.qbittorrent.org/news#tuesday-february-15th-2022---qbittorrent-v4.4.1-release >MACOS: Builds will be uploaded in the next days. https://www.qbittorrent.org/news#thursday-january-06th-2022---qbittorrent-v4.4.0-release >The macOS build will follow. https://www.qbittorrent.org/news#thursday-november-21st-2019---qbittorrent-v4.2.0rc_20191121_9c1617b9778-release >The macOS builds will follow in a couple of days. https://www.qbittorrent.org/news#monday-november-19th-2018---qbittorrent-v4.1.4-release >macOS builds will follow. https://www.qbittorrent.org/news#friday-december-1st-2017---qbittorrent-v4.0.2-release >macOS packages might follow. https://www.qbittorrent.org/news#monday-august-7th-2017---qbittorrent-v3.4.0beta_20170807_0320f9d5b5e-release

deekerman commented

Author

Owner

@Piccirello commented on GitHub (Jun 12, 2025):

I didn't realize this. What's the cause of the delay?

@Piccirello commented on GitHub (Jun 12, 2025): I didn't realize this. What's the cause of the delay?

deekerman commented

Author

Owner

@xavier2k6 commented on GitHub (Jun 12, 2025):

What's the cause of the delay?

You'd have to ask our maintainer....it may be to do with Xcode/Signing, time constraints or they may have been waiting for Qt 6.9.1 to be released, which it since has.......

Not sure what physical mac or indeed macOS Version/Xcode maintainer has access to.

@xavier2k6 commented on GitHub (Jun 12, 2025): >What's the cause of the delay? You'd have to ask our maintainer....it may be to do with Xcode/Signing, time constraints or they may have been waiting for Qt 6.9.1 to be released, which it since has....... Not sure what physical mac or indeed macOS Version/Xcode maintainer has access to.

deekerman commented

Author

Owner

@Piccirello commented on GitHub (Jun 12, 2025):

macOS builds aren't notarized, so I don't believe the delay is from that. GitHub also has macOS runners that we can use for these builds. I personally would love to see all binaries moved to GitHub.

Is the maintainer in this case @sledgehammer999?

@Piccirello commented on GitHub (Jun 12, 2025): macOS builds aren't notarized, so I don't believe the delay is from that. GitHub also has macOS runners that we can use for these builds. I personally would love to see all binaries [moved to GitHub](https://github.com/qbittorrent/qBittorrent/discussions/21345). Is the maintainer in this case @sledgehammer999?

deekerman commented

Author

Owner

@xavier2k6 commented on GitHub (Jun 12, 2025):

Is the maintainer in this case @sledgehammer999?

Yes

@xavier2k6 commented on GitHub (Jun 12, 2025): > Is the maintainer in this case [@sledgehammer999](https://github.com/sledgehammer999)? Yes

deekerman commented

Author

Owner

@Piccirello commented on GitHub (Jun 12, 2025):

@sledgehammer999 can be difficult to get a hold of. Perhaps @glassez or @Chocobo1 have more context?

@Piccirello commented on GitHub (Jun 12, 2025): @sledgehammer999 can be difficult to get a hold of. Perhaps @glassez or @Chocobo1 have more context?

deekerman commented

Author

Owner

@glassez commented on GitHub (Jun 13, 2025):

@sledgehammer999 can be difficult to get a hold of. Perhaps @glassez or @Chocobo1 have more context?

What kind of context are you interested in?

@sledgehammer999 is often unavailable (through any communication channels).
In recent years, @sledgehammer999 has been repeatedly offered to automate the production of release builds (e.g., transfer them to GitHub), but he has always rejected this.

@glassez commented on GitHub (Jun 13, 2025): > [@sledgehammer999](https://github.com/sledgehammer999) can be difficult to get a hold of. Perhaps [@glassez](https://github.com/glassez) or [@Chocobo1](https://github.com/Chocobo1) have more context? What kind of context are you interested in? 1. @sledgehammer999 is often unavailable (through any communication channels). 2. In recent years, @sledgehammer999 has been repeatedly offered to automate the production of release builds (e.g., transfer them to GitHub), but he has always rejected this.

deekerman commented

Author

Owner

@Piccirello commented on GitHub (Jun 13, 2025):

That's exactly the context I was looking for.

Performing production builds locally, in 2025, is a bit surprising. Has there been a reason stated for why builds are still done this way? (Asking in case @sledgehammer999 has previously mentioned it, but of course would be great to hear from him directly)

Building out the infrastructure/GitHub Actions for these builds is surely something many people would be happy to volunteer their time doing. It would also more easily enable notarized builds on macOS (relevant).

@Piccirello commented on GitHub (Jun 13, 2025): That's exactly the context I was looking for. Performing production builds locally, in 2025, is a bit surprising. Has there been a reason stated for why builds are still done this way? (Asking in case @sledgehammer999 has previously mentioned it, but of course would be great to hear from him directly) Building out the infrastructure/GitHub Actions for these builds is surely something many people would be happy to volunteer their time doing. It would also more easily enable notarized builds on macOS ([relevant](https://github.com/qbittorrent/qBittorrent/issues/21683#issuecomment-2452440189)).

deekerman commented

https://github.com/neysofu/awesome-github-actions-runners

Author

Owner

@userdocs commented on GitHub (Jun 13, 2025):

Maybe they have access to better/faster systems locally, compared to default runners, so i'm going to drop this link here since you can get access to decent third party runners pretty affordably.

@userdocs commented on GitHub (Jun 13, 2025): Maybe they have access to better/faster systems locally, compared to default runners, so i'm going to drop this link here since you can get access to decent third party runners pretty affordably. https://github.com/neysofu/awesome-github-actions-runners

deekerman commented

Author

Owner

@Piccirello commented on GitHub (Jun 13, 2025):

Releases are performed, on average, ~once per month, so speed isn't a major concern.

@Piccirello commented on GitHub (Jun 13, 2025): Releases are performed, on average, ~once per month, so speed isn't a major concern.

deekerman commented

Author

Owner

@glassez commented on GitHub (Jun 15, 2025):

would be great to hear from him directly

So let him answer. Perhaps this will encourage him to think about it again.

@glassez commented on GitHub (Jun 15, 2025): > would be great to hear from him directly So let him answer. Perhaps this will encourage him to think about it again.

deekerman commented

https://www.qbittorrent.org/news

Author

Owner

@userdocs commented on GitHub (Jun 22, 2025):

Builds are currently available only from old trusty SourceForge. FossHub either locked the account or has login issues. Time will tell.

ok.

@userdocs commented on GitHub (Jun 22, 2025): https://www.qbittorrent.org/news > Builds are currently available only from old trusty SourceForge. FossHub either locked the account or has login issues. Time will tell. ok.

deekerman commented

Author

Owner

@xavier2k6 commented on GitHub (Jun 23, 2025):

Builds are currently available only from old trusty SourceForge. FossHub either locked the account or has login issues. Time will tell.

This affects the "check for updates" as 5.1.0 will only be offered to users who are using lower versions & those already on 5.1.0 will be informed they're running the latest due to us only relying on FossHub's feed via "check for updates", a backup to alternative/failover feed e.g. -> sourceforge needs to be looked at too.

@xavier2k6 commented on GitHub (Jun 23, 2025): >Builds are currently available only from old trusty SourceForge. FossHub either locked the account or has login issues. Time will tell. This affects the "check for updates" as 5.1.0 will only be offered to users who are using lower versions & those already on 5.1.0 will be informed they're running the latest due to us only relying on FossHub's feed via "check for updates", a backup to alternative/failover feed e.g. -> sourceforge needs to be looked at too.

deekerman commented

Author

Owner

@userdocs commented on GitHub (Jun 23, 2025):

I assume the sourceforge releases are built offline and uploaded to a release, manually.

Could have just done the same thing with a Github release as it seems to require the same effort to create a release.

@userdocs commented on GitHub (Jun 23, 2025): I assume the sourceforge releases are built offline and uploaded to a release, manually. Could have just done the same thing with a Github release as it seems to require the same effort to create a release.

deekerman commented

Author

Owner

@sledgehammer999 commented on GitHub (Jul 2, 2025):

Just a heads up.
The following days I'll be focusing on making changes for the release files now that FossHub is essentially gone.
So I'll handle this issue too.

@sledgehammer999 commented on GitHub (Jul 2, 2025): Just a heads up. The following days I'll be focusing on making changes for the release files now that FossHub is essentially gone. So I'll handle this issue too.

deekerman commented

Author

Owner

@Piccirello commented on GitHub (Jul 2, 2025):

@sledgehammer999 any chance we can get releases hosted on GitHub?

@Piccirello commented on GitHub (Jul 2, 2025): @sledgehammer999 any chance we can get releases hosted on GitHub?

deekerman commented

Author

Owner

@gerardp commented on GitHub (Aug 22, 2025):

Any updates on this matter?

@gerardp commented on GitHub (Aug 22, 2025): Any updates on this matter?

deekerman commented

Author

Owner

@fff7d1bc commented on GitHub (Sep 22, 2025):

Looks like the qbittorrent was marked as deprecated in homebrew and will be removed later in 2026 out of tree due to lack of updates. I found https://github.com/qbittorrent/qBittorrent/wiki/Compilation-macOS-(x86_64,-arm64,-cross-compilation) and will see if I can build it locally.

@fff7d1bc commented on GitHub (Sep 22, 2025): Looks like the qbittorrent was marked as deprecated in homebrew and will be removed later in 2026 out of tree due to lack of updates. I found https://github.com/qbittorrent/qBittorrent/wiki/Compilation-macOS-(x86_64,-arm64,-cross-compilation) and will see if I can build it locally.

deekerman commented

https://formulae.brew.sh/cask/qbittorrent#default

Author

Owner

@xavier2k6 commented on GitHub (Oct 5, 2025):

Looks like the qbittorrent was marked as deprecated in homebrew and will be removed later in 2026 out of tree due to lack of updates.

Yep!

qbittorrent (deprecated)
Disable date: 2026-09-01

qbittorrent@lt20 (deprecated)
Disable date: 2026-09-01

https://formulae.brew.sh/cask/qbittorrent@lt20

@xavier2k6 commented on GitHub (Oct 5, 2025): >Looks like the qbittorrent was marked as deprecated in homebrew and will be removed later in 2026 out of tree due to lack of updates. Yep! ____ >qbittorrent (deprecated) >Disable date: 2026-09-01 https://formulae.brew.sh/cask/qbittorrent#default ____ >qbittorrent@lt20 (deprecated) >Disable date: 2026-09-01 https://formulae.brew.sh/cask/qbittorrent@lt20

deekerman commented

Author

Owner

@fff7d1bc commented on GitHub (Oct 5, 2025):

I tried to build it but it now depends on qt6 that gave me some troubles, also the build systems of libtorrent and qt seems to actually hardcode /opt/homebrew so I had to rename this directiory for the duration of building to get it to even link against the openssl and libtorrent I installed into prefix and not the system one. Hope someone more up to the speed with building it will step up and at least update the building instruction, especially that for example openssl needs to be of 3.x.x line and there you need to build it with deprecated interfaces otherwise libtorrent-2.x.x fails to build, while the instruction actually tells you to disable deprecated interfaces, which surely was the case with 1.1.1 but not with 3.x.x.

@fff7d1bc commented on GitHub (Oct 5, 2025): I tried to build it but it now depends on qt6 that gave me some troubles, also the build systems of libtorrent and qt seems to actually hardcode `/opt/homebrew` so I had to rename this directiory for the duration of building to get it to even link against the openssl and libtorrent I installed into prefix and not the system one. Hope someone more up to the speed with building it will step up and at least update the building instruction, especially that for example openssl needs to be of 3.x.x line and there you need to build it with deprecated interfaces otherwise libtorrent-2.x.x fails to build, while the instruction actually tells you to disable deprecated interfaces, which surely was the case with 1.1.1 but not with 3.x.x.

deekerman commented

Author

Owner

@fff7d1bc commented on GitHub (Nov 2, 2025):

Successfuly made a MacOS build of qbt 5.1.2 on MacOS Tahoe 26.0.1 using a script made by another user, updated it a bit to make it work. You can find gist under https://gist.github.com/fff7d1bc/223881d03d33cd2b176f0695eaa7fe8e

I can try to make it a github action, then the qbittorrent team could ad-hoc run it to get a build if you'd use it.

@fff7d1bc commented on GitHub (Nov 2, 2025): Successfuly made a MacOS build of qbt 5.1.2 on MacOS Tahoe 26.0.1 using a script made by another user, updated it a bit to make it work. You can find gist under https://gist.github.com/fff7d1bc/223881d03d33cd2b176f0695eaa7fe8e I can try to make it a github action, then the qbittorrent team could ad-hoc run it to get a build if you'd use it.

deekerman commented

Author

Owner

@fff7d1bc commented on GitHub (Nov 2, 2025):

I just noticed that qbittorrent actually does have CI for macos builds -- https://github.com/qbittorrent/qBittorrent/actions/workflows/ci_macos.yaml

Makes me wonder if there's any need for me to work on it. @Chocobo1 I noticed you are active in the commits to ci_macos workflows. Can you comment on whatever the release tags could also be made into release packages for MacOS?

@fff7d1bc commented on GitHub (Nov 2, 2025): I just noticed that qbittorrent actually does have CI for macos builds -- https://github.com/qbittorrent/qBittorrent/actions/workflows/ci_macos.yaml Makes me wonder if there's any need for me to work on it. @Chocobo1 I noticed you are active in the commits to ci_macos workflows. Can you comment on whatever the release tags could also be made into release packages for MacOS?

deekerman commented

Author

Owner

@Ryu481 commented on GitHub (Nov 13, 2025):

Any update on this? Version 5.1.3 also didn't got released for macos.

@Ryu481 commented on GitHub (Nov 13, 2025): Any update on this? Version 5.1.3 also didn't got released for macos.

deekerman commented

Author

Owner

@xavier2k6 commented on GitHub (Nov 14, 2025):

master Build below from Tahoe runner:
https://github.com/qbittorrent/qBittorrent/discussions/23288#discussioncomment-14967272

@xavier2k6 commented on GitHub (Nov 14, 2025): `master` Build below from Tahoe runner: https://github.com/qbittorrent/qBittorrent/discussions/23288#discussioncomment-14967272

deekerman commented

Author

Owner

@xavier2k6 commented on GitHub (Nov 14, 2025):

@Ryu481 You may be interested in the workflow from https://github.com/xavier2k6/qBittorrent/actions/runs/19349464381

"macos-14", "macos-15", "macos-15-intel", "macos-26" runners being used with latest stable version(s) of Xcode.

@xavier2k6 commented on GitHub (Nov 14, 2025): @Ryu481 You may be interested in the workflow from https://github.com/xavier2k6/qBittorrent/actions/runs/19349464381 `"macos-14", "macos-15", "macos-15-intel", "macos-26"` runners being used with latest stable version(s) of `Xcode`.

deekerman commented

Author

Owner

@fff7d1bc commented on GitHub (Nov 14, 2025):

I've updated gist at https://gist.github.com/fff7d1bc/223881d03d33cd2b176f0695eaa7fe8e to 5.1.3 and uploaded qBittorrent-release-5.1.3-macOS-arm64.dmg build for ARM64 based MacOS there in comments. If for whatever reason you cannot build it yourself, try this artifact, works for me.

@fff7d1bc commented on GitHub (Nov 14, 2025): I've updated gist at https://gist.github.com/fff7d1bc/223881d03d33cd2b176f0695eaa7fe8e to 5.1.3 and uploaded `qBittorrent-release-5.1.3-macOS-arm64.dmg` build for ARM64 based MacOS there in comments. If for whatever reason you cannot build it yourself, try this artifact, works for me. <img width="817" height="524" alt="Image" src="https://github.com/user-attachments/assets/81440152-efa8-49fb-be8c-c86246d2cf37" />

deekerman commented

Author

Owner

@Ryu481 commented on GitHub (Nov 14, 2025):

I wasn't able to build 5.1.3 with libtorrent 1.2.20 on Tahoe. This is also the case in the github workflows so compiling with libtorrent 1.2.20 seems to not work on Tahoe. However I could build it with libtorrent 1.2.20 on Sequoia and this build also works on Tahoe. Building it with libtorrent 2 works fine on Tahoe. Is libtorrent 1 going to fade out or will it get updated to work on Tahoe? Also I would like to know why there a no official builds available, is there any problem with qBittorrent 5.1.x on mac so the builds don't get released?

@Ryu481 commented on GitHub (Nov 14, 2025): I wasn't able to build 5.1.3 with libtorrent 1.2.20 on Tahoe. This is also the case in the github workflows so compiling with libtorrent 1.2.20 seems to not work on Tahoe. However I could build it with libtorrent 1.2.20 on Sequoia and this build also works on Tahoe. Building it with libtorrent 2 works fine on Tahoe. Is libtorrent 1 going to fade out or will it get updated to work on Tahoe? Also I would like to know why there a no official builds available, is there any problem with qBittorrent 5.1.x on mac so the builds don't get released?

deekerman commented

Author

Owner

@grr commented on GitHub (Nov 14, 2025):

I've updated gist at https://gist.github.com/fff7d1bc/223881d03d33cd2b176f0695eaa7fe8e to 5.1.3 and uploaded qBittorrent-release-5.1.3-macOS-arm64.dmg build for ARM64 based MacOS there in comments. If for whatever reason you cannot build it yourself, try this artifact, works for me.

Note, this build requires minimum macOS version of 13.0, whereas latest official build requires only macOS 11.0.

@grr commented on GitHub (Nov 14, 2025): > I've updated gist at https://gist.github.com/fff7d1bc/223881d03d33cd2b176f0695eaa7fe8e to 5.1.3 and uploaded `qBittorrent-release-5.1.3-macOS-arm64.dmg` build for ARM64 based MacOS there in comments. If for whatever reason you cannot build it yourself, try this artifact, works for me. Note, this build requires minimum macOS version of 13.0, whereas latest official build requires only macOS 11.0.

deekerman commented

Author

Owner

@xavier2k6 commented on GitHub (Nov 14, 2025):

I've updated gist at https://gist.github.com/fff7d1bc/223881d03d33cd2b176f0695eaa7fe8e to 5.1.3 and uploaded qBittorrent-release-5.1.3-macOS-arm64.dmg build for ARM64 based MacOS there in comments. If for whatever reason you cannot build it yourself, try this artifact, works for me.

Note, this build requires minimum macOS version of 13.0, whereas latest official build requires only macOS 11.0.

This is because Qt 6.10.x (used in that build) is only supported on macOS 13+ & is set at min target of 13.

https://doc.qt.io/qt-6/supported-platforms.html#macos

Qt 6.9.x supports macOS 12+

https://doc.qt.io/qt-6.9/supported-platforms.html#macos

The last official build of 5.0.5 used Qt 6.7.x which supports macOS11+

https://doc.qt.io/archives/qt-6.7/supported-platforms.html#macos

@xavier2k6 commented on GitHub (Nov 14, 2025): > > I've updated gist at https://gist.github.com/fff7d1bc/223881d03d33cd2b176f0695eaa7fe8e to 5.1.3 and uploaded `qBittorrent-release-5.1.3-macOS-arm64.dmg` build for ARM64 based MacOS there in comments. If for whatever reason you cannot build it yourself, try this artifact, works for me. > > Note, this build requires minimum macOS version of 13.0, whereas latest official build requires only macOS 11.0. This is because Qt 6.10.x (used in that build) is only supported on macOS 13+ & is set at min target of 13. * https://doc.qt.io/qt-6/supported-platforms.html#macos Qt 6.9.x supports macOS 12+ * https://doc.qt.io/qt-6.9/supported-platforms.html#macos The last official build of 5.0.5 used Qt 6.7.x which supports macOS11+ * https://doc.qt.io/archives/qt-6.7/supported-platforms.html#macos

deekerman commented

Author

Owner

@Zulith commented on GitHub (Nov 14, 2025):

Thank you very much for the 5.1.3 build for macos 13+. It would be nice to get an official release for those who don't dig through github issue discussions. I hope we can get there!

@Zulith commented on GitHub (Nov 14, 2025): Thank you very much for the 5.1.3 build for macos 13+. It would be nice to get an official release for those who don't dig through github issue discussions. I hope we can get there!

deekerman commented

Author

Owner

@xavier2k6 commented on GitHub (Dec 22, 2025):

@sledgehammer999 Can you provide an update on the status of a 5.1.x "official" release?

@xavier2k6 commented on GitHub (Dec 22, 2025): @sledgehammer999 Can you provide an update on the status of a 5.1.x "official" release?

deekerman commented

Author

Owner

@iyanucodes commented on GitHub (Dec 22, 2025):

I've updated gist at https://gist.github.com/fff7d1bc/223881d03d33cd2b176f0695eaa7fe8e to 5.1.3 and uploaded qBittorrent-release-5.1.3-macOS-arm64.dmg build for ARM64 based MacOS there in comments. If for whatever reason you cannot build it yourself, try this artifact, works for me.

seems the gofile link is down

@iyanucodes commented on GitHub (Dec 22, 2025): > I've updated gist at https://gist.github.com/fff7d1bc/223881d03d33cd2b176f0695eaa7fe8e to 5.1.3 and uploaded `qBittorrent-release-5.1.3-macOS-arm64.dmg` build for ARM64 based MacOS there in comments. If for whatever reason you cannot build it yourself, try this artifact, works for me. > > <img alt="Image" width="817" height="524" src="https://private-user-images.githubusercontent.com/180211/514369508-81440152-efa8-49fb-be8c-c86246d2cf37.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NjY0MzIxODIsIm5iZiI6MTc2NjQzMTg4MiwicGF0aCI6Ii8xODAyMTEvNTE0MzY5NTA4LTgxNDQwMTUyLWVmYTgtNDlmYi1iZThjLWM4NjI0NmQyY2YzNy5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjUxMjIyJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI1MTIyMlQxOTMxMjJaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT0zODEyNTExNzFmYTg5YTVhZTExY2RlNjEwMzk3M2QzYzZlOTAxMmEwMDQ4ZDY3MjgxYmQ0ODc1ZjMxMzhhNjUyJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.HY4WYW6lVvG0UgqrReSiUUuBA_0jhvEXBwFnzejhbJI"> seems the gofile link is down

deekerman commented

Author

Owner

@fff7d1bc commented on GitHub (Dec 22, 2025):

I've updated gist at https://gist.github.com/fff7d1bc/223881d03d33cd2b176f0695eaa7fe8e to 5.1.3 and uploaded qBittorrent-release-5.1.3-macOS-arm64.dmg build for ARM64 based MacOS there in comments. If for whatever reason you cannot build it yourself, try this artifact, works for me.

seems the gofile link is down

You can get qBittorrent-release-5.1.4-macOS-arm64.dmg from https://gofile.io/d/tvCte7

This link will too eventually expire.

@fff7d1bc commented on GitHub (Dec 22, 2025): > > I've updated gist at https://gist.github.com/fff7d1bc/223881d03d33cd2b176f0695eaa7fe8e to 5.1.3 and uploaded `qBittorrent-release-5.1.3-macOS-arm64.dmg` build for ARM64 based MacOS there in comments. If for whatever reason you cannot build it yourself, try this artifact, works for me. > > <img alt="Image" width="817" height="524" src="https://private-user-images.githubusercontent.com/180211/514369508-81440152-efa8-49fb-be8c-c86246d2cf37.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NjY0MzIxODIsIm5iZiI6MTc2NjQzMTg4MiwicGF0aCI6Ii8xODAyMTEvNTE0MzY5NTA4LTgxNDQwMTUyLWVmYTgtNDlmYi1iZThjLWM4NjI0NmQyY2YzNy5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjUxMjIyJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI1MTIyMlQxOTMxMjJaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT0zODEyNTExNzFmYTg5YTVhZTExY2RlNjEwMzk3M2QzYzZlOTAxMmEwMDQ4ZDY3MjgxYmQ0ODc1ZjMxMzhhNjUyJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.HY4WYW6lVvG0UgqrReSiUUuBA_0jhvEXBwFnzejhbJI"> > > seems the gofile link is down You can get `qBittorrent-release-5.1.4-macOS-arm64.dmg` from https://gofile.io/d/tvCte7 This link will too eventually expire.

deekerman commented

Author

Owner

@ghost commented on GitHub (Dec 23, 2025):

For everyone here searching for a more permanent answer(at least until mac release builds come back to the download page), the solution would be installing through nix.

Install nix

Install qbittorrent from nixpkgs: $ nix-env -iA nixpkgs.qbittorrent

It will show you where the path of the current build of qbittorrent has been installed,

/nix/store/5lgsfj3gazbd9bfj37p82mgqzl50qam5-qbittorrent-5.1.4 in this case.

Open that path: $ open /nix/store/5lgsfj3gazbd9bfj37p82mgqzl50qam5-qbittorrent-5.1.4/Applications

Open the .app or copy it to the user's Applications folder to add it to the path and there you have it.

When you want a newer version, just repeat steps 2-4, but do check if the version has been updated in nixpkgs.

@ghost commented on GitHub (Dec 23, 2025): For everyone here searching for a more permanent answer(at least until mac release builds come back to the download page), the solution would be installing through [nix](https://nixos.org/download/#nix-install-macos). - [x] Install nix <img width="708" height="49" alt="Image" src="https://github.com/user-attachments/assets/da299c84-0c2c-42a2-a675-eee2323db764" /> - [x] Install qbittorrent from nixpkgs: [`$ nix-env -iA nixpkgs.qbittorrent`](https://search.nixos.org/packages?channel=unstable&show=qbittorrent) It will show you where the path of the current build of qbittorrent has been installed, <img width="1340" height="52" alt="Image" src="https://github.com/user-attachments/assets/613e6465-70cd-48d2-b3ee-5a59b8724220" /> `/nix/store/5lgsfj3gazbd9bfj37p82mgqzl50qam5-qbittorrent-5.1.4` in this case. - [x] Open that path: `$ open /nix/store/5lgsfj3gazbd9bfj37p82mgqzl50qam5-qbittorrent-5.1.4/Applications` <img width="582" height="124" alt="Image" src="https://github.com/user-attachments/assets/47457cbf-b26e-481d-bcb5-ee13769d711d" /> - [x] Open the .app or copy it to the user's Applications folder to add it to the path and there you have it. When you want a newer version, just repeat steps 2-4, but do check if the version has been updated in nixpkgs. <img width="458" height="312" alt="Image" src="https://github.com/user-attachments/assets/78a9c960-13bf-4811-b7ac-c8acda901edc" />

deekerman commented

Author

Owner

@iyanucodes commented on GitHub (Dec 27, 2025):

Partially unrelated but just some feedback. The latest build from @fff7d1bc does provide greater upload speeds and performance in my testing. However checking is extremely slow compared to the previous 5.1.0rc I was using prior. I don't know if it's related to the lt version since this is 2.0 vs 1.2 or something related to Qt.

@iyanucodes commented on GitHub (Dec 27, 2025): Partially unrelated but just some feedback. The latest build from @fff7d1bc does provide greater upload speeds and performance in my testing. However checking is extremely slow compared to the previous 5.1.0rc I was using prior. I don't know if it's related to the lt version since this is 2.0 vs 1.2 or something related to Qt.

deekerman commented

Author

Owner

@xavier2k6 commented on GitHub (Dec 27, 2025):

@iyanucodes try https://github.com/qbittorrent/qBittorrent/discussions/23288#discussioncomment-15336973

@xavier2k6 commented on GitHub (Dec 27, 2025): @iyanucodes try https://github.com/qbittorrent/qBittorrent/discussions/23288#discussioncomment-15336973

deekerman commented

Author

Owner

@iyanucodes commented on GitHub (Dec 27, 2025):

@iyanucodes try #23288 (reply in thread)

Awesome, thank you! Merry Christmas to you too.

@fff7d1bc could you please build this?

@iyanucodes commented on GitHub (Dec 27, 2025): > [@iyanucodes](https://github.com/iyanucodes) try [#23288 (reply in thread)](https://github.com/qbittorrent/qBittorrent/discussions/23288#discussioncomment-15336973) Awesome, thank you! Merry Christmas to you too. @fff7d1bc could you please build this?

deekerman commented

Author

Owner

@fff7d1bc commented on GitHub (Dec 28, 2025):

@iyanucodes try #23288 (reply in thread)

Awesome, thank you! Merry Christmas to you too.

@fff7d1bc could you please build this?

The link that you got from Xavier is a ready build, there's a .dmg file inside that linked .zip.

@fff7d1bc commented on GitHub (Dec 28, 2025): > > [@iyanucodes](https://github.com/iyanucodes) try [#23288 (reply in thread)](https://github.com/qbittorrent/qBittorrent/discussions/23288#discussioncomment-15336973) > > Awesome, thank you! Merry Christmas to you too. > > [@fff7d1bc](https://github.com/fff7d1bc) could you please build this? The link that you got from Xavier is a ready build, there's a .dmg file inside that linked .zip.

deekerman commented

Author

Owner

@iyanucodes commented on GitHub (Jan 5, 2026):

Seems xavier's build is 5.1.2 not 5.1.4. Your build has superior performance for me but it seems that I am running into #17218

@iyanucodes commented on GitHub (Jan 5, 2026): Seems xavier's build is 5.1.2 not 5.1.4. Your build has superior performance for me but it seems that I am running into [#17218](https://github.com/qbittorrent/qBittorrent/issues/17218)

deekerman commented

Author

Owner

@xavier2k6 commented on GitHub (Jan 6, 2026):

Seems xavier's build is 5.1.2 not 5.1.4. Your build has superior performance for me

My build is from master which is 5.2.0

but it seems that I am running into #17218

That ticket is only related to Windows Builds??

@xavier2k6 commented on GitHub (Jan 6, 2026): > Seems xavier's build is 5.1.2 not 5.1.4. Your build has superior performance for me My build is from `master` which is **5.2.0** >but it seems that I am running into [#17218](https://github.com/qbittorrent/qBittorrent/issues/17218) That ticket is only related to Windows Builds??

deekerman commented

Author

Owner

@iyanucodes commented on GitHub (Jan 8, 2026):

I read the version number wrong but yes the ticket is in fact for windows builds but I find that I am running into the same issue on MacOS. Seems the lt2.0 builds do not have the setting to limit RAM usage.

@iyanucodes commented on GitHub (Jan 8, 2026): I read the version number wrong but yes the ticket is in fact for windows builds but I find that I am running into the same issue on MacOS. Seems the lt2.0 builds do not have the setting to limit RAM usage.

deekerman commented

Author

Owner

@godzfire commented on GitHub (Jan 10, 2026):

@sledgehammer999 can we please get some automated Mac builds here? The Mac released version is so far behind.

Can someone please build a version for those of us on Intel Macs and still on OS Sequoia 15? I'm stuck on 5.0.5.

@godzfire commented on GitHub (Jan 10, 2026): @sledgehammer999 can we please get some automated Mac builds here? The Mac released version is so far behind. Can someone please build a version for those of us on Intel Macs and still on OS Sequoia 15? I'm stuck on 5.0.5.

deekerman commented

Author

Owner

@ultratiem commented on GitHub (Jan 27, 2026):

@fff7d1bc why are you not linking the dmg to a simple post attachment? All your links on gofile are already gone, less than a month from posting.

Why code all this and never release it to the public? I don’t understand coders like those that run this project. What good is code if it’s just being gate kept?

This is peak gas lighting ☹️😠

@ultratiem commented on GitHub (Jan 27, 2026): @fff7d1bc why are you not linking the dmg to a simple post attachment? All your links on gofile are already gone, less than a month from posting. Why code all this and never release it to the public? I don’t understand coders like those that run this project. What good is code if it’s just being gate kept? This is peak gas lighting ☹️😠

deekerman commented

Author

Owner

@xavier2k6 commented on GitHub (Jan 27, 2026):

@ultratiem I was going to respond to the macos26 tahoe discussion but since you posted here too, I'll respond here.

Why code all this and never release it to the public? I don’t understand coders like those that run this project. What good is code if it’s just being gate kept?

The code in this repository is publicly available!
Our CI Builds are available for testing etc.

This is peak gas lighting

Nonsense! - Our CI Builds & code are available for testing & modification etc.

The only thing missing is an actual official release which are done by our maintainer which currently are outside of our control.

why are you not linking the dmg to a simple post attachment? All your links on gofile are already gone, less than a month from posting.

I've provided a build in https://github.com/qbittorrent/qBittorrent/discussions/23288#discussioncomment-15518605 which was built on a macos26 runner & had latest commits/dependencies at that time & I will continue to provide builds when time permits.

@xavier2k6 commented on GitHub (Jan 27, 2026): @ultratiem I was going to respond to the macos26 tahoe discussion but since you posted here too, I'll respond here. >Why code all this and never release it to the public? I don’t understand coders like those that run this project. What good is code if it’s just being gate kept? * The code in this repository is publicly available! * Our CI Builds are available for testing etc. >This is peak gas lighting Nonsense! - Our CI Builds & code are available for testing & modification etc. The only thing missing is an actual official release which are done by our maintainer which currently are outside of our control. >why are you not linking the dmg to a simple post attachment? All your links on gofile are already gone, less than a month from posting. I've provided a build in https://github.com/qbittorrent/qBittorrent/discussions/23288#discussioncomment-15518605 which was built on a macos26 runner & had latest commits/dependencies at that time & I will continue to provide builds when time permits.

deekerman commented

Author

Owner

@xavier2k6 commented on GitHub (Jan 27, 2026):

@godzfire Have you tried any of our CI builds or any other builds provided here?

@xavier2k6 commented on GitHub (Jan 27, 2026): @godzfire Have you tried any of our CI builds or any other builds provided here?

deekerman commented

Author

Owner

@godzfire commented on GitHub (Jan 27, 2026):

@godzfire Have you tried any of our CI builds or any other builds provided here?

I can't. As I stated, there are those of us still on Intel Macs and stuck on OS Sequoia 15.

@godzfire commented on GitHub (Jan 27, 2026): > [@godzfire](https://github.com/godzfire) Have you tried any of our CI builds or any other builds provided here? I can't. As I stated, there are those of us still on Intel Macs and stuck on OS Sequoia 15.

deekerman commented

Author

Owner

@grr commented on GitHub (Jan 27, 2026):

I can't. As I stated, there are those of us still on Intel Macs and stuck on OS Sequoia 15.

some of us are still on macOS 11 Big Sur

@grr commented on GitHub (Jan 27, 2026): > I can't. As I stated, there are those of us still on Intel Macs and stuck on OS Sequoia 15. some of us are still on macOS 11 Big Sur

deekerman commented

Author

Owner

@xavier2k6 commented on GitHub (Jan 27, 2026):

some of us are still on macOS 11 Big Sur

Unfortunately, you may not see any other official build for that OS than which is currently available.

@xavier2k6 commented on GitHub (Jan 27, 2026): >some of us are still on macOS 11 Big Sur Unfortunately, you may not see any other official build for that OS than which is currently available.

deekerman commented

Author

Owner

@xavier2k6 commented on GitHub (Jan 27, 2026):

I can't. As I stated, there are those of us still on Intel Macs and stuck on OS Sequoia 15.

What error do you get with our CI builds?

@xavier2k6 commented on GitHub (Jan 27, 2026): >I can't. As I stated, there are those of us still on Intel Macs and stuck on OS Sequoia 15. What error do you get with our CI builds?

deekerman commented

Author

Owner

@ultratiem commented on GitHub (Jan 27, 2026):

@ultratiem I was going to respond to the macos26 tahoe discussion but since you posted here too, I'll respond here.

Why code all this and never release it to the public? I don’t understand coders like those that run this project. What good is code if it’s just being gate kept?

The code in this repository is publicly available!

Our CI Builds are available for testing etc.

This is peak gas lighting

Nonsense! - Our CI Builds & code are available for testing & modification etc.

The only thing missing is an actual official release which are done by our maintainer which currently are outside of our control.

why are you not linking the dmg to a simple post attachment? All your links on gofile are already gone, less than a month from posting.

I've provided a build in #23288 (reply in thread) which was built on a macos26 runner & had latest commits/dependencies at that time & I will continue to provide builds when time permits.

I know the codebase is publicly available. But sadly most everyone using your app and code is not a dev. Even if they were, it is absolutely EXHAUSTING to have to hunt down the requirements of the project and then any inevitably subsequent error associated with the build process. Because let's face it, I haven't seen a single wiki or guide that was even remotely up to date. Most involve filtering thru endless discussion threads that in itself is just soul crushing.

I appreciate the work and the builds. I think everyone does, truly. Software is on fumes and 2026 hasn't really changed that. 99% of software is just trash or ad driven or worse. So, we ALL owe everyone in this project a huge thanks.

With that said, wouldn't it make sense to get a working version out to everyone? As I said in my other reply, you doom the macOS client if you can't even kick out an automated build alongside the other ones. Perhaps it's time to have an internal discussion as the project's management as it just seems be throwing you and others like you that have put in a lot of their time, under the bus.

Again, I know this is a touchy topic.

@ultratiem commented on GitHub (Jan 27, 2026): > [@ultratiem](https://github.com/ultratiem) I was going to respond to the macos26 tahoe discussion but since you posted here too, I'll respond here. > > > Why code all this and never release it to the public? I don’t understand coders like those that run this project. What good is code if it’s just being gate kept? > > * The code in this repository is publicly available! > * Our CI Builds are available for testing etc. > > > This is peak gas lighting > > Nonsense! - Our CI Builds & code are available for testing & modification etc. > > The only thing missing is an actual official release which are done by our maintainer which currently are outside of our control. > > > why are you not linking the dmg to a simple post attachment? All your links on gofile are already gone, less than a month from posting. > > I've provided a build in [#23288 (reply in thread)](https://github.com/qbittorrent/qBittorrent/discussions/23288#discussioncomment-15518605) which was built on a macos26 runner & had latest commits/dependencies at that time & I will continue to provide builds when time permits. I know the codebase is publicly available. But sadly most everyone using your app and code is not a dev. Even if they were, it is absolutely EXHAUSTING to have to hunt down the requirements of the project and then any inevitably subsequent error associated with the build process. Because let's face it, I haven't seen a single wiki or guide that was even remotely up to date. Most involve filtering thru endless discussion threads that in itself is just soul crushing. I appreciate the work and the builds. I think everyone does, truly. Software is on fumes and 2026 hasn't really changed that. 99% of software is just trash or ad driven or worse. So, we ALL owe everyone in this project a huge thanks. With that said, wouldn't it make sense to get a working version out to everyone? As I said in my other reply, you doom the macOS client if you can't even kick out an automated build alongside the other ones. Perhaps it's time to have an internal discussion as the project's management as it just seems be throwing you and others like you that have put in a lot of their time, under the bus. Again, I know this is a touchy topic.

deekerman commented

Author

Owner

@godzfire commented on GitHub (Jan 29, 2026):

I can't. As I stated, there are those of us still on Intel Macs and stuck on OS Sequoia 15.

What error do you get with our CI builds?

Where do I find these CI builds? If you mean here (https://github.com/qbittorrent/qBittorrent/actions/workflows/ci_macos.yaml) I don't see any prebuilt programs to download there and don't have the knowledge how to build one, nor does the vast majority of the QBT base. Hence the critical need for proper official builds being done.

@godzfire commented on GitHub (Jan 29, 2026): > > I can't. As I stated, there are those of us still on Intel Macs and stuck on OS Sequoia 15. > > What error do you get with our CI builds? Where do I find these CI builds? If you mean here (https://github.com/qbittorrent/qBittorrent/actions/workflows/ci_macos.yaml) I don't see any prebuilt programs to download there and don't have the knowledge how to build one, nor does the vast majority of the QBT base. Hence the critical need for proper official builds being done.

deekerman commented

Author

Owner

@xavier2k6 commented on GitHub (Feb 1, 2026):

@godzfire Download your preferred build under "Artifacts" at end of https://github.com/qbittorrent/qBittorrent/actions/runs/21560709925

@xavier2k6 commented on GitHub (Feb 1, 2026): @godzfire Download your preferred build under "Artifacts" at end of https://github.com/qbittorrent/qBittorrent/actions/runs/21560709925

deekerman commented

Author

Owner

@godzfire commented on GitHub (Feb 1, 2026):

@xavier2k6 No I can't because as I stated above I have an Intel Mac and those are all Apple Silicon only. Where are the Universal builds?

Also, having someone go to a page like https://github.com/qbittorrent/qBittorrent/actions/runs/21560709925 and then try to figure out what to click/use? There's no way in heck a regular/average user would in any way know what they are supposed to do.

This just highlights the reason why regular official releases for the Mac is needed. I don't understand why this is an issue.

@godzfire commented on GitHub (Feb 1, 2026): @xavier2k6 No I can't because as I stated above I have an Intel Mac and those are all Apple Silicon only. Where are the Universal builds? Also, having someone go to a page like https://github.com/qbittorrent/qBittorrent/actions/runs/21560709925 and then try to figure out what to click/use? There's no way in heck a regular/average user would in any way know what they are supposed to do. This just highlights the reason why regular official releases for the Mac is needed. I don't understand why this is an issue.

deekerman commented

Author

Owner

@godzfire commented on GitHub (Feb 1, 2026):

Look let's be frank, it's been over half a year and despite @sledgehammer999 being tagged and asked to automate this process, it's obvious he's ghosting this and doesn't care. We need actual, ready to go, just download and use GUI builds.

Can someone please take this over? @glassez @Chocobo1

@godzfire commented on GitHub (Feb 1, 2026): Look let's be frank, it's been over half a year and despite @sledgehammer999 being tagged and asked to automate this process, it's obvious he's ghosting this and doesn't care. We need actual, ready to go, just download and use GUI builds. Can someone please take this over? @glassez @Chocobo1

deekerman commented

Author

Owner

@glassez commented on GitHub (Feb 1, 2026):

This just highlights the reason why regular official releases for the Mac is needed. I don't understand why this is an issue.

To do this, the one who produces the official release builds (our maintainer) must have a Mac, right? But he doesn't have it. That's the problem.
An even bigger problem is that the vast majority of qBittorrent contributors (including main developers) also do not have Macs, so we cannot provide any testing on this platform, as well as full-fledged handling of Mac-specific issues.

@glassez commented on GitHub (Feb 1, 2026): > This just highlights the reason why regular official releases for the Mac is needed. I don't understand why this is an issue. To do this, the one who produces the official release builds (our maintainer) must have a Mac, right? But he doesn't have it. That's the problem. An even bigger problem is that the vast majority of qBittorrent contributors (including main developers) also do not have Macs, so we cannot provide any testing on this platform, as well as full-fledged handling of Mac-specific issues.

deekerman commented

Author

Owner

@godzfire commented on GitHub (Feb 1, 2026):

@glassez where have the builds that are on the official site come from?

Providing testing ≠ having actual builds to use. At least with having equal builds available to the general public, they can use the newest versions vs outdated/unfixed old ones. Users will still submit issues.

@godzfire commented on GitHub (Feb 1, 2026): @glassez where have the builds that are on the official site come from? Providing testing ≠ having actual builds to use. At least with having equal builds available to the general public, they can use the newest versions vs outdated/unfixed old ones. Users will still submit issues.

deekerman commented

Author

Owner

@xavier2k6 commented on GitHub (Feb 1, 2026):

where have the builds that are on the official site come from?

our maintainer does all the release builds irrespective of OS.

@xavier2k6 commented on GitHub (Feb 1, 2026): >where have the builds that are on the official site come from? our maintainer does all the release builds irrespective of OS.

deekerman commented

Author

Owner

@glassez commented on GitHub (Feb 1, 2026):

@glassez where have the builds that are on the official site come from?

It was mentioned above:

the one who produces the official release builds (our maintainer) must have a Mac

Official builds are produced by the qBittorrent maintainer @sledgehammer999.

@glassez commented on GitHub (Feb 1, 2026): > [@glassez](https://github.com/glassez) where have the builds that are on the official site come from? It was mentioned above: > the one who produces the official release builds (our maintainer) must have a Mac Official builds are produced by the qBittorrent maintainer @sledgehammer999.

deekerman commented

Author

Owner

@xavier2k6 commented on GitHub (Feb 1, 2026):

I've mentioned this before, maybe here but also in the tahoe compatability discussion....

qBittorrent will not even build via CI using a macos-15-intel runner image provided by GitHub (at least with libtorrent 2.x/latest Boost.

@xavier2k6 commented on GitHub (Feb 1, 2026): I've mentioned this before, maybe here but also in the tahoe compatability discussion.... qBittorrent will not even build via CI using a `macos-15-intel` runner image provided by GitHub (at least with libtorrent 2.x/latest Boost. ![Image](https://github.com/user-attachments/assets/35d2d900-8408-4e60-88e1-41b7c11c6ee7)

deekerman commented

Author

Owner

@glassez commented on GitHub (Feb 1, 2026):

Providing testing ≠ having actual builds to use. At least with having equal builds available to the general public, they can use the newest versions vs outdated/unfixed old ones. Users will still submit issues.

I meant that the lack of official builds is not the only problem of Mac users. Some issues cannot be fixed without being able to test/debug on the target platform.

@glassez commented on GitHub (Feb 1, 2026): > Providing testing ≠ having actual builds to use. At least with having equal builds available to the general public, they can use the newest versions vs outdated/unfixed old ones. Users will still submit issues. I meant that the lack of official builds is not the only problem of Mac users. Some issues cannot be fixed without being able to test/debug on the target platform.

deekerman commented

Author

Owner

@ultratiem commented on GitHub (Feb 1, 2026):

To do this, the one who produces the official release builds (our maintainer) must have a Mac, right?

No. You can set up automated builds easy enough to handle compile. You just can't test anything. Which is fine because that's why we have GH. Search online for "how to compile for a Mac without having one". There are tons of options, like using Linux or Windows. It's a non issue really.

Which is why someone made this post. There is no technical hurdle to make macOS builds anymore.

@ultratiem commented on GitHub (Feb 1, 2026): > To do this, the one who produces the official release builds (our maintainer) must have a Mac, right? No. You can set up automated builds easy enough to handle compile. You just can't test anything. Which is fine because that's why we have GH. Search online for "how to compile for a Mac without having one". There are tons of options, like using Linux or Windows. It's a non issue really. Which is why someone made this post. There is no technical hurdle to make macOS builds anymore.

deekerman commented

Author

Owner

@glassez commented on GitHub (Feb 2, 2026):

To do this, the one who produces the official release builds (our maintainer) must have a Mac, right?

No. You can set up automated builds easy enough to handle compile. You just can't test anything. Which is fine because that's why we have GH.

Yes. But to do this, @sledgehammer999 should decide to use an automated builds for official releases, and he still hasn't done that.

There are tons of options, like using Linux or Windows. It's a non issue really.

Using macOS on a non-Mac computer is not the same as using Linux on Windows (or Windows on Linux).

@glassez commented on GitHub (Feb 2, 2026): > > To do this, the one who produces the official release builds (our maintainer) must have a Mac, right? > > No. You can set up automated builds easy enough to handle compile. You just can't test anything. Which is fine because that's why we have GH. Yes. But to do this, @sledgehammer999 should decide to use an automated builds for official releases, and he still hasn't done that. > There are tons of options, like using Linux or Windows. It's a non issue really. Using macOS on a non-Mac computer is not the same as using Linux on Windows (or Windows on Linux).

deekerman commented

Author

Owner

@godzfire commented on GitHub (Feb 3, 2026):

If @sledgehammer999 doesn't have a mac, then how can he make a mac build? It's clear that @sledgehammer999 is not able or willing to do this, so this either needs to get automated or authorization be given to other people who are able to.

@godzfire commented on GitHub (Feb 3, 2026): If @sledgehammer999 doesn't have a mac, then how can he make a mac build? It's clear that @sledgehammer999 is not able or willing to do this, so this either needs to get automated or authorization be given to other people who are able to.

deekerman commented

Author

Owner

@ultratiem commented on GitHub (Feb 3, 2026):

There is no need for anyone on the team to own a Mac. That is a non issue here.

There is very clearly a skill issue that the internal team need to work out. I think at this point the community has done all it can.

A shame that both developers and users are thrown under the bus by the whims of the elite. Feels awfully familiar to world events going on.

In any case, I am signing off from this discussion. Appreciate the builds your posting @xavier2k6. I'll test those for the time being 🙏

@ultratiem commented on GitHub (Feb 3, 2026): There is no need for anyone on the team to own a Mac. That is a non issue here. There is very clearly a skill issue that the internal team need to work out. I think at this point the community has done all it can. A shame that both developers and users are thrown under the bus by the whims of the elite. Feels awfully familiar to world events going on. In any case, I am signing off from this discussion. Appreciate the builds your posting @xavier2k6. I'll test those for the time being 🙏

deekerman commented

Author

Owner

@Piccirello commented on GitHub (Feb 3, 2026):

GitHub Actions supports macOS runners. This isn't a hardware issue. @sledgehammer999 refuses to engage in any discussion related to automating builds.

@Piccirello commented on GitHub (Feb 3, 2026): GitHub Actions supports macOS runners. This isn't a hardware issue. @sledgehammer999 refuses to engage in any discussion related to automating builds.

deekerman commented

Author

Owner

@xavier2k6 commented on GitHub (Feb 4, 2026):

GitHub Actions supports macOS runners.

It seems that some users can't use any build from these runners as they are arm & qBittorrent is having build issues on macos-15-intel based runners.

GitHub will also only provide arm based runners from 2027 as Apple themselves are dropping x86_x64 support from macOS 26+ (Tahoe)
https://github.blog/changelog/2025-09-19-github-actions-macos-13-runner-image-is-closing-down/#notice-of-macos-x86_64-intel-architecture-deprecation

Edit:

Homebrew are also starting to drop support of older macOS:
https://docs.brew.sh/Support-Tiers#future-macos-support

macOS 14 Runners will soon be removed also...
[macOS] The macOS 14 Sonoma based runner images will begin deprecation on July 6th and will be fully unsupported by November 2nd for GitHub Actions and Azure DevOps

@xavier2k6 commented on GitHub (Feb 4, 2026): >GitHub Actions supports macOS runners. It seems that some users can't use any build from these runners as they are arm & qBittorrent is having build issues on `macos-15-intel` based runners. GitHub will also only provide arm based runners from 2027 as Apple themselves are dropping x86_x64 support from macOS 26+ (Tahoe) https://github.blog/changelog/2025-09-19-github-actions-macos-13-runner-image-is-closing-down/#notice-of-macos-x86_64-intel-architecture-deprecation Edit: Homebrew are also starting to drop support of older macOS: https://docs.brew.sh/Support-Tiers#future-macos-support macOS 14 Runners will soon be removed also... [[macOS] The macOS 14 Sonoma based runner images will begin deprecation on July 6th and will be fully unsupported by November 2nd for GitHub Actions and Azure DevOps](https://github.com/actions/runner-images/issues/13518)

deekerman commented

Author

Owner

@Ryu481 commented on GitHub (Feb 4, 2026):

Because someone has asked for an intel version I have compiled qBittorrent 5.1.4 as an universal binary. Works both on my intel and arm mac. I hope this works for you. https://workupload.com/file/zBgpVN7xmTh

@Ryu481 commented on GitHub (Feb 4, 2026): Because someone has asked for an intel version I have compiled qBittorrent 5.1.4 as an universal binary. Works both on my intel and arm mac. I hope this works for you. https://workupload.com/file/zBgpVN7xmTh

deekerman commented

Author

Owner

@xavier2k6 commented on GitHub (Feb 4, 2026):

@Ryu481 thank you, @godzfire test build above.

@xavier2k6 commented on GitHub (Feb 4, 2026): @Ryu481 thank you, @godzfire test build above.

deekerman commented

Author

Owner

@xavier2k6 commented on GitHub (Feb 4, 2026):

@Ryu481 Just for clarification, do our CI builds (master & v5_1_x branches) work for you on both your intel/arm mac's & what macOS version are you running on them?

@xavier2k6 commented on GitHub (Feb 4, 2026): @Ryu481 Just for clarification, do our CI builds (`master` & `v5_1_x` branches) work for you on both your intel/arm mac's & what macOS version are you running on them?

deekerman commented

Author

Owner

@Ryu481 commented on GitHub (Feb 4, 2026):

The ci builds work for me on my arm mac on Tahoe but they are arm only. So they don't run on my intel mac because arm software can't run on intel. The build above was compiled locally with Sequoia. I haven't figured out how to make an intel build or universal binary with github ci. I compiled on sequoia because I can't compile with libtorrent 1.2.20 on Tahoe but the build is running fine for me on Tahoe.

I haven't found any ci builds with intel support. Do you think that github ci can work for intel or would automating the build process end the intel support?

@Ryu481 commented on GitHub (Feb 4, 2026): The ci builds work for me on my arm mac on Tahoe but they are arm only. So they don't run on my intel mac because arm software can't run on intel. The build above was compiled locally with Sequoia. I haven't figured out how to make an intel build or universal binary with github ci. I compiled on sequoia because I can't compile with libtorrent 1.2.20 on Tahoe but the build is running fine for me on Tahoe. I haven't found any ci builds with intel support. Do you think that github ci can work for intel or would automating the build process end the intel support?

deekerman commented

Author

Owner

@godzfire commented on GitHub (Feb 4, 2026):

@Ryu481 's intel build worked for me, thank you. Yes, something does need to get done for the Intel Mac crowd so they aren't forgotten in this.

@godzfire commented on GitHub (Feb 4, 2026): @Ryu481 's intel build worked for me, thank you. Yes, something does need to get done for the Intel Mac crowd so they aren't forgotten in this.

deekerman commented

Author

Owner

@xavier2k6 commented on GitHub (Feb 4, 2026):

I can't compile with libtorrent 1.2.20 on Tahoe

What's stopping this?? (last time, I checked via CI - it worked.)

BTW libtorrent 1.2.x is limited/stuck using Boost <=1.86.0

I haven't found any ci builds with intel support.

qBittorrent fails to build on macos-15-intel runner which is last of the available x86_x64/Intel based images.

@xavier2k6 commented on GitHub (Feb 4, 2026): >I can't compile with libtorrent 1.2.20 on Tahoe What's stopping this?? (last time, I checked via CI - it worked.) BTW libtorrent 1.2.x is limited/stuck using Boost <=1.86.0 >I haven't found any ci builds with intel support. qBittorrent fails to build on `macos-15-intel` runner which is last of the available x86_x64/Intel based images.

deekerman commented

Author

Owner

@xavier2k6 commented on GitHub (Feb 4, 2026):

@godzfire @Ryu481 Can either of you post a screenshot of the about screen for the libraries used in that intel build.

@xavier2k6 commented on GitHub (Feb 4, 2026): @godzfire @Ryu481 Can either of you post a screenshot of the about screen for the libraries used in that intel build.

deekerman commented

Author

Owner

@Ryu481 commented on GitHub (Feb 4, 2026):

This is the about screen of the libraries.

@Ryu481 commented on GitHub (Feb 4, 2026): This is the about screen of the libraries. <img width="767" height="260" alt="Image" src="https://github.com/user-attachments/assets/3a149681-56a2-4c82-a0db-0980bd91e2bf" />

deekerman commented

Author

Owner

@xavier2k6 commented on GitHub (Feb 4, 2026):

@Ryu481 The build failures that I'm seeing for the macos-15-intel runner when building qBittorrent master with libtorrent RC_2_0 seem to be related to OpenSSL

use of old-style cast [-Werror,-Wold-style-cast]
'SKM_DEFINE_STACK_OF_INTERNAL'

I must retry with libtorrent 1.2.x

@xavier2k6 commented on GitHub (Feb 4, 2026): @Ryu481 The build failures that I'm seeing for the `macos-15-intel` runner when building qBittorrent `master` with libtorrent `RC_2_0` seem to be related to `OpenSSL` >use of old-style cast [-Werror,-Wold-style-cast] 'SKM_DEFINE_STACK_OF_INTERNAL' I must retry with libtorrent 1.2.x

deekerman commented

Author

Owner

@Ryu481 commented on GitHub (Feb 4, 2026):

In the ci is the compiler setting to treat warnings as errors. You could try to disable that.

@Ryu481 commented on GitHub (Feb 4, 2026): In the ci is the compiler setting to treat warnings as errors. You could try to disable that.

deekerman commented

Author

Owner

@xavier2k6 commented on GitHub (Feb 4, 2026):

In the ci is the compiler setting to treat warnings as errors. You could try to disable that.

workflow is essentially the same as our own master ci except, I use a matrix for os/Qt & have an action to use latest available Xcode provided on the runner image.

@xavier2k6 commented on GitHub (Feb 4, 2026): > In the ci is the compiler setting to treat warnings as errors. You could try to disable that. workflow is essentially the same as our own master ci except, I use a matrix for os/Qt & have an action to use latest available Xcode provided on the runner image.

deekerman commented