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
Version Number: 1.4.56-0 Reproducible in staging?: y Reproducible in production?: n If this was caught during regression testing, add the test name, ID and link from TestRail:https://applause-ts.slack.com/archives/G01CL838B8T/p1711126060917069 Issue reported by: Applause - Internal Team
Action Performed:
Go to staging.new.expensify.com
Navigate to FAB> Start chat> Enter email address and select it
Expected Result:
Chat should be open immediately and there should be no lagging for conversation history
Actual Result:
When create new 1:1 or group chat chat conversation history is lagging
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
👋 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:
Identify the pull request that introduced this issue and revert it.
Activity
github-actions commentedon Mar 22, 2024
👋 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:
melvin-bot commentedon Mar 22, 2024
Triggered auto assignment to @pecanoro (
Engineering), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.pecanoro commentedon Mar 22, 2024
I don't seem to be able to reproduce this
pecanoro commentedon Mar 22, 2024
Hmm, it takes a bit longer than production but not too bad in my case as the video
pecanoro commentedon Mar 22, 2024
I am not sure which PR could have caused this, I am looking into #37930 and #30269
pecanoro commentedon Mar 25, 2024
It seems to be pretty fast now, we probably CPed some fixes or something related, so closing