-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Web - LHN- The workspace name reverts to the default name when you come back online. #17111
Comments
Triggered auto assignment to @sonialiap ( |
Bug0 Triage Checklist (Main S/O)
|
I think this is sort of a dupe of #16090 if this is specifically a bug about the workspace name going back to the old name after you go online. I'm pretty sure this, #16090, and #16776 all probably have the same root cause for the workspace name not properly updating so I think we should focus on #16090 to fix that. This and #16776 also deal with deleting the workspace though so there may be another bug in these flows as well that has to deal with deleting the workspace so if we could isolate what that is exactly from the name change not working that'd be great! |
@sonialiap Whoops! This issue is 2 days overdue. Let's get this updated quick! |
@sonialiap Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
Thanks Bondy! All of those issues seem like they're really closely connected. Since this issue was reported after the others, I am going to close it out as a dupe. If this issue persists after the others are fixed, then we should reopen it. |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Action Performed:
5.Disable the internet connection in the main testing device.
Expected Result:
The name of the workspace should be saved after coming back online.
Actual Result:
The workspace name reverts to the default name when you come back online.
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number: 1.2.96.3
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
Bug6009092_Recording__2098.mp4
Expensify/Expensify Issue URL:
Issue reported by: Applause - internal team
Slack conversation:
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: