Open marcotrevisan opened 4 days ago
By reopening the client (i.e. quitting and relaunching the app) brings back the sync status to OK. The debug archive contains some errors, in the current case:
Very frequently:
Nil deleted metadatas received in change read at https://.../remote.php/dav/files/user for user: user https://...
Much less frequently:
err: Error while sending authentication request to nextcloud: Error while connecting to nextcloud: error sending request for url (https://.../index.php/apps/notify_push/uid
and also:
1 depth read of url https://.../remote.php/dav/files/user did not complete successfully, error: Impossibile trovare un server con il nome host specificato.
(this looks like a DNS lookup failure)
Last but not least: if possible, it would be great to add timestamps at the beginning of each line in the debug log file.
⚠️ Before submitting, please verify the following: ⚠️
Bug description
On the 3.14-macOS-vfs clients that we are using, we often see the exclamation mark icon on the status bar. Hovering on it, it says the vfs sync had an issue. However, opening the settings panel and clicking on "Create debug archive" freezes the UI and the Nextcloud process becomes unresponsive. This seems to be related (kind of a side effect) to the sync issue itself, because when the sync status is OK, it's possible to generate the debug archive without freezes.
The problem is, I have no clue on what the problem is and therefore haven't found a way to prevent/work around it. ...
Steps to reproduce
Expected behavior
The debug archive should be created. Observed behaviour: the panel hangs and the process becomes unresponsive, I have to kill it. Seems similar to what happened a few versions back, on opening the settings panel, where the process froze and needed to be killed. ...
Which files are affected by this bug
-
Operating system
macOS
Which version of the operating system you are running.
Sonoma 14.6.1
Package
Official macOS 12+ universal pkg
Nextcloud Server version
29.0.6
Nextcloud Desktop Client version
3.14.0-vfs
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 Disabled
Are you using an external user-backend?
Nextcloud Server logs
No response
Additional info
No response