New languages (except Chinese): Teachers Unite is not translated

[nlemma]

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: v9.1.68-2
Reproducible in staging?: Yes
Reproducible in production?: N/A - new feature, doesn't exist in prod
If this was caught during regression testing, add the test name, ID and link from TestRail: #64282
Email or phone of affected tester (no customers): Expensifail account
Issue reported by: Applause Internal Team
Device used: MacOS Big Sur
App Component: Other

Action Performed:

Precondition: use expensifail account.

1. Go to Account > Preferences
2. Language > choose every of a new language (except Chinese)
3. Go to Account > Save the world

Expected Result:

'Teachers Unite' is translated in chosen language.

Actual Result:

'Teachers Unite' is not translated in chosen language. Only in Chinese it is ok.

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

Bug6863678_1750263617900.Screen_Recording_2025-06-18_at_7.18.40_PM.mp4

View all open jobs on GitHub

[melvin-bot]

Current assignee @trjExpensify is eligible for the Bug assigner, not assigning anyone new.

[trjExpensify]

Consolidating.

[nabi-ebrahimi]

Proposal

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

New languages (except Chinese): Teachers Unite is not translated

What is the root cause of that problem?

We missed the translation for Teachers Unite in the following places

App/src/languages/fr.ts

Line 5996 in 76728bc

teachersUnite: 'Teachers Unite',

and

App/src/languages/ja.ts

Line 5919 in 76728bc

teachersUnite: 'Teachers Unite',

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

We should add the appropriate translations for both places.

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)