fix: handle NoCommonProtocol error while starting conversation #3120
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
borichellow
requested review from
alexandreferris,
MohamadJaara,
vitorhugods,
Garzas and
saleniuk
Test Results825 tests 825 ✅ 9m 33s ⏱️ Results for commit bdff00f. ♻️ This comment has been updated with latest results. |
|
APKs built during tests are available here. Scroll down to Artifacts! |
vitorhugods
approved these changes
Jun 24, 2024
…rror-while-starting-conversation
|
|
APKs built during tests are available here. Scroll down to Artifacts! |
Garzas
approved these changes
Jun 25, 2024
borichellow
deleted the
fix/handle-no-common-protocol-error-while-starting-conversation
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What's new in this PR?
Issues
When user is trying to start 1o1 conversation with user that has no common protocol with, the error is no displayed anyhow.
Causes (Optional)
Error handling in creating conversation was implemented only for NoKeypackages error.
Solutions
Add handling for all errors (specific texts for
NoKeypackagesandNoCommonProtocolerrors and some default text for other errors.)Attachments (Optional)