[Bug]: macOS package folders do not sync correctly

[privatepublic-de]

⚠️ 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

When copying a macOS package folder (looks like a file in finder but actually is a folder) into a macOS virtual files Nextcloud share, the client keeps generating empty folders with filename postfix counting up (xxx 1, xxx 2, xxx 3).

Steps to reproduce

1. Copy a package folder (e.g. ".app" or old ".pages" format) in virtual share with finder or cp -r on command line
   ...

Expected behavior

The package folder should be treated as any other folder and synced with all files and subfolders.
...

Which files are affected by this bug

.app packages, old formats of e.g. .pages, .ooutliner, .graffle

Operating system

macOS

Which version of the operating system you are running.

macOS 26.1

Package

Official macOS Virtual files 12+ universal pkg

Nextcloud Server version

Hetzner Storage Share

Nextcloud Desktop Client version

4.0.1

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 Enabled

Are you using an external user-backend?

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

Nextcloud Server logs

Additional info

No response

[Rello]

{"category":"Item","date":"2025.11.11 13:06:22.789","details":{},"level":"error","message":"Could not create new folder at: https:\/\/...\/Documents\/test\/AusweisApp.app,\n received error: 405\n The resource you tried to create already exists"}

[i2h3]

I missed this and probably duplicated it with #9827.

[i2h3]

To reduce redundant issues and also due to new information in #9827, I close this issue. Please follow #9827 for updates in this matter which replaces this one.