Onboarding - Unread marker reappears on onboarding task after returning online.

[applause-bot]

If you haven’t already, check out our contributing guidelines for onboarding. To join our Slack channel, fill out this form.

---

Version Number: 9.4.49-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #95766
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)
App Component: Workspace Settings

Action Performed:

Prerequisite: Sign in with a new account invited to a workspace as an admin so the "Review your workspace settings" task exists in the onboarding/Concierge chat.

1. Open the Expensify app.
2. Turn off internet connection.
3. Navigate to "Workspaces" > Workspace > "Overview"
4. Make any edition. (For example: Change workspace´s name)
5. Navigate to Concierge chat.
6. Open the "Review your workspace settings" task.
7. Note that "Marked as complete" message, with unread marker appears.
8. Return to Concierge chat and reopen task.
9. Note that unread marker disappeared.
10. Turn on internet connection.
11. Note that unread marked reappears, despite message being already read.

Expected Result:

Unread marker shouldn´t reappear for read messages when returning online.

Actual Result:

Unread marker on "Marked as complete" message on "Review your workspace settings" task, reappears when user completes task offline and returns online.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7225615_1785852432243.Onboard_6.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Svetlana Lazutkina
Bug ID: 7225615

[applause-bot]

While Applause doesn't embed attachments for this bug, here are the links for quick view:
https://platform.applause.com/services/links/v1/external/4f77fd79fe1b84dd1364324caac22b70a8100a7c26e71a9fcfde8e57d9cc2f33

[melvin-bot]

You have been assigned to this deploy blocker because you recently merged this PR: #95766

[melvin-bot]

@robertjchen @situchan you have been assigned to this deploy blocker because you reviewed the offending PR: #95766

[melvin-bot]

@FitseTLT you have been assigned to this deploy blocker because you authored the offending PR: #95766

[melvin-bot]

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

[github-actions]

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