[$500] Contact method - Error message when add contact method is not translated to Spanish

[lanitochka17]

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: 1.4.10-0
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:

Action Performed:

1. Open staging.new.expensify.com
2. Navigate to Settings> Preferences> Language> Spanish
3. Go to Settings> Profile> Contact Method
4. Add receipts@expensify.com
   as contact method

Expected Result:

Error message should be present in Spanish language

Actual Result:

Error message is displayed in English

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

• Android: Native
• Android: mWeb Chrome
• iOS: Native
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

Bug6306304_1702070204501.az_recorder_20231208_185325.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~01e336f47edd43fd48
• Upwork Job ID: 1733237184652222464
• Last Price Increase: 2023-12-08

Issue Owner

Current Issue Owner: @garrettmknight

[melvin-bot]

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

[melvin-bot]

Triggered auto assignment to @garrettmknight (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

[melvin-bot]

Bug0 Triage Checklist (Main S/O)

• This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
• This bug is not a duplicate report (check E/App issues and #expensify-bugs)
  • If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead
• This bug is reproducible using the reproduction steps in the OP. S/O
  • If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
  • If the reproduction steps aren't clear and you determine the correct steps, please update the OP.
• This issue is filled out as thoroughly and clearly as possible
  • Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.
• I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

[melvin-bot]

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

[ZhenjaHorbach]

Looks like BE issue

[nikos-amofa]

Proposal

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

Error message while adding receipts@expensify.com as contact method doesn't show in Spanish, when the language preference is set to Spanish

What is the root cause of that problem?

The error message is from the backend when failed to add the contact method.
The UI just shows the error message.

Screen.Recording.2023-12-08.at.5.20.25.PM.mov

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

This requires collaboration with the backend team.

1. The error message in En/Sp will be added to src/languages/en.ts and es.ts
2. If the code: 666(OR type: Expensify\\Error\\User\\CannotAddSecondaryLogin) corresponds to this error case, check the code and show the error message from the message added step 1. This will be decided with the collaboration of the backend team.
3. Else, collaborate with the backend team to add a new field, something like reason: ADMINISTRATOR_RESTRICTED. And for this error, show the error message from step 1.

[AmjedNazzal]

This is a BE issue as it was decided not to expand on local translation and there will be consideration in the future to support Spanish by the BE side and local translation will be deprecated eventually from what I understood looking at discussions of similar issues in the past.

[Santhosh-Sellavel]

@garrettmknight I think we can close this, Can you check internally let me whats the action plan, thanks!

[garrettmknight]

@AmjedNazzal can you point me to the thread where this was decided? I couldn't find it on a quick search.

[AmjedNazzal]

@garrettmknight #26621 (comment) not the exact same issue but the general idea I was trying to talk about is that the BE doesn't return Spanish and it seem to be something that was decided to be put aside along with similar Spanish related issues until BE localisation becomes supported.

[garrettmknight]

Thanks @AmjedNazzal - closing!