-
Notifications
You must be signed in to change notification settings - Fork 801
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
macOS client - M1 CPU #2659
Comments
+1 (the current client runs fine with Rosetta 2 btw) |
That's a good request 👌 |
This is a great request. I can only agree with it |
any detailed plan to support Apple Silicon natively? or how can we contribute |
maybe it's a good opportunity to upgrade to QT6? |
+1 here |
+1 here. I've found that the x86 version of the Nextcloud desktop software ends up being a memory hog on my Mac mini (M1 version). The app consistently takes up the most memory on my computer. |
Does it work fine for you under Rosetta? I am having problems where recent builds often quit after a few seconds, while with the latest daily built it doesn't quit but I get checksum errors when syncing. |
So Version 3.1.1 is M1 ready ? |
@F3000 I installed it on a new computer yesterday and it's still working under Rosetta. |
Yes for me also . So with 3.1.0 it couldn't be installed ? I have seen in the system report that the NC client is still the "intel" version |
Following. +1 |
Following |
Hey everyone. Please stop spamming this issue with "following" or "+1" messages. Instead, click "thumbs up" on the first comment or subscribe to this issue in notifications section. Thanks! |
Probably not the place to post this, but in my usage on an M1 Mac mini with version 3.1 (build 4316), when I set up the connection to the server, if I want to specify a local directory other than the default, the client provides a dialog box to navigate to and/or create a local directory for the sync. This dialog box is unresponsive to mouse/trackpad, but can be used with keyboard commands. |
The client does not really work on my M1 mac. |
I would suggest doing work to make the iOS / iPad app a universal app that you just download from the Mac app store. Then you can drop QT all together and just use apples native gui tools. Also this would mean that any features added to the mobile app would also be in the desktop app and vice versa |
iOS/ iPad app can already be installed on your M1 Mac. Just search in the Mac App Store. |
How does it really work ? thanks |
The iOS app doesn't really work as a background sync the way that the desktop app does. Same with Dropbox, Google Drive, or any other similar software. The NextCloud desktop app actually syncs folders to and from your computers drive, but the iOS app just gives you access to those files in the cloud, and thankfully integrates with the Files app. Using the iOS app with an M1 Mac would not enable doing things like directly seeing the files in finder or from the terminal, or saving to a folder you are syncing and knowing it will upload the data. |
Same request here! Recently some news declare than Rosseta 2 apps are taking extra swap from the ssd's, port the client to the "Universal" .app architecture would be ideal... |
If anyone on this thread has the time and the head space to you do this, here are the steps to build a universal binary of the source. and since nextcloud-desktop uses In full disclosure, I don't have a mac, so I personally can't do any of this. |
+1 for this. Nexctloud is one of the very few apps that have to be run via Rosetta2 on my new MacBook M1 Air. |
I would like to help creating a native Apple Silicon client as the Intel version via Rosetta 2 really eats away at the battery. Unfortunately, I do not think I can do this on my own. Can anyone, who is familiar with the development workflow of nextcloud work with me on this? |
@davidpfahler I bring that up internally and come back to you with an answer on how we will handle that. |
Fine for me just wanted to point it out, if it would be a mistake, thanks for your effort! |
@FlexW: Big thank you and much appreciation to the Nextcloud team for getting this Apple Silicon build up for us to test. So far everything seems to be working perfectly and in fact the app indicator in the top bar is also now sized correctly! I like the refreshed dropdown menu as well. Cheers |
Just a note, that in my case the following was required after installation: sudo xattr -r -d com.apple.quarantine /Applications/Nextcloud.app/ |
When trying to install the release candidate ( |
client seems to be working as Kind=Apple, but can confirm installer seemed to be an intel process when it ran. (I was a bit annoyed as something seems to have installed rosetta 2 when I wasn't looking; I was deliberately not doing that, and expected to give a report like the one above, and now I have to find how to uninstall it again. But... I think that's probably not on you, or (I must concede probably) I misread the dialog this time and let it happen myself 🤦♀️ I'm short on sleep!) I have had similar happen a couple of times since getting the new MBP: With the Temurin (JDK) installer and with the Caldigit docking station utility, in both cases the thing being installed was properly universal but the installer required Rosetta. |
@StrangeNoises @timbrd thanks for your feedback. I'll try to look into this, but the installer is not developed by us. Maybe there is a solution to this problem as well. |
@StrangeNoises @timbrd If you want you can give this build a try and check if the installer now runs natively on the M1 and does not ask to install Rosetta https://cloud.nextcloud.com/s/KpWay3rZXCmixGt . |
I have already finished installing my new Macbook and since I couldn't find a way to either disable or uninstall Rosetta 2, I had to check the reported arch type of the installer process on the activity monitor. The installer was running as a native Apple silicon app. I'm not sure though if this is a sufficient proof. Btw, the new version runs flawlessly on my device. Two weeks before I had installed the stable release on a different Macbook and it was quite power hungry. The release candidate on the other hand draws a lot less battery. 👍 |
Works like a charm. I just start the pkg and install it over the existing intel one and it works without any problems. Thank you :) |
I get an SSL handshake error when trying to connect to my Nextcloud instance. The latest Intel version works fine... I created an issue ticket for that, but sadly nobody replied yet. I hope you guys find a solution for that, as the Intel version is energy hungry... BTW this handshake issue was present in the self-signed build from Eric-pierce as well, if that helps. Cheers |
fwiw I did not have this issue on my M1 install. all went fine apart from the intel installer. (the Nextcloud instance in question is a snap on an ubuntu server nearby, and via that, will be using LetsEncrypt for the cert.) |
I have an installation on a Synology NAS also with letsencrypt and it is working with iOS and Intel MacOS but not with the universal binary for some reason. |
I've just received an update to nextcloud 3.4.0 and it seems to be a native ARM build 🎉 |
I don't see an update, are you on the stable channel?
…On Thu, Dec 2, 2021 at 3:09 PM thenickname ***@***.***> wrote:
I've just received an update to nextcloud 3.4.0 and it seems to be a
native ARM build 🎉
Thank you very much!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2659 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABZBOZ2RWXN7QBLKQ2PVWXTUO7VC5ANCNFSM4T753T5A>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
I had to reinstall it from the official website. The MacOS version now it M1 compiled. Just download it from the official website.
|
Using homebrew you should get the M1 native update automatically (the next time you do a |
@Skatox Did you do anything in particular to get the m1 version? I see there's only one option for mac on the official website, and that's the amd64 version unfortunately. @thenickname I would like to save the client's settings (I have lots of folders and only some of them are synced) so if I switch to the brew version, I'm afraid I'm going to lose that. |
@lethargosapatheia Universal binaries are shipping in the 3.4.0 release candidate builds. As a 3.4.0 final release hasn't been published yet, you can find the pre-releases under https://github.com/nextcloud/desktop/releases . |
Yes, install 3.4.0 from github. Use the appimage version.
You can install it from github releases, use 3.4. On the official page you can get the betas. The stable one doesn't work yet. |
Hi, I downloaded the AppImage on my M1 Mac and changed the permission to be executable (chmod +x). The file does not run and I get this error: zsh: exec format error: ./Nextcloud-3.4.1-x86_64.AppImage Did I do something wrong? Thanks! |
Hi @fdzaebel, The AppImage is for Linux, if you are on Mac Os you need to download .pkg. https://github.com/nextcloud/desktop/releases/download/v3.4.1/Nextcloud-3.4.1.pkg Have a nice day, |
Version 3.4.1 with native Apple Silicon support is now available from homebrew |
I just installed Version 3.4.1 on my M1 - and it shows the Server Folders. but it does not synchronize with my local folders (yet). Any suggestions? Do I have to install/adjust anything else? have a nice day. |
I have the same Problem after client update to 3.4.1 showing me SSL-Protokoll error |
3.4.1 (with NC-server 23.00) is buggy for me on Catalina (intel) AND Montery (ARM/M1). |
@bendschs just for your information: if you're not giving concrete details, it's almost as if your comment doesn't exist :) |
I am so sorry... |
Probably not the best place to post this, but couldn't find anything better. Is there a roadmap for getting a native Apple Silicon, ie a Universal App, for macOS? I'd love to get on the beta program when such a client appears
The text was updated successfully, but these errors were encountered: