Skip to content

Request money - “Hmm… it’s not here” shown when adding a receipt to a manual request #34388

Closed

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: 1.4.24-4
Reproducible in staging?: Y
Reproducible in production?: N
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: Applause - Internal Team
Slack conversation:

Issue found when executing PR #32764

Action Performed:

  1. Go to any chat
  2. Request money with the scan tab and scan a receipt
  3. Request money again as manual request
  4. Go to the manual request
  5. Select the three dots on top right
  6. Add receipt

Expected Result:

The add receipt UI is shown and user can add a receipt after adding a manual expense

Actual Result:

After scanning a receipt seems that the new manual request isn't synced immediately and adding a receipt to it fails with the error message

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

Bug6339213_1704997607887.az_recorder_20240111_182210.mp4

View all open jobs on GitHub

Activity

  1. github-actions commented on Jan 11, 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.
  2. melvin-bot commented on Jan 11, 2024

    @melvin-bot

    Triggered auto assignment to @deetergp (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

  3. situchan commented on Jan 11, 2024

    @situchan
    Contributor

    I am not able to reproduce on main

  4. deetergp commented on Jan 12, 2024

    @deetergp
    Contributor

    I was unable to reproduce it in web. My Android environment is (unsurprisingly) being difficult, making it hard to test there. Either way, I don't feel like this warrants "Blocker" status. Anyone disagree?

  5. kavimuru commented on Jan 12, 2024

    @kavimuru

    Still able to reproduce in Native app

    Rpreplay.Final1705032101-1.mp4
  6. situchan commented on Jan 12, 2024

    @situchan
    Contributor

    @kavimuru can you please confirm this doesn't happen on production?

  7. situchan commented on Jan 12, 2024

    @situchan
    Contributor

    I think this is dupe of #34417

  8. removed
    DeployBlockerCashThis issue or pull request should block deployment
    on Jan 12, 2024
  9. Gonals commented on Jan 12, 2024

    @Gonals
    Contributor

    Agreed. Closing as duplicate!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions