After changing the security settings on my MB Pro M1 with macOS Sequoia 15.5 from “disabled” to “full” or “reduced” the client (3.16.6) terminates right after launching with the message “Client App damaged …” (translated from German). Changing the security back to “disabled” lets the client run again without problems. I used the recovery console to change these settings. Of course I re-downloaded the latest version without any result.
Any idea? I’d be happy to get some information (couldn’t find any in the net).
I’m not sure if you have more information what part of Nextcloud triggers the problem, if the app is not signed at all, or not by Apple, or it uses modules it is not supposed to use, …
I don’t know about the internals of the NextCloud Client app. But, if it were not signed correctly, others should have the same problem as well, don’t you think so?
Yes, but I don’t know if you want to use this special apple security feature, you perhaps need another developer status, or the app has to go through some apple review process, …
Or it is on the Nextcloud side, that it cannot use certain resources (or has to change something if they want to use it).
For that reason the a detailed error might be helpful, e.g. if you accessed your cloud without https and apple considered this as unsafe, this would be something linked to your configuration.
This security feature is turned on by default, or do you have to activate it specifically? Most other apps work with it I suppose?
I disabled this feature to be able to use XtraFinder which requires it to make some code injections when it runs. Because I don’t use XtraFinder anymore I wanted to re-enable the security feature again.
Yes, the Nextcloud client is the only app I found that makes problems like this. I’ve been using the official client app for years without problems and of course I’d like to in the future, too.