-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Request money - “Hmm… it’s not here” shown when adding a receipt to a manual request #34388
Comments
👋 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:
|
Triggered auto assignment to @deetergp ( |
I am not able to reproduce on main |
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? |
Still able to reproduce in Native app Rpreplay.Final1705032101-1.mp4 |
@kavimuru can you please confirm this doesn't happen on production? |
I think this is dupe of #34417 |
Agreed. Closing as duplicate! |
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:
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?
Screenshots/Videos
Add any screenshot/video evidence
Bug6339213_1704997607887.az_recorder_20240111_182210.mp4
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: