[CP Staging] Put the reject money request flow behind a beta by lakchote · Pull Request #70579 · Expensify/App

lakchote · 2025-09-15T15:34:10Z

Explanation of Change

On HOLD until QA has done all their tests to identify bugs.

Context: https://expensify.slack.com/archives/C01GTK53T8Q/p1757950510790829?thread_ts=1757943373.718019&cid=C01GTK53T8Q

canRejectReportAction() is called several times to show the report action. We now put it behind a beta.

Here:

App/src/libs/ReportSecondaryActionUtils.ts

Line 670 in b315370

if (canRejectReportAction(report, policy)) {

Also here:

App/src/libs/ReportSecondaryActionUtils.ts

Line 755 in b315370

if (canRejectReportAction(parentReport, policy)) {

Fixed Issues

$
PROPOSAL:

Tests

Verify that no errors appear in the JS console

Prerequisites:

A workspace
A submitter
An approver

Submitter:
Create a new report with an expense and submit it

Approver:

Open the report with the expense
Click on the More menu for one expense
Verify the Reject option is not shown

Offline tests

QA Steps

Verify that no errors appear in the JS console

Same as in tests

PR Author Checklist

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

melvin-bot · 2025-09-15T15:34:46Z

@MarioExpensify Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

luacmartins · 2025-09-15T20:57:51Z

Reviewer Checklist

I have verified the author checklist is complete (all boxes are checked off).
I verified the correct issue is linked in the ### Fixed Issues section above
I verified testing steps are clear and they cover the changes made in this PR
- I verified the steps for local testing are in the Tests section
- I verified the steps for Staging and/or Production testing are in the QA steps section
- I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
- I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
I checked that screenshots or videos are included for tests on all platforms
I included screenshots or videos for tests on all platforms
I verified that the composer does not automatically focus or open the keyboard on mobile unless explicitly intended. This includes checking that returning the app from the background does not unexpectedly open the keyboard.
I verified tests pass on all platforms & I tested again on:
- Android: HybridApp
- Android: mWeb Chrome
- iOS: HybridApp
- iOS: mWeb Safari
- MacOS: Chrome / Safari
- MacOS: Desktop
If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
I verified there are no new alerts related to the canBeMissing param for useOnyx
I verified proper code patterns were followed (see Reviewing the code)
- I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
- I verified that comments were added to code that is not self explanatory
- I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
- I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
- I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
- I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
- I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
- I verified the JSDocs style guidelines (in STYLE.md) were followed
If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
I verified that this PR follows the guidelines as stated in the Review Guidelines
I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
If a new component is created I verified that:
- A similar component doesn't exist in the codebase
- All props are defined accurately and each prop has a /** comment above it */
- The file is named correctly
- The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
- The only data being stored in the state is data necessary for rendering and nothing else
- For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
- Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
- All JSX used for rendering exists in the render method
- The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
If any new file was added I verified that:
- The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
If a new CSS style is added I verified that:
- A similar style doesn't already exist
- The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)
If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
- I verified that all the inputs inside a form are aligned with each other.
- I added Design label and/or tagged @Expensify/design so the design team can review the changes.
If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
For any bug fix or new feature in this PR, I verified that sufficient unit tests are included to prevent regressions in this flow.
If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: HybridApp

Android: mWeb Chrome

iOS: HybridApp

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

…equest [CP Staging] Put the reject money request flow behind a beta (cherry picked from commit f824cbf) (cherry-picked to staging by lakchote)

OSBotify · 2025-09-15T21:21:30Z

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

OSBotify · 2025-09-15T21:35:45Z

🚀 Cherry-picked to staging by https://github.com/lakchote in version: 9.2.14-3 🚀

platform	result
🖥 desktop 🖥	success ✅
🕸 web 🕸	success ✅
🤖 android 🤖	cancelled 🔪
🍎 iOS 🍎	cancelled 🔪

@Expensify/applauseleads please QA this PR and check it off on the deploy checklist if it passes.

lakchote · 2025-09-15T21:49:04Z

CP did work

OSBotify · 2025-09-16T18:03:43Z

🚀 Deployed to production by https://github.com/Beamanator in version: 9.2.14-7 🚀

platform	result
🖥 desktop 🖥	success ✅
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	success ✅

OSBotify · 2025-09-16T18:33:31Z

🚀 Cherry-picked to staging by https://github.com/lakchote in version: 9.2.15-0 🚀

platform	result
🖥 desktop 🖥	success ✅
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	success ✅

@Expensify/applauseleads please QA this PR and check it off on the deploy checklist if it passes.

OSBotify · 2025-09-19T22:24:47Z

🚀 Deployed to production by https://github.com/Beamanator in version: 9.2.15-15 🚀

platform	result
🖥 desktop 🖥	success ✅
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	success ✅

lakchote added 2 commits September 15, 2025 17:26

add NEWDOT_REJECT beta

dc7d5de

implement NEWDOT_REJECT beta

f51b1ed

lakchote self-assigned this Sep 15, 2025

lakchote requested a review from a team as a code owner September 15, 2025 15:34

melvin-bot bot requested review from MarioExpensify and removed request for a team September 15, 2025 15:34

lakchote changed the title ~~[CP Staging] Put the reject money request flow behind a beta~~ [CP Staging] [HOLD] Put the reject money request flow behind a beta Sep 15, 2025

luacmartins approved these changes Sep 15, 2025

View reviewed changes

lakchote changed the title ~~[CP Staging] [HOLD] Put the reject money request flow behind a beta~~ [CP Staging] Put the reject money request flow behind a beta Sep 15, 2025

lakchote changed the title ~~[CP Staging] Put the reject money request flow behind a beta~~ [CP Staging] [HOLD] Put the reject money request flow behind a beta Sep 15, 2025

lakchote changed the title ~~[CP Staging] [HOLD] Put the reject money request flow behind a beta~~ [CP Staging] Put the reject money request flow behind a beta Sep 15, 2025

lakchote merged commit f824cbf into main Sep 15, 2025
30 of 31 checks passed

lakchote deleted the lucien/use-beta-RejectMoneyRequest branch September 15, 2025 21:09

OSBotify added the CP Staging marks PRs that have been CP'd to staging label Sep 15, 2025

OSBotify mentioned this pull request Sep 15, 2025

Deploy Checklist: New Expensify 2025-09-15 #70557

Closed

84 tasks

Beamanator mentioned this pull request Sep 16, 2025

Revert "feat: Reject Expense in NewDot" #70574

Closed

Beamanator mentioned this pull request Sep 16, 2025

[Reject] Rejected expense shows negative amount, error resubmitting rejected expense #70560

Closed

8 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[CP Staging] Put the reject money request flow behind a beta#70579

[CP Staging] Put the reject money request flow behind a beta#70579
lakchote merged 2 commits intomainfrom
lucien/use-beta-RejectMoneyRequest

lakchote commented Sep 15, 2025 •

edited

Loading

Uh oh!

melvin-bot bot commented Sep 15, 2025

Uh oh!

luacmartins commented Sep 15, 2025 •

edited

Loading

Uh oh!

Uh oh!

OSBotify commented Sep 15, 2025

Uh oh!

OSBotify commented Sep 15, 2025

Uh oh!

lakchote commented Sep 15, 2025

Uh oh!

OSBotify commented Sep 16, 2025

Uh oh!

OSBotify commented Sep 16, 2025

Uh oh!

OSBotify commented Sep 19, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Conversation

lakchote commented Sep 15, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Explanation of Change

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

Uh oh!

melvin-bot bot commented Sep 15, 2025

Uh oh!

luacmartins commented Sep 15, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Reviewer Checklist

Screenshots/Videos

Uh oh!

Uh oh!

OSBotify commented Sep 15, 2025

Uh oh!

OSBotify commented Sep 15, 2025

Uh oh!

lakchote commented Sep 15, 2025

Uh oh!

OSBotify commented Sep 16, 2025

Uh oh!

OSBotify commented Sep 16, 2025

Uh oh!

OSBotify commented Sep 19, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

lakchote commented Sep 15, 2025 •

edited

Loading

luacmartins commented Sep 15, 2025 •

edited

Loading