Open lanitochka17 opened 5 days ago
Triggered auto assignment to @francoisl (DeployBlockerCash
), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.
:wave: 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:
We think that this bug might be related to #wave-collect - Release 1
I also notice a short delay on production, albeit shorter than on staging. Roughly like 50ms on production, and 200ms on staging. It doesn't look like there's any API call happening when returning to the parent report, so it's probably not due to anything changing in Onyx.
There's nothing that stands out in the checklist so I'm going to open this up for proposals. Doesn't seem worthy of blocking though.
Job added to Upwork: https://www.upwork.com/jobs/~021839062492993280361
Triggered auto assignment to Contributor-plus team member for initial proposal review - @fedirjh (External
)
The second expense preview is hidden briefly after returning to expense report via header subtitle
loadNewerChats
is called with a delay here because we wrapped it in InteractionManager.runAfterInteractions
and requestAnimationFrame
That leads isFirstLinkedActionRender
ref being updated to false
after more delay here
As a result, it takes more time to change reportActions
from [preview1]
(isFirstLinkedActionRender.current
is true
) to [preview1, preview 2]
(isFirstLinkedActionRender
is changed to false
)
We use goBack
with shouldEnforceFallback
as true
to ensure we navigate to the previous report instead of going back. Then because it's a new screen in the stack, this bug happens as the reason at the point 1.
Navigation.isNavigationReady
here instead of passing shouldEnforceFallback
param as true
Navigation.isNavigationReady().then(() => {
Navigation.goBack(ROUTES.REPORT_WITH_ID.getRoute(parentReportID, parentReportActionID));
});
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Version Number: 9.0.40-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: N/A Email or phone of affected tester (no customers): applausetester+kh230901@applause.expensifail.com Issue reported by: Applause - Internal Team
Action Performed:
Expected Result:
The second expense preview will show instantly after returning to expense report via header subtitle (production behavior)
Actual Result:
The second expense preview is hidden briefly after returning to expense report via header subtitle
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
https://github.com/user-attachments/assets/e1087dab-4a1b-4535-817f-34e0dff15c91
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @fedirjh