[HOLD for payment 2023-08-10] [HOLD for payment 2023-08-08] IOU - When a new IOU is opened, the sum of the previous IOU is displayed in the modal window

[lanitochka17]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Action Performed:

Preconditions:
Start creating an IOU, but close the modal window at the moment you select a contact

1. Open https://staging.new.expensify.com/

2. Click on the "Global action" button (Big green plus button in LHN)

3. Click on "Request money"

Expected Result:

The amount of the previous IOU should not be saved when opening a new IOU

Actual Result:

When opening a new IOU in the modal window, the amount of the previous uncompleted IOU has already been entered

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

• Android / native
• Android / Chrome
• iOS / native
• iOS / Safari
• MacOS / Chrome / Safari
• MacOS / Desktop

Version Number: 1.3.48.0

Reproducible in staging?: Yes

Reproducible in production?: No

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

Notes/Photos/Videos: Any additional supporting documentation

Bug6148717_Recording_Regression_23945_All.mp4

Expensify/Expensify Issue URL:

Issue reported by: Applause - Internal Tam / @Natnael-Guchima

Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1690830970030189?thread_ts=1690829632.233769&cid=C049HHMV9SM

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @marcaaron (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

[OSBotify]

👋 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:

1. Identify the pull request that introduced this issue and revert it.
2. Find someone who can quickly fix the issue.
3. Fix the issue yourself.

[marcaaron]

No idea which PR might have introduced this. Nothing obvious stands out. I'd maybe check to see if the recent Onyx changes have something to do with it first.

[ahmdshrif]

I can't repo this on main .. but it's repo in staging. looks like there is a PR fixed it.

Screen.Recording.2023-08-01.at.3.34.57.PM.mov

[shubham1206agra]

No idea which PR might have introduced this. Nothing obvious stands out. I'd maybe check to see if the recent Onyx changes have something to do with it first.

This PR #23749 introduces the issue.

[shubham1206agra]

Proposal

Please re-state the problem that we are trying to solve in this issue.

IOU - When a new IOU is opened, the sum of the previous IOU is displayed in the modal window

What is the root cause of that problem?

As I have discussed with @hannojg on slack. This issue #23749 creates read faster than writes, due to this,

App/src/libs/actions/IOU.js

Line 1441 in 6c9e459

function startMoneyRequest(iouType, reportID = '') {

depends on

App/src/libs/actions/IOU.js

Lines 64 to 72 in 6c9e459

	function resetMoneyRequestInfo(id = '') {
	Onyx.merge(ONYXKEYS.IOU, {
	id,
	amount: 0,
	currency: lodashGet(currentUserPersonalDetails, 'localCurrencyCode', CONST.CURRENCY.USD),
	comment: '',
	participants: [],
	});
	}

.

As Onyx.update is slow, at MoneyRequestAmountPage older values populate the page due to read cached behaviour.

What changes do you think we should make in order to solve the problem?

Since Onyx.update returns a promise, we can chain

App/src/libs/actions/IOU.js

Line 1443 in 6c9e459

Navigation.navigate(ROUTES.getMoneyRequestRoute(iouType, reportID));

under a .then so we make sure that MoneyRequestAmountPage opens with latest values.

What alternative solutions did you explore? (Optional)

N/A

[hannojg]

The proposal looks valid to me, and fixes the issue, yes!

[hannojg]

We will revert the PR causing the regression and make a separate PR that will include all the fixes. Your proposal will be incorporated in that PR.
Not sure how we handle compensation in that case (cc @Beamanator as we were talking about this) ?

[melvin-bot]

⚠️ Looks like this issue was linked to a Deploy Blocker here

If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

If a regression has occurred and you are the assigned CM follow the instructions here.

If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

[Beamanator]

@hannojg yeah good question, I feel like we should collapse all of these issues into 1 😅 I think it's fair to compensate if we use their solution 👍

[melvin-bot]

⚠️ Looks like this issue was linked to a Deploy Blocker here

If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

If a regression has occurred and you are the assigned CM follow the instructions here.

If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

[melvin-bot]

⚠️ Looks like this issue was linked to a Deploy Blocker here

If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

If a regression has occurred and you are the assigned CM follow the instructions here.

If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

[Beamanator]

Should be fixed now, as of #24003

[melvin-bot]

Reviewing label has been removed, please complete the "BugZero Checklist".

[melvin-bot]

The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.48-5 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

• [CP Staging] [Revert] Perf/onyx upgrade use cache directly #24003

If no regressions arise, payment will be issued on 2023-08-08. 🎊

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

As a reminder, here are the bonuses/penalties that should be applied for any External issue:

• Merged PR within 3 business days of assignment - 50% bonus
• Merged PR more than 9 business days after assignment - 50% penalty

[melvin-bot]

The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.49-3 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

• [CP Staging] [Revert] Perf/onyx upgrade use cache directly #24003

If no regressions arise, payment will be issued on 2023-08-10. 🎊

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

As a reminder, here are the bonuses/penalties that should be applied for any External issue:

• Merged PR within 3 business days of assignment - 50% bonus
• Merged PR more than 9 business days after assignment - 50% penalty

[Natnael-Guchima]

A gentle bump for reporting payment @Beamanator 🙂

[Beamanator]

@marcaaron can you help get a BZ assigned to sort out payment? 🙏

[melvin-bot]

Triggered auto assignment to @slafortune (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

[melvin-bot]

Bug0 Triage Checklist (Main S/O)

• This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
• This bug is not a duplicate report (check E/App issues and #expensify-bugs)
  • If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead
• This bug is reproducible using the reproduction steps in the OP. S/O
  • If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
  • If the reproduction steps aren't clear and you determine the correct steps, please update the OP.
• This issue is filled out as thoroughly and clearly as possible
  • Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.
• I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

[marcaaron]

@slafortune can you help with #23973 (comment) 🙏

[slafortune]

External issue reporter - @Natnael-Guchima $250 - OFFER sent
Contributor that fixed the issue - NA
Contributor+ that helped on the issue and/or PR - NA

[Natnael-Guchima]

Accepted the offer. Thanks @slafortune