Skip to content

[Due for payment 2026-10-16] Expense - Error shows up when guest member submits report #103525

Closed

Description

@applause-bot

If you haven’t already, check out our contributing guidelines for onboarding. To join our Slack channel, fill out this form.


Version Number: 9.5.6-0
Reproducible in staging?: Yes
Reproducible in production?: N/A - new feature, doesn't exist in prod
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #97644
Email or phone of affected tester (no customers): jsiojsdonjodsji@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.5 / Chrome
App Component: Money Requests

Action Performed:

Precondition:

  • Create a Control workspace.
  • Invite a member as guest.
  • Perform the steps below as guest:
  1. Go to staging.new.expensify.com
  2. Go to workspace chat.
  3. Create an expense.
  4. Open the report.
  5. Click Submit.

Expected Result:

Guest can submit the report without error.

Actual Result:

Error shows up when guest member submits report.

Workaround:

Unknown

Platforms:

  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome Safari

Screenshots/Videos

Bug7281560_1791489859545.3.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Nathan Lemma
Bug ID: 7281560

Issue OwnerCurrent Issue Owner: @nkdengineer

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    on Oct 8, 2026
  2. applause-bot commented on Oct 8, 2026

    @applause-bot
    Author

    While Applause doesn't embed attachments for this bug, here are the links for quick view:
    https://platform.applause.com/services/links/v1/external/66560412d0d97b03fa03434a6ffe394ef68621880d69e92cd22a18e7a11e9e64

  3. melvin-bot commented on Oct 8, 2026

    @melvin-bot

    You have been assigned to this deploy blocker because you recently merged this PR: #97644

  4. melvin-bot commented on Oct 8, 2026

    @melvin-bot

    @JmillsExpensify @flodnv @nkdengineer you have been assigned to this deploy blocker because you reviewed the offending PR: #97644

  5. melvin-bot commented on Oct 8, 2026

    @melvin-bot

    @ShridharGoel you have been assigned to this deploy blocker because you authored the offending PR: #97644

  6. github-actions commented on Oct 8, 2026

    @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.
  7. 2 remaining items

  8. nkdengineer commented on Oct 9, 2026

    @nkdengineer
    Contributor

    @ShridharGoel Look like it's a backend issue.

  9. m-natarajan commented on Oct 9, 2026

    @m-natarajan

    Issue not repro. (Feature reverted) Windows 11/ Chrome v9.5.6-5

    bandicam.2026-10-09.19-47-28-153.2.mp4
  10. added and removed
    ReviewingHas a PR in review
    on Oct 9, 2026
  11. changed the title [-]Expense - Error shows up when guest member submits report[/-] [+][Due for payment 2026-10-16] Expense - Error shows up when guest member submits report[/+] on Oct 9, 2026
  12. melvin-bot commented on Oct 9, 2026

    @melvin-bot

    @nkdengineer

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.5.6-6 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

    If no regressions arise, payment will be issued on 2026-10-16. 🎊

    The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the Contributor+ Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]. If no checklist is needed for this issue, you can click: [no checklist button]

  13. melvin-bot commented on Oct 19, 2026

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

    If a regression has occurred and you are the assigned CM follow the instructions here.

    If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

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.EngineeringReviewingHas a PR in reviewWeeklyKSv2

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions