You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Due for payment 2026-01-21] QBO - Search field in QuickBooks Online debit card export page is missing "Search" label #79458
Version Number: 9.3.0-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:#79080 Email or phone of affected tester (no customers):applausetester+120101abc@applause.expensifail.com Issue reported by: Applause Internal Team Bug source: Exploratory - Significant User Experience Deterioration Device used: Mac 26.1 / Chrome App Component: Workspace Settings
Action Performed:
Precondition:
Assign a company card to any workspace member.
Workspace is connected to QBO.
Go to staging.new.expensify.com
Go to workspace settings > Accounting.
Click Export > Export company card expenses as.
Click Export as > Debit card.
Close the RHP.
Go to workspace settings > Company card.
Click on the assigned company card.
Click QuickBooks Online debit card export.
Expected Result:
Search field in QuickBooks Online debit card export page will show "Search" label.
Actual Result:
Search field in QuickBooks Online debit card export page is missing "Search" label.
👋 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:
Identify the pull request that introduced this issue and revert it.
Classification: Frontend bug Causing PR: #79080 - "Make SelectionScreen use new SelectionList" by @zfurtak (High confidence) Related Issues: None
Recommendation: REVERT
The PR introduced a bug in the SelectionScreen component where textInputOptions is created with incorrect property names (textInputLabel and textInputValue instead of label and value), causing the search field label to not display.
📋 Detailed Analysis
Evidence
PR #79080 refactored SelectionScreen to use the new SelectionList component instead of SelectionListWithSections. During this migration, the way text input options are passed changed:
Old approach (SelectionListWithSections):
Direct props: textInputLabel, textInputValue, onChangeText
New approach (SelectionList):
Single object prop: textInputOptions with properties: label, value, onChangeText
The Bug:
In src/components/SelectionScreen.tsx lines 150-154, the code creates:
consttextInputOptions={
onChangeText,
textInputLabel,// ❌ Should be: label
textInputValue,// ❌ Should be: value};
The new SelectionList component expects textInputOptions.label and textInputOptions.value, but SelectionScreen is passing textInputOptions.textInputLabel and textInputOptions.textInputValue.
In BaseSelectionList.tsx line 85:
shouldShowTextInput=!!textInputOptions?.label,
And line 307:
accessibilityLabel={textInputOptions?.label}
Since textInputOptions.label is undefined, the label is not displayed.
Root Cause
During the refactoring from SelectionListWithSections to SelectionList, the property names in the textInputOptions object were not updated to match the new API. This affects all pages using SelectionScreen with a search field, including the QuickBooks Online debit card export page mentioned in this issue.
Reproduction
The bug is reproducible in staging only (not production) and affects all platforms. It impacts any page using SelectionScreen with search functionality, particularly visible in:
changed the title [-]QBO - Search field in QuickBooks Online debit card export page is missing "Search" label[/-][+][Due for payment 2026-01-21] QBO - Search field in QuickBooks Online debit card export page is missing "Search" label[/+]on Jan 14, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.1-1 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@grgia@mallenexpensify@zfurtak The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]
Activity
melvin-bot commentedon Jan 13, 2026
You have been assigned to this deploy blocker because you recently merged this PR: #79080
melvin-bot commentedon Jan 13, 2026
💬 A slack conversation has been started in #expensify-open-source
melvin-bot commentedon Jan 13, 2026
Triggered auto assignment to @mallenexpensify (
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 commentedon Jan 13, 2026
👋 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:
OSBotify commentedon Jan 13, 2026
🔍 Investigation Summary
Classification: Frontend bug
Causing PR: #79080 - "Make
SelectionScreenuse newSelectionList" by @zfurtak (High confidence)Related Issues: None
Recommendation: REVERT
The PR introduced a bug in the SelectionScreen component where textInputOptions is created with incorrect property names (
textInputLabelandtextInputValueinstead oflabelandvalue), causing the search field label to not display.📋 Detailed Analysis
Evidence
PR #79080 refactored SelectionScreen to use the new SelectionList component instead of SelectionListWithSections. During this migration, the way text input options are passed changed:
Old approach (SelectionListWithSections):
textInputLabel,textInputValue,onChangeTextNew approach (SelectionList):
textInputOptionswith properties:label,value,onChangeTextThe Bug:
In
src/components/SelectionScreen.tsxlines 150-154, the code creates:The new SelectionList component expects
textInputOptions.labelandtextInputOptions.value, but SelectionScreen is passingtextInputOptions.textInputLabelandtextInputOptions.textInputValue.In
BaseSelectionList.tsxline 85:And line 307:
Since
textInputOptions.labelis undefined, the label is not displayed.Root Cause
During the refactoring from SelectionListWithSections to SelectionList, the property names in the textInputOptions object were not updated to match the new API. This affects all pages using SelectionScreen with a search field, including the QuickBooks Online debit card export page mentioned in this issue.
Reproduction
The bug is reproducible in staging only (not production) and affects all platforms. It impacts any page using SelectionScreen with search functionality, particularly visible in:
3 remaining items
[-]QBO - Search field in QuickBooks Online debit card export page is missing "Search" label[/-][+][Due for payment 2026-01-21] QBO - Search field in QuickBooks Online debit card export page is missing "Search" label[/+]melvin-bot commentedon Jan 14, 2026
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Jan 14, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.1-1 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
SelectionScreen#79484If no regressions arise, payment will be issued on 2026-01-21. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Jan 14, 2026
@grgia @mallenexpensify @zfurtak The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]
mallenexpensify commentedon Jan 23, 2026
No payment due. No test case cuz issues came from one. Closing