Reports - Bulk Reject button is not displayed after relogin

[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.2.41-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: #72855
Email or phone of affected tester (no customers): applausetester+ndk62@applause.expensifail.com
Issue reported by: Applause Internal Team
Device used: Pixel 7a/ Android 16
App Component: User Settings

Action Performed:

Prerequisites:

• having a workspace
• workspace owner: Epensifail account
• submitter: submit at least 2 expense to workspace chat

1. As workspace owner open https://staging.new.expensify.com/
2. Navigate to 'Reports' > Expense
3. Enable select mode
4. Select some expenses
5. Tap on green button on top left
6. Verify Reject button displayed
7. Logout and re-login as workspace owner again
8. Repeat steps 2-5

Expected Result:

Reject button should be displayed

Actual Result:

Reject button is not displayed

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

1.mp4

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @NicMendonca (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]

Triggered auto assignment to @inimaga (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

[melvin-bot]

💬 A slack conversation has been started in #expensify-open-source

[github-actions]

👋 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:

1. Identify the pull request that introduced this issue and revert it.
2. Find someone who can quickly fix the issue.
3. Fix the issue yourself.