mirror of
https://github.com/SchildiChat/SchildiChat-android.git
synced 2024-12-12 01:26:13 +01:00
278bba3ada
Verification flows have something called a transaction id. This is a client-set custom ID that identifies the flow and is established by the first message that gets sent out. This transaction ID needs to be kept the same and be part of all events that are sent during the verification flow. To-device requests have something called a transaction id. This is a client-set custom ID that identifies a given request. It is used to ensure idempotency of requests, i.e. retrying to send a request won't result in two events being sent as long as the transaction id is kept the same. This patch removes usage of the first type of transaction ID for the second use-case. This closes: #3589.
2 lines
65 B
Plaintext
2 lines
65 B
Plaintext
Don't use the transaction ID of the verification for the request
|