Ensure E2EE never tracks UnknownError #7304
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We have been using
UnknownError
analytics event to track some types of E2EE errors. This error type is however used for other unrelated events as well (notably VOIP), which makes it impossible to distinguish the area of concern.To solve this we will never use the generic
UnknownError
to track E2EE errors and instead only rely on the existingOlmUnspecifiedError
(even if the "Olm" in the name is misleading). Further details about the error are always present in thecontext
property