Skip to content

[BYOC] Bulk assign cards - Update assign card flow in RHP#77931

Merged
carlosmiceli merged 54 commits intobyoc-bulk-card-assign-r1from
byoc-bulk-card-assign-r1-card-flow
Dec 18, 2025
Merged

[BYOC] Bulk assign cards - Update assign card flow in RHP#77931
carlosmiceli merged 54 commits intobyoc-bulk-card-assign-r1from
byoc-bulk-card-assign-r1-card-flow

Conversation

@carlosmiceli
Copy link
Contributor

@carlosmiceli carlosmiceli commented Dec 17, 2025

Explanation of Change

New card assignment flow:

  • Select a card from the table
  • Pick a member in the RHP
  • Confirm the details in confirmation screen in RHP
  • Cardholder, card name, and start date are editable
  • Also updated back navigation for all possible flows

Fixed Issues

$ #77796
PROPOSAL:

Tests

  • Verify that no errors appear in the JS console

Offline tests

QA Steps

// TODO: These must be filled out, or the issue title must include "[No QA]."

  • 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 verified there are no new alerts related to the canBeMissing param for useOnyx
  • I followed proper code patterns (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
      • If any non-english text was added/modified, I used JaimeGPT to get English > Spanish translation. I then posted it in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
    • 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 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)
  • 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
  • I verified that if a function's arguments changed that all usages have also been updated correctly
  • 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 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.
  • 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.
  • 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

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

@hungvu193
Copy link
Contributor

One thing I noticed during testing is, sometimes Last updated field is empty after assigning a card. We probably should hide it if it's empty

Screen.Recording.2025-12-18.at.16.36.16.mov

@hungvu193
Copy link
Contributor

hungvu193 commented Dec 18, 2025

Not related to this PR but I think it's good to fix it (if you think it's under the scope of this PR), we have similiar issue here, but looks like they don't fix it in every other places.

Bug: App crashes when reloading card details bug

  1. Click on any card on Company Card Page.
  2. Reload the page.
Screen.Recording.2025-12-18.at.16.46.11.mov

Co-authored-by: Hans <hungvu193@users.noreply.github.com>
@hungvu193
Copy link
Contributor

hungvu193 commented Dec 18, 2025

Another thing I ,guess we should need to fix, user can still assign the card when the card connection is broken:

  1. Import Plaid card > Click Assign to assign the card.
  2. Notice in the background, there's an error shows that card connection is broken > go back to Company Card page
  3. Notice that the Assign button is disabled.
  4. Reload the page and click on Assign button again.
  5. Notice that even when the error appears, you're still able to assign that card.
Screen.Recording.2025-12-18.at.22.54.27.mov

carlosmiceli and others added 3 commits December 18, 2025 11:19
Co-authored-by: Hans <hungvu193@users.noreply.github.com>
…leton

Implement loading skeleton for Company Cards table
@hungvu193
Copy link
Contributor

Bug: Card name is overflow when it's too long

  1. Open company card page.
  2. Click Assign.
  3. Change the card name to a very long name (100 characters) save and Assign the card.
  4. Notice the Card display name in company card page.
Screen.Recording.2025-12-19.at.00.06.06.mov

@github-actions
Copy link
Contributor

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

@github-actions
Copy link
Contributor

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

Android 🤖 iOS 🍎
https://ad-hoc-expensify-cash.s3.amazonaws.com/android/77931/index.html https://ad-hoc-expensify-cash.s3.amazonaws.com/ios/77931/index.html
Android iOS
Desktop 💻 Web 🕸️
⏩ SKIPPED ⏩ https://77931.pr-testing.expensify.com
The build for Desktop was skipped Web

👀 View the workflow run that generated this build 👀

@@ -51,7 +53,10 @@ function ConfirmationStep({policyID, feed, backTo}: ConfirmationStepProps) {
const [cardFeeds] = useCardFeeds(policyID);

const data = assignCard?.data;
Copy link
Contributor

Choose a reason for hiding this comment

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

I don't think this constant is valuable. I would update everything to reference assigneCard?.data (which some places do already).

Copy link
Contributor

Choose a reason for hiding this comment

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

✅ Updated.

Comment on lines +44 to +48
const backTo = route?.params?.backTo;
if (backTo) {
Navigation.goBack(backTo);
return;
}
Copy link
Contributor

Choose a reason for hiding this comment

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

There is a pretty big refactoring underway to remove backTo. I don't think the necessary foundation is in place yet to refactor this, so it will probably need to remain as-is for now.

Comment on lines +138 to +155
onPress={() => {
if (!assignedCard) {
onAssignCard(cardIdentifier);
return;
}

if (!assignedCard?.accountID || !assignedCard?.fundID) {
return;
}

return Navigation.navigate(
ROUTES.WORKSPACE_COMPANY_CARD_DETAILS.getRoute(
policyID,
assignedCard.cardID.toString(),
getCompanyCardFeedWithDomainID(assignedCard?.bank as CompanyCardFeed, assignedCard.fundID),
),
);
}}
Copy link
Contributor

Choose a reason for hiding this comment

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

Can you please move this function to be declared outside of return ()?

Copy link
Contributor

Choose a reason for hiding this comment

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

return (
<WorkspaceCompanyCardsFeedAddedEmptyPage
shouldShowGBDisclaimer={shouldShowGBDisclaimer}
handleAssignCard={onAssignCard}
Copy link
Contributor

Choose a reason for hiding this comment

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

All other places in this PR the code is andleAssignCard={() => onAssignCard()}. Is this OK like this? I assume it's passing a cardID to the callback and the other references are specifically NOT passing a cardID?

Copy link
Contributor

Choose a reason for hiding this comment

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

@ikevin127
Copy link
Contributor

♻️ Checking comments / issues reported by @hungvu193 & @tgolen and addressing them...

@dannymcclain dannymcclain requested a review from a team December 18, 2025 20:25
@dannymcclain
Copy link
Contributor

dannymcclain commented Dec 18, 2025

🐛 BUG: Somehow this card ended up with an empty Card name field (kinda). I'm not really sure how to reproduce this as this is just kinda how the feed loaded in for me.

CardNameEmptySomehow.mp4

@dylanexpensify
Copy link
Contributor

dylanexpensify commented Dec 18, 2025

🐛 BUG: Clicking update card for a card after assigning doesn't result in an updated timestamp

Screen.Recording.2025-12-18.at.4.19.36.PM.mov

@dylanexpensify
Copy link
Contributor

dylanexpensify commented Dec 18, 2025

🐛 BUG: Going offline while on plaid card feed and navigating to commercial card feeds throws an Uh oh error

Screen.Recording.2025-12-18.at.4.21.42.PM.mov

@dannymcclain
Copy link
Contributor

🐛 BUG: When I simulate failed network requests, the assign button doesn't do anything.

NothingHappensWhenRequestFails.mp4

@dannymcclain
Copy link
Contributor

🧼 Polish / 🐛 Bug: There are no slide transitions on the RHP screens, the screens just change instantly.

NoTransitions.mp4

@dannymcclain
Copy link
Contributor

🐛 BUG: Header changes on Start date screen causing an unnecessary UI jump:

Normal Extra text
CleanShot 2025-12-18 at 16 01 06@2x CleanShot 2025-12-18 at 16 01 25@2x

@dylanexpensify
Copy link
Contributor

🧼 Polish: transition for unassigning card can be quicker/more seamless. Currently it disappears and reappears.

Screen.Recording.2025-12-18.at.4.25.09.PM.mov

@dannymcclain
Copy link
Contributor

🧼 Polish: Card icon reloads for every kind of filtering transition:

IconReloading.mp4

cc @chrispader

@carlosmiceli carlosmiceli merged commit 70531b6 into byoc-bulk-card-assign-r1 Dec 18, 2025
35 of 55 checks passed
@carlosmiceli carlosmiceli deleted the byoc-bulk-card-assign-r1-card-flow branch December 18, 2025 21:59
@carlosmiceli carlosmiceli restored the byoc-bulk-card-assign-r1-card-flow branch December 18, 2025 22:00
@OSBotify
Copy link
Contributor

🚀 Deployed to staging by https://github.com/carlosmiceli in version: 9.2.86-0 🚀

platform result
🖥 desktop 🖥 success ✅
🕸 web 🕸 success ✅
🤖 android 🤖 failure ❌
🍎 iOS 🍎 success ✅

@OSBotify
Copy link
Contributor

🚀 Deployed to production by https://github.com/marcaaron in version: 9.2.86-4 🚀

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

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants