-
Notifications
You must be signed in to change notification settings - Fork 3k
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
[HOLD for payment 2024-01-09] [HOLD for payment 2024-01-05] Mweb/Chrome - IOU - Scan page keeps loading infinitely #33732
Comments
👋 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:
|
Triggered auto assignment to @marcaaron ( |
#32577 is the offending PR confirmed with revert test branch - https://github.com/ishpaul777/App/tree/revert-32577-perf/request-money-tabs-animation |
Thanks @ishpaul777. Will wait to see what @mountiny wants to do here. |
ProposalPlease re-state the problem that we are trying to solve in this issueMweb/Chrome - IOU - Scan page keeps loading infinitely What is the root cause of that problem?This is happening because we disabled animation here for web platforms https://github.com/Expensify/App/pull/32577/files#r1437995158. And we use What changes do you think we should make in order to solve the problem?Remove Result: Screen.Recording.2023-12-29.at.11.08.46.AM.movWhat alternative solutions did you explore? (Optional)We can split |
@kacper-mikolajczak Can you check the above proposal ^ ? |
Thanks @marcaaron I will take over this blocker as deployer |
@kacper-mikolajczak is making the PR |
Hey @shubham1206agra thanks for the proposal, please take a look at the implementation here #33754 and let me know what you think 👍 Quick summary: Based on the investigations from intial proposal by @shubham1206agra, this PR aims to re-implement
This solution uses navigation state (
While investigating behaviour of |
We decided to revert as the fix was not straightforwards and the regression was complete increasing chances of some other issues slipping through |
Reverted and CPed, going to handle this again next week on this issue #31190 |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.19-2 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2024-01-05. 🎊 After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.
For reference, here are some details about the assignees on this issue:
|
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.20-3 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2024-01-09. 🎊 After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.
For reference, here are some details about the assignees on this issue:
|
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: 1.4.19
Reproducible in staging?: Y
Reproducible in production?: N
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: Applause - Internal Team
Slack conversation:
Action Performed:
4.Tap Scan
Expected Result:
Scan page must be displayed properly and it must not load infinitely
Actual Result:
Scan page keeps loading infinitely
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6327927_1703803005223.az_recorder_20231229_032924.mp4
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: