[Bug]: Shared file gets unshared without user interaction before expiry

[typorian]

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

I have a service account that I use to hold my keepass database. I share that file to another user, and the share breaks on its own within days of sharing, regardless of any settings.

Steps to reproduce

1. Share a file
2. do nothing
3. file gets unshared without interaction

Expected behavior

A file that gets shared without expiry date should stay shared.

Nextcloud Server version

32

Operating system

Debian/Ubuntu

PHP engine version

PHP 8.3

Web server

Apache (supported)

Database engine version

MariaDB

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

Upgraded to a MAJOR version (ex. 31 to 32)

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

[joshtrichards]

I'm afraid without more details (you left the template mostly blank) there isn't much to go on here.

Are you sure Keepass isn't just removing the original file and uploading a new one in its place?

Does this happen with any other shares?

If stuck, perhaps turn on audit logging and troubleshoot further via the community forum: https://help.nextcloud.com

[typorian]

Are you sure Keepass isn't just removing the original file and uploading a new one in its place?

Now that you put it like that, that could absolutely be what's happening in certain cases with the android app I'm using. Thank you, I will investigate that.

[typorian]

@joshtrichards thank you so much, this is actually caused by keepass2android.