[Search v1] New Search Page - Page shows blank UI

[kavimuru]

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!

---

Version Number: 1.4.78-2
Reproducible in staging?: y
Reproducible in production?: n (test preference is not in production)
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. Access new.staging.expensify.com
2. Sign into a valid account
3. Go to Account Settings > Troubleshoot > New search page

Expected Result:

User expects the new search page to show and display all IOUS

Actual Result:

A blank UI is shown

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

View all open jobs on GitHub

[melvin-bot]

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

[melvin-bot]

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

[github-actions]

👋 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.

[kavimuru]

@alexpensify FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors.

[alexpensify]

Moving this to Daily since help is on the way

[alexpensify]

@luacmartins It looks like the PR was rolled back, what's the plan for this one? Thanks for the update!

[luacmartins]

Correct, we reverted this PR along with many others due to the fire. However, we already merged the re-revert PR and it should go out with the next Auth deploy

[luacmartins]

This is now fixed. We're done here

[alexpensify]

Awesome, thanks for the update @luacmartins!