Skip to content

[$500] Approve button not disappear after approving report offline if advanced approval set #47264

Description

@izarutskaya

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.0.19.2
Reproducible in staging?: Y
Reproducible in production?: N
Found when validating PR : #44940
Logs: https://stackoverflow.com/c/expensify/questions/4856
Issue reported by: Applause-Internal team

Action Performed:

Precondition: create a control workspace, set "Manually approve all expenses" over to $10 and set advanced approval in OD:

  • boss owner (admin) submits to mini owner
  • mini owner (admin) submits boss owner
  • manager (employee) submits to mini owner forwards to mini owner over limit forwards (limit 100) to boss owner
  • employee 1 (employee) submits to manager
  • employee 2(employee) submits to manager
  1. Log in as an employee 1 and submit an expense below $100, e.g. $25
  2. Log in as an manager
  3. Disable internet connection
  4. Approve the report

Expected Result:

The approve button dsiappears

Actual Result:

The approve button is still displayed until user returns online

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

Bug6570173_1723484236470.Recording__666.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~01682c8c3ddb795078
  • Upwork Job ID: 1829413690213012581
  • Last Price Increase: 2024-09-06
  • Automatic offers:
    • FitseTLT | Contributor | 103937090
Issue OwnerCurrent Issue Owner: @

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    DeployBlockerIndicates it should block deploying the API
    on Aug 12, 2024
  2. melvin-bot commented on Aug 12, 2024

    @melvin-bot

    Triggered auto assignment to @adelekennedy (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.

  3. melvin-bot commented on Aug 12, 2024

    @melvin-bot

    Triggered auto assignment to @marcaaron (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

  4. github-actions commented on Aug 12, 2024

    @github-actions
    Contributor

    👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

    1. Identify the pull request that introduced this issue and revert it.
    2. Find someone who can quickly fix the issue.
    3. Fix the issue yourself.
  5. izarutskaya commented on Aug 12, 2024

    @izarutskaya
    Author

    We think this issue might be related to the #wave-control

  6. izarutskaya commented on Aug 12, 2024

    @izarutskaya
    Author

    Production

    Recording.668.mp4
  7. 56 remaining items

  8. adelekennedy commented on Sep 18, 2024

    @adelekennedy
    Contributor

    PR is in progress

  9. adelekennedy commented on Oct 1, 2024

    @adelekennedy
    Contributor

    Deployed to prod today!

  10. mananjadhav commented on Oct 8, 2024

    @mananjadhav
    Collaborator

    @adelekennedy this should be ready for payout. I couldn't exactly pinpoint the offending PR. Closest I think this should've been a part of https://github.com/Expensify/App/pull/44940/files.

    Meanwhile I don't know if a regression test exists for the whole advance approval workflow. @adelekennedy can you confirm this? I think it should exists and in that case we don't need a regression test here.

  11. adelekennedy commented on Oct 9, 2024

    @adelekennedy
    Contributor

    Payouts due:

    • Contributor: $500 @FitseTLT (Upwork) @FitseTLT will you confirm you received the payment? I know we've been experiencing an Upwork bug, in this case i released payment first and then closed the contract
    • Contributor+: $500 @mananjadhav (NewDot)

    Upwork job is here.

  12. FitseTLT commented on Oct 9, 2024

    @FitseTLT
    Contributor

    @adelekennedy I received the payment Thx!

  13. AngadManroy commented on Oct 13, 2024

    @AngadManroy

    is the issue still live?

  14. melvin-bot commented on Oct 13, 2024

    @melvin-bot

    📣 @AngadManroy! 📣
    Hey, it seems we don’t have your contributor details yet! You'll only have to do this once, and this is how we'll hire you on Upwork.
    Please follow these steps:

    1. Make sure you've read and understood the contributing guidelines.
    2. Get the email address used to login to your Expensify account. If you don't already have an Expensify account, create one here. If you have multiple accounts (e.g. one for testing), please use your main account email.
    3. Get the link to your Upwork profile. It's necessary because we only pay via Upwork. You can access it by logging in, and then clicking on your name. It'll look like this. If you don't already have an account, sign up for one here.
    4. Copy the format below and paste it in a comment on this issue. Replace the placeholder text with your actual details.
      Screen Shot 2022-11-16 at 4 42 54 PM
      Format:
    Contributor details
    Your Expensify account email: <REPLACE EMAIL HERE>
    Upwork Profile Link: <REPLACE LINK HERE>
    
  15. garrettmknight commented on Oct 15, 2024

    @garrettmknight
    Contributor

    $250 approved for @mananjadhav

  16. mananjadhav commented on Oct 15, 2024

    @mananjadhav
    Collaborator

    @garrettmknight The amount is $500.

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.EngineeringExternalAdded to denote the issue can be worked on by a contributorReviewingHas a PR in reviewWeeklyKSv2

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions