User selection components refuse to repeat interactions for the same value

[QuantumToasted]

Description

We are designing a user-created private VC solution for our server, which includes the ability to invite (add) and kick (remove) users from the VC as the owner desires. If for any reason, the owner needs to invite the same user a second time (such as accidentally kicking the wrong user), they are unable to do so because the selection will not/does not re-send an interaction for the same selected user on repeated selections.

I assume this might be due to selected value caching, but it is definitely annoying and breaks the flow we were designing around.

Steps to Reproduce

1. Select user A in a drop-down/user selection component
2. Click the ✕ to clear the selection
3. Select user A again in the same drop-down/user selection component

Expected Behavior

Another interaction is sent to the bot with user A as the selected value.

Current Behavior

No interaction is sent whatsoever. The only way to sent an interaction for user A again is to select user B, then user A again.
Alternatively, you must click away to another channel and then back to the channel the component is in to be able to re-select the previously selected value.

Screenshots/Videos

Client and System Information

Client:

Stable 432049 (38be209)
Host 1.0.9202 x64 (66976)
Windows 10 64-bit (10.0.19045)

Library: Disqord

[advaith1]

As a workaround, you can change the custom_id value whenever someone does a selection, to clear the state.

[QuantumToasted]

As a workaround, you can change the custom_id value whenever someone does a selection, to clear the state.

Thanks for the proposed workaround, but it doesn't seem to fix the issue unfortunately...
We reworked this system to add an incrementing number like so:

• "custom_id": "VC:Invite:1:1406001979196706911"
• User interacts with selection menu, the interaction callback edits the message, switching to "custom_id": "VC:Invite:2:1406001979196706911"

This still causes the erroneous behavior and does not clear the previously populated user selection component. However, we are editing the message directly via PATCH /channels/{channel.id}/messages/{message.id} instead of using interaction callbacks. If you were testing the workaround yourself before you mentioned it, were you using the latter instead of the former?