[Due for payment 2025-10-27] [$250] Missing padding between next steps message and selected button

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

---

Version Number: 9.2.27-4
Reproducible in staging?: Y
Reproducible in production?: Y
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: @dukenv0307
Slack conversation (hyperlinked to channel name): #Expensify Bugs

Action Performed:

1. Create a workspace
2. Submit 2 expenses
3. Resize the window
4. Select an expense
5. Observe that there is no padding between next steps message and selected button

Expected Result:

Enough padding between next steps message and selected button

Actual Result:

No padding between next steps message and selected button

Workaround:

Unknown

Platforms:

Select the officially supported platforms where the issue was reproduced:

• Android: App
• Android: mWeb Chrome
• iOS: App
• iOS: mWeb Safari
• iOS: mWeb Chrome
• Windows: Chrome
• MacOS: Chrome / Safari
• MacOS: Desktop

Platforms Tested:

On which of our officially supported platforms was this issue tested:

• Android: App
• Android: mWeb Chrome
• iOS: App
• iOS: mWeb Safari
• iOS: mWeb Chrome
• Windows: Chrome
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

bug.1.mov

Recording.1742.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021976009232925957632
• Upwork Job ID: 1976009232925957632
• Last Price Increase: 2025-10-08
• Automatic offers:
• FitseTLT | Reviewer | 109056076
• daledah | Contributor | 109056077

Issue Owner

Current Issue Owner: @alexpensify

[melvin-bot]

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

[daledah]

Proposal

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

Missing padding between next steps message and selected button

What is the root cause of that problem?

When we show the selected button, we are missing the bottom padding here.

App/src/components/MoneyReportHeader.tsx

Lines 1252 to 1263 in 977be2e

	{!shouldDisplayNarrowMoreButton &&
	(shouldShowSelectedTransactionsButton ? (
	<View style={[styles.dFlex, styles.w100, styles.ph5]}>
	<ButtonWithDropdownMenu
	onPress={() => null}
	options={selectedTransactionsOptions}
	customText={translate('workspace.common.selected', {count: selectedTransactionIDs.length})}
	isSplitButton={false}
	shouldAlwaysShowDropdownMenu
	wrapperStyle={styles.w100}
	/>
	</View>

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

We simply need to add styles.pb3 where we show the selected button

App/src/components/MoneyReportHeader.tsx

Line 1254 in 977be2e

<View style={[styles.dFlex, styles.w100, styles.ph5]}>

What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?

None UI bug

What alternative solutions did you explore? (Optional)

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~021976009232925957632

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @FitseTLT (External)

[alexpensify]

@FitseTLT - When you have a chance, please review if one of these proposals will resolve the issue. Thanks!

[Eskalifer1]

Proposal

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

Missing padding between next steps message and selected button

What is the root cause of that problem?

We dont pass any paddingBottom here:

App/src/components/MoneyReportHeader.tsx

Line 1254 in 5b1f3a0

<View style={[styles.dFlex, styles.w100, styles.ph5]}>

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

Add pb3 here

What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?

N/A

What alternative solutions did you explore? (Optional)

Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job.

[FitseTLT]

I know @daledah 's original proposal wasn't pointing to the correct code line but they updated the perma link on the solution section seconds before @Eskalifer1 proposal so I have to select @daledah proposal

🎀 👀 🎀 C+ reviewed