Closed lanitochka17 closed 1 month ago
Triggered auto assignment to @puneetlath (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 #vip-vsp
Just out of curiosity - why is the title in Russian ?
@hannojg sorry, corrected
Job added to Upwork: https://www.upwork.com/jobs/~01b903d59d2cb795a3
Triggered auto assignment to Contributor-plus team member for initial proposal review - @rayane-djouah (External
)
Maybe from https://github.com/Expensify/App/pull/45240, verifying by reverting here https://github.com/Expensify/App/pull/46526
Edit: its fixed with revert π
Conversation is displayed bold in LHN starting from second sent message Unread marker is displayed in the conversation history over messages once away and back to conversation
The condition here https://github.com/Expensify/App/blob/3f025eb2649b99b78d16322032f527f9a8033a68/src/pages/home/report/ReportActionsList.tsx#L467 is wrong in the case of scrollingVerticalOffset.current < MSG_VISIBLE_THRESHOLD
. If that is true
, we need to check reportAction.created > (userActiveSince.current ?? '')
(or >=
) instead of reportAction.created < (userActiveSince.current ?? '')
, because the former means that the report action is created after the user was active on the report, thus should be shown, and isWithinVisibleThreshold
and subsequently shouldDisplay
should be true
const isWithinVisibleThreshold = scrollingVerticalOffset.current < MSG_VISIBLE_THRESHOLD ? reportAction.created > (userActiveSince.current ?? '') : true;
Confirmed that it's fixed by the revert π
@nkdengineer - The isWithinVisibleThreshold
condition that your proposal is pointing to is not a recent change, see the commit that introduced it
@hurali97 @mkhutornyi @grgia I've confirmed that this regression is caused by https://github.com/Expensify/App/pull/45240 as suggested here
Thanks @ishpaul777. Can you put your PR up for review? And I'll merge it and get it CPd.
Hello, i read your job post for github issue. that was fixed?
π£ @tJonPope727! π£ Hey, it seems we donβt have your contributor details yet! You'll only have to do this once, and this is how we'll hire you on Upwork. Please follow these steps:
Contributor details
Your Expensify account email: <REPLACE EMAIL HERE>
Upwork Profile Link: <REPLACE LINK HERE>
Contributor details Your Expensify account email: notmemeapp@gmail.com Upwork Profile Link: https://www.upwork.com/freelancers/~01a5523c1adec76313
β Contributor details stored successfully. Thank you for contributing to Expensify!
you have issues yet, please let me know.
Confirmed that the revert/CP fixed it. Removing blocker labels.
Am i eligible for payment for PR for this https://github.com/Expensify/App/pull/46526
π£ @rayane-djouah π An offer has been automatically sent to your Upwork account for the Reviewer role π Thanks for contributing to the Expensify app!
π£ @ishpaul777 π An offer has been automatically sent to your Upwork account for the Contributor role π Thanks for contributing to the Expensify app!
Offer link Upwork job Please accept the offer and leave a comment on the Github issue letting us know when we can expect a PR to be ready for review π§βπ» Keep in mind: Code of Conduct | Contributing π
This is ready for payment @puneetlath : )
It looks like this is the PR: https://github.com/Expensify/App/pull/45240
It was raised by @ishpaul777 and reviewed by @mkhutornyi, so both are due payment.
Does that sound right?
No, PR was https://github.com/Expensify/App/pull/46526 and it was reviewed by you
Oh I see. Well glad I asked then π
Paid. Thanks @ishpaul777!
Paid. Thanks @ishpaul777!
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.14-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: https://expensify.testrail.io/index.php?/tests/view/4784111 Email or phone of affected tester (no customers): applausetester+83pronin@applause.expensifail.com Issue reported by: Applause - Internal Team
Action Performed:
Expected Result:
Verify the unread marker is not displayed in the conversation history over the new messages Verify the conversation is not bold in LHN
Actual Result:
Conversation is displayed bold in LHN starting from second sent message Unread marker is displayed in the conversation history over messages once away and back to conversation
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/7e6fb0ef-d4d5-4b9e-ab04-ef91256a84f5
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @rayane-djouah