Improve handling of invalid keys on message compose

[sosnovsky]

When user tries to send encrypted message, but stored local keys are invalid (expired or revoked) then we just show Your account keys are not usable for encryption error message:

In this case, before showing error message, we should try to fetch updated keys from EKM and show error only if there are no valid keys on EKM.

[ioanmo226]

Currently, I don't believe retrieving the public key is related to EKM. We only seem to use EKM for fetching and updating private keys, during which we update KeypairRealmObject. However, for retrieving public keys, we use RecipientRealmObject.

Should I add functionality to retrieve public keys from KeypairRealmObject as well?
Or am I misunderstanding something here?

flowcrypt-ios/FlowCrypt/Functionality/Services/Local Contacts Provider/LocalContactsProvider.swift

Line 147 in de5c954

try storage.object(ofType: RecipientRealmObject.self, forPrimaryKey: email)

flowcrypt-ios/FlowCrypt/Functionality/DataManager/Encrypted Storage/EncryptedStorage.swift

Line 194 in 914a16e

let object = try KeypairRealmObject(key, passphrase: passPhrase, source: source, user: user)

In this case, before showing error message, we should try to fetch updated keys from EKM and show error only if there are no valid keys on EKM.

[sosnovsky]

Here I meant retrieving of private keys, as it was reported by customer - some user had expired private key on EKM and couldn't sent encrypted message. Then key on EKM was updated but user still got error keys are not usable for encryption, as updated key wasn't fetched.

So here we should attempt to fetch the latest keys from EKM if sender's local keys can't be used for encryption.

[ioanmo226]

Aha, I see