[HOLD for payment 2024-08-02] Dupe detection - Confirm button is below the content instead of page bottom

[m-natarajan]

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

---

Issue found when validating #42571
Version Number: 9.0.10-2
Reproducible in staging?: y
Reproducible in production?: new feature
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:

Preconditon:

• Device font size may need to be reduced.

1. Launch New Expensify app.
2. Go to workspace chat.
3. Submit two same expenses (same amount and merchant).
4. Go to transaction thread of any expense.
5. Tap Review duplicates.
6. Tap Keep this one (any).
7. Proceed to confirmation page.

Expected Result:

Confirm button will be docked to the bottom.

Actual Result:

Confirm button is below the content.

Workaround:

unknown

Platforms:

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

• Android: Native
• Android: mWeb Chrome
• iOS: Native
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Bug6547713_1721437274135.Screen_Recording_20240720_085209_New_Expensify.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @sonialiap

[melvin-bot]

Triggered auto assignment to @sonialiap (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.

[github-actions]

👋 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 @grgia (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

[Krishna2323]

This can be handled here. Posting my proposal from there incase we decide to fix this separately.

Proposal

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

Dupe detection - Green Confirm button is shorter in width

What is the root cause of that problem?

There are two issues here.:

1. Confirmation width/height is shorter.

• large prop isn't passed to Button.

• App/src/pages/TransactionDuplicate/Confirmation.tsx

  Lines 83 to 88 in fa738c6

  	<Button
  	text={translate('common.confirm')}
  	success
  	style={[styles.ph5, styles.mt2]}
  	onPress={mergeDuplicates}
  	/>

2. Confirmation button isn't at the bottom

• ScrollView content container doesn't take full available height.
• We have applied styles.mt2 instead of styles.auto to Button element.

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

• We should add large prop to Button element.
• We need to pass contentContainerStyle={styles.flex1} to ScrollView.
• Replace styles.mt2 with styles.auto on Button element.

What alternative solutions did you explore? (Optional)

• We can remove style={styles.mb3} from ScrollView and add contentContainerStyle={styles.flex1}.
• Wrap Button with FixedFooter and apply style={[styles.mtAuto]} to `FixedFooter.
• Remove style prop from Button or only keep margin top if required.

Result

Before fix

After fix

[mountiny]

cc @pecanoro @JmillsExpensify @parasharrajat

[parasharrajat]

I thought that is by design 😄

[mountiny]

Lets get that confirmed, I can see the reasoning but its against our patterns in the app

[mountiny]

Asked here

[mountiny]

Discussed in Slack this is not a blocker as the feature is behind beta.

We should however dock this to the bottom @kubabutkiewicz @parasharrajat

[kubabutkiewicz]

Hi, I will create PR to fix that issue soon @mountiny @parasharrajat @pecanoro

[pecanoro]

@grgia I am reassigning the issue to myself so I can review and track the fixes since this is for the duplicate detection project that I am handling.

[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 9.0.12-0 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

• Polish: Dupe detection #45890

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

For reference, here are some details about the assignees on this issue:

• @parasharrajat requires payment through NewDot Manual Requests

[melvin-bot]

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:

• [@parasharrajat] The PR that introduced the bug has been identified. Link to the PR:
• [@parasharrajat] 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:
• [@parasharrajat] 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:
• [@parasharrajat] Determine if we should create a regression test for this bug.
• [@parasharrajat] 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.
• [@sonialiap] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:

[sonialiap]

@pecanoro @parasharrajat looks like payment will be handled here, is that correct?

[parasharrajat]

Yes, let's close it.