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
[Due for payment 2026-01-29] Bank - Date of birth field placeholder shows YYYY-MM-DD when the new format is MM/DD/YYYY #80011
Version Number: 9.3.5-0 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 BrowserStack:#78251 Email or phone of affected tester (no customers):applausetester+sdjois2jd@applause.expensifail.com Issue reported by: Applause Internal Team Bug source: Exploratory - Significant User Experience Deterioration Device used: Mac 26.1 / Chrome App Component: Workspace Settings
Action Performed:
Go to staging.new.expensify.com
Go to Workspaces > Workflows.
Click Add bank account.
Click Connect manually.
Proceed to Personal info - Date of birth step.
Select a birth date.
Expected Result:
Date of birth field placeholder should be MM/DD/YYYY.
Actual Result:
Date of birth field placeholder shows YYYY-MM-DD when the new format is MM/DD/YYYY.
👋 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.
Classification: Frontend bug Causing PR: #78251 - Fix localization: dates not being localized correctly by @sofi-a (High confidence)
Recommendation: ROLL FORWARD
The fix is straightforward - remove the placeholder prop from DateOfBirthStep.tsx (line 102). A revert would undo all the date localization improvements across the entire app, which would be much more disruptive than applying a simple one-line fix.
Labels: Keeping DeployBlockerCash (App deploy is blocked). Removing DeployBlocker if present (backend is not affected).
Evidence
PR #78251 introduced localized date formatting throughout the app. The DatePicker component now computes placeholders dynamically based on the user's locale using Intl.DateTimeFormat.
However, the component has a logic bug in lines 61-80 of src/components/DatePicker/index.tsx - when a placeholder prop is explicitly passed, it returns that placeholder instead of computing the localized one.
Verification
The DateOfBirthStep component (src/components/SubStepForms/DateOfBirthStep.tsx line 102) passes placeholder={translate('common.dateFormat')} which evaluates to YYYY-MM-DD.
This is the only usage in the codebase that passes translate('common.dateFormat') as a placeholder to DatePicker. Because a placeholder is explicitly passed, the DatePicker uses the old YYYY-MM-DD format instead of computing the localized MM/DD/YYYY format.
Root Cause
When PR #78251 added locale-aware placeholder computation, it did not account for existing code that was passing the old translate('common.dateFormat') placeholder. The DatePicker's computedPlaceholder logic checks if a placeholder exists, and if so, uses it directly - bypassing the new localization logic.
Proposed Fix
Remove the placeholder prop from line 102 of src/components/SubStepForms/DateOfBirthStep.tsx. The DatePicker will then automatically compute the correct localized placeholder based on the user's locale.
changed the title [-]Bank - Date of birth field placeholder shows YYYY-MM-DD when the new format is MM/DD/YYYY[/-][+][Due for payment 2026-01-29] Bank - Date of birth field placeholder shows YYYY-MM-DD when the new format is MM/DD/YYYY[/+]on Jan 22, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.6-4 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@iwiznia@heyjennahay The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]
Activity
melvin-bot commentedon Jan 20, 2026
You have been assigned to this deploy blocker because you recently merged this PR: #78251
melvin-bot commentedon Jan 20, 2026
💬 A slack conversation has been started in #expensify-open-source
melvin-bot commentedon Jan 20, 2026
Triggered auto assignment to @heyjennahay (
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 commentedon Jan 20, 2026
👋 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:
OSBotify commentedon Jan 20, 2026
Investigation Summary
Classification: Frontend bug
Causing PR: #78251 - Fix localization: dates not being localized correctly by @sofi-a (High confidence)
Recommendation: ROLL FORWARD
The fix is straightforward - remove the placeholder prop from DateOfBirthStep.tsx (line 102). A revert would undo all the date localization improvements across the entire app, which would be much more disruptive than applying a simple one-line fix.
Labels: Keeping DeployBlockerCash (App deploy is blocked). Removing DeployBlocker if present (backend is not affected).
Evidence
PR #78251 introduced localized date formatting throughout the app. The DatePicker component now computes placeholders dynamically based on the user's locale using Intl.DateTimeFormat.
However, the component has a logic bug in lines 61-80 of src/components/DatePicker/index.tsx - when a placeholder prop is explicitly passed, it returns that placeholder instead of computing the localized one.
Verification
The DateOfBirthStep component (src/components/SubStepForms/DateOfBirthStep.tsx line 102) passes placeholder={translate('common.dateFormat')} which evaluates to YYYY-MM-DD.
This is the only usage in the codebase that passes translate('common.dateFormat') as a placeholder to DatePicker. Because a placeholder is explicitly passed, the DatePicker uses the old YYYY-MM-DD format instead of computing the localized MM/DD/YYYY format.
Root Cause
When PR #78251 added locale-aware placeholder computation, it did not account for existing code that was passing the old translate('common.dateFormat') placeholder. The DatePicker's computedPlaceholder logic checks if a placeholder exists, and if so, uses it directly - bypassing the new localization logic.
Proposed Fix
Remove the placeholder prop from line 102 of src/components/SubStepForms/DateOfBirthStep.tsx. The DatePicker will then automatically compute the correct localized placeholder based on the user's locale.
Beamanator commentedon Jan 20, 2026
@sofi-a @akinwale @iwiznia can y'all see if your PR #78251 caused this? And work on a revert if so?
iwiznia commentedon Jan 20, 2026
@sofi-a can you fix this? Or we could revert the PR...
Beamanator commentedon Jan 21, 2026
Looks like this same as in prod now
[-]Bank - Date of birth field placeholder shows YYYY-MM-DD when the new format is MM/DD/YYYY[/-][+][Due for payment 2026-01-29] Bank - Date of birth field placeholder shows YYYY-MM-DD when the new format is MM/DD/YYYY[/+]melvin-bot commentedon Jan 22, 2026
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Jan 22, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.6-4 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2026-01-29. 🎊
melvin-bot commentedon Jan 22, 2026
@iwiznia @heyjennahay The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]