session-desktop
session-desktop copied to clipboard
Native Apple Silicon Support
Please provide builds for apple m1 CPUs
I'm using it on an M1, so perhaps this has been solved?
I'm using it on an M1, so perhaps this has been solved?
That's because Rosetta 2
Relates #1635
Did anybody try bulding Session on Apple's aarch64?
any news about Session client for M1?
How is this still not done mid 2023? You literally only have to build a universal binary and you're done?
+1
Session Desktop is really laggy compared to other IMs, just noticed it's the only app on my M1 still using Intel 💀
Duplicated: https://github.com/oxen-io/session-desktop/issues/2781
I come here once again, it's impossible to use Session on battery (M1 Pro), the high CPU usage overheats my laptop and I can see the battery going down in real-time.
Good news everyone: I built & QA tested Session Desktop on macOS arm64 and everything works perfectly without any change, so this issue is simply just to add a new build to the release script.
Can anyone assist with the GitHub Actions do to so? cc/ @Bilb
The UI is so fast now, day and night difference!
cd session-desktop
nvm use 18.15.0
yarn install --frozen-lockfile
yarn build-everything
yarn test
729 passing (2s)
3 pending
✨ Done in 3.74s.
This is being tracked on Jira: https://optf.atlassian.net/browse/SES-1696
Github Actions is having issues producing ARM builds for M series Mac's which don't crash on startup, we are investigating, but we can produce these working builds locally, so shouldn't be too long before we figure this out. We are in the process of migrating to a different built machines for our CI process.
~~Resolved by https://github.com/oxen-io/session-desktop/pull/3163. Next release will include native silicon builds~~
The new release 1.13.2 is still an Intel only build.
Hi @pashynskykh, the team realized that we needed to investigate the auto update behaviour now that Session Desktop supports both macOS architectures. A lot of testing is required to ensure the update is smooth and doesn't breaking auto updating. Because this release had critical fixes for attachments and logging we decided to ship it without arm64 support.
I'll reopen this issue. 🙏
Hi @yougotwill,
I hope you are having a great day.
Thanks for the quick response and update on this issue.
I understand that testing might take some time, but would be very grateful for a rough ETA for the arm64 build, like a week, a month, or two months.
Thank you very much!
Best regards, Vladyslav
@pashynskykh We have a couple of high priority things in the pipeline so honestly expect about 1 month. Will ping you when it's released. 🙏
@yougotwill thanks you very much for your work! I look forward to trying the build for arm64.