Split bill - Red dot appears in the split bill from "Teachers Unite!" workspace

[lanitochka17]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Issue found when executing PR #27952

Action Performed:

1. Go to https://staging.new.expensify.com/teachersunite
2. Select I am a teacher and submit the form
3. Go to "Teachers Unite!" workspace
4. Create a split bill
5. Log in to ND using the principal account that is entered in the form in Step 2
6. Open the split bill

Expected Result:

here is no red dot in the IOU

Actual Result:

The split bill IOU appears with a red dot, and there is no error message

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

• Android / native
• Android / Chrome
• iOS / native
• iOS / Safari
• MacOS / Chrome / Safari
• MacOS / Desktop

Version Number: 1.3.79-3

Reproducible in staging?: Yes

Reproducible in production?: Yes

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

Notes/Photos/Videos: Any additional supporting documentation

0-02-01-814709aa7f3dd4044910c82a4820640f3370c9addb3d1639fa8d2b296bd30570_14a4a0e325b737cf.mp4

Expensify/Expensify Issue URL:

Issue reported by: Applause - Internal Team

Slack conversation:

View all open jobs on GitHub

[melvin-bot]

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

[melvin-bot]

Bug0 Triage Checklist (Main S/O)

• This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
• This bug is not a duplicate report (check E/App issues and #expensify-bugs)
  • If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead
• This bug is reproducible using the reproduction steps in the OP. S/O
  • If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
  • If the reproduction steps aren't clear and you determine the correct steps, please update the OP.
• This issue is filled out as thoroughly and clearly as possible
  • Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.
• I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

[Pujan92]

Seems a BE issue as openReport api responds with "Report no longer exists"

[dylanexpensify]

@RachCHopkins @youssef-lr @marcochavezf assigning you since it's a TU issue!

[RachCHopkins]

@dylanexpensify I'm not part of the BugZero team. What is it you want me to do here?

[youssef-lr]

Investigating this one today.