Skip to content

WPB-27892: fix: resolve original caller for call-end "called" message - #22101

Draft
blackheaven wants to merge 1 commit into
mainfrom
gdifolco/fix-original-caller
Draft

WPB-27892: fix: resolve original caller for call-end "called" message#22101
blackheaven wants to merge 1 commit into
mainfrom
gdifolco/fix-original-caller

Conversation

@blackheaven

@blackheaven blackheaven commented Aug 4, 2026

Copy link
Copy Markdown
TaskWPB-27892 Missed-call conversation message names the wrong user ("$USER called")

https://wearezeta.atlassian.net/browse/WPB-27892

handleMissedCall injected the deactivate event with the missedh userId (the sender of the missed-trigger message), so the "$USER called" conversation message named the wrong participant.

Use the original caller captured at ring time (call.initiator = AVS SETUP sender) when a Call object exists for the conversation, falling back to the missedh userId only when none is present (e.g. the app cold-launched straight into a missed call). callClosed already used call.initiator.

It's LLM-generated, please, review it carefully.

Depends on wireapp/wire-avs#199

handleMissedCall injected the deactivate event with the missedh userId
(the sender of the missed-trigger message), so the "$USER called"
conversation message named the wrong participant.

Use the original caller captured at ring time (call.initiator = AVS
SETUP sender) when a Call object exists for the conversation, falling
back to the missedh userId only when none is present (e.g. the app
cold-launched straight into a missed call). callClosed already used
call.initiator.
@blackheaven blackheaven changed the title fix: resolve original caller for call-end "called" message WPB-27892: fix: resolve original caller for call-end "called" message Aug 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant