Skip to content

[HOLD for payment 2024-06-20] [$250] [HIGH] [API reliability] Opening a thread calls OpenReport twice #43120

Description

@mountiny

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:
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @puneetlath
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1717528890813739

Action Performed:

Break down in numbered steps

  1. Navigate to a report that has messages with threads
  2. Open Networks tab in the inspector
  3. Open some thread
  4. Notice that OpenReport for that report has been called twice

Expected Result:

Describe what you think should've happened

Only one OpenReport should have been called/ executed

Actual Result:

Describe what actually happened

there are two - this is not acceptable 😡

Workaround:

Can the user still use Expensify without this being fixed? Have you informed them of the workaround?

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

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @
Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~019365aabd7a4925c3
  • Upwork Job ID: 1798334405705949184
  • Last Price Increase: 2024-06-05
  • Automatic offers:
    • hoangzinh | Reviewer | 102636342
    • bernhardoj | Contributor | 102636344
Issue OwnerCurrent Issue Owner: @garrettmknight

Activity

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.ExternalAdded to denote the issue can be worked on by a contributorWeeklyKSv2

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions