Merge branch 'krille/null-boolean' into 'main'
fix: Workaround for null boolean See merge request famedly/company/frontend/famedlysdk!909
This commit is contained in:
commit
0fae025332
|
|
@ -1813,7 +1813,13 @@ class Client extends MatrixApi {
|
||||||
final deviceKeysList =
|
final deviceKeysList =
|
||||||
_userDeviceKeys[userId] ??= DeviceKeysList(userId, this);
|
_userDeviceKeys[userId] ??= DeviceKeysList(userId, this);
|
||||||
final failure = _keyQueryFailures[userId.domain];
|
final failure = _keyQueryFailures[userId.domain];
|
||||||
if (deviceKeysList.outdated &&
|
|
||||||
|
// deviceKeysList.outdated is not nullable but we have seen this error
|
||||||
|
// in production: `Failed assertion: boolean expression must not be null`
|
||||||
|
// So this could either be a null safety bug in Dart or a result of
|
||||||
|
// using unsound null safety. The extra equal check `!= false` should
|
||||||
|
// save us here.
|
||||||
|
if (deviceKeysList.outdated != false &&
|
||||||
(failure == null ||
|
(failure == null ||
|
||||||
DateTime.now()
|
DateTime.now()
|
||||||
.subtract(Duration(minutes: 5))
|
.subtract(Duration(minutes: 5))
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue