Describe the bug:
When adding a contact that does not exist in the pod, an exception message is displayed on the web page instead of informing the user that the contact could not be found. The exception message is long and likely would not make sense to an end user.
Current Error Message:
Add contact failed. Reason: Fetching the Resource at [http://localhost:3000/test-name/profile/card#me] failed: [404] [Not Found] <b0> <http://purl.org/dc/terms/title> "NotFoundHttpError"; <http://purl.org/dc/terms/description> "".
Expected behavior:
If the user adds a contact that does not exist, the displayed message should indicate that the contact could not be found in the pod. The message could further inform the user to ensure the contact's name matches the username the contact signed up for in the same pod.
Actual Behavior:
If the user adds a contact that does not exist, the displayed message includes technical information that is unhelpful to end users.
Screenshots:
To Reproduce:
Steps to reproduce the behavior:
- Login and navigate to Add Contact
- Fill in the OIDC Provider and a bogus username
- Hit add contact
- See error
Desktop (please complete the following information):
- OS: Fedora 41, KDE Plasma 6.2.3
- Browser: Firefox
- Version: 132.0.1 (64-bit)
Possible Fix:
If the caught exception notes that a correctly formatted username was not found, then the message should indicate the user does not exist or could not be found.
Additional context:
This has only been tested with a local pod. Testing with community pods is yet to be tested.
Describe the bug:
When adding a contact that does not exist in the pod, an exception message is displayed on the web page instead of informing the user that the contact could not be found. The exception message is long and likely would not make sense to an end user.
Current Error Message:
Add contact failed. Reason: Fetching the Resource at [http://localhost:3000/test-name/profile/card#me] failed: [404] [Not Found] <b0> <http://purl.org/dc/terms/title> "NotFoundHttpError"; <http://purl.org/dc/terms/description> "".Expected behavior:
If the user adds a contact that does not exist, the displayed message should indicate that the contact could not be found in the pod. The message could further inform the user to ensure the contact's name matches the username the contact signed up for in the same pod.
Actual Behavior:
If the user adds a contact that does not exist, the displayed message includes technical information that is unhelpful to end users.
Screenshots:
To Reproduce:
Steps to reproduce the behavior:
Desktop (please complete the following information):
Possible Fix:
If the caught exception notes that a correctly formatted username was not found, then the message should indicate the user does not exist or could not be found.
Additional context:
This has only been tested with a local pod. Testing with community pods is yet to be tested.