Can't login until all data is erased: Session Meta was already set

[jmartinesp]

Sometimes I've come across some issues when signing in that left the login process in an intermediate broken state where the user can't log in again no matter what they try, until all the data related to the Rust SDK is deleted.

The error message is consistent, and it'll be returned on every single login attempt after the first failed one:

org.matrix.rust.sdk: matrix_sdk::http_client: Got response | crates/matrix-sdk/src/http_client/mod.rs:192 | spans: login{method="identifier and password"} > send{server_versions=[V1_0, V1_1, V1_2, V1_3, V1_4, V1_5, V1_6, V1_7, V1_8, V1_9, V1_10] config=RequestConfig { timeout: 30s, retry_limit: 3 } request_id="REQ-5" method=POST uri="https://matrix-client.matrix.org/_matrix/client/v3/login" request_size="155 B" status=200 response_size="233 B"}
05-31 12:21:37.808 29417 29504 E org.matrix.rust.sdk: log: thread '<unnamed>' panicked at 'Session Meta was already set: SessionMeta { user_id: "@jorgem_test:matrix.org", device_id: "WTXEBDWXNA" }': /tmp/tmpe1vb2k3c/crates/matrix-sdk-base/src/store/mod.rs:193

The rest of the stacktrace is not much helpful since the SDK doesn't contain the debug symbols. While ideally we'd want to fix the issues that cause this state (I'll try to find the logs for those too), could we have some way to reset this broken state so at least the users won't be stuck?

[toshanmugaraj]

yes same here