-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
IOU-Error "hhm its not here" displayed on refreshing split bill confirmation page #32934
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 @luacmartins ( |
Looking now |
I could not reproduce this on mWeb Safari, iOS native, Desktop nor MacOs chrome. I'm not able to test android devices. |
Just reproduced on dev MacOS Chrome. Gonna investigate |
This seems fixed in latest main. I think #32849 fixed it. |
Gonna close this issue. |
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.11-13
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:
Action Performed:
Expected Result:
Error "hhm its not here" must not be displayed on refreshing split bill confirmation page
Actual Result:
Error "hhm its not here" displayed on refreshing split bill confirmation page
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6310599_1702394557178.hmm_not.mp4
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: