You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[$500] Message "Receipt pending match with credit card." not displayed. #42563
Version Number: 1.4.75-0 Reproducible in staging?: Y Reproducible in production?: Y 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):rybkina+052324n@gmail.com Issue reported by: Applause - Internal Team
@dylanexpensify this issue was created 2 weeks ago. Are we close to a solution? Let's make sure we're treating this as a top priority. Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks!
This issue has not been updated in over 15 days. @slafortune, @aimane-chnaif eroding to Monthly issue.
P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do!
📣 @dominictb 🎉 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 📖
After investigating carefully this issue and #40354 conversation history, it turned out that QA misunderstood the reproduction steps. They need to manually mock data for RTER violation to reproduce it. But as deducted from the videos in OP, they misunderstood the mock data step (i.e. they did not do it, from 0:32). So obviously the violation message didn't show in that case.
These steps in this issue OP are just to create sample money requests to mock data:
Create at least 2 Money Request on a single chat
Create a single Money Request on a different chat
I tried to mock the data correctly as mentioned in #40354 OP and it did show the violation message.
@slafortune I believe we can close this issue without any further action.
Activity
melvin-bot commentedon May 23, 2024
Triggered auto assignment to @dylanexpensify (
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.melvin-bot commentedon May 27, 2024
@dylanexpensify Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!
dylanexpensify commentedon May 29, 2024
Sorry will review!
melvin-bot commentedon Jun 3, 2024
@dylanexpensify Huh... This is 4 days overdue. Who can take care of this?
dylanexpensify commentedon Jun 5, 2024
Hmm, trying again tday
melvin-bot commentedon Jun 6, 2024
@dylanexpensify this issue was created 2 weeks ago. Are we close to a solution? Let's make sure we're treating this as a top priority. Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks!
melvin-bot commentedon Jun 10, 2024
@dylanexpensify Eep! 4 days overdue now. Issues have feelings too...
159 remaining items
melvin-bot commentedon Nov 29, 2024
This issue has not been updated in over 15 days. @slafortune, @aimane-chnaif eroding to Monthly issue.
P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do!
melvin-bot commentedon Dec 3, 2024
📣 @dominictb 🎉 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 📖
slafortune commentedon Dec 3, 2024
Sorry for the delay @dominictb I've assigned you now.
slafortune commentedon Dec 30, 2024
@dominictb, what is the status of this? Still reproducible?
dominictb commentedon Jan 15, 2025
Yes it's still reproducible and we're waiting for proposals.
NJ-2020 commentedon Jan 15, 2025
@dominictb Could you please share the reproduction steps?
dominictb commentedon Jan 16, 2025
After investigating carefully this issue and #40354 conversation history, it turned out that QA misunderstood the reproduction steps. They need to manually mock data for RTER violation to reproduce it. But as deducted from the videos in OP, they misunderstood the mock data step (i.e. they did not do it, from 0:32). So obviously the violation message didn't show in that case.
These steps in this issue OP are just to create sample money requests to mock data:
I tried to mock the data correctly as mentioned in #40354 OP and it did show the violation message.
@slafortune I believe we can close this issue without any further action.