fix: New verification requests on requesting history
If requesting history happens to contain a m.key.verification.request we currently create a new key verification object and push it to the client. This fixes it.
This commit is contained in:
parent
77ca7523d0
commit
62fe7a1704
|
|
@ -135,7 +135,8 @@ class Encryption {
|
||||||
}
|
}
|
||||||
|
|
||||||
Future<void> handleEventUpdate(EventUpdate update) async {
|
Future<void> handleEventUpdate(EventUpdate update) async {
|
||||||
if (update.type == EventUpdateType.ephemeral) {
|
if (update.type == EventUpdateType.ephemeral ||
|
||||||
|
update.type == EventUpdateType.history) {
|
||||||
return;
|
return;
|
||||||
}
|
}
|
||||||
if (update.content['type'].startsWith('m.key.verification.') ||
|
if (update.content['type'].startsWith('m.key.verification.') ||
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue