[Bug]: Shared Folder with Custom Permissions Displays as "View Only"

[kesselb]

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

When sharing a folder with custom permissions (e.g., "Read & Share"), the share functions correctly, but the list of shares incorrectly displays the permissions as "View Only," causing confusion for users.

Steps to reproduce

1. Share a folder with another user using custom permissions ("Read & Share").
2. The list of shares for the share owner shows "View only"

The share itself seems to work, only the permissions are shown wrong.

Screencast.From.2024-12-20.14-27-39.webm

Expected behavior

The list should display "custom permissions

Nextcloud Server version

30

[diegmero]

En navegador Chrome se ve bien, compruebalo. Observo que tienes un PWA

[sorbaugh]

@nfebe suspected frontend issue that happens in specific browsers, can you check 🙏

[skjnldsv]

Same goes for the opposite.
If you create a view-only, then open the menu and click "customize", it will be shown as "custom permissions"

This is because we have the default sharing including share to allow users to add link shares to their own account with this UI

server/apps/files_sharing/lib/Controller/ShareAPIController.php

Lines 717 to 719 in beea885

	if ($this->shareManager->outgoingServer2ServerSharesAllowed()) {
	$permissions |= Constants::PERMISSION_SHARE;
	}

server/apps/files_sharing/src/mixins/SharesMixin.js

Lines 135 to 142 in d6efc53

	hasCustomPermissions() {
	const bundledPermissions = [
	BUNDLED_PERMISSIONS.ALL,
	BUNDLED_PERMISSIONS.READ_ONLY,
	BUNDLED_PERMISSIONS.FILE_DROP,
	]
	return !bundledPermissions.includes(this.share.permissions)
	},

[skjnldsv]

@nfebe this is a customer issue. We need to find a fix for the next release early January

[sushifrick]

Any news here on this issue? Is there a chance this will be fixed with 30.0.5 next week?