-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
When Tom tries to verify me, it claims I rejected him, and that he rejected me. Neither is true #12479
Comments
Looking at the rageshake, it looks like there might be two |
Rageshake on Matthews side: https://github.com/matrix-org/riot-web-rageshakes/issues/2303 |
There are two verification requests in the rageshakes: Request 1 ($15825381791905OwmLr:lant.uk)From Matthew's side:
From Tom's side:
Request 2 ($15825383061909HatdB:lant.uk)From Matthew's side:
From Tom's side:
|
In both requests, Matthew's client sent a second (and even third for request 2) |
Looking into what's happening on Matthew's side before the second .accept gets send, there seems to be quite a bit megolm activity before. |
Have been investigating and still not sure why Matthew's client is sending 2 Apart from waiting for more repros and having added more logging, not sure what else to do for now so parking this. |
This turned out to be Matthew's iOS client sending the second .accept, closing. |
Bruno & I just spent a while digging further into this, and spotted that the duplicate .accept()s are coming one from Chrome and the other from iOS. In other words, Riot/iOS (on 0.110 - 20200221165108) was sitting in the background(?) sending rogue .accept()s. I thought we fixed this shortly after FOSDEM? :-/ @manuroe, @SBiOSoftWhare: is this a known issue? It's a really nasty failure mode :( |
Created an issue for Riot iOS, so this one can be closed. |
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
No description provided.
The text was updated successfully, but these errors were encountered: