Fix card widget title clipping on Android 16 by mountiny · Pull Request #83807 · Expensify/App

mountiny · 2026-03-01T21:01:07Z

Explanation of Change

On Android 16, the card widget section title "Tus tarjetas Expensify" (Spanish) is truncated to "Tus tarjetas" on narrow devices. This is an Android 16 rendering limitation where text gets clipped when a parent View has flexDirection: 'row' and text width is wrap-content.

The fix removes the redundant styles.flexRow and styles.alignItemsCenter from the WidgetContainer title wrapper View. Since this View only contains a single Text child, these styles are unnecessary and removing them allows the text to take the full available width, preventing clipping.

Fixed Issues

$ #83791
PROPOSAL: #83791 (comment)

Tests

Open the app on an Android device (Pixel 7A or similar narrow-screen device)
Navigate to Settings and switch the language to Spanish (Español)
Navigate to Home
Verify the card widget section title displays "Tus tarjetas Expensify" (not truncated to "Tus tarjetas")
Switch the language back to English
Verify the card widget section title displays "Your Expensify Cards"

Verify that no errors appear in the JS console

Offline tests

N/A - This is a styling fix that does not affect network behavior.

QA Steps

Open the app on an Android device
Navigate to Settings > Preferences > Language and switch to Spanish (Español)
Navigate to Home
Verify the card widget section title displays "Tus tarjetas Expensify" (not truncated)
Switch the language back to English and verify title displays "Your Expensify Cards"

Verify that no errors appear in the JS console

PR Author Checklist

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

Remove redundant flexRow and alignItemsCenter styles from WidgetContainer title wrapper. On Android 16, flexDirection: 'row' with wrap-content text causes the title to be clipped at word boundaries. Since the View only contains a single Text child, these styles are unnecessary. Made-with: Cursor

github-actions · 2026-03-01T21:07:07Z

🚧 @mountiny has triggered a test Expensify/App build. You can view the workflow run here.

mountiny · 2026-03-03T21:32:27Z

This should be fixed #83791 (comment)

mountiny · 2026-03-03T21:32:51Z

@MelvinBot can you sync up this PR with main please?

…ner-title-clipping Co-authored-by: Vit Horacek <mountiny@users.noreply.github.com>

MelvinBot · 2026-03-03T21:37:36Z

Merged main into this branch to sync it up. ✅

mountiny · 2026-03-03T23:11:08Z

@MelvinBot can you merge main again? the typescript should be fixed on main

…ner-title-clipping Co-authored-by: Vit Horacek <mountiny@users.noreply.github.com>

MelvinBot · 2026-03-03T23:16:13Z

Merged main into this branch again. The TypeScript fix from main should now be included. ✅

melvin-bot · 2026-03-03T23:19:26Z

@brunovjk Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

mountiny · 2026-03-03T23:19:55Z

@brunovjk can you please make sure to test on all the platforms? thanks

melvin-bot · 2026-03-03T23:20:00Z

@youssef-lr Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

trjExpensify

Straightforward bug 👍

mountiny · 2026-03-04T22:24:08Z

Asked about the review in Slakc https://expensify.slack.com/archives/C02NK2DQWUX/p1772663037384719

brunovjk · 2026-03-05T13:20:14Z

Reviewer Checklist

I have verified the author checklist is complete (all boxes are checked off).
I verified the correct issue is linked in the ### Fixed Issues section above
I verified testing steps are clear and they cover the changes made in this PR
- I verified the steps for local testing are in the Tests section
- I verified the steps for Staging and/or Production testing are in the QA steps section
- I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
- I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
I checked that screenshots or videos are included for tests on all platforms
I included screenshots or videos for tests on all platforms
I verified that the composer does not automatically focus or open the keyboard on mobile unless explicitly intended. This includes checking that returning the app from the background does not unexpectedly open the keyboard.
I verified tests pass on all platforms & I tested again on:
- Android: HybridApp
- Android: mWeb Chrome
- iOS: HybridApp
- iOS: mWeb Safari
- MacOS: Chrome / Safari
If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
I verified proper code patterns were followed (see Reviewing the code)
- I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
- I verified that comments were added to code that is not self explanatory
- I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
- I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
- I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
- I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
- I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
- I verified the JSDocs style guidelines (in STYLE.md) were followed
If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
I verified that this PR follows the guidelines as stated in the Review Guidelines
I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
If a new component is created I verified that:
- A similar component doesn't exist in the codebase
- All props are defined accurately and each prop has a /** comment above it */
- The file is named correctly
- The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
- The only data being stored in the state is data necessary for rendering and nothing else
- For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
- Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
- All JSX used for rendering exists in the render method
- The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
If any new file was added I verified that:
- The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
If a new CSS style is added I verified that:
- A similar style doesn't already exist
- The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)
If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
- I verified that all the inputs inside a form are aligned with each other.
- I added Design label and/or tagged @Expensify/design so the design team can review the changes.
If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
For any bug fix or new feature in this PR, I verified that sufficient unit tests are included to prevent regressions in this flow.
If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: HybridApp

83807_android_native.mov

Android: mWeb Chrome

83807_android_web.mov

iOS: HybridApp

83807_ios_native.mov

iOS: mWeb Safari

83807_ios_web.mov

MacOS: Chrome / Safari

83807_web_chrome.mov

melvin-bot · 2026-03-05T13:21:23Z

@lakchote Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

lakchote

LGTM

github-actions · 2026-03-05T17:38:08Z

🚧 @lakchote has triggered a test Expensify/App build. You can view the workflow run here.

github-actions · 2026-03-05T17:44:38Z

🧪🧪 Use the links below to test this adhoc build on Android, iOS, and Web. Happy testing! 🧪🧪
Built from App PR #83807.

Android 🤖	iOS 🍎
https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-android-Adhoc-dd7f6de-4f7f7ed-bf646305d72912783145ab3ef089a1509859bb9e/index.html	https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-ios-device-AdHoc-dd7f6de-4f7f7ed-2531e3e28280e37c44624fc7675c94c51133c502/index.html

Web 🕸️
https://83807.pr-testing.expensify.com

👀 View the workflow run that generated this build 👀

OSBotify · 2026-03-06T04:15:21Z

🚀 Deployed to staging by https://github.com/lakchote in version: 9.3.32-0 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	success ✅

OSBotify · 2026-03-06T22:44:34Z

🚀 Deployed to production by https://github.com/blimpich in version: 9.3.32-3 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	success ✅

melvin-bot bot assigned mountiny Mar 1, 2026

This comment has been minimized.

Sign in to view

apeyada mentioned this pull request Mar 3, 2026

[$250] Android-Home- Cards widget section title is 'Tus tarjetas' in Spanish #83791

Open

7 tasks

Merge remote-tracking branch 'origin/main' into vit-fix-widget-contai…

2325344

…ner-title-clipping Co-authored-by: Vit Horacek <mountiny@users.noreply.github.com>

Merge remote-tracking branch 'origin/main' into vit-fix-widget-contai…

cc1116f

…ner-title-clipping Co-authored-by: Vit Horacek <mountiny@users.noreply.github.com>

mountiny marked this pull request as ready for review March 3, 2026 23:19

mountiny requested review from a team as code owners March 3, 2026 23:19

melvin-bot bot requested a review from brunovjk March 3, 2026 23:19

melvin-bot bot requested review from a team and heyjennahay and removed request for a team March 3, 2026 23:19

mountiny requested review from a team and grgia and removed request for heyjennahay March 3, 2026 23:19

melvin-bot bot requested review from trjExpensify and removed request for a team March 3, 2026 23:19

melvin-bot bot requested review from youssef-lr and removed request for a team March 3, 2026 23:19

trjExpensify approved these changes Mar 4, 2026

View reviewed changes

brunovjk approved these changes Mar 5, 2026

View reviewed changes

melvin-bot bot requested a review from lakchote March 5, 2026 13:21

lakchote approved these changes Mar 5, 2026

View reviewed changes

lakchote merged commit dd7f6de into main Mar 5, 2026
43 of 45 checks passed

lakchote deleted the vit-fix-widget-container-title-clipping branch March 5, 2026 16:20

OSBotify mentioned this pull request Mar 6, 2026

Deploy Checklist: New Expensify 2026-03-06 #84352

Closed

92 tasks

jponikarchuk mentioned this pull request Mar 6, 2026

feat: Handle the REJECTEDTOSUBMITTER #84053

Merged

53 tasks

Conversation

mountiny commented Mar 1, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Explanation of Change

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

Uh oh!

github-actions bot commented Mar 1, 2026

Uh oh!

This comment has been minimized.

mountiny commented Mar 3, 2026

Uh oh!

mountiny commented Mar 3, 2026

Uh oh!

MelvinBot commented Mar 3, 2026

Uh oh!

mountiny commented Mar 3, 2026

Uh oh!

MelvinBot commented Mar 3, 2026

Uh oh!

melvin-bot bot commented Mar 3, 2026

Uh oh!

mountiny commented Mar 3, 2026

Uh oh!

melvin-bot bot commented Mar 3, 2026

Uh oh!

trjExpensify left a comment

Choose a reason for hiding this comment

Uh oh!

mountiny commented Mar 4, 2026

Uh oh!

brunovjk commented Mar 5, 2026

Reviewer Checklist

Screenshots/Videos

Uh oh!

melvin-bot bot commented Mar 5, 2026

Uh oh!

lakchote left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

github-actions bot commented Mar 5, 2026

Uh oh!

github-actions bot commented Mar 5, 2026

Uh oh!

OSBotify commented Mar 6, 2026

Uh oh!

OSBotify commented Mar 6, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

6 participants

mountiny commented Mar 1, 2026 •

edited

Loading