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 2024-08-02] Dupe detection - Confirm button is below the content instead of page bottom #45831
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.
Launch New Expensify app.
Go to workspace chat.
Submit two same expenses (same amount and merchant).
Go to transaction thread of any expense.
Tap Review duplicates.
Tap Keep this one (any).
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?
👋 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.
changed the title [-] Dupe detection - Confirm button is below the content instead of page bottom[/-][+][HOLD for payment 2024-08-02] Dupe detection - Confirm button is below the content instead of page bottom[/+]on Jul 26, 2024
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:
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:
Activity
melvin-bot commentedon Jul 20, 2024
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 commentedon Jul 20, 2024
👋 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 Jul 20, 2024
Triggered auto assignment to @grgia (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.Krishna2323 commentedon Jul 20, 2024
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.:
largeprop isn't passed toButton.App/src/pages/TransactionDuplicate/Confirmation.tsx
Lines 83 to 88 in fa738c6
ScrollViewcontent container doesn't take full available height.styles.mt2instead ofstyles.autotoButtonelement.What changes do you think we should make in order to solve the problem?
largeprop toButtonelement.contentContainerStyle={styles.flex1}toScrollView.styles.mt2withstyles.autoonButtonelement.What alternative solutions did you explore? (Optional)
style={styles.mb3}fromScrollViewand addcontentContainerStyle={styles.flex1}.ButtonwithFixedFooterand applystyle={[styles.mtAuto]}to `FixedFooter.Buttonor only keep margin top if required.Result
Before fix
After fix
17 remaining items
[-] Dupe detection - Confirm button is below the content instead of page bottom[/-][+][HOLD for payment 2024-08-02] Dupe detection - Confirm button is below the content instead of page bottom[/+]melvin-bot commentedon Jul 26, 2024
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Jul 26, 2024
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:
If no regressions arise, payment will be issued on 2024-08-02. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Jul 26, 2024
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:
sonialiap commentedon Aug 2, 2024
@pecanoro @parasharrajat looks like payment will be handled here, is that correct?
parasharrajat commentedon Aug 2, 2024
Yes, let's close it.