-
Notifications
You must be signed in to change notification settings - Fork 805
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
[Bug]: Automatically check for updates setting has no effect on macOS #5429
Comments
Hi, I wasn't able to reproduce this bug on a copy of 3.7.x. Do you have any logs from when this happens? (or could you provide them the next time this happens?) Could you check if your |
Hi! Thanks for looking into this again :) Here's a log from my test setup on version 3.7.3. I've left the update notification window open while generating the debug. This is with 'skipUpdateCheck=true', we also have clients using the older 'autoUpdateCheck=false' but the result is the same. In the GUI the update check shows as disabled (or doesn't show at all), but the update still gets offered. Let me know if there's anything else I can check or provide! |
+1 |
I have a similar problem on Windows, I guess: #5639 |
I hate to keep bumping this, but this bug still isn't fixed. I just got an update notification yet again, even though the checkbox is unchecked and I can see the following lines in my nextcloud.cfg folder:
Changing the checkbox causes that bool to flip from true to false. But even with it set to false, it still does the auto update check. |
The error still occurs and is particularly annoying as I have to roll out the client updates via MDM. In my case, the user is always asked for an update which he cannot install due to a lack of update admin rights and I cannot switch it off. |
Bug description
Even after turning off "Automatically check for updates" in Nextcloud's settings, the user will still get pestered by automatic update notifications.
This is related to #5077 and #4711. Neither of those issues were apparently ever properly resolved, even though they are closed.
Steps to reproduce
Expected behavior
Naturally there should be no update notifications when this setting is not checked
Which files are affected by this bug
N/A
Operating system
Mac OS
Which version of the operating system you are running.
macOS 10.14 - macOS 12.6.2
Package
Other
Nextcloud Server version
N/A
Nextcloud Desktop Client version
3.7.1
Is this bug present after an update or on a fresh install?
Updated from a minor version (ex. 3.4.2 to 3.4.4)
Are you using the Nextcloud Server Encryption module?
Encryption is Enabled
Are you using an external user-backend?
Nextcloud Server logs
No response
Additional info
Unfortunately due this bug only being verifiably present when there is an update available, it is therefore impossible for me to confirm whether it's present in the latest version of Nextcloud!
However I have experienced it in Nextcloud 3.7.x.
The text was updated successfully, but these errors were encountered: