On MacOS the client starts twice after a reboot. One of them crashes, the other is unresponsive until the crashed version is killed in Activity manager.
We have two MacBooks that connect to Nextcloud AIO, both have this behaviour. On is on Macos Tahoe, the other on Sequoia.
It looks rather similar to this issue described in German (my German is meh, though).
How can this be solved?
I found a report on github with an old launchAgent that launches the app a second time. It seems that you can disable this:
opened 06:38AM - 30 Apr 26 UTC
closed 12:03PM - 07 May 26 UTC
1. to develop
bug
os:
### ⚠️ Before submitting, please verify the following: ⚠️
- [x] This is a **bug… **, not a question or a configuration issue.
- [x] This issue is **not** already reported on Github (I've searched it).
- [x] Nextcloud Server and Desktop Client are **up to date**. See [Server Maintenance and Release Schedule](https://github.com/nextcloud/server/wiki/Maintenance-and-Release-Schedule) and [Desktop Releases](https://nextcloud.com/install/#install-clients) for supported versions.
- [x] I agree to follow Nextcloud's [Code of Conduct](https://nextcloud.com/contribute/code-of-conduct/)
### Bug description
When the Mac starts, nextcloud is also among the services active at login.
This pwer loads with a double instance.
The icon appears twice in the top tray, and the process appears twice in the "Activity Monitor."
When in this condition, the app becomes unresponsive and must be killed.
### Steps to reproduce
Start the Mac.
### Expected behavior
starting a single instance
### Which files are affected by this bug
No files interested
### Operating system
macOS
### Which version of the operating system you are running.
Sequoia 15.7.5
### Package
Other
### Nextcloud Server version
33.0.3 Cocoa Version
### Nextcloud Desktop Client version
33.0.3
### Is this bug present after an update or on a fresh install?
Updated from a minor version (ex. 3.16.1 to 3.16.2)
### Are you using the Nextcloud Server Encryption module?
Encryption is Enabled
### Are you using an external user-backend?
- [ ] Default internal user-backend
- [ ] LDAP/ Active Directory
- [ ] SSO - SAML
- [ ] Other
### Nextcloud Server logs
```shell
```
### Additional info
_No response_
And it seems that they fixed the bug for the next release 33.0.5 (not sure if there is a release every 4-6 weeks or so).