Skip to content

Missing To field, Send from field shows Unavailable workspace when sending invoice from chat #61637

Closed

Description

@mitarachim

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: 9.1.42-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from TestRail: Exp
Email or phone of affected tester (no customers): shdnuihshis@gmail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.3 / Chrome
App Component: Money Requests

Action Performed:

Precondition:

  • Log in with a new Gmail account.
  • Workspace has invoicing feature.
  1. Go to staging.new.expensify.com
  2. Open FAB > Send invoice.
  3. Send invoice to any user.
  4. Open invoice chat.
  5. Click + > Send invoice.
  6. Enter amount > Next.
  7. Might need to repeat Step 5 and 6 again if the issue does not reproduce.

Expected Result:

There will be To and Send from fields.

Actual Result:

To field is missing.
Send from field shows Unavailable workspace.

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

Bug6825047_1746667831898.20250508_092715.mp4

View all open jobs on GitHub

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    DeployBlockerIndicates it should block deploying the API
    on May 8, 2025
  2. melvin-bot commented on May 8, 2025

    @melvin-bot

    Triggered auto assignment to @slafortune (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.

  3. melvin-bot commented on May 8, 2025

    @melvin-bot

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

  4. melvin-bot commented on May 8, 2025

    @melvin-bot

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

  5. github-actions commented on May 8, 2025

    @github-actions
    Contributor

    👋 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.
  6. mollfpr commented on May 8, 2025

    @mollfpr
    Contributor

    This seems to be a regression from #60940.

    cc @ishakakkad @getusha

  7. mollfpr commented on May 8, 2025

    @mollfpr
    Contributor

    We will revert the PR #60940

  8. ishakakkad commented on May 8, 2025

    @ishakakkad
    Contributor

    @mollfpr About to create follow up PR or you want to revert it? Draft PR is ready #61690

  9. mollfpr commented on May 8, 2025

    @mollfpr
    Contributor

    @ishakakkad For now, we will revert it 🙏

  10. removed
    DeployBlockerIndicates it should block deploying the API
    on May 9, 2025
  11. melvin-bot commented on Jun 2, 2025

    @melvin-bot

    This issue has not been updated in over 15 days. @slafortune, @mollfpr eroding to Monthly issue.

    P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do!

  12. slafortune commented on Jun 2, 2025

    @slafortune
    Contributor

    @ishakakkad @mollfpr What is the status on this? Should this be closed? Did the revert correct the issue or are you still working on another fix here? Is there any money owed? For what? Thanks!

  13. mollfpr commented on Jun 3, 2025

    @mollfpr
    Contributor

    @slafortune We can close this since it's fixed by revert.

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

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.EngineeringMonthlyKSv2ReviewingHas a PR in review

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions