[$250] Expense - Amount is out of view when merchant is very long

[jponikarchuk]

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.1.54-2
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from TestRail: Exp
Email or phone of affected tester (no customers): applausetester+300503kh@applause.expensifail.com
Issue reported by: Applause Internal Team
Device used: iPhone 15 Pro Max / iOS 18.5
App Component: Money Requests

Action Performed:

1. Launch Expensify app.
2. Go to workspace chat.
3. Submit two expenses with very long merchant.
4. Tap on the expense preview.

Expected Result:

Amount will be wrapped within the expense row when merchant is very long.

Actual Result:

Amount is out of view when merchant is very long.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

1.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021929566938333240862
• Upwork Job ID: 1929566938333240862
• Last Price Increase: 2025-06-02

Issue Owner

Current Issue Owner: @getusha

[melvin-bot]

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

[nabi-ebrahimi]

🚨 Edited by proposal-police: This proposal was edited at 2025-05-30 13:36:34 UTC.

Proposal

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

Expense - Amount is out of view when merchant is very long

What is the root cause of that problem?

We didn't set flex: 1, so MerchantCell doesn't know its limit, so it takes up as much space as it needs.

App/src/components/TransactionItemRow/DataCells/MerchantCell.tsx

Lines 15 to 21 in 8bb818d

	<TextWithTooltip
	shouldShowTooltip={shouldShowTooltip}
	text={merchantToDisplay}
	style={[!shouldUseNarrowLayout ? styles.lineHeightLarge : styles.lh20, styles.pre, styles.justifyContentCenter]}
	/>
	);
	}

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

We should only add flex: 1 to allow the component to share available space rather than grow uncontrollably.

in MerchantCell

 <TextWithTooltip
            shouldShowTooltip={shouldShowTooltip}
            text={merchantToDisplay}
            style={[!shouldUseNarrowLayout ? styles.lineHeightLarge : styles.lh20, styles.pre, styles.justifyContentCenter, styles.flex1]}
        />

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)

[ryntgh]

Proposal

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

Expense - Amount is out of view when merchant is very long

What is the root cause of that problem?

When the merchant name is very long, the MerchantCell component takes up too much space and pushes the TotalCell (amount) out of view

App/src/components/TransactionItemRow/index.tsx

Lines 297 to 309 in df2c3c1

	{!isMerchantEmpty && (
	<View style={[styles.flexRow, styles.alignItemsCenter, styles.justifyContentBetween, styles.gap2]}>
	<MerchantCell
	transactionItem={transactionItem}
	shouldShowTooltip={shouldShowTooltip}
	shouldUseNarrowLayout={shouldUseNarrowLayout}
	/>
	<TotalCell
	transactionItem={transactionItem}
	shouldShowTooltip={shouldShowTooltip}
	shouldUseNarrowLayout={shouldUseNarrowLayout}
	/>
	</View>

The issue occurs because:

1. The MerchantCell has no flex constraints, allowing it to grow indefinitely
2. The TotalCell has flexShrink0 preventing it from shrinking

Both are in a flexRow with justifyContentBetween, causing the amount to be pushed out of view

App/src/components/TransactionItemRow/DataCells/MerchantCell.tsx

Line 18 in df2c3c1

style={[!shouldUseNarrowLayout ? styles.lineHeightLarge : styles.lh20, styles.pre, styles.justifyContentCenter]}

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

Add flexShrink1 to the MerchantCell component so it can wrap/truncate when space is limited, ensuring the amount remains visible

style={[!shouldUseNarrowLayout ? styles.lineHeightLarge : styles.lh20, styles.pre, styles.justifyContentCenter, styles.flexShrink1]}

App/src/components/TransactionItemRow/DataCells/MerchantCell.tsx

Line 18 in df2c3c1

style={[!shouldUseNarrowLayout ? styles.lineHeightLarge : styles.lh20, styles.pre, styles.justifyContentCenter]}

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

N/A (UI issue)

[melvin-bot]

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

[melvin-bot]

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

[kaushiktd]

Proposal

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

Expense - Amount is out of view when merchant is very long

What is the root cause of that problem?

To arrange content evenly in a row, you must use flex.
You did not use flex in the MerchantCell here., and you used flexShrink: 0 in the TotalCell which means it refuses to shrink, even if there’s not enough room, so the layout breaks.

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

You need to add flex to fill available space evenly or flexShrink to shrink the content at the end of here.

style={[!shouldUseNarrowLayout ? styles.lineHeightLarge : styles.lh20, styles.pre, styles.justifyContentCenter, styles.flex1]}

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

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.