-
Notifications
You must be signed in to change notification settings - Fork 493
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
One time keys upload can try to upload the same key again #3721
Comments
This is not a network management error. I don't know the reason of this error yet but it leads to UISIs. The reason is that the SDK keeps trying to upload its local OTKs and getting the same error until the existing OTK published on the server is consumed. Then, the upload succeeds and an OTK with an already used ID is published on the server. |
This is a mitigation for element-hq/element-ios#3721. But it does not fix the root issue.
This issue is a bit hard to reproduce outside a real usage for severals days. The quickest way I found is to:
As we upload only 1 OTK at the time, at the step #3, we will try to upload a key with an existing id. |
This is a mitigation for element-hq/element-ios#3721. But it does not fix the root issue.
Should be fixed by the merged PR. |
To get "E2EE: One time keys upload can try to upload the same key again" (vector-im#3721)
There is probably a bad management of network errors when uploading them.
The server answers:
The application is then stuck in this configuration and cannot upload new keys.
The error even pops up as a modal if you clear the cache from app settings.
The text was updated successfully, but these errors were encountered: