Skip to content

[Due for payment 2025-06-25] [$250] Workspace - App crashes after the workspace is deleted from the secondary device #61485

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: v9.1.40-0
Reproducible in staging?: Yes
Reproducible in production?: Yes
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): n/a
Issue reported by: Applause Internal Team
Device used: Mac 15.3.2/Safari, Desktop, iPhone 13 iOS 18.4.1 Safari
App Component: Workspace Settings

Action Performed:

  1. Navigate to https://staging.new.expensify.com
  2. Log in with the same workspace admin account on the main device and secondary device
  3. Create a Workspace
  4. On the main device, navigate to the WS Overview
  5. Delete the workspace from the secondary device
  6. Navigate the app on the main device

Expected Result:

After deleting WS on the secondary device, the app doesn't crash on the main device.

Actual Result:

After the WS is deleted from the secondary device, on the main device the LHN the app crashes

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

Bug6822852_1746534313226!Console.txt

Bug6822852_1746534289235.Recording__985.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021922346993579861382
  • Upwork Job ID: 1922346993579861382
  • Last Price Increase: 2025-05-20
Issue OwnerCurrent Issue Owner: @muttmuure

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on May 6, 2025
  2. melvin-bot commented on May 6, 2025

    @melvin-bot

    Triggered auto assignment to @muttmuure (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 12, 2025

    @melvin-bot

    @muttmuure Eep! 4 days overdue now. Issues have feelings too...

  4. moved this to Bugs and Follow Up Issues in #expensify-bugson May 13, 2025
  5. added
    ExternalAdded to denote the issue can be worked on by a contributor
    on May 13, 2025
  6. changed the title [-]Workspace - App crashes after the workspace is deleted from the secondary device[/-] [+][$250] Workspace - App crashes after the workspace is deleted from the secondary device[/+] on May 13, 2025
  7. melvin-bot commented on May 13, 2025

    @melvin-bot
  8. added
    Help WantedApply this label when an issue is open to proposals by contributors
    on May 13, 2025
  9. melvin-bot commented on May 13, 2025

    @melvin-bot

    Triggered auto assignment to Contributor-plus team member for initial proposal review - @eh2077 (External)

  10. 42 remaining items

  11. melvin-bot commented on Jun 18, 2025

    @melvin-bot

    @eh2077 @muttmuure @eh2077 The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero 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]

  12. eh2077 commented on Jun 20, 2025

    @eh2077
    Contributor

    BugZero Checklist:

    • [Contributor] Classify the bug:
    Bug classification

    Source of bug:

    • 1a. Result of the original design (eg. a case wasn't considered)
    • 1b. Mistake during implementation
    • 1c. Backend bug
    • 1z. Other:

    Where bug was reported:

    • 2a. Reported on production (eg. bug slipped through the normal regression and PR testing process on staging)
    • 2b. Reported on staging (eg. found during regression or PR testing)
    • 2d. Reported on a PR
    • 2z. Other:

    Who reported the bug:

    • 3a. Expensify user
    • 3b. Expensify employee
    • 3c. Contributor
    • 3d. QA
    • 3z. Other:
    • [Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.

      Link to comment: https://github.com/Expensify/App/pull/37421/files#r2158040347

    • [Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.

      Link to discussion: NA

    • [Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.

    • [BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.

      Link to issue:

    Regression Test Proposal

    Precondition:

    • NA

    Test:

    1. Login on the same account on web and desktop app
    2. Open the same workspace on both versions of the app
    3. On web app delete that workspace
    4. On desktop app you should get Not found view, press on Go back to home page
    5. You should end up on list of workspaces, pressing on the tab again doesn't crash the app and show FullPageNotFoundView

    Do we agree 👍 or 👎

  13. melvin-bot commented on Jun 25, 2025

    @melvin-bot

    Payment Summary

    Upwork Job

    • Contributor: @MrMuzyk is from an agency-contributor and not due payment
    • Reviewer: @eh2077 owed $250 via NewDot

    BugZero Checklist (@muttmuure)

    • I have verified the correct assignees and roles are listed above and updated the necessary manual offers
    • I have verified that there are no duplicate or incorrect contracts on Upwork for this job (https://www.upwork.com/ab/applicants/1922346993579861382/hired)
    • I have paid out the Upwork contracts or cancelled the ones that are incorrect
    • I have verified the payment summary above is correct
  14. melvin-bot commented on Jun 30, 2025

    @melvin-bot

    @muttmuure Huh... This is 4 days overdue. Who can take care of this?

  15. melvin-bot commented on Jun 30, 2025

    @melvin-bot

    @muttmuure Eep! 4 days overdue now. Issues have feelings too...

  16. melvin-bot commented on Jul 2, 2025

    @melvin-bot

    @muttmuure 6 days overdue. This is scarier than being forced to listen to Vogon poetry!

  17. melvin-bot commented on Jul 4, 2025

    @melvin-bot

    @muttmuure Now this issue is 8 days overdue. Are you sure this should be a Daily? Feel free to change it!

  18. muttmuure commented on Jul 7, 2025

    @muttmuure
    Contributor

    @eh2077 C+ $250

  19. moved this from Bugs and Follow Up Issues to Done in #expensify-bugson Jul 7, 2025
  20. JmillsExpensify commented on Jul 14, 2025

    @JmillsExpensify
    Contributor

    $250 approved for @eh2077

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

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.DailyKSv2ExternalAdded to denote the issue can be worked on by a contributorretest-weeklyApply this label if you want this issue tested on a Weekly basis by Applause

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions