App: [HOLD for payment 2024-04-25] [$500] `MISSING_TRANSLATION` is shown in pronoun field even without any pronouns set

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

Action Performed:

Login to an account in which no pronouns set
Open the profile page

Expected Result:

Pronoun field is empty

Actual Result:

Appears as ``Missing Translation" Also there are console logs

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

image (23)

image (24)

View all open jobs on GitHub

Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~019e0d665061e60d96
Upwork Job ID: 1774914293176807424
Last Price Increase: 2024-04-01
Automatic offers:

ntdiary | Reviewer | 0
gijoe0295 | Contributor | 0

Issue Owner

Current Issue Owner: @johncschuster

Most upvoted comments

BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

[@ntdiary] The PR that introduced the bug has been identified. Link to the PR: #12301

[@ntdiary] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment: https://github.com/Expensify/App/pull/12301/files#r1581826250

[@ntdiary] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion: No need

[@ntdiary] Determine if we should create a regression test for this bug. No need

[@ntdiary] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again. No need

[@johncschuster] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:

After this migration, this issue should not reappear if the list of pronouns remains unchanged in the future, so I don’t feel strongly about creating a regression test. Do you have different thoughts? 😃

If the list is subject to change in the future, we should also pay attention to maintaining them simultaneously.

ntdiary on Apr 27, 2024

Payment has been issued. @ntdiary, can you please complete the BZ list above?

johncschuster on Apr 26, 2024

Issue not reproducible during KI retests. (Second week)

mvtglobally on Apr 18, 2024

I like going with solution 2, and I would like to recommend to use an Onyx migration instead of using the profile page to correct the pronouns.

tgolen on Apr 2, 2024