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
[HOLD for payment 2023-12-20] [$500] IOU - User is redirected to participant selection page after adding a receipt #32834
Version Number: v1.4.11-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: 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:
Launch New Expensify app.
Tap + > Request money > Manual.
Enter amount and select a participant.
On the confirmation page, tap 3-dot menu > Add receipt.
Add a receipt from gallery (not able to reproduce issue if photo is taken from camera).
Expected Result:
After adding a receipt, user will be redirected to confirmation page.
Actual Result:
After adding a receipt, user is redirected to participant selection page.
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
👋 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:
Identify the pull request that introduced this issue and revert it.
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.11-25 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 2023-12-20. 🎊
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.
External issue reporter
Contributor that fixed the issue
Contributor+ that helped on the issue and/or PR
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:
[@c3024] The PR that introduced the bug has been identified. Link to the PR: No specific PR caused this. Similar logic is used in different components however in this case value was undefined causing the bug.
[@c3024] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment: N/A
[@c3024] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion: N/A. this is an edge case
[@c3024] Determine if we should create a regression test for this bug.
[@c3024] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.
[@joekaufmanexpensify] Link the GH issue for creating/updating the regression test once above steps have been agreed upon: N/A
[@c3024] The PR that introduced the bug has been identified. Link to the PR: No specific PR caused this. Similar logic is used in different components however in this case value was undefined causing the bug.
[@c3024] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment: N/A
[@c3024] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion: N/A. this is an edge case
[@c3024] Determine if we should create a regression test for this bug: Not necessary as this is a minor change and does not affect anything else.
[@c3024] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again. N/A
Activity
github-actions commentedon Dec 11, 2023
👋 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:
melvin-bot commentedon Dec 11, 2023
Triggered auto assignment to @marcochavezf (
Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.abzokhattab commentedon Dec 11, 2023
Proposal
Please re-state the problem that we are trying to solve in this issue.
USer is redirected to particpants page after adding a receipt
What is the root cause of that problem?
in case of mobile we redirect the user to selection page :
App/src/pages/iou/request/step/IOURequestStepScan/index.native.js
Line 245 in 4c61f05
What changes do you think we should make in order to solve the problem?
redirect the user to the confirmation page
also we need to update this:
App/src/pages/iou/request/MoneyTemporaryForRefactorRequestParticipantsSelector.js
Line 221 in a630084
to use lodashGet because it thows an error when adding a recept in IOS:
marcochavezf commentedon Dec 11, 2023
Thanks @abzokhattab, the proposed solution looks good, assigning you 🚀
melvin-bot commentedon Dec 11, 2023
Triggered auto assignment to @joekaufmanexpensify (
Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.melvin-bot commentedon Dec 11, 2023
Bug0 Triage Checklist (Main S/O)
Platformsin OP are ✅)28 remaining items
melvin-bot commentedon Dec 13, 2023
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Dec 13, 2023
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.11-25 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 2023-12-20. 🎊
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:
melvin-bot commentedon Dec 13, 2023
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:
joekaufmanexpensify commentedon Dec 18, 2023
@c3024 could you please handle the BZ checklist so we can prep to issue payment on Wednesday? TY!
joekaufmanexpensify commentedon Dec 19, 2023
Bumped in Slack
c3024 commentedon Dec 19, 2023
joekaufmanexpensify commentedon Dec 19, 2023
BZ checklist complete. All set to issue payment tomorrow, which is:
joekaufmanexpensify commentedon Dec 20, 2023
All set to issue payment.
joekaufmanexpensify commentedon Dec 20, 2023
@abzokhattab $500 sent and contract ended!
joekaufmanexpensify commentedon Dec 20, 2023
@c3024 $500 sent and contract ended!
joekaufmanexpensify commentedon Dec 20, 2023
Upwork job removed.
joekaufmanexpensify commentedon Dec 20, 2023
All set. Thanks everyone!