Skip to content

mWeb - Back button on workspace chat returns to workspace list instead of workspace settings #54303

Closed

Description

@IuliiaHerets

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.77-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): applausetester+kh1311020@applause.expensifail.com
Issue reported by: Applause Internal Team
Device used: iPhone 15 Pro Max / iOS 18.2
App Component: Workspace Settings

Action Performed:

  1. Go to staging.new.expensify.com
  2. Go to workspace settings.
  3. Tap on the workspace chat under "Submit expenses using your workspace chat below".
  4. Tap app back button.

Expected Result:

App will return to the workspace settings (production behavior).

Actual Result:

App returns to workspace list.

Workaround:

Unknown

Platforms:

  • Android: Standalone
  • Android: HybridApp
  • Android: mWeb Chrome
  • iOS: Standalone
  • iOS: HybridApp
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Bug6698064_1734534131513.ScreenRecording_12-18-2024_23-00-05_1.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @twilight2294

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    on Dec 18, 2024
  2. melvin-bot commented on Dec 18, 2024

    @melvin-bot

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

  3. melvin-bot commented on Dec 18, 2024

    @melvin-bot

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

  4. melvin-bot commented on Dec 18, 2024

    @melvin-bot

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

  5. github-actions commented on Dec 18, 2024

    @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. tgolen commented on Dec 18, 2024

    @tgolen
    Contributor

    I'm going to demote this from being a blocker because it doesn't interfere with any workflows.

  7. removed
    DeployBlockerCashThis issue or pull request should block deployment
    on Dec 18, 2024
  8. 18 remaining items

  9. melvin-bot commented on Jan 6, 2025

    @melvin-bot

    This issue has not been updated in over 14 days. @JmillsExpensify, @tgolen, @twilight2294 eroding to Weekly issue.

  10. tgolen commented on Jan 17, 2025

    @tgolen
    Contributor

    What's the status of this issue? I think everything has been fixed.

  11. moved this to Bugs and Follow Up Issues in #expensify-bugson Jan 21, 2025
  12. JmillsExpensify commented on Jan 21, 2025

    @JmillsExpensify
    Contributor

    Ah looks like the payment automation failed. Payment summary: $250 to @twilight2294 via Upwork.

  13. JmillsExpensify commented on Jan 21, 2025

    @JmillsExpensify
    Contributor

    Actually I'm having trouble finding a linked PR. Do we need a regression test for this issue? It looks like no, since it was caught via a deploy blocker.

  14. JmillsExpensify commented on Jan 22, 2025

    @JmillsExpensify
    Contributor

    Thanks for the confirmation @twilight2294. I just sent you an offer via Upwork.

  15. twilight2294 commented on Jan 22, 2025

    @twilight2294
    Contributor

    accepted, thanks

  16. JmillsExpensify commented on Jan 22, 2025

    @JmillsExpensify
    Contributor

    All paid out. Thanks!

  17. moved this from Bugs and Follow Up Issues to Done in #expensify-bugson Jan 22, 2025
  18. parasharrajat commented on Jan 22, 2025

    @parasharrajat
    Member

    @JmillsExpensify This issue was a regression from #53985 and @twilight2294 was original author of the PR so there should be no payment here.

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.EngineeringWeeklyKSv2

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions