Skip to content
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 - Lost Chat with a new user page after switch the tab #7412

Closed
kbecciv opened this issue Jan 26, 2022 · 16 comments
Closed

Web - Lost Chat with a new user page after switch the tab #7412

kbecciv opened this issue Jan 26, 2022 · 16 comments

Comments

@kbecciv
Copy link

kbecciv commented Jan 26, 2022

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:

  1. Go to https://staging.new.expensify.com
  2. Log in with any account
  3. Create a new room
  4. Click on Plus button and Click Create New Chat
  5. Select any user which you have never chat before
  6. Move to another tap ( I used a google)
  7. Back to https://staging.new.expensify.com

Expected Result:

After switch the tab the Chat with a user should be displayed in https://staging.new.expensify.com

Actual Result:

Lost Chat with a new user page after switch the tab

Workaround:

Unknown

Platform:

Where is this issue occurring?

  • Web

Version Number: 1.1.31.1

Reproducible in staging?: Yes

Reproducible in production?: No

Logs: https://stackoverflow.com/c/expensify/questions/4856

Recording.135.mp4

Notes/Photos/Videos: Any additional supporting documentation

Expensify/Expensify Issue URL:

Issue reported by: Applause

Slack conversation:

View all open jobs on GitHub

@kbecciv kbecciv added the DeployBlockerCash This issue or pull request should block deployment label Jan 26, 2022
@OSBotify
Copy link
Contributor

👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open StagingDeployCash deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

  1. Identify the pull request that introduced this issue and revert it.
  2. Find someone who can quickly fix the issue.
  3. Fix the issue yourself.

@MelvinBot
Copy link

Triggered auto assignment to @joelbettner (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

@joelbettner
Copy link
Contributor

Thanks @roryabraham!

@roryabraham
Copy link
Contributor

To investigate, I'm starting by looking at the difference between the staging and production branches to identify a list of pull requests that seem like possible culprits for this regression.

@roryabraham
Copy link
Contributor

@roryabraham
Copy link
Contributor

Okay, I'm actually not able to reproduce this issue on main

@roryabraham
Copy link
Contributor

Is creating a room first a necessary step to reproduce this issue? Without creating a new room first, I can't reproduce this issue on staging either.

@roryabraham
Copy link
Contributor

Added myself to the policyRooms beta so I can test this further. But so far I have been unable to reproduce this issue.

@roryabraham
Copy link
Contributor

Yep, still not able to reproduce this. Can we retest? I'm tempted to close this.

@mvtglobally
Copy link

@roryabraham checking if we can get more info

@mvtglobally
Copy link

mvtglobally commented Jan 27, 2022

@roryabraham, It looks like whatever CPs we pushed in the recent build fixed the issue, so Some Team members are no longer able to repro as well with 1.1.33-3. We will keep an eye

Recording.141.1.mp4

While another still can. Really not sure

Recording.167.mp4

@roryabraham
Copy link
Contributor

Okay, I'm going to demote this from DeployBlocker and make it a weekly. Please add it to the KI retests for now.

@roryabraham roryabraham added Weekly KSv2 and removed DeployBlockerCash This issue or pull request should block deployment Hourly KSv2 labels Jan 27, 2022
@roryabraham roryabraham removed their assignment Jan 27, 2022
@mvtglobally
Copy link

Issue not reproducible during KI retests. (First week)

@mvtglobally
Copy link

Issue not reproducible during KI retests. (Second week)

@MelvinBot
Copy link

This issue has not been updated in over 15 days. eroding to Monthly issue.

P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do!

@MelvinBot MelvinBot added Monthly KSv2 and removed Weekly KSv2 labels Feb 21, 2022
@MelvinBot MelvinBot removed the Overdue label Feb 21, 2022
@mvtglobally
Copy link

Issue not reproducible during KI retests. (Third week) Closing

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants