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
It's unclear if it's the m.call.invite re-appearing during initialSync or being re-paginated in, but we shouldn't be trying to show incoming calls at all until the room has fully synced.
This may be a regression related to the indexeddb stuff.
The text was updated successfully, but these errors were encountered:
I just reproduced this (kept calling between two test clients; hitting reject; refreshing) and worst still the call continued to ring. Hitting reject didn't stop it from ringing.
It's unclear if it's the m.call.invite re-appearing during initialSync or being re-paginated in, but we shouldn't be trying to show incoming calls at all until the room has fully synced.
This may be a regression related to the indexeddb stuff.
The text was updated successfully, but these errors were encountered: