Skip to content

[$500] Thread - Message sent after returning from thread is not shown after refreshing the page #40037

Closed

Description

@kbecciv

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: 1.4.62-0
Reproducible in staging?: y
Reproducible in production?: n
Issue found when executing PR: #39454
Issue reported by: Applause - Internal Team

Action Performed:

  1. Go to staging.new.expensify.com
  2. Go to chat.
  3. Send a message.
  4. Right click on the message > Reply in thread.
  5. Click on the header subtitle.
  6. Send a message back in the main chat.
  7. Refresh the page.

Expected Result:

The message sent in Step 6 will appear in the chat history.

Actual Result:

The message sent in Step 6 does not appear in the chat history after refreshing the page.

Workaround:

n/a

Platforms:

Which of our officially supported platforms is this issue occurring on?

  • Android: Native
  • Android: mWeb Chrome
  • iOS: Native
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

Bug6444996_1712777240325.20240411_032158.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~019444184000784869
  • Upwork Job ID: 1780314828568719360
  • Last Price Increase: 2024-04-16

Activity

  1. melvin-bot commented on Apr 10, 2024

    @melvin-bot

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

  2. kbecciv commented on Apr 10, 2024

    @kbecciv
    Author

    We think that this bug might be related to #wave-collect - Release 1

  3. github-actions commented on Apr 10, 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.
  4. Julesssss commented on Apr 11, 2024

    @Julesssss
    Contributor

    Possibly introduced by this PR

  5. added
    ReviewingHas a PR in review
    and removed
    ReviewingHas a PR in review
    on Apr 11, 2024
  6. stitesExpensify commented on Apr 16, 2024

    @stitesExpensify
    Contributor

    @kbecciv can you re-test this? I'm not able to reproduce

  7. thienlnam commented on Apr 16, 2024

    @thienlnam
    Contributor
  8. kbecciv commented on Apr 16, 2024

    @kbecciv
    Author

    Issue is still reproducible on Windows/Chrome, build 1.4.64.11

    Recording.6163.mp4
  9. added
    ExternalAdded to denote the issue can be worked on by a contributor
    on Apr 16, 2024
  10. melvin-bot commented on Apr 16, 2024

    @melvin-bot
  11. changed the title [-]Thread - Message sent after returning from thread is not shown after refreshing the page[/-] [+][$250] Thread - Message sent after returning from thread is not shown after refreshing the page[/+] on Apr 16, 2024
  12. added
    Help WantedApply this label when an issue is open to proposals by contributors
    on Apr 16, 2024
  13. melvin-bot commented on Apr 16, 2024

    @melvin-bot

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

  14. changed the title [-][$250] Thread - Message sent after returning from thread is not shown after refreshing the page[/-] [+][$500] Thread - Message sent after returning from thread is not shown after refreshing the page[/+] on Apr 16, 2024
  15. melvin-bot commented on Apr 16, 2024

    @melvin-bot

    Upwork job price has been updated to $500

  16. thienlnam commented on Apr 16, 2024

    @thienlnam
    Contributor

    We still are having trouble reproducing this in this thread - going to go ahead and close https://expensify.slack.com/archives/C01GTK53T8Q/p1713295362543849. We can address if we run into this again

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

Metadata

Metadata

Labels

EngineeringExternalAdded to denote the issue can be worked on by a contributorHelp WantedApply this label when an issue is open to proposals by contributorsHourlyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions