[Bug]: macOS VFS 3.17.0 An Error Occurred while trying to delete the local copy

[AndyXheli]

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

• This is a bug, not a question or a configuration issue.
• This issue is not already reported on Github (I've searched it).
• Nextcloud Server and Desktop Client are up to date. See Server Maintenance and Release Schedule and Desktop Releases for supported versions.
• I agree to follow Nextcloud's Code of Conduct

Bug description

Getting this message while

The share dialog is looking incomplete.
...

Steps to reproduce

...

Expected behavior

Should not get this message
...

Which files are affected by this bug

ALL

Operating system

macOS

Which version of the operating system you are running.

15.6 (24G84)

Package

Official macOS 12+ universal pkg

Nextcloud Server version

31.0.8

Nextcloud Desktop Client version

3.17.0

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

Fresh desktop client install

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

Additional info

No response

[i2h3]

Analysis

This is an unhandled error bubbling up from the file provider framework (NSFileProviderError.Code.nonEvictable). Also relevant API method: evictItem(identifier:completionHandler:).

Basically, there appears to be materialized item which we offer to evict through this user interface while it actually cannot be evicted for one of the following reasons per documentation of the file provider framework:

• It has unsynchronized content
• It is marked as non-purgeable by the provider itself
• The item or one of its children has an open file handle
• Something with hard links

This is a problem which simply is not covered yet by the current implementation.

Suggestion

Either we disable the offering of eviction or present a user-friendly error message which actually leverages the underlying error and related item information to explain properly why it cannot be evicted (yet).

[AndyXheli]

Analysis

This is an unhandled error bubbling up from the file provider framework (NSFileProviderError.Code.nonEvictable). Also relevant API method: evictItem(identifier:completionHandler:).

Basically, there appears to be materialized item which we offer to evict through this user interface while it actually cannot be evicted for one of the following reasons per documentation of the file provider framework:

• It has unsynchronized content
• It is marked as non-purgeable by the provider itself
• The item or one of its children has an open file handle
• Something with hard links

This is a problem which simply is not covered yet by the current implementation.

Suggestion

Either we disable the offering of eviction or present a user-friendly error message which actually leverages the underlying error and related item information to explain properly why it cannot be evicted (yet).

Yes, exactly that user interface give you everything even if the files has not been download. So id there a way to show only files are are download and available offline ?

[i2h3]

es, exactly that user interface give you everything even if the files has not been download. So id there a way to show only files are are download and available offline ?

I am sorry, I do not fully understand what you mean. Do you mean that the Nextcloud client user interface for deleting local copies also lists data-less items which do not occupy space on the local storage? I have not verified that yet, I took over just recently.

[AndyXheli]

First, I want to thank you and say welcome! :) Looking forward to working together.

So, if you look at the picture, you'll see that all these folders haven’t downloaded anything—they’re empty—but they’re still listed under “Local Copies.” From what I can tell, the “Local Copies” section also includes folders or files that were merely discovered, not necessarily downloaded.

When I try to delete one or more of these folders, I get an error. Technically, the error makes sense because the system can’t delete something that isn’t actually stored locally. That said, I think the “Local Copies” label needs to be reworked to reflect only the data that’s actually been downloaded—not just discovered or indexed.

So far, it seems that deleting folders or files that were truly downloaded works fine. It’s only the ones that haven’t been downloaded that trigger the error.

[i2h3]

Ah, thank you, now I get it. Well, then clearly we need to take care of this.