You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After social media links were added and clicked on "Update Profile" in the Profile-Settings page, an error toast message from the Backend was displayed
#556
Closed
Preetha007 opened this issue
Nov 26, 2021
· 0 comments
· Fixed by #576
After social media links were added and clicked on "Update Profile" in the Profile-Settings page, an error toast message from the Backend was displayed
Click on Login Button, where user gets redirected to Login page
Enter the Email Id and Password in the Login Page, where the user gets inside the profile in Nullcast
Click on the Avatar icon, where a menu "Settings" gets listed in the popover along with other menus
Click on the "Settings" page. Update or fill all the social media username fields
After updation by clicking on "Update Profile", an error toast message from the Backend was displayed
Expected behavior
After social media links are added and clicked on "Update Profile" in the Profile-Settings page, only success toast messages need to be displayed Recording attached
Desktop: ThinkPad
OS: Linux
Browser: Google Chrome
Version: Version 95.0.4638.54 (Official Build) (64-bit)
Smartphone: Not tested Additional context
Tested in test site
Settings3.mp4
The text was updated successfully, but these errors were encountered:
After social media links were added and clicked on "Update Profile" in the Profile-Settings page, an error toast message from the Backend was displayed
Steps To Reproduce
Expected behavior
After social media links are added and clicked on "Update Profile" in the Profile-Settings page, only success toast messages need to be displayed
Recording attached
Desktop: ThinkPad
OS: Linux
Browser: Google Chrome
Version: Version 95.0.4638.54 (Official Build) (64-bit)
Smartphone: Not tested
Additional context
Tested in test site
Settings3.mp4
The text was updated successfully, but these errors were encountered: