IljaP
March 25, 2019, 5:11pm
1
Can´t start app client anymore. After double click on app icon nothing happens.
Had anyone experienced the same issue? Does anyone know a solution?
Operating system: OSX El Capitan 10.11.1
Client version: 2.5.4 (build 11456)
I´m grateful for any advice!
dmitry
March 25, 2019, 5:16pm
2
Hi,
is there a reason that you are on 10.11.1?
IljaP
March 25, 2019, 5:28pm
3
Hi, no special reason, it´s just the version I´m working on.
IljaP
March 25, 2019, 5:38pm
5
The latest version I can update to is 10.11.6. I thought it made no big difference. I´ll give it a try though.
ghau
March 25, 2019, 5:43pm
6
Same here. Running OSX 10.11.6 (the latest my machine can support).
I rebooted the machine to no avail.
It is definitely not working.
ghau
March 25, 2019, 5:58pm
7
An update:
Deleting the app (drag to trash bin), and then installing the previous version (2.5.3.11290) restored the function. However if I do the same with the latest version (2.5.4.11456) it will not run.
When the client is running properly, (2.5.3), then these are the processes running:
505 1015 1 0 2:53pm ?? 0:01.00 /Applications/owncloud.app/Contents/PlugIns/FinderSyncExt.appex/Contents/MacOS/FinderSyncExt
505 1030 1 0 2:53pm ?? 0:01.82 /Applications/owncloud.app/Contents/MacOS/owncloud
However when the latest version (2.5.4) is run, only one of the processes run:
505 974 1 0 2:51pm ?? 0:00.35 /Applications/owncloud.app/Contents/PlugIns/FinderSyncExt.appex/Contents/MacOS/FinderSyncExt
IljaP
March 25, 2019, 8:48pm
8
Yep! 2.5.3 (build 11290) works. Thanks for the tip!
We’re working on a version that supports 10.11. See https://github.com/owncloud/client/issues/7106
2 Likes
I am having the same issue on MAC OS X Yosemite 10.10.5 How do i fix it urgently, as I am not connecting to our shared work folders, which create a lot of conflicts once re-connection happens.
Hey,
i think the question is if 10.10 will be ever be supported again? It seems they are only working on a version that supports 10.11. again:
Maybe you can also ask for support of 10.10 in that issue as well?
10.10 and 10.11 should be more or less the same in this case.
1 Like
It was the same for me (OS X 10.11.6).
But this new build works.
Thank you