⚠️ This issue respects the following points: ⚠️

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

Bug description

About the file lock on federation:

• If locked on the main instance that owns the file, the lock is working but UX on the other instance is bad. you dont know the file is locked and even saving only keeps local cache up. meaning that you think that the file is saved, with the right content (like opening the file again will kept the modification (with the text app). However, if i download the file, i have the original (locked) version of the file

• If locked on the other instance, the main instance can still edit the file

Steps to reproduce

Open / wite a file lock with federation

Expected behavior

File locking should also work in federation

Nextcloud Server version

30

Operating system

None

PHP engine version

None

Web server

None

Database engine version

None

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

None

Are you using the Nextcloud Server Encryption module?

None

What user-backends are you using?

• Default user-backend (database)
• LDAP/ Active Directory
• SSO - SAML
• Other

Configuration report

List of activated Apps

Nextcloud Signing status

Nextcloud Logs

Additional info

No response