Repository navigation
Expense - Error when submitting distance expense to non-existing workspace chat #51286
Description
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.0.52-2
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: N/A
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Email or phone of affected tester (no customers): applausetester+kh1610015@applause.expensifail.com
Issue reported by: Applause - Internal Team
Action Performed:
- Go to OD
- Create a new Control workspace
- Go to ND
- Go to FAB > Submit expense > Distance
- Enter waypoints > Next
- Select the Control workspace chat created on OD
- On confirmation page, click Rate
- Note that Rate list is empty
- Submit the distance expense
- Go to transaction thread
Expected Result:
In Step 8, Rate list should not be empty
In Step 10, the distance expense will be submitted without issue
Actual Result:
In Step 8, Rate list is empty
In Step 10, error happens when submitting distance expense to non-existing workspace chat
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
- Android: Standalone
- Android: HybridApp
- Android: mWeb Chrome
- iOS: Standalone
- iOS: HybridApp
- iOS: mWeb Safari
- MacOS: Chrome / Safari
- MacOS: Desktop
Activity
melvin-bot commentedon Oct 22, 2024
Triggered auto assignment to @blimpich (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Oct 22, 2024
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Oct 22, 2024
👋 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:
lanitochka17 commentedon Oct 22, 2024
@blimpich FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors
lanitochka17 commentedon Oct 22, 2024
We think that this bug might be related to #wave-control
blimpich commentedon Oct 22, 2024
Probably related to #49412, checking locally if reverting it fixes this.
blimpich commentedon Oct 22, 2024
Reverting does seem to fix the issue, discussing possible solutions other than reverting in Slack: https://expensify.slack.com/archives/C01GTK53T8Q/p1729624660433179?thread_ts=1729612151.981119&cid=C01GTK53T8Q
blimpich commentedon Oct 22, 2024
Decided to revert, working on that now.
blimpich commentedon Oct 22, 2024
Steps still needed:
blimpich commentedon Oct 22, 2024
Will be afk for 1.5 hours, will continue steps above once I'm back
blimpich commentedon Oct 22, 2024
Not reproducible, closing.