search

Expensify / App

Welcome to New Expensify: a complete re-imagination of financial collaboration, centered around chat. Help us build the next generation of Expensify by sharing feedback and contributing to the code.
https://new.expensify.com
MIT License
3.48k stars 2.83k forks source link

Hybrid iOS app –IOU –Approval button is missing after payment of the report with hold expense #50932

Open IuliiaHerets opened 1 day ago

IuliiaHerets commented 1 day ago

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: v9.0.49-0 Reproducible in staging?: N Reproducible in production?: Y If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Y Issue was repro when executing this PR: https://github.com/Expensify/App/pull/49910 Email or phone of affected tester (no customers): applausetester+jp_1151024@applause.expensifail.com Issue reported by: Applause Internal Team

Action Performed:

  1. Go to Hybrid app
  2. Log in with your Approver account
  3. As employee Go to the room with the two expenses
  4. As employee: hold one expense
  5. As Approver: Approve just the pending amount
  6. As Approver: back to room by click to the header

Expected Result:

The approval button should load after payment of the report with hold expense

Actual Result:

The approval button is missing after payment of the report with hold expense

Workaround:

Unknown

Platforms:

Screenshots/Videos

https://github.com/user-attachments/assets/67048841-44e5-4b1e-b58b-72f35b0f159f

View all open jobs on GitHub

melvin-bot[bot] commented 1 day ago

Triggered auto assignment to @sonialiap (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

IuliiaHerets commented 1 day ago

@sonialiap FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors