Reports -"Nothing to show" when filter reports and chats by today's date

[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: 9.3.4-0
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from BrowserStack: https://test-management.browserstack.com/projects/2219752/folder/13176922/test-cases/41237507
Email or phone of affected tester (no customers): N/A
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: MacBook Air 15.7.3 Chrome, iPhone 15 iOS 26.1
App Component: Search

Action Performed:

Preconditions: tested in PST timezone, current date is January. 16 2026 from 6 to 7 pm, Friday

1. Sign in to ND
2. Create a workspace
3. Navigate to the workspace chat and create a report
4. Observe the report title - it shows the next day
5. Add a new manual expense, which defaulted to todays date, to the report - report title was updated
6. Create chats. send some messages
7. Navigate to the Reports/ Reports
8. Open Date filter - On - select today's date - Apply
9. Repeat step 9 with Chats

Expected Result:

The report and chats are displayed

Actual Result:

"Nothing to show" screen appears. When selecting the next day in the filter, the report and chats show up. Works good, when using date filter with expenses and invoices.

Workaround:

Unknown

Platforms:

• Android: App
• Android: mWeb Chrome
• iOS: App
• iOS: mWeb Safari
• iOS: mWeb Chrome
• Windows: Chrome
• MacOS: Chrome / Safari

Screenshots/Videos

Bug7051562_1768621953974.Reports_next_day.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @huult

[melvin-bot]

Triggered auto assignment to @RachCHopkins (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.

[annaweber830]

Proposal

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

When a user filters Reports or Chats by today’s date, the app incorrectly shows a “Nothing to show” empty state even though there are reports/chats created today. In the same scenario, newly created reports can display a title date that looks like the next day.

What is the root cause of that problem?

This is a timezone boundary mismatch:

• The date filter input is a local calendar day (e.g. “Jan 16” in PST).
• Some report/chat “date” values are derived from UTC-based timestamps (or timestamps stored in a “DB time” format without timezone info), so items created later in the day in negative timezones (e.g. PST evenings) can be interpreted as belonging to the next UTC day.
• As a result, filtering for the local “today” day excludes those items, and date-derived UI (like report title dates) can appear shifted by one day.

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

• Normalize parsing of backend “DB time” strings (YYYY-MM-DD HH:mm:ss[.SSS]) to be treated as UTC rather than local time when we format or compute date-based strings. This prevents “next day” display issues caused by JS interpreting those strings as local timestamps.
• For Search date filtering on Reports/Chats, adjust the Search request payload so that a user-selected local date is translated into the UTC date(s) that overlap that local day (sometimes 1 UTC date, sometimes 2). This ensures results created late in the local day aren’t excluded by UTC-day boundaries, while keeping the user’s selected filter concept (“today”) intact.
  We should add this code to Search.ts
  ```

function getUTCDatesThatOverlapLocalDate(localDate: string): string[] {
    const startOfLocalDay = parse(localDate, CONST.DATE.FNS_FORMAT_STRING, new Date());
    const endOfLocalDayInclusive = subMilliseconds(addDays(startOfLocalDay, 1), 1);

    const startUTCDate = DateUtils.formatInTimeZoneWithFallback(startOfLocalDay, 'UTC', CONST.DATE.FNS_FORMAT_STRING);
    const endUTCDate = DateUtils.formatInTimeZoneWithFallback(endOfLocalDayInclusive, 'UTC', CONST.DATE.FNS_FORMAT_STRING);

    return startUTCDate === endUTCDate ? [startUTCDate] : [startUTCDate, endUTCDate];
}

function expandLocalDateFilterToOverlappingUTCDates(filters: ASTNode | undefined, searchType: SearchDataTypes): ASTNode | undefined {
    if (!filters) {
        return filters;
    }

    const shouldExpand = searchType === CONST.SEARCH.DATA_TYPES.CHAT || searchType === CONST.SEARCH.DATA_TYPES.EXPENSE_REPORT;
    if (!shouldExpand) {
        return filters;
    }

    const traverse = (node: ASTNode): ASTNode => {
        const left = typeof node.left === 'object' ? traverse(node.left) : node.left;
        const right = typeof node.right === 'object' && node.right && !Array.isArray(node.right) ? traverse(node.right) : node.right;

        // Leaf node: key/operator/value
        if (
            typeof left === 'string' &&
            left === CONST.SEARCH.SYNTAX_FILTER_KEYS.DATE &&
            node.operator === CONST.SEARCH.SYNTAX_OPERATORS.EQUAL_TO &&
            typeof right === 'string' &&
            isValidDate(right)
        ) {
            const utcDates = getUTCDatesThatOverlapLocalDate(right);
            return utcDates.length > 1 ? {...node, left, right: utcDates} : {...node, left, right: utcDates.at(0) ?? right};
        }

        return {...node, left, right};
    };

    return traverse(filters);
}

App/src/libs/actions/Search.ts

Lines 402 to 409 in e54cfd4

	const {flatFilters, ...queryJSONWithoutFlatFilters} = queryJSON;
	const query = {
	...queryJSONWithoutFlatFilters,
	searchKey,
	offset,
	filters: queryJSONWithoutFlatFilters.filters ?? null,
	shouldCalculateTotals,
	};

const {flatFilters, ...queryJSONWithoutFlatFilters} = queryJSON;
    const expandedFilters = expandLocalDateFilterToOverlappingUTCDates(queryJSONWithoutFlatFilters.filters, queryJSON.type);
    const query = {
        ...queryJSONWithoutFlatFilters,
        searchKey,
        offset,
        filters: expandedFilters ?? null,
        shouldCalculateTotals,
    };

App/src/libs/FormulaDatetime.ts

Lines 236 to 240 in e54cfd4

	try {
	const date = new Date(dateString);
	if (Number.isNaN(date.getTime())) {
	return '';
	}

try {
        const isDBTimeUTCWithoutTZ = /^\d{4}-\d{2}-\d{2} \d{2}:\d{2}:\d{2}(\.\d+)?$/.test(dateString);
        const normalizedDateString = isDBTimeUTCWithoutTZ ? `${dateString.replace(' ', 'T')}Z` : dateString;

        const date = new Date(normalizedDateString);
        if (Number.isNaN(date.getTime())) {
            return '';
        }

What alternative solutions did you explore? (Optional)

[melvin-bot]

📣 @moaead! 📣
Hey, it seems we don’t have your contributor details yet! You'll only have to do this once, and this is how we'll hire you on Upwork.
Please follow these steps:

1. Make sure you've read and understood the contributing guidelines.
2. Get the email address used to login to your Expensify account. If you don't already have an Expensify account, create one here. If you have multiple accounts (e.g. one for testing), please use your main account email.
3. Get the link to your Upwork profile. It's necessary because we only pay via Upwork. You can access it by logging in, and then clicking on your name. It'll look like this. If you don't already have an account, sign up for one here.
4. Copy the format below and paste it in a comment on this issue. Replace the placeholder text with your actual details.
   
   Format:

Contributor details
Your Expensify account email: <REPLACE EMAIL HERE>
Upwork Profile Link: <REPLACE LINK HERE>

[RachCHopkins]

This is weird, not sure what Melvin was up to here.

[IuliiaHerets]

@RachCHopkins Chrome / v9.3.16-0
Not reproducible by an EU-based tester.
Asked also original tester to check

Screen.Recording.2026-02-10.at.09.42.46.mp4

[IuliiaHerets]

@RachCHopkins issue is still repro by the original US-tester, build 9.3.17-0, Mac Chrome

Retest.1.1.mp4