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
Currently I am trying to setup e2ee with the new initRustCrypto() everything works as far as I can see however my console is filled with POST requests to /client/v3/keys/upload with recieves error code 400:
{"errcode":"M_UNKNOWN","error":"One time key signed_curve25519:AAAAAAAAAA0 already exists ... "}
It tries to upload the keys everytime we do a SYNC request
For me it is always the same curve and the same string behind the curve, regardless of which account is logged in. In issue #4132 a user reports the same issue but with AAA...8
The text was updated successfully, but these errors were encountered:
It looks like the rust crypto library has forgotten that it has already created a one-time-key for this device with that ID, but this information should be stored in indexeddb.
This could happen if:
you initialise two MatrixClient instances with the same access token, but your indexeddb isn't working (or you have cleared it out somehow), or:
you have called the /login REST API, passing a device ID for a device that already exists.
Currently I am trying to setup e2ee with the new
initRustCrypto()
everything works as far as I can see however my console is filled with POST requests to/client/v3/keys/upload
with recieves error code 400:{"errcode":"M_UNKNOWN","error":"One time key signed_curve25519:AAAAAAAAAA0 already exists ... "}
It tries to upload the keys everytime we do a SYNC request
.
I am starting the client like this:
For me it is always the same curve and the same string behind the curve, regardless of which account is logged in. In issue #4132 a user reports the same issue but with AAA...8
The text was updated successfully, but these errors were encountered: