8000 `ChatEventKind.callFinished` event was ignored for some reason · Issue #976 · team113/messenger · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
ChatEventKind.callFinished event was ignored for some reason #976
Closed
@SleepySquash

Description

@SleepySquash

Might be fixed by #27

Summary

While testing application, the following happened: I started a dialog call in browser (separate window for a call was opened) and then closed it before the conversation even began. Yet I could still see the ended call treated as ongoing, despite being already finished. This is happening due to ChatEventKind.callFinished event being ignored for some reason in this scenario.

Steps to reproduce

  1. Start a call in browser.
  2. End the call.
  3. See the call still being treated as ongoing (meaning ChatItem displaying Calling... text and join call buttons being present in RecentChatTile and on Chat page)

What is the current bug behavior?

Call being treated as ongoing due to ChatEventKind.callFinished event being ignored.

What is the expected correct behavior?

ChatEventKind.callFinished isn't ignored.

Relevant logs and/or screenshots

Снимок экрана 2024-04-24 в 09 14 56

Possible fixes

I have two thoughts:

  1. Perhaps popup call for some reason still overwrites the Chat, which causes Hive in main tab to lose information.
  2. Perhaps version for some reason of the events is not incrementing or is not compared properly?

I suggest the first though is more likely, as after refreshing the page I saw the ChatCall marked as ended right away.

Metadata

Metadata

Assignees

Labels

bugBugs and incorrectness problemsk::UI/UXUI (user interface) and UX (user experience) changes

Type

No type

Projects

Status

Done

Relationships

None yet

Development

No branches or pull requests

Issue actions

    0