[$250] Report - No green button to create report in reports for new account

[jponikarchuk]

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: v9.3.55-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/test-runs/TR-17121/41237673/1317002614?sort=%2Bidentifier
Email or phone of affected tester (no customers): N/A
Issue reported by: Applause Internal Team
Bug source: Regression TC Execution
Device used: Windows 11/ Chrome, Android 13
App Component: Chat Report View

Action Performed:

1. Sign up with a new account to staging.new.expensify.com
2. Finish the onboarding modal with any route (eg. Get paid back..)
3. Navigate to Reports
4. Click on "take a test drive" and finish through the test drive

Expected Result:

User is navigated to a blank reports page with a text "Use the green button below to create a report." and a green create button below the text.

Actual Result:

No green button below text

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

bandicam.2026-04-09.13-19-53-963.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @FitseTLT

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~022042193283633356871
• Upwork Job ID: 2042193283633356871
• Last Price Increase: 2026-04-16

[MelvinBot]

Proposal

What is the root cause of that problem?

The FAB (floating action button) used to be green (success color) but was redesigned to use buttonDefaultBG — which is beige/tan in light theme (#E6E1DA) and dark teal in dark theme (#1A3D32) — see FloatingActionButton.tsx:44,68. However, the empty-state text in EmptySearchView.tsx:307 still says "Use the green button below to create a report." (translation key search.searchResults.emptyReportResults.subtitleWithOnlyCreateButton). Since the button is no longer green, users look for a green button, don't find one, and report it as missing.

This is the same root cause as #86449.

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

Update the translation string subtitleWithOnlyCreateButton in src/languages/en.ts (and es.ts) to remove the color reference. For example, change:

"Use the green button below to create a report."

to:

"Use the + button below to create a report."

This matches the current FAB appearance (a "+" icon) and avoids coupling the copy to a specific button color.

What alternative solutions did you explore? (Optional)

• Change the FAB back to green: This would conflict with the broader redesign that moved the FAB to the current neutral theme color. The design was intentional.
• Add a dedicated "Create report" CTA button in the empty state: There is already logic for this at EmptySearchView.tsx:317-340, but it only renders when groupPoliciesWithChatEnabled.length > 0. New accounts without a paid group policy see no CTA button, only the text pointing to the FAB. Expanding this CTA is tracked separately in [Due for payment 2026-04-07] [$250] Show Create Report CTA for users without a workspace #83782.

Investigation details

Evidence chain:

1. After test drive, hasSeenTour becomes true via setSelfTourViewed in src/libs/actions/Welcome/index.ts
2. EmptySearchView.tsx:303-307 renders the subtitleWithOnlyCreateButton text when hasSeenTour is true and there are no expense reports
3. The buttons array at line 308-316 removes the "Take a test drive" button (since tour is done) and only shows "Create report" if groupPoliciesWithChatEnabled.length > 0
4. For a new account without a paid group policy, the buttons array is empty — the only guidance is the subtitle text pointing to the "green button" (the FAB)
5. The FAB is rendered by NavigationTabBarFloatingActionButton → FloatingActionButtonAndPopover → FABButtons → FloatingActionButton
6. FloatingActionButton.tsx:44,68 uses buttonDefaultBG from theme, which is colors.productLight400 (#E6E1DA, beige) in light theme

Possibly related issues:

• [Due for payment 2026-04-20] [$250] Onboarding instructions reference green button but the global-create button is now grey #86449 — same root cause (FAB color doesn't match "green button" text), already open and in "Reviewing" state
• [Due for payment 2026-04-07] [$250] Show Create Report CTA for users without a workspace #83782 — adds a dedicated "Create Report" CTA for users without a workspace (complementary fix)

---

Next Steps for Contributor+ team: Reply with @MelvinBot implement this to create a draft PR, @MelvinBot <your feedback> to refine this analysis, or explain why you are rejecting Melvin's proposal.

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @FitseTLT (External)

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~022042193283633356871

[ryntgh]

🚨 Edited by proposal-police: This proposal was edited at 2026-04-09 10:54:04 UTC.

Proposal

What is the root cause of that problem?

After finishing the test drive, the subtitle switches to the copy that expects only a green create button, but the button is still gated behind groupPoliciesWithChatEnabled.length > 0
For new accounts with "Get paid back" onboarding option, this can be 0, so the page shows the "Use the green button..." text without rendering the button.

App/src/pages/Search/EmptySearchView.tsx

Line 317 in 441332c

...(groupPoliciesWithChatEnabled.length > 0

We can simply remove the gate, but the empty reports Create report action routes users to workspace selection when there is no default workspace, but it does not handle the "no valid workspace exists yet" case. That sends the user to a workspace selector with an empty list.

App/src/pages/Search/EmptySearchView.tsx

Lines 323 to 333 in 441332c

	const workspaceIDForReportCreation = defaultChatEnabledPolicyID;
	if (
	!workspaceIDForReportCreation ||
	(shouldRestrictUserBillableActions(workspaceIDForReportCreation, ownerBillingGracePeriodEnd, userBillingGracePeriodEnds) &&
	groupPoliciesWithChatEnabled.length > 1)
	) {
	// If we couldn't guess the workspace to create the report, or a guessed workspace is past it's grace period and we have other workspaces to choose from
	Navigation.navigate(ROUTES.NEW_REPORT_WORKSPACE_SELECTION.getRoute());
	return;
	}

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

We should remove the groupPoliciesWithChatEnabled.length > 0 condition. And then in the empty Reports Create report button action, handle the no-workspace case before navigating to workspace selection, using the same MONEY_REQUEST_UPGRADE route pattern already used in the search create action here

                        buttons: [
                            ...(!hasSeenTour
                                ? [
                                      {
                                          buttonText: translate('emptySearchView.takeATestDrive'),
                                          buttonAction: startTestDriveAction,
                                      },
                                  ]
                                : []),
                            {
                                buttonText: translate('quickAction.createReport'),
                                buttonAction: () => {
                                    interceptAnonymousUser(() => {
                                        const workspaceIDForReportCreation = defaultChatEnabledPolicyID;

                                        if (groupPoliciesWithChatEnabled.length === 0) {
                                            const freshReportID = generateReportID();
                                            const freshTransactionID = generateReportID();
                                            Navigation.navigate(
                                                ROUTES.MONEY_REQUEST_UPGRADE.getRoute({
                                                    action: CONST.IOU.ACTION.CREATE,
                                                    iouType: CONST.IOU.TYPE.CREATE,
                                                    transactionID: freshTransactionID,
                                                    reportID: freshReportID,
                                                    upgradePath: CONST.UPGRADE_PATHS.REPORTS,
                                                }),
                                            );
                                            return;
                                        }

                                        if (
                                            !workspaceIDForReportCreation ||
                                            (shouldRestrictUserBillableActions(workspaceIDForReportCreation, ownerBillingGracePeriodEnd, userBillingGracePeriodEnds) &&
                                                groupPoliciesWithChatEnabled.length > 1)
                                        ) {
                                            // If we couldn't guess the workspace to create the report, or a guessed workspace is past it's grace period and we have other workspaces to choose from
                                            Navigation.navigate(ROUTES.NEW_REPORT_WORKSPACE_SELECTION.getRoute());
                                            return;
                                        }

                                        if (!shouldRestrictUserBillableActions(workspaceIDForReportCreation, ownerBillingGracePeriodEnd, userBillingGracePeriodEnds)) {
                                            handleCreateReportClick();
                                        } else {
                                            Navigation.navigate(ROUTES.RESTRICTED_ACTION.getRoute(workspaceIDForReportCreation));
                                        }
                                    });
                                },
                                success: true,
                            },
                        ],

App/src/pages/Search/EmptySearchView.tsx

Lines 308 to 346 in 441332c

	buttons: [
	...(!hasSeenTour
	? [
	{
	buttonText: translate('emptySearchView.takeATestDrive'),
	buttonAction: startTestDriveAction,
	},
	]
	: []),
	...(groupPoliciesWithChatEnabled.length > 0
	? [
	{
	buttonText: translate('quickAction.createReport'),
	buttonAction: () => {
	interceptAnonymousUser(() => {
	const workspaceIDForReportCreation = defaultChatEnabledPolicyID;
	if (
	!workspaceIDForReportCreation ||
	(shouldRestrictUserBillableActions(workspaceIDForReportCreation, ownerBillingGracePeriodEnd, userBillingGracePeriodEnds) &&
	groupPoliciesWithChatEnabled.length > 1)
	) {
	// If we couldn't guess the workspace to create the report, or a guessed workspace is past it's grace period and we have other workspaces to choose from
	Navigation.navigate(ROUTES.NEW_REPORT_WORKSPACE_SELECTION.getRoute());
	return;
	}
	if (!shouldRestrictUserBillableActions(workspaceIDForReportCreation, ownerBillingGracePeriodEnd, userBillingGracePeriodEnds)) {
	handleCreateReportClick();
	} else {
	Navigation.navigate(ROUTES.RESTRICTED_ACTION.getRoute(workspaceIDForReportCreation));
	}
	});
	},
	success: true,
	},
	]
	: []),
	],

Result.mp4

Note: We can add ...((hasSeenTour) check before showing the Create report button if we don't want to show two buttons when the user has not seen the tour yet

What alternative solutions did you explore? (Optional)

We can just remove groupPoliciesWithChatEnabled.length > 0 condition without routing to MONEY_REQUEST_UPGRADE

[github-actions]

⚠️ @ryntgh Thanks for your proposal. Please update it to follow the proposal template, as proposals are only reviewed if they follow that format (note the mandatory sections).

[twilight2294]

🚫 Duplicated proposal withdrawn by 🤖 ProposalPolice.

[github-actions]

⚠️ @twilight2294 Your proposal is a duplicate of an already existing proposal and has been automatically withdrawn to prevent spam. Please review the existing proposals before submitting a new one.

[KJ21-ENG]

Proposal

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

After completing onboarding/test drive, the empty Reports page tells users to use a green create button below, but in this state the button is missing, so users are left without the expected call to action.

What is the root cause of that problem?

In the empty expense-report state, the subtitle switches to subtitleWithOnlyCreateButton when hasSeenTour is true, but the actual Create report button is only rendered when groupPoliciesWithChatEnabled.length > 0.

App/src/pages/Search/EmptySearchView.tsx

Lines 383 to 395 in 1d43910

	title: translate('search.searchResults.emptyReportResults.title'),
	subtitle: translate(hasSeenTour ? 'search.searchResults.emptyReportResults.subtitleWithOnlyCreateButton' : 'search.searchResults.emptyReportResults.subtitle'),
	buttons: [
	...(!hasSeenTour
	? [
	{
	buttonText: translate('emptySearchView.takeATestDrive'),
	buttonAction: startTestDriveAction,
	},
	]
	: []),
	...(groupPoliciesWithChatEnabled.length > 0
	? [

For new users, groupPoliciesWithChatEnabled can be empty because it only includes paid group policies with expense chat enabled and visible to the user. In that case, the subtitle still references a button that is not rendered.

App/src/libs/PolicyUtils.ts

Lines 1695 to 1701 in 1d43910

	function getGroupPaidPoliciesWithExpenseChatEnabled(policies: OnyxCollection<Policy> | null) {
	if (isEmptyObject(policies)) {
	return CONST.EMPTY_ARRAY;
	}
	return Object.values(policies).filter(
	(policy) => policy?.isPolicyExpenseChatEnabled && isPaidGroupPolicy(policy) && !policy?.isJoinRequestPending && shouldShowPolicy(policy, false, undefined),
	);

App/src/pages/Search/EmptySearchView.tsx

Lines 98 to 99 in 1d43910

	const groupPoliciesWithChatEnabled = getGroupPaidPoliciesWithExpenseChatEnabled(allPolicies);

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

1. Keep the post-test-drive empty-state subtitle/button contract consistent by ensuring a Create report CTA is always shown for this state.
2. Update the CTA handler to support the no-chat-enabled-policy case by routing to workspace selection (or equivalent report creation entry) instead of hiding the button.
3. If we intentionally cannot offer report creation in a given state, switch subtitle copy to the generic message rather than the “green button below” guidance.
4. Add coverage for the matrix: hasSeenTour=true with groupPoliciesWithChatEnabled equal to 0, 1, and >1, asserting both copy and CTA visibility/behavior.

What alternative solutions did you explore? (Optional)

A smaller alternative is only changing the subtitle text when groupPoliciesWithChatEnabled is empty. That avoids mismatch, but still removes a clear recovery action for new users, so I prefer keeping a visible CTA with a fallback navigation path.