Teacher Unite - QAB open not here page

[applause-bot]

If you haven’t already, check out our contributing guidelines for onboarding. To join our Slack channel, fill out this form.

---

Version Number: v9.4.77-1
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: https://test-management.browserstack.com/projects/2219752/test-runs/73545242/folder/52724024/41237964/1749949976?sort=%2Bidentifier
Email or phone of affected tester (no customers): applausetester+vq+14081@applause.expensifail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Windows 10/Chrome
App Component: Money Requests

Action Performed:

Precondition: Use the Expensifail account, a Principal account has invited the Teacher account before

1. Open the New Dot app
2. Login with the teacher account
3. Navigate to Profile settings
4. Click on Save the World
5. Click on "I am a teacher"
6. Fill the I'm a teacher form - in the principal field, enter the account that referred the teacher (account in Precondition)
7. Navigate to the created workspace chat
8. Click FAB > QAB

Expected Result:

Scan tab opens like Prod

Actual Result:

Not here page appears.
Same with the Principal account

Workaround:

Unknown

Platforms:

• Android: App
• Android: mWeb Chrome
• iOS: App
• iOS: mWeb Safari
• iOS: mWeb Chrome
• Windows: Chrome
• MacOS: Chrome Safari

Screenshots/Videos

Bug7259355_1789389435554.teacher.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Svetlana Lazutkina
Bug ID: 7259355

[applause-bot]

While Applause doesn't embed attachments for this bug, here are the links for quick view:
https://platform.applause.com/services/links/v1/external/024a7a776f97e59cad56a4fe572ffb2c9f72a328c0cadf0eda512f9f71af0416

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

[melvin-bot]

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

[melvin-bot]

💬 A slack conversation has been started in #expensify-open-source

[MelvinBot]

🔍 Investigation Summary

Classification: Frontend bug (the fix belongs in Expensify/App)
Causing PR: #97858 - "fix: use TRACK instead of SUBMIT for Teachers Unite expenses" by @huult (Medium confidence) — ⚠️ merged 2026-08-26 and already on production, it is NOT in the current deploy checklist
Related Issues: none found

Recommendation: ROLL FORWARD

The "Not here" page is produced by a Teachers Unite restriction that is already live on production, and no PR in this release touches the Quick Action → create-expense path, so a revert of a checklist PR would not fix it. The fix is small and forward-only: the quick action entry points must navigate with an IOU type that a Teachers Unite chat actually allows (split), or getMoneyRequestOptions must keep an allowed type for these chats. @deetergp — since this is not a regression from 9.4.77, this is also a reasonable candidate for demotion off the blocker list, but I have not removed any label.

Assigned: @huult (PR author), @QichenZhu and @rlinoz (approving reviewers) of #97858, which introduced the restriction that triggers the not-found page
Labels: No changes. DeployBlockerCash kept (App-side fix, and the issue does not reproduce on production). DeployBlocker was never applied, so nothing to remove.

📋 Detailed Analysis

Evidence

The "I am a teacher" flow creates the workspace chat on the Teachers Unite policy (addSchoolPrincipal builds the policy expense chat with policyID = TEACHERS_UNITE.PROD_POLICY_ID | TEST_POLICY_ID), so isTeachersUniteReport() is true for that chat.

For such a report, getMoneyRequestOptions deliberately skips submit (and request/track), and only adds split at L10804-L10811:

const isTeachersUniteReportValue = isTeachersUniteReport(report);
...
if (canRequestMoney(report, policy, otherParticipants, rules, currentUserAccountID)) {
    if (!isTeachersUniteReportValue) {
        options = [...options, CONST.IOU.TYPE.SUBMIT];
        ...
    }
}

The Quick Action Button, however, always starts the scan flow as submit:

• fallback branch (no saved quick action, the "Scan receipt" QAB shown against the active workspace chat): QuickActionMenuItem.tsx#L237-L238
• saved quick action branch: QuickActionNavigation.ts#L52-L54

startMoneyRequest then routes to MONEY_REQUEST_CREATE_TAB_SCAN with iouType=submit, and the create page is gated by the CREATE access variant of AccessOrNotFoundWrapper, L66:

(isEmptyObject(report?.reportID) || canCreateRequest(report, policy, iouType, isReportArchived, betas, rules, isRestrictedToPreferredPolicy))

canCreateRequest returns ['split', 'create'] for a Teachers Unite chat, submit is not in the list, so the wrapper renders NotFoundPage — the "Not here" page the tester sees. The QAB itself is not gated the same way in the fallback branch, which is why the button is visible but its destination is blocked.

Why this is not a 9.4.77 regression: I diffed production...staging (296 commits, 307 files) and none of the files in this path changed:

• src/pages/inbox/sidebar/FABPopoverContent/menuItems/QuickActionMenuItem.tsx — unchanged
• src/libs/actions/QuickActionNavigation.ts, src/libs/QuickActionUtils.ts — unchanged
• src/libs/actions/IOU/MoneyRequest.ts (startMoneyRequest), src/pages/iou/request/IOURequestStartPage.tsx, withWritableReportOrNotFound.tsx — unchanged
• src/libs/ReportUtils.ts — changed, but only isInvoiceReport, getOneOnOneChatParticipants and the removal of getTripIDFromTransactionParentReportID; getMoneyRequestOptions / canCreateRequest / the Teachers Unite branch are byte-identical to production
• src/pages/workspace/AccessOrNotFoundWrapper.tsx — changed only by Remove rulesRevamp beta. #98662 (removal of the rulesRevamp beta from isPolicyFeatureEnabled), which is not evaluated here because no featureName is passed by the create page
• no changes to ROUTES, SCREENS or the linking config

The Teachers Unite restriction itself is on production (isTeachersUniteReportValue is present in ReportUtils.ts at ref=production), which is why the "not reproducible on production" result most likely reflects a data difference (which workspace chat the QAB resolves to / whether the live Teachers Unite policy ID matches the hardcoded constant per environment) rather than a code difference.

Verification

• Affected files: src/libs/ReportUtils.ts (getMoneyRequestOptions, canCreateRequest), src/pages/workspace/AccessOrNotFoundWrapper.tsx (CREATE access variant), src/pages/inbox/sidebar/FABPopoverContent/menuItems/QuickActionMenuItem.tsx and src/libs/actions/QuickActionNavigation.ts (both hardcode CONST.IOU.TYPE.SUBMIT for the scan quick action).
• fix: use TRACK instead of SUBMIT for Teachers Unite expenses #97858 modified src/libs/ReportUtils.ts and added src/libs/isTeachersUnitePolicyID.ts, i.e. exactly the code that produces the empty option set for Teachers Unite chats (gh pr view 97858 --json files).
• Every PR in the current checklist was checked against the production...staging diff; none modify the quick action, the create-expense route, or the two access checks above.

Root Cause

Teachers Unite policy expense chats are restricted to split (+ the generic create) expenses, but both quick action entry points still start the scan flow with iouType = submit. The create route's CREATE access variant calls canCreateRequest(...), submit is not among the allowed options for that report, and the route renders NotFoundPage instead of the Scan tab. The mismatch is between the option list produced in getMoneyRequestOptions and the hardcoded submit used by the quick action, so the fix is to make the QAB use an allowed type for Teachers Unite chats (or to hide/redirect it there).