Well, should have done things in reverse order. I posted about my last Nautilus/Webdav fail and then tried yet another time.
For some reason, everything is working just as expected.
Bonus.
This test version is even more broken then the first one.
Do you not install your own package before releasing it?
Itās impossible to login and when logged in (on an existing device) the connection is broken.
TLS problems.
You guys have some internal problems if you ask me.
2 Likes
Yeah, seems so. Even one week after the announcement, there is still no stable 2.6 release. Their link to grab the 2.6 release still points to the last stable version 2.5.3
1 Like
So that was my mistake - I had mis-understood the desktop client ppl, thought it was a final release when it was an RCā¦ The final version will come soon, though, and Iām sure the testing is appreciated.
2 Likes
I am running macOS Mojave 10.14.6. The official NextCloud desktop clients consume memory continuously until they are using over 1GB and more of RAM and I am forced to uninstall. By chance I downloaded the OwnCloud desktop client and whether I install the stable or nightly version, behaviour is impeccable and communication with my NextCloud install is perfect. I donāt know whatās happening with the NextCloud client but itās not fit for purpose.
I am happy to say that most of our Desktop client users disagree with you 
In any case, when you find any issues in the Desktop client, please contribute by commenting in the existing issues on Github or by opening a new one. Thanks!
1 Like
Really? I was told by another experienced Nextcloud user that version 2.3.3 is the most recent version that works correctly on macOS and doesnāt eat memory. Iād be interested to see evidence of your assertion that most of your Mac desktop client users disagree with me. Why should the client continuously consume RAM on my Mac, even after I erased the mac OS partition and reinstalled Mojave? I have only around 1GB of files stored in Nextcloud and use it for CalDAV and CardDAV syncing. Iām also interested as to why the Owncloud client works perfectly, over several versions too.
I have opened a new issue on Github.
1 Like
The people I talk about include our customers, my colleagues and other users who are always updating their Desktop Client to the latest. Another reason also might be the fact that most of our users are using Windows and Linux. That definitely could be an exclusive problem on Mac OS. I canāt answer about the Owncloud client.
I have seen the issue you opened. Opening issues on Github are a much more effective way of giving feedback than commenting in a forum.
2 Likes
Iāll just say that I use the Mac app on several of my machines, 2 of which are 2012=3 MacBook Airs with 8G of ram, and I have not noted any issues. Doesnāt mean there isnāt one, but seems to work OK for me.
2 Likes
@camila Iām currently a little bit confused about the current status of the Nextcloud desktop client. As far as I understood the Nextcloud Client v2.6.0 for Windows includes the new virtual drive technology and automatically installs the Dokany library if not already installed on a Windows PC, right? The screenshot on the following site seems to confirm that behavior:
Unfortunately I cannot see that the Dokany component is automatically installed nor is a virtual drive shown on my PC. Do I still need to install the Dokany package separately as it was necessary for the preview version? It would be nice if you could shed some light on it.
No you are wrong
The 2.6.0 have nothing about virtual Drive.
Itās a test preview build that you can find in https://download.nextcloud.com
Your nextcloud serveur must use TLS 1.3 in order to work with the test build.
@Nemskiller Thank you for the clarification. The ongoing discussion about the virtual drive and the new desktop version 2.6.0 let me to the assumption that it has already been included into that package.
as for today v2.6.0 wants to update automaticallyā¦ so i think itās now officially a final version 
yay. hi-5 for that!
and keep the good work up @camila
1 Like
There is still a problem with logging in (authentication) in this version (2.6). A problem (loop) arises where the client makes an http request. A problem arises (loop) where the client makes an http request. This is not found to be safe.
I change the url in the browser [form methode=āPOSTā action ="http://xxxx] into [form methode=āPOSTā action ="https://xxxx]
Now the client and server accepted the login-request.
Now I am not really a specialist in this area. It seems that the settlement of the POST action is not proceeding correctly.