[CP Staging] Revert: Submit button with manager email prompt

[hungvu193]

Explanation of Change

Revert #87998
Related to #87264

Fixed Issues

$ #94254
$ #94323
$ #94304
$ #94281
PROPOSAL:N/A

Tests

• Verify that no errors appear in the JS console

Offline tests

QA Steps

// TODO: These must be filled out, or the issue title must include "[No QA]."

• Verify that no errors appear in the JS console

PR Author Checklist

• I linked the correct issue in the ### Fixed Issues section above
• I wrote clear testing steps that cover the changes made in this PR
  • I added steps for local testing in the Tests section
  • I added steps for the expected offline behavior in the Offline steps section
  • I added steps for Staging and/or Production testing in the QA steps section
  • I added steps to cover 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 tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
• I included screenshots or videos for tests on all platforms
• I ran the tests on all platforms & verified they passed on:
  • Android: Native
  • Android: mWeb Chrome
  • iOS: Native
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
• I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
• I followed proper code patterns (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 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)
• If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
• I followed the guidelines as stated in the Review Guidelines
• I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
• 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 new assets were added or existing ones were modified, I verified that:
  • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
  • The assets load correctly across all supported platforms.
• 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.
• I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user 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.

Screenshots/Videos

Android: Native

Screen.Recording.2026-06-23.at.23.09.40.mov

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

[melvin-bot]

Hey, I noticed you changed src/languages/en.ts in a PR from a fork. For security reasons, translations are not generated automatically for PRs from forks.

If you want to automatically generate translations for other locales, an Expensify employee will have to:

1. Look at the code and make sure there are no malicious changes.
2. Run the Generate static translations GitHub workflow. If you have write access and the K2 extension, you can simply click: [this button]

Alternatively, if you are an external contributor, you can run the translation script locally with your own OpenAI API key. To learn more, try running:

npx ts-node ./scripts/generateTranslations.ts --help

Typically, you'd want to translate only what you changed by running npx ts-node ./scripts/generateTranslations.ts --compare-ref main

[melvin-bot]

@rojiphil 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]

[melvin-bot]

@shubham1206agra @mountiny @carlosmiceli @roryabraham One of you needs to 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]

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 1f343bf6d3

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[hungvu193]

Failing test is not related.

[github-actions]

🚧 @roryabraham has triggered a test Expensify/App build. You can view the workflow run here.

[carlosmiceli]

@MelvinBot assigned, try again

[MelvinBot]

Thanks carlosmiceli — but I still can't push, because the assignee that needs adding is you, not me. The current assignees are MelvinBot and hungvu193; carlosmiceli isn't on the list yet.

My gate requires the requester to be the PR author, an assignee, or an existing co-author before I make code changes. So either:

• add carlosmiceli as an assignee and retry, or
• have the author/assignee (hungvu193) reply tagging me to direct the fix.

Once one of those is in place, ping me again and I'll fix the ESLint failures (and check test (job 2)).

[carlosmiceli]

@MelvinBot try again

[MelvinBot]

Fixed the failing ESLint check and pushed to this branch (384a307).

The revert reintroduced older code that no longer matched current lint rules / the auto-tightened eslint-seatbelt baseline:

• src/libs/actions/Search.ts — converted the disallowed import * as API from '@libs/API' namespace import (no-restricted-syntax) to named imports (makeRequestWithSideEffects, read, write), matching the rest of src/libs/actions. Removed the now-unused rulesdir/no-api-side-effects-method disable comment, since that rule only fires on the API.makeRequestWithSideEffects member form.
• config/eslint/eslint.seatbelt.tsv — re-widened the @typescript-eslint/no-unsafe-type-assertion baseline by 1 for Search.ts (18→19) and tests/actions/IOUTest/ReportWorkflowTest.ts (63→64). These are pre-existing grandfathered assertions the revert legitimately brings back, so per the docs this is the SEATBELT_INCREASE escape hatch (main will re-tighten after merge).

Verified locally: ./scripts/lint.sh --no-cache passes on both files, prettier is clean, and typecheck passes.

⚠️ Note: test (job 2) was also failing and is not a lint issue — it looks like a unit-test failure from the revert itself (likely in ReportWorkflowTest.ts). I left that untouched. Let me know if you'd like me to look into it separately.

[github-actions]

🚧 carlosmiceli has triggered a test Expensify/App build. You can view the workflow run here.

[melvin-bot]

@carlosmiceli looks like this was merged without a test passing. Please add a note explaining why this was done and remove the Emergency label if this is not an emergency.

[github-actions]

🧪🧪 Use the links below to test this adhoc build on Android, iOS, and Web. Happy testing! 🧪🧪
Built from App PR #94333.

Android 🤖	iOS 🍎
https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-android-Adhoc-a7895e2cc19-64af33b-868d018119f816dde63273490b10cdfff7016d35/index.html	https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-ios-device-AdHoc-a7895e2-64af33b-8aae145dcd0cd97600e4b6be1c17162e0b7ecaac/index.html

Web 🕸️
https://94333.pr-testing.expensify.com

---

👀 View the workflow run that generated this build 👀

[OSBotify]

✋ 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]

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

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

Bundle Size Analysis (Sentry):

• Android
• iOS

[MelvinBot]

🤖 I reviewed this PR against the help site articles under docs/articles. No help site changes are required, so I did not create a draft PR.

Why:

• This PR reverts #87998 ("Submit button with manager email prompt"), removing the popover that let users choose a workspace member or enter an email address for who should receive a report submission.
• The original feature PR [Submit] Submit button with manager email prompt #87998 did not touch any docs/articles files, so there is no documentation describing the reverted behavior that would now be stale.
• The only relevant help article, Create-and-Submit-Reports.md, documents the standard flow — "Open an expense report that includes at least one expense → Select Submit" — which already matches the restored post-revert behavior. It never referenced choosing a recipient or entering a manager email, so no edits are needed.

@carlosmiceli, since there is no help site PR to link (no docs changes were needed), there is nothing to mark Ready for review. If you believe the submit-to-recipient behavior should still be documented somewhere, let me know and I'll draft it.

[OSBotify]

🚀 Deployed to production by https://github.com/blimpich in version: 9.4.17-3 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	failure ❌

[blimpich]

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

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

Bundle Size Analysis (Sentry):

• Android
• iOS

This is being manually posted because the deploy failed to comment on all PRs.

[OSBotify]

🚀 Deployed to production by https://github.com/blimpich in version: 9.4.17-3 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	failure ❌

[OSBotify]

🚀 Deployed to production by https://github.com/blimpich in version: 9.4.18-2 🚀

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