Skip to content

Commit df4e72d

Browse files
mahibiAndyScherzinger
authored andcommitted
fix(moderators): Make the self PIN row non-interactive
In the participant actions sheet, the current user's own row shows their attendee PIN via the same `remove` slot used for actual remove/leave actions, so tapping the PIN text fired ParticipantOpsAction.RemoveFromConversation and removed the user from the conversation. As a result i got: 2026-08-25 13:49:51.393 23038-23038 Conversati...oViewModel com.nextcloud.talk2 E Error loading participants retrofit2.adapter.rxjava2.HttpException: HTTP 404 Every other branch of computeVisibility() already renders its PIN through infoPin, a plain non-interactive row. Route the self row's PIN through infoPin as well instead of wrapping it in a clickable RemoveOption. Signed-off-by: Marcel Hibbe <dev@mhibbe.de> (cherry picked from commit 4613dd3)
1 parent b888794 commit df4e72d

1 file changed

Lines changed: 2 additions & 4 deletions

File tree

app/src/main/java/com/nextcloud/talk/conversationinfo/ui/ParticipantOperationsSheet.kt

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -81,16 +81,14 @@ private fun computeVisibility(
8181
!canModerate -> ParticipantOpsVisibility()
8282

8383
model.isSelf -> ParticipantOpsVisibility(
84-
infoPin = null,
84+
infoPin = pin,
8585
showPromote = false,
8686
showDemote = false,
8787
showPromoteToOwner = false,
8888
// An owner may step down, but only as far as moderator, to avoid locking themselves out
8989
showDemoteOwnerToModerator = canDemoteFromOwner,
9090
showDemoteOwnerToUser = false,
91-
remove = pin?.let {
92-
RemoveOption(R.drawable.ic_lock_grey600_24px, stringResource(R.string.nc_attendee_pin, it))
93-
},
91+
remove = null,
9492
showBan = false
9593
)
9694

0 commit comments

Comments
 (0)