Use correct border color for bot avatar edit icon by MelvinBot · Pull Request #91337 · Expensify/App

MelvinBot · 2026-05-21T17:38:38Z

Explanation of Change

The bot avatar edit icon on EditAgentPage and AddAgentPage uses styles.profilePageAvatar which sets borderColor: theme.highlightBG. This is wrong because those pages render the avatar on theme.appBG (not inside a Section card like ProfilePage), so the border doesn't match the background.

Switched both pages to use styles.smallEditIconAccount which sets borderColor: theme.appBG, matching the actual background.

Fixed Issues

$ #91335
PROPOSAL: #91335 (comment)

Tests

Go to account
Click on agents
Click on Create Agent
Verify that inside the avatar image -> in the edit icon: the border matches the expected design (ignore the pencil per https://expensify.slack.com/archives/C090U774ZH7/p1779385538010099?thread_ts=1779356769.547799&cid=C090U774ZH7):

Verify that no errors appear in the JS console

Offline tests

N/A — this is a style-only change with no network behavior.

QA Steps

Same as tests

Verify that no errors appear in the JS console

PR Author Checklist

AI Tests

Prettier: passed (no changes needed)
ESLint: passed
TypeScript: pre-existing errors only (unrelated ConvertGpsPointsTo2DArray.ts)
Jest (Agent-related tests): 8 suites, 111 tests passed
React Compiler: could not run (missing git remote in CI environment)

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

The agent pages render the avatar on appBG background, but were using profilePageAvatar style which sets borderColor to highlightBG. Switch to smallEditIconAccount which uses appBG to match the actual background. Co-authored-by: Nicolás Bonet <NicolasBonet@users.noreply.github.com>

melvin-bot · 2026-05-21T17:51:28Z

@jayeshmangwani 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]

puneetlath · 2026-05-21T17:57:12Z

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 shown in the product is localized by adding it to src/languages/* files and using the translation method
- I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
- 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)
- I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
- I verified the JSDocs style guidelines (in STYLE.md) were followed
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)
I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
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.
If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
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

MelvinBot · 2026-05-21T17:58:57Z

All checks on this PR are currently passing (or skipping/pending where expected). There are no failing CI checks to fix.

The review check shows "pending" because it's waiting for reviewer approval — that's not a CI failure.

github-actions · 2026-05-21T18:00:59Z

🚧 @puneetlath has triggered a test Expensify/App build. You can view the workflow run here.

github-actions · 2026-05-21T18:07:28Z

🧪🧪 Use the links below to test this adhoc build on Android, iOS, and Web. Happy testing! 🧪🧪
Built from App PR #91337.

Android 🤖	iOS 🍎
https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-android-Adhoc-4817a84-fdf8a2c-5e7c0434144e798272a0ed8d1325b8e7651cca29/index.html	https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-ios-device-AdHoc-4817a84-fdf8a2c-aa8900a6f1265a5b311c560613bdf2f375c98d72/index.html

Web 🕸️
https://91337.pr-testing.expensify.com

👀 View the workflow run that generated this build 👀

OSBotify · 2026-05-21T18:10:41Z

✋ 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 · 2026-05-21T21:54:22Z

🚀 Deployed to staging by https://github.com/puneetlath in version: 9.3.79-1 🚀

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

Bundle Size Analysis (Sentry):

Android
iOS

MelvinBot · 2026-05-21T21:56:19Z

No help site changes are required for this PR. It is a style-only fix that corrects the border color of the bot avatar edit icon on the Add Agent and Edit Agent pages. No user-facing features, workflows, settings, or terminology were added or changed.

OSBotify · 2026-05-22T22:28:17Z

🚀 Deployed to production by https://github.com/roryabraham in version: 9.3.79-4 🚀

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

MelvinBot assigned NicolasBonet May 21, 2026

MelvinBot requested a review from a team May 21, 2026 17:38

MelvinBot mentioned this pull request May 21, 2026

[Due for payment 2026-05-29] Border color on edit icon for bot avatar is using slightly wrong color #91335

Closed

NicolasBonet marked this pull request as ready for review May 21, 2026 17:51

NicolasBonet requested a review from a team as a code owner May 21, 2026 17:51

melvin-bot Bot requested review from jayeshmangwani and trjExpensify and removed request for a team May 21, 2026 17:51

melvin-bot Bot removed request for a team and trjExpensify May 21, 2026 17:51

NicolasBonet requested review from puneetlath and shawnborton May 21, 2026 17:52

shawnborton approved these changes May 21, 2026

View reviewed changes

puneetlath approved these changes May 21, 2026

View reviewed changes

puneetlath merged commit 4817a84 into main May 21, 2026
61 of 70 checks passed

puneetlath deleted the claude-fixBotAvatarEditIconBorderColor branch May 21, 2026 18:00

OSBotify mentioned this pull request May 21, 2026

Deploy Checklist: New Expensify 2026-05-21 #91350

Closed

quinthar added the #ai label Aug 11, 2026

Navigation Menu

Use correct border color for bot avatar edit icon - #91337

Use correct border color for bot avatar edit icon#91337
puneetlath merged 1 commit into
mainfrom
claude-fixBotAvatarEditIconBorderColor

MelvinBot commented May 21, 2026 •

edited by puneetlath

Loading

Uh oh!

melvin-bot Bot commented May 21, 2026

Uh oh!

puneetlath commented May 21, 2026 •

edited

Loading

Uh oh!

MelvinBot commented May 21, 2026

Uh oh!

Uh oh!

github-actions Bot commented May 21, 2026

Uh oh!

github-actions Bot commented May 21, 2026

Uh oh!

OSBotify commented May 21, 2026

Uh oh!

OSBotify commented May 21, 2026

Uh oh!

MelvinBot commented May 21, 2026

Uh oh!

OSBotify commented May 22, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

6 participants

Conversation

MelvinBot commented May 21, 2026 • edited by puneetlath Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Explanation of Change

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

AI Tests

Screenshots/Videos

Uh oh!

melvin-bot Bot commented May 21, 2026

Uh oh!

puneetlath commented May 21, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Reviewer Checklist

Screenshots/Videos

Uh oh!

MelvinBot commented May 21, 2026

Uh oh!

Uh oh!

github-actions Bot commented May 21, 2026

Uh oh!

github-actions Bot commented May 21, 2026

Uh oh!

OSBotify commented May 21, 2026

Uh oh!

OSBotify commented May 21, 2026

Uh oh!

MelvinBot commented May 21, 2026

Uh oh!

OSBotify commented May 22, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

6 participants

MelvinBot commented May 21, 2026 •

edited by puneetlath

Loading

puneetlath commented May 21, 2026 •

edited

Loading