[$250] Merge account - Long email is cut off on magic code page

@allroundexperts

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.24-2
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: #56911
Email or phone of affected tester (no customers): applausetester+sdsoidsj@applause.expensifail.com
Issue reported by: Applause - Internal Team

Action Performed:

Go to staging.new.expensify.com
Go to Settings > Security
Tap Merge account
Enter long email
Mark "I understand this is not reversible" checkbox
Click Next

Expected Result:

The long email will be wrapped into two lines

Actual Result:

The long email is cut off

Workaround:

Unknown

Platforms:

Select the officially supported platforms where the issue was reproduced:

Platforms Tested:

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

Screenshots/Videos

Add any screenshot/video evidence

Bug6795521_1744068702443.ScreenRecording_04-08-2025_07-29-36_1.1.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~021909751045190760799
Upwork Job ID: 1909751045190760799
Last Price Increase: 2025-04-08
Automatic offers:

dominictb | Reviewer | 106853268

Issue Owner

Current Issue Owner: @allroundexperts

@marcaaron

Triggered auto assignment to @marcaaron (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

💬 A slack conversation has been started in #expensify-open-source

👋 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.
Find someone who can quickly fix the issue.
Fix the issue yourself.

Proposal

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

The long email is cut off

What is the root cause of that problem?

We don't add style word-break: 'break-word'

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

We should add word-break: 'break-word' to cover case very long email

App/src/pages/settings/Security/MergeAccounts/AccountValidatePage.tsx

Lines 126 to 135 in 689e60c

    
           <View> 
        
               <Text style={[styles.mb3]}> 
        
                   {translate('mergeAccountsPage.accountValidate.lossOfUnsubmittedData')} 
        
                   <Text style={styles.textStrong}>{email}</Text>. 
        
               </Text> 
        
               <Text> 
        
                   {translate('mergeAccountsPage.accountValidate.enterMagicCode')} 
        
                   <Text style={styles.textStrong}>{email}</Text>. 
        
               </Text> 
        
           </View>

App/src/pages/settings/Security/MergeAccounts/MergeResultPage.tsx

Line 272 in 689e60c

descriptionStyle={{...descriptionStyle, ...styles.textSupporting}}

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

None

What alternative solutions did you explore? (Optional)

NA

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.

@marcaaron

@marcaaron i can help to raise a quick PR if needed

Yeahh this doesn't need to be a blocker, I can't remember the last time I saw a customer with such a long email address.

@dominictb

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

@daledah

This is straightforward. @daledah proposal LGTM

🎀👀🎀 C+ reviewed

@amyevans

Triggered auto assignment to @amyevans, see https://stackoverflow.com/c/expensify/questions/7972 for more details.

@allroundexperts

@allroundexperts looks like you're fixing this in a polish PR, yeah? I'll assign you. Also, please comment on any other Merge Account polish issues you plan to take so that you can be assigned, our internal engineers have varying levels of awareness of what features are in progress, who's working on what, etc. Thanks!

@dominictb

📣 @dominictb 🎉 An offer has been automatically sent to your Upwork account for the Reviewer role 🎉 Thanks for contributing to the Expensify app!

Offer link
Upwork job

I am working on this!

Navigation Menu

Repository navigation

[$250] Merge account - Long email is cut off on magic code page #59757

Action Performed:

Expected Result:

Actual Result:

Workaround:

Platforms:

Screenshots/Videos

Proposal

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

What is the root cause of that problem?

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

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

What alternative solutions did you explore? (Optional)

2 remaining items

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

	<View>
	<Text style={[styles.mb3]}>
	{translate('mergeAccountsPage.accountValidate.lossOfUnsubmittedData')}
	<Text style={styles.textStrong}>{email}</Text>.
	</Text>
	<Text>
	{translate('mergeAccountsPage.accountValidate.enterMagicCode')}
	<Text style={styles.textStrong}>{email}</Text>.
	</Text>
	</View>

[$250] Merge account - Long email is cut off on magic code page #59757

Description

Action Performed:

Expected Result:

Actual Result:

Workaround:

Platforms:

Screenshots/Videos

Activity

melvin-bot commented on Apr 8, 2025

melvin-bot commented on Apr 8, 2025

github-actions commented on Apr 8, 2025

daledah commented on Apr 8, 2025

Proposal

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

What is the root cause of that problem?

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

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

What alternative solutions did you explore? (Optional)

daledah commented on Apr 8, 2025

jasperhuangg commented on Apr 8, 2025

2 remaining items

melvin-bot commented on Apr 8, 2025

dominictb commented on Apr 9, 2025

melvin-bot commented on Apr 9, 2025

amyevans commented on Apr 9, 2025

melvin-bot commented on Apr 9, 2025

allroundexperts commented on Apr 9, 2025

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions