App: [$500] Report preview showing `Approve`button for the already appoved report when going back to workspace chat from report details page

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: @puneetlath Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1711381662761299

Action Performed:

  1. Go to a workspace chat
  2. Create an expense report
  3. Submit the report to approver
  4. Sign in as approver
  5. Go to the expense report
  6. Click on the report in the preview to open the expense details page
  7. Click on the receipt and go back to details page
  8. Click on the approve button
  9. Immediately go back to workspace chat and look at the expense report preview

Expected Result:

Button should show “pay” option are approved state

Actual Result:

Approve button appears and LHN has GBR as if it is needing an approval

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

https://github.com/Expensify/App/assets/38435837/61f1bb61-9f62-4f69-af5c-ba76ee2656a6

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~012899cb6011a89274
  • Upwork Job ID: 1774966548252495872
  • Last Price Increase: 2024-04-02
  • Automatic offers:
    • getusha | Reviewer | 0

About this issue

  • Original URL
  • State: closed
  • Created 3 months ago
  • Comments: 19 (11 by maintainers)

Most upvoted comments

I tried a couple times and wasn’t able to. Let’s close for now and I’ll reopen if it happens again.

It sounds like both @kubabutkiewicz and @getusha also cannot repro this issue now. @puneetlath - is this still happening? If not, I’ll close this.

Hi, I’m Jakub from Callstack - expert contributor group - and I would like to work on this issue.