Skip to content

Fix : Reports - Create report button does not show upgrade page when account has no workspace#78995

Open
M00rish wants to merge 20 commits intoExpensify:mainfrom
M00rish:upgradepath
Open

Fix : Reports - Create report button does not show upgrade page when account has no workspace#78995
M00rish wants to merge 20 commits intoExpensify:mainfrom
M00rish:upgradepath

Conversation

@M00rish
Copy link
Copy Markdown
Contributor

@M00rish M00rish commented Jan 7, 2026

Explanation of Change

Fixed Issues

$ #73762
PROPOSAL:
comment

Tests

Precondition: Account has self DM and no workspace

  1. Go to self DM
  2. Create an expense
  3. Go to Reports > Expenses
  4. Select the expense via checkbox
  5. Click dropdown menu > Move expense > create
  6. verify Upgrade page opens
  7. verify when go back you land at previous screen (create menu)
  8. verify when confirm new workspace the expense get moved.
  9. verify bulk move work
  • 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 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 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.
  • 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
Android.webm
Android: mWeb Chrome
AndroidWeb.webm
iOS: Native
ios.webm
iOS: mWeb Safari
iosWeb.webm
MacOS: Chrome / Safari
web.webm

@M00rish M00rish changed the title show upgrade first Fix : Reports - Create report button does not show upgrade page when account has no workspace Jan 7, 2026
@codecov
Copy link
Copy Markdown

codecov bot commented Jan 7, 2026

Codecov Report

✅ Changes either increased or maintained existing code coverage, great job!

Files with missing lines Coverage Δ
...rc/pages/workspace/upgrade/UpgradeConfirmation.tsx 72.22% <100.00%> (ø)
...rc/pages/Search/SearchTransactionsChangeReport.tsx 0.00% <0.00%> (ø)
...c/pages/iou/request/step/IOURequestStepUpgrade.tsx 0.00% <0.00%> (ø)
... and 58 files with indirect coverage changes

@M00rish M00rish marked this pull request as ready for review January 29, 2026 07:11
@M00rish M00rish requested review from a team as code owners January 29, 2026 07:11
@melvin-bot melvin-bot bot requested review from heyjennahay and shubham1206agra and removed request for a team January 29, 2026 07:11
@melvin-bot
Copy link
Copy Markdown

melvin-bot bot commented Jan 29, 2026

@shubham1206agra 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 melvin-bot bot removed the request for review from a team January 29, 2026 07:11

const description = useMemo(() => {
if (isCategorizing ?? isReporting) {
if (isCategorizing || isReporting) {
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

CONSISTENCY-2

The ?? operator was likely intentional for null/undefined checking, but || treats falsy values differently (including false, 0, ""). If isCategorizing or isReporting are explicitly false, this will incorrectly fall through to the condition.

Suggested fix: Keep the nullish coalescing operator if the intent was to only check for null/undefined:

if (isCategorizing ?? isReporting) {

Or if you intended OR logic, use explicit checks:

if (isCategorizing || isReporting) {

Note: This appears to be a logical change rather than just a style fix - ensure the new behavior is correct.


Please rate this suggestion with 👍 or 👎 to help us improve! Reactions are used to monitor reviewer efficiency.

Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: db5cf3efa9

ℹ️ 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".

Comment on lines +114 to +118
policy: newPolicy,
reportNextStep,
policyCategories: allPolicyCategories?.[`${ONYXKEYS.COLLECTION.POLICY_CATEGORIES}${policyID}`],
allTransactions,
});
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Pass selected transactions data to bulk move

In this upgrade flow you pass allTransactions from the Onyx TRANSACTION collection into changeTransactionsReport, but the selected items here come from SearchContext (snapshot search results) and aren’t guaranteed to exist in that Onyx collection. changeTransactionsReport filters missing entries and returns early when none are found, so the post-upgrade bulk move can become a no-op for search-based selections. Consider building the allTransactions map from selectedTransactions (as the search change-report flow does) or otherwise ensuring the selected IDs are present before calling.

Useful? React with 👍 / 👎.

@shubham1206agra
Copy link
Copy Markdown
Contributor

@M00rish Please fix errors

@M00rish
Copy link
Copy Markdown
Contributor Author

M00rish commented Feb 9, 2026

Done @shubham1206agra

@ShridharGoel
Copy link
Copy Markdown
Contributor

ShridharGoel commented Feb 9, 2026

I'll take this up for review based on Slack

@ShridharGoel
Copy link
Copy Markdown
Contributor

@JmillsExpensify On staging, it says "Collect" plan before upgrading, and "Control" plan after it's done. Is it a bug?

Screen.Recording.2026-02-10.at.1.44.03.AM.mov

const expenseReportID = policyDataRef.current?.expenseChatReportID ?? reportID;
const policyID = policyDataRef.current?.policyID;

if (upgradePath === CONST.UPGRADE_PATHS.REPORTS && policyID && selectedTransactionsKeys.length > 0) {
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

But this can be true for actions other than move-expenses also?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Export, Merge, and Delete never navigate to STEP_UPGRADE.

if (upgradePath === CONST.UPGRADE_PATHS.REPORTS && policyID && selectedTransactionsKeys.length > 0) {
const newPolicy = allPolicies?.[`${ONYXKEYS.COLLECTION.POLICY}${policyID}`];

const optimisticReport = createNewReport(currentUserPersonalDetails, hasViolations, isASAPSubmitBetaEnabled, newPolicy, betas);
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shouldn't we use selectedReport?.ownerAccountID ? See how it's done in IOURequestEditReport.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes thanks for the catch.

Comment on lines +104 to +113
const navigateWithMicrotask = useCallback(
(route: Route) => {
if (isWeb) {
Navigation.setNavigationActionToMicrotaskQueue(() => Navigation.navigate(route));
} else {
Navigation.navigate(route);
}
},
[isWeb],
);
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why has this been changed?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

reverted it

const expenseReportID = policyDataRef.current?.expenseChatReportID ?? reportID;
const policyID = policyDataRef.current?.policyID;

if (upgradePath === CONST.UPGRADE_PATHS.REPORTS && policyID && selectedTransactionsKeys.length > 0) {
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also, why not handle this via switch inside CONST.UPGRADE_PATHS.REPORTS ?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

that would complicate things and require a rewrite of the function especially with Navigation.goBack()

Copy link
Copy Markdown
Contributor

@ShridharGoel ShridharGoel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bug and the reason: Bulk-move can run for unrelated upgrade flows due to shared SearchContext state. If selectedTransactions remains populated (for example user entered upgrade from Search, backed out, then went to a normal submit-upgrade flow), this will move the older selected expenses.

See how the first expense got moved even though we did it for the second expense individually.

Screen.Recording.2026-02-15.at.10.43.15.PM.mov

@M00rish
Copy link
Copy Markdown
Contributor Author

M00rish commented Feb 19, 2026

Screencast.from.2026-02-18.00-31-35.webm

fixed @ShridharGoel

@ShridharGoel
Copy link
Copy Markdown
Contributor

ShridharGoel commented Feb 20, 2026

Shouldn't the upgrade page open directly after clicking "Move expenses" and before the "Create report" option shows? Similar to how it works when we click on the reports row in expense details

@ShridharGoel
Copy link
Copy Markdown
Contributor

@heyjennahay Can you confirm the expected behaviour?

@M00rish
Copy link
Copy Markdown
Contributor Author

M00rish commented Feb 24, 2026

This was discussed and decided here: #77040 (review)

@ShridharGoel
Copy link
Copy Markdown
Contributor

ShridharGoel commented Feb 25, 2026

Bug: Name shows empty in the subtitle and "waiting for" statement, after moving expense in offline mode possibly due to ownerAccountID missing.

Screenshot 2026-02-25 at 1 15 21 PM

@M00rish
Copy link
Copy Markdown
Contributor Author

M00rish commented Feb 27, 2026

will check that today.

@M00rish
Copy link
Copy Markdown
Contributor Author

M00rish commented Mar 4, 2026

Sorry for the delay will have an update today *or tomorow

@M00rish
Copy link
Copy Markdown
Contributor Author

M00rish commented Mar 11, 2026

image

looks good on my end @ShridharGoel

@ShridharGoel
Copy link
Copy Markdown
Contributor

Can you merge main here?

@ShridharGoel
Copy link
Copy Markdown
Contributor

looks good on my end

Did you try with offline mode?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants