[ASAP-Submit] Update expense reports Next Steps for retracted reports in Auto-Submit workspaces

[ishpaul777]

Explanation of Change

cc @MarioExpensify
Retracted reports will not auto-submit, so we’ll update the Next steps (see buildNextStep) to “Waiting for to submit these expense(s).“

Fixed Issues

$ #63197
PROPOSAL:

Tests

• Verify that no errors appear in the JS console
  Prerequisite: you should be on asapSubmit beta

1. create a WS. Disable delayed submissions
2. (Go offline temporary step)
3. create a expense. it will not be in submit state, click on more button submit it
4. Click on more button and undo submit
5. verify next step in header says: "Waiting for you to submit expense(s)."

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
  Same as tests

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
  • MacOS: Desktop
• 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 verified there are no new alerts related to the canBeMissing param for useOnyx
• 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 shown in the product is localized by adding it to src/languages/* files and using the translation method
    • If any non-english text was added/modified, I used JaimeGPT to get English > Spanish translation. I then posted it in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
  • 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 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)
• 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
• I verified that if a function's arguments changed that all usages have also been updated correctly
• 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.
• 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.2025-07-08.at.3.50.42.AM.mov

Android: mWeb Chrome

Screen.Recording.2025-07-08.at.3.50.42.AM.mov

iOS: Native

Simulator.Screen.Recording.-.iPhone.16.Pro.-.2025-07-08.at.01.36.41.mp4

iOS: mWeb Safari

Simulator.Screen.Recording.-.iPhone.16.Pro.-.2025-07-08.at.01.27.54.mp4

MacOS: Chrome / Safari

Screen.Recording.2025-07-08.at.1.28.22.AM.mov

MacOS: Desktop

Screen.Recording.2025-07-08.at.3.46.05.AM.mov

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

[rojiphil]

Reviewing today

[rojiphil]

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

65510-android-hybrid-001.mp4

Android: mWeb Chrome

65510-mweb-chrome-001.mp4

iOS: HybridApp

65510-ios-hybrid-001.mp4

iOS: mWeb Safari

65510-mweb-safari-001.mp4

MacOS: Chrome / Safari

65510-web-chrome-001.mp4

MacOS: Desktop

65510-desktop-001.mp4

[rojiphil]

@ishpaul777 Thanks for the PR.
Changes work well but why is the PR author checklist not complete?
Also, how can we do away with the lint errors?
Otherwise, the code LGTM.

[rojiphil]

@MarioExpensify Changes LGTM and works well too.
Over to you for review. Thanks.

[melvin-bot]

We did not find an internal engineer to review this PR, trying to assign a random engineer to #63197 as well as to this PR... Please reach out for help on Slack if no one gets assigned!

[ishpaul777]

Also, how can we do away with the lint errors?

all eslint fails seems unrelated, Onyx.connect for allBetas introduced in this will be eventually removed so lets keep it out of scope

[danieldoglas]

looks like the failing jest test is not related to the beta though

[ishpaul777]

Looking into it 👀

[ishpaul777]

Ran the failed test locally its passing. @danieldoglas can you please rerun action

[MarioExpensify]

@ishpaul777 as per this comment, we must wait until BE is ready to merge this. I'll review it but we'll need to HOLD for now while I work on BE.

[trjExpensify]

PR is part of the auto-submit project, scoped in a design doc. 👍

[ishpaul777]

hey @MarioExpensify! can i get update on when i might be able to resume work on FE PRs, Thanks!

[ishpaul777]

Any updates @MarioExpensify ?

[MarioExpensify]

@ishpaul777 we have the ASAP Submit flow gated in an Explicit Beta. Handling a few issues and it will be ready to test this PR!

[rojiphil]

@MarioExpensify @ishpaul777 What's the latest on this one?

[MarioExpensify]

@rojiphil we just deployed a BE PR I'm testing on, if everything is good we can review and merge this one. We'll need someone else to move forward with what @ishpaul777 started, so I assigned the issue to myself and if any change is needed I can work on or look for other contributor.

[rojiphil]

Ah nice @MarioExpensify. This PR worked well on offline scenarios as mentioned in review checklist videos here.
The only pending work is to test in online scenarios after which we are done here.
Can you please add roji+test905@owesee.com to asapSubmit beta so that I can test with the online scenario? Thanks

[MarioExpensify]

@Krishna2323 can you please merge main here so we can get this tested / move forward? BE is ready to test.

[MarioExpensify]

@rojiphil added to asapSubmit beta!

[Krishna2323]

@MarioExpensify should I open a new PR? I don’t have write access to this branch, and it’s also behind by 12,000 commits with several conflicts.

[Krishna2323]

I can’t directly make changes to this PR, so I’ve opened a new PR here. Some util functions were changed, so I need to check why they were modified or removed in recent updates.

@MarioExpensify could you please grant me access to the docs mentioned here? I’ve requested viewer access using my email belivethatkg@gmail.com. Also, please add dev.krishna.react@gmail.com to the asapSubmit beta. Thanks!

[MarioExpensify]

@Krishna2323 access granted, thank you for opening up a new PR!

[ishpaul777]

closing this PR, thank you for taking over @Krishna2323!