Skip to content
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]: Upgrade to 3.14.0 changes update channel from Stable to Daily #7178

Open
4 of 8 tasks
Tracked by #7191
uselpa opened this issue Sep 21, 2024 · 13 comments
Open
4 of 8 tasks
Tracked by #7191

[Bug]: Upgrade to 3.14.0 changes update channel from Stable to Daily #7178

uselpa opened this issue Sep 21, 2024 · 13 comments
Assignees

Comments

@uselpa
Copy link

uselpa commented Sep 21, 2024

⚠️ Before submitting, please verify the following: ⚠️

Bug description

Version 3.14.0 changes the update channel. It should not.

Steps to reproduce

Update Nextcloud desktop client from 3.13.4 to 3.14.0

Expected behavior

Do not touch that setting.

Which files are affected by this bug

none

Operating system

macOS

Which version of the operating system you are running.

15.0

Package

Official macOS 12+ universal pkg

Nextcloud Server version

28

Nextcloud Desktop Client version

3.14.0

Is this bug present after an update or on a fresh install?

Updated to a major version (ex. 3.3.6 to 3.4.0)

Are you using the Nextcloud Server Encryption module?

Encryption is Disabled

Are you using an external user-backend?

  • Default internal user-backend
  • LDAP/ Active Directory
  • SSO - SAML
  • Other

Nextcloud Server logs

No response

Additional info

No response

@MariusQuabeck
Copy link
Member

can confirm, my client on stable channel just updated itself to 3.14.0daily

@jonasgarstick
Copy link

Same here.

@camilasan camilasan self-assigned this Sep 23, 2024
@camilasan camilasan mentioned this issue Sep 23, 2024
15 tasks
@mgallien
Copy link
Collaborator

@MariusQuabeck @jonasgarstick which OS are you using ?

@mgallien
Copy link
Collaborator

@uselpa @MariusQuabeck @jonasgarstick
I just tested on Windows upgrading from 3.13.4 to 3.14.0 and could not reproduce
would you be able to reproduce it and generate a debug archive once you have the issue ?
I can provide an upload only share link if you need

@jonasgarstick
Copy link

@MariusQuabeck @jonasgarstick which OS are you using ?

It was on a macOS with Ventura v13.6.6. My desktop client on macOS v14.6.1 installed 3.14.0daily but did not switch the update channel to daily.

@camilasan
Copy link
Member

camilasan commented Sep 26, 2024

I couldn't reproduce this on mac OS (Sonoma 14.5).
When the client updates to a new version, it create a backup of the config file. Could you check in the back up config file if the value of updateChannel is set to anything like: updateChannel=stable?
The backup files are found in ~/Library/Preferences/Nextcloud, it should be named something like nextcloud.cfg.backup_20240926_120253_3.13.4stable (build 25658).

@uselpa
Copy link
Author

uselpa commented Sep 26, 2024

n.b. the following is after having set the channel back to "stable"

pu@Greenmac 504 ~/Library/Preferences/Nextcloud $  ls -altr *.cfg*
-rw-r--r--  1 pu  staff    37 28 Apr 13:46 nextcloud.cfg.backup_20240428_134646
-rw-------  1 pu  staff     0 22 May 18:03 nextcloud.cfg.dGbycF
-rw-r--r--  1 pu  staff     0  9 Jun 00:29 nextcloud.cfg.jeIcCg
-rw-r--r--  1 pu  staff     0 29 Jun 20:04 nextcloud.cfg.MjVWDE
-rw-r--r--  1 pu  staff  1163  4 Jul 18:35 nextcloud.cfg.backup_20240704_183504_3.13.0git (build 22490)
-rw-r--r--  1 pu  staff  1166  9 Jul 21:51 nextcloud.cfg.backup_20240709_215119_3.13.1stable (build 24143)
-rw-r--r--  1 pu  staff  1691 26 Aug 16:06 nextcloud.cfg.backup_20240826_160626_3.13.2stable (build 24386)
-rw-r--r--  1 pu  staff  1691 13 Sep 14:24 nextcloud.cfg.backup_20240913_142456_3.13.3stable (build 25180)
-rw-r--r--  1 pu  staff  1692 21 Sep 10:23 nextcloud.cfg.backup_20240921_102337_3.13.4stable (build 25658)
-rw-r--r--  1 pu  staff  2303 26 Sep 07:01 nextcloud.cfg

pu@Greenmac 505 ~/Library/Preferences/Nextcloud $  diff "nextcloud.cfg.backup_20240921_102337_3.13.4stable (build 25658)" nextcloud.cfg
2c2
< clientVersion=3.13.4stable (build 25658)
---
> clientVersion=3.14.0daily
4a5
> desktopEnterpriseChannel=daily
15a17
> updateChannel=stable
29a32,41
> 0\networkDownloadLimit=0
> 0\networkDownloadLimitSetting=-2
> 0\networkProxyHostName=
> 0\networkProxyNeedsAuth=false
> 0\networkProxyPort=0
> 0\networkProxySetting=0
> 0\networkProxyType=0
> 0\networkProxyUser=
> 0\networkUploadLimit=0
> 0\networkUploadLimitSetting=-2
30a43
> 0\serverHasValidSubscription=false
46a60,69
> 1\networkDownloadLimit=0
> 1\networkDownloadLimitSetting=-2
> 1\networkProxyHostName=
> 1\networkProxyNeedsAuth=false
> 1\networkProxyPort=0
> 1\networkProxySetting=0
> 1\networkProxyType=0
> 1\networkProxyUser=
> 1\networkUploadLimit=0
> 1\networkUploadLimitSetting=-2
47a71
> 1\serverHasValidSubscription=false
``

@stacheldrahtje
Copy link

Same here on openSUSE Tumbleweed

@core-code
Copy link

core-code commented Oct 22, 2024

apart from the "update channel", just downloading recent releases on macOS you can see that the official releases are now being labeled "daily" instead of "stable". this should obviously not happen for official releases.

Image
Image

the change happend with 3.14.0, which was the first official release being labeled as "daily".

in technical terms the issue here is the in CFBundleShortVersionString stored in the Info.plist file

could it be that what the others are seeing here is also just a change in the labels that are being used, since the official stable releases are now labelled "daily"?

@MariusQuabeck
Copy link
Member

I am also back on daily without my doing 🙃 . I had to reinstall last time to get on stable again, please let me know if you need any files for debugging before I nuke and pave again.

@lenaulrich
Copy link

Updated around 14 Nextcloud clients:
6x Windows: No issues; clients remain on the correct update channel
8x macOS (various OS versions, minimum Sonoma): All clients already updated to versions 3.14.0 or 3.14.1 were unexpectedly on the daily update channel and displayed no further updates. After manually switching these clients back to the stable channel, the update to version 3.14.3 became visible and could be installed. Following this update, the channel remains set to stable.

Any ideas how this can be resolved without requiring user interaction?

@core-code
Copy link

still broken in 3.15 :(

Image

@core-code
Copy link

but fixed in 3.15.1 :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

8 participants