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] Date - Wrong date (moved back by one day) displayed in date field #80024
Version Number: v9.3.5-0 Reproducible in staging?: Yes Reproducible in production?: No If this was caught during regression testing, add the test name, ID and link from BrowserStack: Exploratory around #78251 Email or phone of affected tester (no customers):kiatest.78+ck118261@gmail.com Issue reported by: Applause Internal Team Bug source: Exploratory - Significant User Experience Deterioration Device used: Windows 11/Chrome, iPhone 16/iOS 18.7.1 App Component: User Settings
Action Performed:
Precondition: User is located in US & current date is 01/20/2026
Navigate to staging.new.expensify.com
Go to Profile >> Status >> Under Clear after, select Custom.
Open the Date picker.
Select a different date
Observe date in date field is moved back by one day
Scroll down to Private section >> Date of birth field
Select any year/date
Observe date in date field is moved back by one day
Save it & observe incorrect date get saved
Repeat steps in Company cards page assigning card to user
Select transaction start date & observe incorrect date get displayed in date field
Expected Result:
Same date selected in date picker should reflect in date field. Date should not be moved back by one day in date field
Actual Result:
Wrong date (moved back by one day) displayed in date field
👋 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) Related Issues: None
Recommendation: REVERT
PR #78251 introduced a timezone conversion bug in the CalendarPicker component. The code attempts to "avoid timezone issues" by converting dates to UTC, but this actually CAUSES the reported issue where selected dates are moved back by one day.
Labels: No label changes needed - keeping DeployBlockerCash as this is a frontend bug affecting the App deploy.
📋 Detailed Analysis
Evidence
Bug is reproducible only in staging (v9.3.5-0), not in production
Bug affects multiple date pickers: Status clear date, Date of birth, Company card transaction dates
Affects users in timezones west of UTC (confirmed with Windows/Chrome and iOS devices)
Verification
The bug is in src/components/DatePicker/CalendarPicker/index.tsx lines 108-111:
constonDayPressed=(day: number)=>{setCurrentDateView((prev)=>{// convert to UTC to avoid timezone issuesconstdate=newDate(Date.UTC(prev.getFullYear(),prev.getMonth(),prev.getDate()));constnewCurrentDateView=setDate(date,day);onSelected?.(format(newDate(newCurrentDateView),CONST.DATE.FNS_FORMAT_STRING));returnnewCurrentDateView;});};
PR #78251 modified this file and introduced the UTC conversion code (lines 108-109).
Root Cause
The code creates a UTC timestamp, then formats it back to local time:
User selects January 20, 2026
Code creates UTC date: Date.UTC(2026, 0, 20) → 2026-01-20 00:00:00 UTC
For users in PST (UTC-8), this UTC timestamp represents 2026-01-19 16:00:00 PST
When format() converts to local time for display, it shows 2026-01-19
The "convert to UTC to avoid timezone issues" comment is ironic - this conversion IS the timezone issue. Dates should remain in local time throughout the selection process.
Impact
This affects all date picker usage across the app for users in western timezones (Americas, parts of Pacific). The selected date is consistently off by one day, causing:
Wrong status clear dates
Incorrect date of birth values saved to user profiles
changed the title [-]Date - Wrong date (moved back by one day) displayed in date field[/-][+][Due for payment 2026-01-29] Date - Wrong date (moved back by one day) displayed in date field[/+]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@garrettmknight 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 @garrettmknight (
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:
lanitochka17 commentedon Jan 20, 2026
Production:
Recording.4767.mp4
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)
Related Issues: None
Recommendation: REVERT
PR #78251 introduced a timezone conversion bug in the CalendarPicker component. The code attempts to "avoid timezone issues" by converting dates to UTC, but this actually CAUSES the reported issue where selected dates are moved back by one day.
Labels: No label changes needed - keeping
DeployBlockerCashas this is a frontend bug affecting the App deploy.📋 Detailed Analysis
Evidence
Verification
The bug is in
src/components/DatePicker/CalendarPicker/index.tsxlines 108-111:PR #78251 modified this file and introduced the UTC conversion code (lines 108-109).
Root Cause
The code creates a UTC timestamp, then formats it back to local time:
Date.UTC(2026, 0, 20)→2026-01-20 00:00:00 UTC2026-01-19 16:00:00 PSTformat()converts to local time for display, it shows2026-01-19The "convert to UTC to avoid timezone issues" comment is ironic - this conversion IS the timezone issue. Dates should remain in local time throughout the selection process.
Impact
This affects all date picker usage across the app for users in western timezones (Americas, parts of Pacific). The selected date is consistently off by one day, causing:
iwiznia commentedon Jan 20, 2026
Alright, this is the 3rd issue with that PR. I think I am reverting the PR...
2 remaining items
iwiznia commentedon Jan 21, 2026
What's merp revert??
situchan commentedon Jan 21, 2026
I can help with manual revert if needed.
Beamanator commentedon Jan 21, 2026
Merp = "shucks". Revert = "revert" 🤣
Beamanator commentedon Jan 21, 2026
fixed in staging 👍
[-]Date - Wrong date (moved back by one day) displayed in date field[/-][+][Due for payment 2026-01-29] Date - Wrong date (moved back by one day) displayed in date field[/+]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 @garrettmknight 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]