[HOLD for payment 2023-06-19] [HOLD for payment 2023-06-15] Group - The IOU details page for split bill doesn't have close button [X]

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

1. Launch App
2. Create Group
3. Open the DM create menu (note below) again and select Split Bill
4. Select all the participants and hit "Split Bill"
5. Tap on the IOU details > try to close it

Expected Result:

The IOU details page should have close button [X]

Actual Result:

The IOU details page for split bill doesn't have close button [X]

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.25.3

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

Bug6083897_RPReplay_Final1686161773.mp4

Expensify/Expensify Issue URL:

Issue reported by: Applause - Internal Team

Slack conversation:

View all open jobs on GitHub

[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.

[melvin-bot]

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

[ahmedGaber93]

Proposal

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

Group - The IOU details page for split bill doesn't have close button [X]

What is the root cause of that problem?

We use header without close button here

App/src/pages/iou/SplitBillDetailsPage.js

Lines 78 to 81 in eb718c0

	<HeaderWithBackButton
	title={props.translate('common.details')}
	shouldShowBackButton={false}
	/>

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

add shouldShowCloseButton and onCloseButtonPress props here like this.

    <HeaderWithBackButton
          title={props.translate('common.details')}
          shouldShowBackButton={false}
          shouldShowCloseButton // <<<<<<<<<<<<<<<<<<<<
          onCloseButtonPress={() => Navigation.dismissModal()} // <<<<<<<<<<<<<<<<<<<<
      />

What alternative solutions did you explore? (Optional)

we can use back button instead of close button by add this props shouldShowBackButton and onBackButtonPress

[melvin-bot]

Looks like something related to react-navigation may have been mentioned in this issue discussion.

As a reminder, please make sure that all proposals are not workarounds and that any and all attempt to fix the issue holistically have been made before proceeding with a solution. Proposals to change our DeprecatedCustomActions.js files should not be accepted.

Feel free to drop a note in #expensify-open-source with any questions.

[dangrous]

So ha, I was just looking into this and was going to write what @ahmedGaber93 wrote . However, what I discovered was that adding shouldShowCloseButton doesn't actually pass the props correctly, it's still just taking the default value. This is also true for the existing shouldShowBackButton={false}. I'm not entirely sure why but that could be the issue.

The new default of false for shouldShowCloseButton was updated here - https://github.com/Expensify/App/pull/18402/files#diff-1e4d0651892fd099137cb93a35cf263dc385cc124164c5c14bcf067fd2f973eaR114 which seems to be causing the issue.

However I'm not sure whether the issue is an incorrect default, or whether something has happened to this component to cause it to no longer take props. cc @mountiny and @MariaHCD since you reviewed the PR. Will look into it more in a second.