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

VoIP call "continues" after hanging up #5189

Closed
kittykat opened this issue Nov 24, 2021 · 3 comments · Fixed by matrix-org/matrix-ios-sdk#1420
Closed

VoIP call "continues" after hanging up #5189

kittykat opened this issue Nov 24, 2021 · 3 comments · Fixed by matrix-org/matrix-ios-sdk#1420
Assignees
Labels
A-VoIP O-Occasional Affects or can be seen by some users regularly or most users rarely S-Critical Prevents work, causes data loss and/or has no workaround T-Defect Something isn't working: bugs, crashes, hangs and other reported problems Z-Ready This issue is ready for development Z-WTF WTF issues: High impact, Low Effort

Comments

@kittykat
Copy link
Contributor

kittykat commented Nov 24, 2021

Steps to reproduce

  1. Receive a call (tested from Android)
  2. Accept from the timeline
  3. Continue seeing overlay at the top of the screen showing an incoming phone and hear ringing
  4. Accept call
  5. Hang up in timeline
  6. See call hang up in timeline
  7. Look at the phone some time later to see call still showing as ongoing

Outcome

What did you expect?

Call hangs up

What happened instead?

Phone still shows call as ongoing (in reality, I don't think that it's ongoing and there is no call showing in Element Web or on the recipient's side)

IMG_20211124_122423

Your phone model

iPhone X

Operating system version

14.6

Application version

1.6.8

Will you send logs?

No

@kittykat kittykat added T-Defect Something isn't working: bugs, crashes, hangs and other reported problems A-VoIP S-Critical Prevents work, causes data loss and/or has no workaround labels Nov 24, 2021
@RiotRobot RiotRobot added this to Incoming in Issue triage Nov 24, 2021
@pixlwave pixlwave added the O-Occasional Affects or can be seen by some users regularly or most users rarely label Nov 25, 2021
@RiotRobot RiotRobot added this to P1 in iOS App Team Nov 25, 2021
@pixlwave
Copy link
Contributor

@kittykat Is this on iOS 15? In that photo it is showing a system call rather than one inside of the app so would be useful to know this.

@pixlwave pixlwave added the X-Needs-Info This issue is blocked pending further information from the reporter label Nov 25, 2021
@github-actions github-actions bot moved this from Incoming to Need info in Issue triage Nov 25, 2021
@kittykat
Copy link
Contributor Author

@pixlwave 14.6, updated description with more info about phone.

@pixlwave pixlwave removed the X-Needs-Info This issue is blocked pending further information from the reporter label Nov 25, 2021
@RiotRobot RiotRobot moved this from Need info to Triaged in Issue triage Nov 25, 2021
@daniellekirkwood daniellekirkwood added the Z-WTF WTF issues: High impact, Low Effort label Jan 10, 2022
@daniellekirkwood daniellekirkwood moved this from P1 to WTFs & Papercuts in iOS App Team Jan 10, 2022
@daniellekirkwood daniellekirkwood added the Z-Ready This issue is ready for development label Jan 26, 2022
@RiotRobot RiotRobot moved this from WTFs & Papercuts to P1 in iOS App Team Jan 26, 2022
@daniellekirkwood daniellekirkwood moved this from Important Issues & Topics (P1) to WTFs & Papercuts in iOS App Team Feb 8, 2022
@aringenbach aringenbach self-assigned this Feb 24, 2022
@aringenbach aringenbach removed their assignment Mar 17, 2022
@Anderas
Copy link
Contributor

Anderas commented Mar 22, 2022

If I understand the description of this issue correctly, it can actually be replicated in far simpler way:

  1. Recieve a call anywhere in the app
  2. Accept the call from the in-app overlay header (no need to interact with the timeline)
  3. Hang up the call

=> The app hungup the call, but the system still shows it as ongoing.

It is not 100% reproducible, but happens often enough. It also suggests that this isn't an issue with double-tapping accept, but rather with accepting from the overlay in general

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-VoIP O-Occasional Affects or can be seen by some users regularly or most users rarely S-Critical Prevents work, causes data loss and/or has no workaround T-Defect Something isn't working: bugs, crashes, hangs and other reported problems Z-Ready This issue is ready for development Z-WTF WTF issues: High impact, Low Effort
Projects
Development

Successfully merging a pull request may close this issue.

5 participants