Skip to content
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

Closed
3 of 6 tasks
lanitochka17 opened this issue Dec 12, 2023 · 7 comments
Closed
3 of 6 tasks
Assignees

Comments

@lanitochka17
Copy link

lanitochka17 commented Dec 12, 2023

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:

  1. Go to https://staging.new.expensify.com/
  2. Click fab
  3. Click request money ----Scan
  4. Upload an image
  5. Select 2 participants and Click split
  6. Click add to split
  7. Click browser refresh button

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?

  • Android: Native
  • Android: mWeb Chrome
  • iOS: Native
  • iOS: mWeb Safari
  • Windows: Chrome
  • MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

Bug6310599_1702394557178.hmm_not.mp4

View all open jobs on GitHub

@lanitochka17 lanitochka17 added the DeployBlockerCash This issue or pull request should block deployment label Dec 12, 2023
Copy link
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.

Copy link

melvin-bot bot commented Dec 12, 2023

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

@luacmartins
Copy link
Contributor

Looking now

@luacmartins
Copy link
Contributor

luacmartins commented Dec 12, 2023

I could not reproduce this on mWeb Safari, iOS native, Desktop nor MacOs chrome. I'm not able to test android devices.

@luacmartins
Copy link
Contributor

Just reproduced on dev MacOS Chrome. Gonna investigate

@luacmartins
Copy link
Contributor

This seems fixed in latest main. I think #32849 fixed it.

@luacmartins
Copy link
Contributor

Gonna close this issue.

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

No branches or pull requests

2 participants