Skip to content

Expense-Skeleton loader when open workspace chat/split expense/reply thread for the first time #71414

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: 9.2.19-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: https://test-management.browserstack.com/projects/2219752/test-runs/TR-962/folder/13176670/41237133/920382496
Email or phone of affected tester (no customers): sosdpsosnjojs@gmail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.5 / Chrome
App Component: Money Requests

Action Performed:

Scenario 1:

  1. Go to staging.new.expensify.com
  2. Create a workspace.
  3. Go to workspace chat.
  4. Create an expense.
  5. Open the expense report.
  6. Click More > Split.
  7. Click Save.
  8. Open the split expense.

Scenario 2:

  1. Go to staging.new.expensify.com
  2. Go to workspace chat.
  3. Send a message .
  4. Right click on the message > Reply in thread.

Expected Result:

Scenario 1:
In Step 3, when opening workspace chat for the first time, skeleton loader will not show (production behavior).
In Step 8, when opening split expense for the first time, skeleton loader will not show (production behavior).

Scenario 2:
Report will not show skeleton loader when replying workspace message in thread for the first time.

Actual Result:

Scenario 1:
In Step 3, when opening workspace chat for the first time, skeleton loader is shown.
In Step 8, when opening split expense for the first time, skeleton loader is shown.

Scenario 2:
Report shows skeleton loader when replying workspace message in thread for the first time.

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

Scenario 1:

Bug6957164_1758936952420.Scenario_2.mp4

Scenario 2:

Bug6957164_1758936926229.Scenario_2.mp4

View all open jobs on GitHub

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    DeployBlockerIndicates it should block deploying the API
    on Sep 27, 2025
  2. melvin-bot commented on Sep 27, 2025

    @melvin-bot

    Triggered auto assignment to @brianlee-expensify (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 Sep 27, 2025

    @melvin-bot

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

  4. melvin-bot commented on Sep 27, 2025

    @melvin-bot

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

  5. github-actions commented on Sep 27, 2025

    @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. VickyStash commented on Sep 29, 2025

    @VickyStash
    Contributor

    This DB is caused by #71084

  7. 2 remaining items

  8. izarutskaya commented on Sep 29, 2025

    @izarutskaya

    Issue is not reproducible on our side on Hybrid App. Retested on Motorola MotoG60 - Android 12 - Build 9.2.19-2

    screen-20250929-122020.mp4

    Issue is not reproducible on mWeb either on our side. Retested on Motorola MotoG60 - Android 12 - Chrome - Build 9.2.19-2

    screen-20250929-122500.mp4

    Issue is not reproducible on Xiaomi Redmi Note 10 / Android 12 / Chrome
    v.9.2.19-2

    Screenrecorder-2025-09-29-18-52-15-737.mp4
  9. Julesssss commented on Sep 29, 2025

    @Julesssss
    Contributor

    The offending PR was reverted: #71458

    Demoting, revert has resolved this. Leaving open for next attempt.

  10. added and removed
    DeployBlockerCashThis issue or pull request should block deployment
    DeployBlockerIndicates it should block deploying the API
    on Sep 29, 2025
  11. mountiny commented on Sep 29, 2025

    @mountiny
    Contributor

    Going to close this one as we are going to handle the fix in a new PR #63253 (comment)

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