You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
If an incoming call rings Element-Android and simultaneously rings Element-Web, and the call is answered on Element-Web, Element-Android continues to ring even though the call has been answered. If the call is dismissed from the android application, the call is terminated on the web session.
To Reproduce
open Element web with account A
Log into Element Android with account A
Use Account B to call Account A
Answer the incoming call to Account A in Element Web, wait to see that Element Android still indicates an incoming call
Decline the incoming call in Element Android after accepting the call (step 4) and see that the call is terminated in the Element Web session
Expected behavior
The call should be connected through Element Web, and Element Android should stop ringing because the call was answered elsewhere. The call should also continue to function in Element Web even if declined in the Element Android session.
Smartphone (please complete the following information):
Device: Google Pixel
OS: Android 10
Additional context
App version and store [1.0.4 - F-Droid]
Homeserver: [jobmachine.org]
The text was updated successfully, but these errors were encountered:
Describe the bug
If an incoming call rings Element-Android and simultaneously rings Element-Web, and the call is answered on Element-Web, Element-Android continues to ring even though the call has been answered. If the call is dismissed from the android application, the call is terminated on the web session.
To Reproduce
Expected behavior
The call should be connected through Element Web, and Element Android should stop ringing because the call was answered elsewhere. The call should also continue to function in Element Web even if declined in the Element Android session.
Smartphone (please complete the following information):
Additional context
The text was updated successfully, but these errors were encountered: