You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Debug - Subheader Fields are not translated to Spanish in Debug menu #75945
Version Number: 9.2.63-0 Reproducible in staging?: Y Reproducible in production?: Unable to validate in Prod If this was caught during regression testing, add the test name, ID and link from TestRail:#73748 Email or phone of affected tester (no customers):applausetester+en@applause.expensifail.com Issue reported by: Applause - Internal Team
Action Performed:
Precond: App is in Spanish
Access staging.new.expensify.com
Log into a valid account
Swipe with 4 fingers to enbable debug menu on iOS app
Open a expense report
Click on header / expense from the report and then its header > debug mode
Scroll down the page and observe the main headers and subheaders
Expected Result:
User expects all aspects of the page to be translated in Spanish
Actual Result:
Subheaders aren't translated to Spanish, only main headers
Workaround:
Unknown
Platforms:
Select the officially supported platforms where the issue was reproduced:
Android: App
Android: mWeb Chrome
iOS: App
iOS: mWeb Safari
iOS: mWeb Chrome
Windows: Chrome
MacOS: Chrome / Safari
MacOS: Desktop
Platforms Tested:
On which of our officially supported platforms was this issue tested:
👋 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.
These are attributes of the reports and the names map to what they're called in the backend, so I don't think it makes sense to translate them. I checked on production and they're also not translated.
Activity
melvin-bot commentedon Nov 24, 2025
Triggered auto assignment to @brianlee-expensify (
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.melvin-bot commentedon Nov 24, 2025
Triggered auto assignment to @francoisl (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Nov 24, 2025
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Nov 24, 2025
👋 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:
francoisl commentedon Nov 24, 2025
These are attributes of the reports and the names map to what they're called in the backend, so I don't think it makes sense to translate them. I checked on production and they're also not translated.