Skip to content
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.

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

incoming phantom call on startup #21294

Closed
eladyn opened this issue Mar 3, 2022 · 3 comments
Closed

incoming phantom call on startup #21294

eladyn opened this issue Mar 3, 2022 · 3 comments
Labels
A-VoIP O-Uncommon Most users are unlikely to come across this or unexpected workflow S-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Defect

Comments

@eladyn
Copy link

eladyn commented Mar 3, 2022

This bug might be similar to the ones mentioned in #18454 or #20954, but is different enough that I decided to open a new issue. Feel free to integrate this into one of the others, if you think that this would fit it better.

Steps to reproduce

  1. don't know how to reproduce that reliably: Have a call in the (recent?) timeline that causes this behavior.
  2. Start/Reload Element with a different room than the one actually causing the problem opened by default (at least that seems to increase the probability.)
  3. Switch to the room with the problematic call.
  4. Watch the room history load.

→ receive a phantom call

Outcome

What did you expect?

Not receiving call notifications, when I'm not actually being called.

What happened instead?

I'm receiving a phantom call.

Additional Information

Reproducing this a few times causes the following to appear in the timeline (Element Android):

grafik

Viewing the decrypted event source shows that they all reference the same call:

{
    "room_id": "!something:some.thing",
    "type": "m.call.reject",
    "content": {
        "version": 1,
        "call_id": "e81b868d-8638-4ec5-ac23-d610888a82e0",
        "party_id": "SOMETHING"
    }
}

After deleting the call that caused all this, the issue isn't reproducible anymore.

Note that all this has only yet been reproducible on Element Desktop.

Operating system

Arch Linux

Application version

Element version: 1.10.6 Olm version: 3.2.8

How did you install the app?

https://flathub.org/apps/details/im.riot.Riot

Homeserver

1.53.0

Will you send logs?

No

@eladyn eladyn added the T-Defect label Mar 3, 2022
@SimonBrandner
Copy link
Contributor

@eladyn, do you agree with this being a duplicate of #4607?

@SimonBrandner SimonBrandner added the X-Needs-Info This issue is blocked awaiting information from the reporter label Mar 3, 2022
@eladyn
Copy link
Author

eladyn commented Mar 3, 2022

The majority of the comments in #4607 seem to suggest that the other issue is actually about Element only ringing for a short time at startup. In my case though, the ringing doesn't stop until I either accept or decline the call. I'm not sure if the original poster was describing my issue or the short ringing (#4607 (comment)). If they were, feel free to close this.

@SimonBrandner SimonBrandner added S-Major Severely degrades major functionality or product features, with no satisfactory workaround A-VoIP O-Uncommon Most users are unlikely to come across this or unexpected workflow and removed X-Needs-Info This issue is blocked awaiting information from the reporter labels Mar 4, 2022
@turt2live
Copy link
Member

Duplicate of #4607

@turt2live turt2live marked this as a duplicate of #4607 Jun 15, 2022
@turt2live turt2live closed this as not planned Won't fix, can't repro, duplicate, stale Jun 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-VoIP O-Uncommon Most users are unlikely to come across this or unexpected workflow S-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Defect
Projects
None yet
Development

No branches or pull requests

3 participants