-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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-04-25] Attachment - Wrong PDF is opened #39833
Comments
Triggered auto assignment to @amyevans ( |
👋 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:
|
@amyevans FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors |
I verified by reverting #39578 locally that it's the source of the regression cc @abzokhattab @hungvu193 @flodnv. Since the package bump PR is tied to a rather non-urgent bug fix I think it makes the most sense to just revert the bump PR, but speak up soon if you disagree. |
PR has been merged but waiting on CP: https://expensify.slack.com/archives/C07J32337/p1712628550724549 |
Hey @amyevans I can reproduce even when I downgrade react-fast-pdf to 1.0.6 |
Screen.Recording.2024-04-09.at.09.14.09.mov |
Can you verify the version is |
For your information, there is an open issue related to the problem where the wrong file is viewed, which can be found at #23546 This may be related to the current issue. |
@amyevans I see, seems like caching. Confirmed it's fixed with 1.0.6. My bad 🤦 |
No worries! |
I confirm this seems to be related to #23546 and the version bump can be a coincidence |
@kidroca I saw you were assigned on that issue, do you have any WIP? So I can test if it solved this issue as well 😄 |
@hungvu193 here's my WIP: |
Awesome! I'll give it a try. Thank you 🙏 |
Testing on: This branch + react-fast-pdf 1.0.8: pr-39930-and-1-0-8.movThe behavior is inconsistent, but it usually seems to do what's in the recording: briefly flashes the wrong attachment before loading the correct (most recent) one. main + react-fast-pdf 1.0.6: main-and-1-0-6.movBug is not reproducible. main + react-fast-pdf 1.0.7: main-and-1-0-7.movBug is reproducible. While perhaps the root cause might be similar to what's being worked on in #39930, I don't think it is coincidental that the bug manifests on 1.0.7 but not on 1.0.6, so I still think proceeding with the revert is the right course of action. Do you all agree or disagree? Cc @Julesssss as well as deployer this week |
Alright I retested on staging following the CP: #39869 (comment). I think we can close this one out, thanks for the discussion! |
Should we open and track an issue for |
Yes, I believe they're working on a patch in the original issue but I left a note (#34816 (comment)) to clarify expectations. |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.62-17 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-04-25. 🎊 |
- Fixed an issue with carousel scrolling in the AttachmentCarousel component - Implemented a new pan gesture for smoother scrolling experience - Adjusted layout calculations for optimal rendering of attachments Related to: - Expensify#23546 - Expensify#39833 - Expensify#22318 - Expensify#21177 - Expensify#31166
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.60-1
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
Issue reported by: Applause - Internal Team
Action Performed:
Expected Result:
The last pdf file should be opened
Actual Result:
The first pdf file is opened
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6442231_1712580406073.Screen_Recording_2024-04-08_at_3.44.37_in_the_afternoon.mp4
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: