Skip to content

[Exploratory] Spend - Split deleted offline disappears automatically and remaining one gets grayed out. #94422

Description

@applause-bot

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.4.18-0
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #93040
Email or phone of affected tester (no customers): ibellicotest+2766@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Motorola MotoG60 / Android 12 (Hybrid app) - Windows 11 / Chrome
App Component: Search

Action Performed:

Prerequisite: Account has at least one workspace.

  1. Open the staging.new.expensify.com website.
  2. Open any workspace chat.
  3. Create a manual expense.
  4. Open the report of the just created expense.
  5. Tap on "More" > "Split" > "Save"
  6. Navigate to "Spend" > "Expenses"
  7. Turn off internet connection.
  8. Select and delete one of the splits.
  9. Note that deleted split disappears automatically instead of being grayed out.
  10. Note that remaining split gets grayed out, despite no edition being made to it.

Expected Result:

Split deleted while offline, should be displayed grayed out and with a strikethrough until recovering internet connection, and remaining split shouldn´t be grayed out as no edition was made to it.

Actual Result:

Split deleted in offline mode while on "Spend", disappears automatically instead of being grayed out, and remaining split gets grayed out, despite no edition being made to it.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7189245_1782268859316.Grayed.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Julia Ponikarchuk
Bug ID: 7189245

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    Status
    No status

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions