Make error messages user-friendly when adding contacts. #706
Conversation
This file contains hidden or 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
leekahung
approved these changes
Aug 23, 2025
Contributor
leekahung
left a comment
leekahung
left a comment
There was a problem hiding this comment.
This looks great, thanks for adding this.
Saw the issue with the GitHub actions checks, should be fine with what you added in the other PR when we merge that.
This was referenced Aug 23, 2025
Merged
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.
This PR:
Resolves #697
This PR updates the error handling in the Add Contact flow to ensure that users see clear, user-friendly error messages instead of raw exception output.
1. Replaced raw exception messages with a getUserFriendlyError helper that maps common errors (401, 403, 404, network) into readable notifications for end users.
Screenshots (if applicable):