-
Notifications
You must be signed in to change notification settings - Fork 3.2k
[Due for payment 2025-05-14] [$125] Bank icons are too small in the "Pay" menu #60579
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Triggered auto assignment to @VictoriaExpensify ( |
This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989 |
ProposalPlease re-state the problem that we are trying to solve in this issue.Bank icons are too small in the "Pay" menu What is the root cause of that problem?App/src/components/Icon/BankIcons/index.ts Lines 36 to 38 in 28fd6af
we are using 26 here Lines 252 to 253 in ab26fec
What changes do you think we should make in order to solve the problem?we need to update this to 40 cardIconHeight: 40, What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?N/A What alternative solutions did you explore? (Optional)Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job. |
ProposalPlease re-state the problem that we are trying to solve in this issue.Bank icons are too small in the "Pay" menu What is the root cause of that problem?We don't set the App/src/components/SettlementButton/index.tsx Lines 166 to 171 in 28fd6af
App/src/components/MenuItem.tsx Lines 727 to 745 in 28fd6af
App/src/components/Icon/index.tsx Lines 58 to 59 in 28fd6af
What changes do you think we should make in order to solve the problem?set App/src/components/SettlementButton/index.tsx Lines 166 to 171 in 28fd6af
Might need to check in other places as well, and do the same Result: What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?None What alternative solutions did you explore? (Optional)None |
@VictoriaExpensify I can reproduce this following the same steps in OP. I can take over as C+ as per this thread. |
🚨 Edited by proposal-police: This proposal was edited at 2025-04-25 03:20:18 UTC. ProposalPlease re-state the problem that we are trying to solve in this issue.Bank icon is too small What is the root cause of that problem?We don't add the iconSize and the border for icon in here App/src/components/SettlementButton/index.tsx Lines 166 to 171 in 28fd6af
And we pass this style here App/src/components/PopoverMenu.tsx Lines 320 to 321 in 28fd6af
What changes do you think we should make in order to solve the problem?We should add the
App/src/components/SettlementButton/index.tsx Lines 166 to 171 in 28fd6af
![]() What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?None What alternative solutions did you explore? (Optional)Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job. |
Agree this is an issue we should fix! |
Job added to Upwork: https://www.upwork.com/jobs/~021914517278232314681 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @hoangzinh ( |
@VictoriaExpensify This one was labeled |
Upwork job price has been updated to $125 |
Making this one $125, it is a minor change |
🚨 Edited by proposal-police: This proposal was edited at 2025-04-22 13:53:24 UTC. ProposalPlease re-state the problem that we are trying to solve in this issue.Bank icons are too small in the "Pay" menu What is the root cause of that problem?We are not setting App/src/components/SettlementButton/index.tsx Lines 166 to 171 in 8d9d43a
What changes do you think we should make in order to solve the problem?Add By default we are using We should use either Lines 81 to 82 in 8d9d43a
Replace this code block with: formattedPaymentMethods.map((formattedPaymentMethod) => ({
text: formattedPaymentMethod?.title ?? '',
description: formattedPaymentMethod?.description ?? '',
icon: formattedPaymentMethod?.icon,
onSelected: () => onPress(CONST.IOU.PAYMENT_TYPE.EXPENSIFY, payAsBusiness, formattedPaymentMethod.methodID, formattedPaymentMethod.accountType),
})); with, const getPaymentSubitems = (payAsBusiness: boolean) =>
formattedPaymentMethods.map((formattedPaymentMethod) => ({
text: formattedPaymentMethod?.title ?? '',
description: formattedPaymentMethod?.description ?? '',
icon: formattedPaymentMethod?.icon,
iconHeight: variables.iconSizeLarge,
iconWidth: variables.iconSizeLarge,
onSelected: () => onPress(CONST.IOU.PAYMENT_TYPE.EXPENSIFY, payAsBusiness, formattedPaymentMethod.methodID, formattedPaymentMethod.accountType),
})); We might also want to add the same in {
text: translate('workspace.invoices.paymentMethods.addBankAccount'),
icon: Expensicons.Bank,
iconHeight: variables.iconSizeLarge,
iconWidth: variables.iconSizeLarge,
onSelected: () => Navigation.navigate(addBankAccountRoute),
},
{
text: translate('iou.payElsewhere', {formattedAmount: ''}),
icon: Expensicons.Cash,
iconHeight: variables.iconSizeLarge,
iconWidth: variables.iconSizeLarge,
value: CONST.IOU.PAYMENT_TYPE.ELSEWHERE,
onSelected: () => onPress(CONST.IOU.PAYMENT_TYPE.ELSEWHERE),
}, What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?NA What alternative solutions did you explore? (Optional)NA |
|
Thank you for posting proposals, everyone. I will try to review them today |
According to the screenshot of the design doc, @nkdengineer's proposal is the most correct. @nkdengineer, do you mind attaching a screenshot of your solution in your proposal? It will help internal engineer review more easily. |
![]() @hoangzinh, here is result |
![]() @hoangzinh i updated the proposal as expected |
@VictoriaExpensify @cristipaval As per this thread:
This issue was marked "needs productions" label and per our guideline, the first C+ who can reproduce should take this issue as a reviewer. I spent my effort to reproduce and posted a comment first here. I think I should be eligible for the C+ role here. |
@dominictb, but at that time, you hadn't confirmed about "reliable reproduction steps". Therefore, your comment here is not eligible, in my opinion. I believe current steps are not enough to reproduce this bug. In my opinion, it should be:
|
@nkdengineer can you update your RCA and problem statement, please? It's not only icon size but also border style. |
@hoangzinh i updated |
Thank you, everyone. @nkdengineer's proposal looks good to me Link to proposal #60579 (comment) 🎀👀🎀 C+ reviewed |
Current assignee @cristipaval is eligible for the choreEngineerContributorManagement assigner, not assigning anyone new. |
📣 @nkdengineer 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app! Offer link |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.40-7 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2025-05-14. 🎊 For reference, here are some details about the assignees on this issue:
|
@hoangzinh @VictoriaExpensify @hoangzinh 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] |
@hoangzinh can you please complete the checklist and I'll process payment? @nkdengineer it looks like you still need to accept the offer so I can process payment. Thank you! |
BugZero Checklist:
Bug classificationSource of bug:
Where bug was reported:
Who reported the bug:
|
Requested payment in ND |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Version Number: 9.1.30-0
Reproducible in staging?: need reproduction (requires real bank)
Reproducible in production?:
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?:
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @shawnborton
Slack conversation (hyperlinked to channel name): #expensify - bugs
Action Performed:
Expected Result:
Band icon should be correct size
Actual Result:
Bank icon is too small
Workaround:
unknown
Platforms:
Select the officially supported platforms where the issue was reproduced:
Platforms Tested:
On which of our officially supported platforms was this issue tested:Screenshots/Videos
Add any screenshot/video evidence
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @Issue Owner
Current Issue Owner: @VictoriaExpensifyThe text was updated successfully, but these errors were encountered: