[Due for payment 2025-10-22] [$50] Workspace -Error message briefly appears when user add the email of an existing member

[mitarachim]

Problem

This batch contains incomplete translations that need to be migrated to use translation parameters instead of split keys or trailing spaces.

Translation Keys to Fix

• subscription.billingBanner.preTrial.subtitleStart
  • Current value: "As a next step, "
• subscription.billingBanner.preTrial.subtitleLink
  • Current value: "complete your setup checklist "
• subscription.subscriptionSettings.learnMore.part1
  • Current value: "Learn more on our "
• subscription.subscriptionSettings.learnMore.part2
  • Current value: " or chat with our team in your "

Example PRs

See these PRs for examples of how to perform this migration:

• Update the images in the Create an Expense help article #54544
• [HOLD for payment 2025-01-24] Trip - Modify trip and Trip support button open the same page #54545
• Merge termsStep translations #70523

More examples can be found in the tracking issue: #62808

Migration Steps

1. Identify where these translation keys are used in the codebase
2. Combine split translations (keys containing "part") into single translation strings with parameters
3. Remove trailing spaces from translation values and combine them properly with whatever rich text content is displayed after them in the app
4. Update the code to pass the appropriate parameters to the translation function, usually wrapping rich text with react-native-render-html as seen in the example PRs
5. Test the changes to ensure the translations render correctly

Issue Owner

Current Issue Owner: @

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021975731976354472571
• Upwork Job ID: 1975731976354472571
• Last Price Increase: 2025-10-08
• Automatic offers:
• twilight2294 | Contributor | 109161566

Issue Owner

Current Issue Owner: @twilight2294

[melvin-bot]

Triggered auto assignment to @VictoriaExpensify (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]

👋 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:

1. Identify the pull request that introduced this issue and revert it.
2. Find someone who can quickly fix the issue.
3. Fix the issue yourself.

[melvin-bot]

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

[melvin-bot]

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

[ChavdaSachin]

Proposal

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

Workspace -Error message briefly appears when user add the email of an existing member (who does not happen to have an existing Expensify account) and user can be again selected and invited.

What is the root cause of that problem?

During recent refactor this commit changed the userToInvite flow.
Where excludeLogins attribute is not being passed.

App/src/libs/OptionsListUtils/index.ts

Line 1927 in 276a46a

userToInvite = filterUserToInvite({currentUserOption: currentUserRef.current, recentReports: recentReportOptions, personalDetails: personalDetailsOptions}, searchString ?? '');

Missing case during initial implementation.

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

Pass excludeLogins attribute here.

        userToInvite = filterUserToInvite({currentUserOption: currentUserRef.current, recentReports: recentReportOptions, personalDetails: personalDetailsOptions}, searchString ?? '', {excludeLogins: excludeLogins});

App/src/libs/OptionsListUtils/index.ts

Line 1927 in 276a46a

userToInvite = filterUserToInvite({currentUserOption: currentUserRef.current, recentReports: recentReportOptions, personalDetails: personalDetailsOptions}, searchString ?? '');

And check for similar miss if anywhere.

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.