Skip to content

[CP Staging] Revert #98603: Copilot list search inputs - #99983

Merged
youssef-lr merged 2 commits into
mainfrom
francois-revert-98603
Sep 1, 2026
Merged

youssef-lr merged 2 commits into
mainfrom
francois-revert-98603

Conversation

@francoisl

@francoisl francoisl commented Sep 1, 2026

Copy link
Copy Markdown
Contributor

Explanation of Change

Reverts #98603, which added search inputs to the Copilot list and the account switcher copilot list. That feature produced four deploy blockers on the 9.4.65-1 checklist, so it is being pulled from staging rather than patched under deploy pressure.

This also reverts #99970, which fixed the padding on the search field that #98603 introduced. It only exists to patch the reverted feature, so it goes with it.

Fixed Issues

$ #99961
$ #99964
$ #99972
$ #99974

Tests

Same as QA

  • Verify that no errors appear in the JS console

QA Steps

Verify that all the blockers linked in "Fixed issues" are no longer reproducible

  • Verify that no errors appear in the JS console

PR Author Checklist

  • I linked the correct issue in the ### Fixed Issues section above
  • I wrote clear testing steps that cover the changes made in this PR
    • I added steps for local testing in the Tests section
    • I added steps for the expected offline behavior in the Offline steps section
    • I added steps for Staging and/or Production testing in the QA steps section
    • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
    • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
    • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
  • I included screenshots or videos for tests on all platforms
  • I ran the tests on all platforms & verified they passed on:
    • Android: Native
    • Android: mWeb Chrome
    • iOS: Native
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
  • I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
  • I followed proper code patterns (see Reviewing the code)
    • I verified that comments were added to code that is not self explanatory
    • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
    • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • I followed the guidelines as stated in the Review Guidelines
  • I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
  • If a new CSS style is added I verified that:
    • A similar style doesn't already exist
    • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))
  • If new assets were added or existing ones were modified, I verified that:
    • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
    • The assets load correctly across all supported platforms.
  • If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
  • If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
  • If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
  • If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
  • If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
    • I verified that all the inputs inside a form are aligned with each other.
    • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
  • I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
  • If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

MacOS: Chrome / Safari

…erSearchBarPadding"

This reverts commit 366ca46, reversing
changes made to 08050ee.
…rch-input-reapply"

This reverts commit cc94f81, reversing
changes made to 6c9b62f.
@codecov

codecov Bot commented Sep 1, 2026

Copy link
Copy Markdown

Codecov Report

❌ Looks like you've decreased code coverage for some files. Please write tests to increase, or at least maintain, the existing level of code coverage. See our documentation here for how to interpret this table.

Files with missing lines Coverage Δ
src/components/Modal/ReanimatedModal/index.tsx 80.00% <100.00%> (ø)
src/components/PopoverMenu/index.tsx 92.38% <100.00%> (+1.26%) ⬆️
src/components/SearchBar/index.tsx 100.00% <100.00%> (ø)
src/pages/settings/Copilot/CopilotPage.tsx 70.94% <100.00%> (-1.03%) ⬇️
...nents/Modal/ReanimatedModal/Backdrop/index.web.tsx 0.00% <0.00%> (ø)
src/components/AccountSwitcher.tsx 82.00% <66.66%> (-1.18%) ⬇️
... and 13 files with indirect coverage changes

@francoisl
francoisl requested a review from youssef-lr September 1, 2026 00:38
@francoisl
francoisl marked this pull request as ready for review September 1, 2026 00:38
@francoisl
francoisl requested review from a team as code owners September 1, 2026 00:38
@melvin-bot
melvin-bot Bot requested review from eh2077 and trjExpensify and removed request for a team September 1, 2026 00:38
@melvin-bot

melvin-bot Bot commented Sep 1, 2026

Copy link
Copy Markdown

@eh2077 Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

@francoisl
francoisl requested review from eh2077 and removed request for eh2077 September 1, 2026 00:39

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: f9b40a2b99

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment on lines +150 to +152
const backdropStyle: ViewStyle = useMemo(() => {
return {width: windowWidth, height: windowHeight, backgroundColor: backdropColor};
}, [windowWidth, windowHeight, backdropColor]);

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Preserve full-viewport web backdrops

On mobile Safari when the reported useWindowDimensions() viewport is smaller than the modal host—particularly during browser chrome or keyboard viewport changes—these explicit pixel dimensions constrain the shared ReanimatedModal backdrop, leaving part of the page undimmed and outside the backdrop press target. This also removes the full-screen wrapper in Backdrop/index.web.tsx, rolling back the generic small-web-screen fix from 8102a6b8c23 even though the search inputs are the feature being reverted; retain the platform-specific web sizing so all BaseModal usages still cover the viewport.

Useful? React with 👍 / 👎.

@youssef-lr

Copy link
Copy Markdown
Contributor

Reviewer Checklist

  • I have verified the author checklist is complete (all boxes are checked off).
  • I verified the correct issue is linked in the ### Fixed Issues section above
  • I verified testing steps are clear and they cover the changes made in this PR
    • I verified the steps for local testing are in the Tests section
    • I verified the steps for Staging and/or Production testing are in the QA steps section
    • I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
    • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
  • I checked that screenshots or videos are included for tests on all platforms
  • I included screenshots or videos for tests on all platforms
  • I verified that the composer does not automatically focus or open the keyboard on mobile unless explicitly intended. This includes checking that returning the app from the background does not unexpectedly open the keyboard.
  • I verified tests pass on all platforms & I tested again on:
    • Android: HybridApp
    • Android: mWeb Chrome
    • iOS: HybridApp
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
  • If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
  • I verified proper code patterns were followed (see Reviewing the code)
    • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
    • I verified that comments were added to code that is not self explanatory
    • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
    • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • I verified that this PR follows the guidelines as stated in the Review Guidelines
  • I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
  • If a new component is created I verified that:
    • A similar component doesn't exist in the codebase
    • All props are defined accurately and each prop has a /** comment above it */
    • The file is named correctly
    • The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
    • The only data being stored in the state is data necessary for rendering and nothing else
    • For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
    • Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
    • All JSX used for rendering exists in the render method
    • The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
  • If any new file was added I verified that:
    • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
  • If a new CSS style is added I verified that:
    • A similar style doesn't already exist
    • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)
  • If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
  • If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
  • If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
  • If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
  • If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
    • I verified that all the inputs inside a form are aligned with each other.
    • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
  • For any bug fix or new feature in this PR, I verified that sufficient unit tests are included to prevent regressions in this flow.
  • If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
  • I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: HybridApp
Android: mWeb Chrome
iOS: HybridApp
iOS: mWeb Safari
MacOS: Chrome / Safari

@youssef-lr
youssef-lr merged commit 8c0fd7e into main Sep 1, 2026
51 of 55 checks passed
@youssef-lr
youssef-lr deleted the francois-revert-98603 branch September 1, 2026 02:16
@github-actions

github-actions Bot commented Sep 1, 2026

Copy link
Copy Markdown
Contributor

🚧 youssef-lr has triggered a test Expensify/App build. You can view the workflow run here.

@OSBotify

OSBotify commented Sep 1, 2026

Copy link
Copy Markdown
Contributor

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

OSBotify pushed a commit that referenced this pull request Sep 1, 2026
[CP Staging] Revert #98603: Copilot list search inputs

(cherry picked from commit 8c0fd7e)

(cherry-picked to staging by roryabraham)
@OSBotify OSBotify added the CP Staging marks PRs that have been CP'd to staging label Sep 1, 2026
@os-botify

os-botify Bot commented Sep 1, 2026

Copy link
Copy Markdown

🔁 Filed a Staging retest request for deploy blockers #99961, #99964, #99972, #99974 after this PR was cherry-picked to staging.

@OSBotify

OSBotify commented Sep 1, 2026

Copy link
Copy Markdown
Contributor

🚀 Cherry-picked to staging by https://github.com/roryabraham in version: 9.4.65-2 🚀

platform result
🕸 web 🕸 success ✅
🤖 android 🤖 success ✅
🍎 iOS 🍎 success ✅

@MelvinBot

Copy link
Copy Markdown
Contributor

No help site changes are required for this PR, so I did not create a docs PR.

This is a pure revert of the Copilot list search inputs. The feature it removes (Expensify/App#98603) and its follow-up padding fix (Expensify/App#99970) never touched docs/articles and were never documented, so reverting them puts the help site back in sync — nothing to add or remove.

What I checked

UI verification

I ran the docs' own steps against the app on this branch. Result: partial — the documented steps work, but one label in the docs does not match the UI. That mismatch is pre-existing and unrelated to this revert.

Step Status Observation
Account > Copilot shows a section labeled "Copilot: Delegated Access" fail The UI renders Copilot: Delegated access (lowercase "access"). Pre-existing docs mismatch, not caused by this PR.
Button to add a copilot is labeled "Add a copilot" pass Matches the docs exactly.
No search / "Find member" input on the Copilot list pass No searchbox node in the accessibility snapshot; "Find member" matches nothing. Revert confirmed.
No search / "Find member" input in the account switcher popover not verifiable The switcher trigger only renders when the account has at least one copilot, and the test account has none, so the popover could not be opened. Code inspection of src/components/AccountSwitcher.tsx confirms this PR removes every search-related prop passed to PopoverMenu.
Evidence (2)

Account > Copilot page showing no search input after the revert

Account > Copilot page showing no search input after the revert

Account sidebar; switcher trigger not rendered for an account with no copilots

Account sidebar; switcher trigger not rendered for an account with no copilots

One separate thing worth fixing

The docs write the section heading as Copilot: Delegated Access, but the UI says Copilot: Delegated access. This appears 11 times across 4 articles (Manage-Copilot-Access.md in both new-expensify and expensify-classic, Act-as-a-Copilot.md, and Create-and-Use-Custom-Agents.md). It predates this PR and is outside the scope of the revert, so I did not open a PR for it. Reply with @MelvinBot fix the Delegated access capitalization in the docs and I'll open a draft PR for just that.

@francoisl — there's no linked help site PR to review or mark Ready for review, because this revert needs no help site changes.


view run

@OSBotify

OSBotify commented Sep 2, 2026

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/francoisl in version: 9.4.65-3 🚀

platform result
🕸 web 🕸 success ✅
🤖 android 🤖 success ✅
🍎 iOS 🍎 success ✅

Bundle Size Analysis (Sentry):

@OSBotify

OSBotify commented Sep 2, 2026

Copy link
Copy Markdown
Contributor

🚀 Cherry-picked to staging by https://github.com/roryabraham in version: 9.4.66-0 🚀

platform result
🕸 web 🕸 success ✅
🤖 android 🤖 success ✅
🍎 iOS 🍎 success ✅

@MelvinBot

MelvinBot commented Sep 2, 2026

Copy link
Copy Markdown
Contributor

No help site changes are required for this PR, so I did not open a docs PR.

This PR reverts the search inputs that #98603 added to the Copilot list and the account switcher's copilot list. No article in App/docs/articles ever documented those search fields, so removing them doesn't invalidate any published step.

What I checked

I also drove the web build on this branch to confirm the Copilot page has no list search field:

Copilot settings page showing Copilot: Delegated access heading and Add a copilot button, with no list search field

Two things worth a look, both outside this PR's scope:

  1. The live section heading is Copilot: Delegated access, but the New Expensify articles write it as Copilot: Delegated Access (capital A) in Manage-Copilot-Access.md and Act-as-a-Copilot.md. Per HELPSITE_NAMING_CONVENTIONS.md only the first word should be capitalized, so the docs are the ones that are wrong. Pre-existing, not caused by this revert — tell me if you want a separate docs PR for it.
  2. During the UI check, clicking Add a copilot opened the help site article instead of the member-selection page. I could not confirm this (the automated click may have landed on the page's help icon, and the session ended there), so treat it as unverified — but it may be worth a manual check on staging.

There's no help site PR to link or mark Ready for review@francoisl, just confirm you agree no docs update is needed, or reply with @MelvinBot if you want me to open a PR for the capitalization fix above.


view run · view recording

@OSBotify

OSBotify commented Sep 2, 2026

Copy link
Copy Markdown
Contributor

🚀 Cherry-picked to staging by https://github.com/roryabraham in version: 9.4.68-0 🚀

platform result
🕸 web 🕸 success ✅
🤖 android 🤖 success ✅
🍎 iOS 🍎 cancelled 🔪

@MelvinBot

Copy link
Copy Markdown
Contributor

No help site changes are required for this PR, so I did not open a docs PR.

This revert removes the search input from the Copilot list and the account switcher. The help site never documented that input, so nothing on the help site is now inaccurate.

How I verified it

The reverted PRs never touched docs. Neither #98603 nor #99970 changed any file under docs/. Both were src/-only, so no help site article was ever written to describe the search field.

No article describes a search field in either list. The only search mention in the Copilot articles is step 3 of "How to add a Copilot" — docs/articles/new-expensify/settings/Manage-Copilot-Access.md:43 ("Search for the member by name or email address"). That is the Add a copilot invite flow, which this PR does not touch. The revert only removes the filter input rendered above the existing delegated-access list in src/pages/settings/Copilot/CopilotPage.tsx and the switcher popover in src/components/AccountSwitcher.tsx.

The documented steps still match the live UI. I checked NewDot web on this branch's code. Account > Copilot shows the Copilot: Delegated access section with the Add a copilot button and no search input above the list — which is what the articles already describe.


One unrelated inaccuracy I noticed while checking labels — flagging it rather than folding it into a revert-scoped PR:

The articles write the section heading as Copilot: Delegated Access, but the live label is Copilot: Delegated access with a lowercase "access" (src/languages/en.ts:10670). It appears 9 times across Manage-Copilot-Access.md, Act-as-a-Copilot.md, and Create-and-Use-Custom-Agents.md. This predates this PR. Reply to me if you want a separate docs PR to correct the capitalization.

@francoisl, since no docs PR was needed here, there is nothing to review or mark Ready for review. Let me know if you'd like the capitalization fix above filed as its own help site PR.


view run

@OSBotify

OSBotify commented Sep 2, 2026

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/francoisl in version: 9.4.68-1 🚀

platform result
🕸 web 🕸 success ✅
🤖 android 🤖 success ✅
🍎 iOS 🍎 success ✅

Bundle Size Analysis (Sentry):

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CP Staging marks PRs that have been CP'd to staging

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants