Skip to content

fix(web): let members take over conversation-backed chats #421

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
setkyar merged 1 commit into from
Oct 15, 2026
+8 −4
Merged

fix(web): let members take over conversation-backed chats #421

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 8 additions & 4 deletions apps/web/src/pages/ChatPage.tsx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -299,9 +299,13 @@ export function ChatPage() {
// about the surviving customer gates the wrong conversation: a thread
// assigned to someone else shows a live composer, and one assigned to this
// user shows the take-over bar that assigning cannot clear.
const { access: composerAccess } = useComposerAccess(
activeThread?.contactId ?? selectedChatId ?? null,
);
// Contact reads accept a conversation UUID and resolve it to a contact, but
// contact mutations do not. Keep the thread's real contact UUID once it has
// been resolved so Take over/Unblock never POST a conversation UUID to a
// `/contacts/:id/*` route (which responds with "Contact not found").
const composerContactId =
activeThread?.contactId ?? selectedContact?.id ?? selectedChatId ?? null;
const { access: composerAccess } = useComposerAccess(composerContactId);
const canSend = composerAccess.kind === "sendable";
// The thread's own JID decides this. A merged customer's surviving contact
// may be neutral and JID-less, which read as "not a group" and stripped
Expand Down Expand Up @@ -450,7 +454,7 @@ export function ChatPage() {
</MessageActionsProvider>
</div>
<ComposerLifecycleArea
contactId={selectedChatId}
contactId={composerContactId!}
access={composerAccess}
isSending={isSending}
contactName={threadContact.name}
Expand Down
Loading