Skip to content

[stable35] fix(mount-provider): Pass the recipient to the federated share storage - #3073

Merged
DerDreschner merged 1 commit into
stable35from
backport/3060/stable35
Oct 20, 2026
Merged

DerDreschner merged 1 commit into
stable35from
backport/3060/stable35

Conversation

@backportbot

@backportbot backportbot Bot commented Oct 19, 2026

Copy link
Copy Markdown

Backport of PR #3060

Since Nextcloud 34.0.5 / 35.0.2, the federated share storage requires the user receiving the share as `recipient` option. Team mounts didn't pass it, so setting up the filesystem of a user with a team share from a remote instance failed with an `Undefined array key "recipient"` exception. This aborted e.g. `occ versions:expire` and `occ versions:cleanup`.

Pass the user the mounts are set up for from getMountsForUser() and getMountsForPath() to the storage.

Assisted-by: ClaudeCode:claude-opus-5-5
Signed-off-by: David Dreschner <david.dreschner@nextcloud.com>
@DerDreschner
DerDreschner force-pushed the backport/3060/stable35 branch from b4b12d1 to a47816a Compare October 20, 2026 09:52
@DerDreschner
DerDreschner merged commit de94997 into stable35 Oct 20, 2026
49 checks passed
@DerDreschner
DerDreschner deleted the backport/3060/stable35 branch October 20, 2026 10:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants