client
client copied to clipboard
owncloud
[QA] Explorer status for spaces remain spinning
Seen with ownCloud-3.0.0.7681-alpha2.7681.x64.msi on Windows 10 21H2 / ocis.ocis-traefik.released.owncloud.works (2.0.0-Beta1)
Steps to reproduce:
- create 'katherine' with role Space Admin on ocis.ocis-traefik.released.owncloud.works
- start client and add account 'katherine' (VFS On)
- on server: create new spaces
- client: use "Add a space" to add the new spaces
Result: the spaces are added and get green check marks - but in 'Explorer' the status icons for the spaces remain spinning.
"Force sync", adding a file to the space or restarting the client don't help.
I could reproduce the issue with ownCloud-3.0.0-daily20220711.7999.x64.msi.
Difference to initial report: there isn't a 'Spaces' folder any longer
Could you check whether it is us or the windows explorer?
- Press F5
- Close and reopen the explorer
I've added one Space and twice the Personal folder. The status icon is correct just for the first Personal folder. For the remaining two the status icon is wrong and reopening or refreshing the explorer doesn't help
@erikjv please ping me for a short introduction before starting to work on the issue.
Maybe enable the code in line https://github.com/owncloud/client-desktop-vfs-win/blob/master/vfs_win.cpp#L684 ? But I guess we have to do more status updates from the plug-in...
For the record: the sync state for the folder containing the space is set to in-sync.
I asked a question on the msdn forums: https://learn.microsoft.com/en-us/answers/questions/1179273/(cfapi)-how-to-set-the-state-of-the-sync-root-fold
It's an issue in Windows, see the 4th comment on the link above. It's been "escalated" internally in MS, so we'll have to wait for a response.
could be related: CfUpdateSyncProviderStatus https://learn.microsoft.com/en-us/windows/win32/api/cfapi/nf-cfapi-cfupdatesyncproviderstatus
Issue on the github project: https://github.com/microsoft/Windows-classic-samples/issues/308
could be related: CfUpdateSyncProviderStatus https://learn.microsoft.com/en-us/windows/win32/api/cfapi/nf-cfapi-cfupdatesyncproviderstatus
I tried that, including first resetting it with CF_PROVIDER_STATUS_CLEAR_FLAGS, but that didn't help. Maybe you can give it a try in case I did something wrong?