Skip to content

[HOLD for payment 2025-01-24] [HOLD for payment 2025-01-13] [$500] After signing out of an account and signing into a different account, cached data remains when searching #48427

Description

@m-natarajan

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?: Needs Reproduction
Reproducible in production?: Needs Reproduction
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: @mallenexpensify
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1725058768402589

Deliverable

Provide reliable reproduction steps and a video for the below bug

Action Performed:

  1. Go offline and add a comment to a report.
  2. Go to Settings tab.
  3. Go online and quickly logout while request is being made.
  4. Sign in with a different account.
  5. Click on Search Icon and observe that reports from previous account is being shown.

Expected Result:

No report that is not associated with second account should not be shown in search results.

Actual Result:

Old chats from Account A in show in search.

Workaround:

Unknown

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

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021838371009986053911
  • Upwork Job ID: 1838371009986053911
  • Last Price Increase: 2024-10-09
  • Automatic offers:
    • huult | Contributor | 104985560
Issue OwnerCurrent Issue Owner: @mallenexpensify

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

Fields

No fields configured for issues without a type.

Projects

Status
Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions