"Not here" error message when opening report fields

[m-natarajan]

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.51-3
Reproducible in staging?: y
Reproducible in production?: y
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: @Ollyws
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1710320724430419

Action Performed:

Preconditon : Have some report fields for the collect workspace in OldDot

1. Open app
2. Sign in as the employee
3. Create an expense report
4. Opent the expense report
5. Click on the report fields

Expected Result:

Should not lead to not here page

Actual Result:

getting a not here page when opening report fields

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

Recording.2849.mp4

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @adelekennedy (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

[hungvu193]

Our BE has updated reportFields logic and this one will be solved when this PR is merge
#36553
So let hold this on #36553

[bernhardoj]

Oh, there is an issue created for this. How about we fix this first separately to unblock #37583?

@hungvu193 @thienlnam

[hungvu193]

Base on this comment I think we still need to hold this one. But let see what's his thought 😄

[adelekennedy]

I think the video above is incorrect

Screen.Recording.2024-03-13.at.09.01.48.mov

[adelekennedy]

@JmillsExpensify I think this falls under wave control release one

[thienlnam]

As mentioned, this App PR should fix things #36553 along with the one back-end PR that should be merged soon

[adelekennedy]

Should this just be put on hold then until then? Or are we confident enough to close it?

[thienlnam]

Either works, I would just link to that issue so we don't re-create this

[adelekennedy]

then I'm closing it! We'll reopen if it's an issue