Closed m-natarajan closed 1 month ago
Triggered auto assignment to @iwiznia (AutoAssignerNewDotQuality
)
Triggered auto assignment to @sonialiap (Bug
), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.
LHN not displayed after page refresh from settings page. Also, menu options inside the about page are not clickable.
Coin animation loading freezes the page.
We can do an async load of the animation in this way:
Add the below in Lottie/index.tsx:
const [animationFile, setAnimationFile] = useState<string | AnimationObject | {uri: string}>();
useEffect(() => {
setAnimationFile(source.file);
}, [setAnimationFile, source.file]);
Now, update to return the below:
animationFile ? <LottieView
// eslint-disable-next-line react/jsx-props-no-spreading
{...props}
source={animationFile}
ref={ref}
style={[aspectRatioStyle, props.style]}
webStyle={{...aspectRatioStyle, ...webStyle}}
onAnimationFailure={() => setIsError(true)}
/> : null
This will fix it for all usages of Lottie animations.
Thank @ShridharGoel proposal, but this issue also happens on other settings screens that use Lottie. This issue only started occurring in a few recent releases, so could you please find the offending PR?
@suneox It has started happening because we have switched to concurrent mode. We can fix this at all places using a common base logic for Lottie animations.
@suneox It has started happening because we have switched to concurrent mode.
@ShridharGoel Thank you. I also tried reverting the code before the merge commit #42592, and the issue doesn’t happen. It only occurs after commit d047467a
enabled React concurrent mode.
We can fix this at all places using a common base logic for Lottie animations.
We don’t need to fix this at all places using Lottie; we just need to fix it in Lottie/index.tsx.
@iwiznia We can fix this issue based on this proposal and implement the fix in Lottie/index.tsx
. I have tested it, and it works as expected.
We don’t need to fix this at all places using Lottie; we just need to fix it in Lottie/index.tsx.
Yes, that's what I meant by the common base logic. Will update to include code example.
Waiting for @ShridharGoel to create the PR.
Will open PR by tomorrow.
@sonialiap Should this have the "High Priority" label since it was marked as critical?
Reviewing
label has been removed, please complete the "BugZero Checklist".
The solution for this issue has been :rocket: deployed to production :rocket: in version 9.0.7-8 and is now subject to a 7-day regression period :calendar:. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2024-07-24. :confetti_ball:
For reference, here are some details about the assignees on this issue:
BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
Payment summary:
- @suneox $250 - offer sent in upwork
@sonialiap Thank you, I have accepted an offer
[Upwork Job]()
This issue was Critical and High Priority so I've adjusted the payouts to $500
This issue was Critical and High Priority so I've adjusted the payouts to $500
Thank you. I really appreciate your recognition of our task.
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.4-0 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 Expensify/Expensify Issue URL: Issue reported by: @suneox Slack conversation: https://expensify.slack.com/archives/C05LX9D6E07/p1720062549074999
Action Performed:
Expected Result:
Page reloads with out any issue
Actual Result:
LHN menu not displayed until navigated to other menu icon
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
https://github.com/Expensify/App/assets/38435837/4e9d1846-c1fa-4a64-92a8-9aa017da1732
https://github.com/Expensify/App/assets/38435837/59988534-303d-43c1-9f52-e2a91f63d275
Add any screenshot/video evidence
View all open jobs on GitHub
Issue Owner
Current Issue Owner: @sonialiap