Skip to content

[Due for payment 2025-08-13] [Due for payment 2025-08-11] Reports - "Auth OpenReport returned an error" when opening expense via arrow after reset app #67590

Description

@lanitochka17

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.1.88-0
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail: https://test-management.browserstack.com/projects/2148171/test-runs/TR-329/folder/12015306/39317680/816208225?sort=%2Bidentifier
Email or phone of affected tester (no customers): sdjisdojdsonsjds@gmail.com
Issue reported by: Applause - Internal Team

Action Performed:

  1. Go to staging.new.expensify.com
  2. Create a workspace
  3. Go to workspace chat
  4. Create two expenses
  5. Go to Account > Troubleshoot
  6. Click Clear cache and restart > Reset and refresh
  7. Go to Reports > Reports
  8. Click View on one of the expense rows
  9. Click next arrow button

Expected Result:

The next expense thread will load

Actual Result:

The next expense thread does not load. It shows "Auth OpenReport returned an error"

Workaround:

Unknown

Platforms:

Select the officially supported platforms where the issue was reproduced:

  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome / Safari
  • MacOS: Desktop
Platforms Tested: On which of our officially supported platforms was this issue tested:
  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence
Bug6904422_1753991153802.20250801_034147.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @johncschuster

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.DailyKSv2Engineering

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions