This repository has been archived by the owner on Apr 12, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 394
E2E: Stale device lists #863
Comments
related to element-hq/element-web#2305. Dunno if we already have a riot-android bug to track this. |
@ylecollen are we using this as the "stale device lists" bug (ie element-hq/element-web#2305) for android? |
25 tasks
@richvdh : yes, let defines this issue as the android "stale device lists" bug . |
So, can I do anything to help this. Any useful logs I could post? This issue is breaking my workflow. |
fixed in version |
reopening this because I think the algorithm we implemented was bogus |
Btw: The Bug I had was fixed but not in this commit. It had something to do with parsing of the key signature. |
we need port matrix-org/matrix-js-sdk#425 / matrix-org/matrix-js-sdk#431 here. |
Theses both issues have been released on Riot versions >= 0.6.10 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I can't aknowledge some keys in my riot client, because the devices don't get listed.
The device information to messages from these devices show "unknown device".
I'm not sure because I don't have too many devices tested, but I think it occurs every time, the device ID starts with a non alphanum char.
The text was updated successfully, but these errors were encountered: