8000 feat: Allow admins to pay with any business bank account they have access to by samranahm · Pull Request #83638 · Expensify/App · GitHub
[go: up one dir, main page]

Skip to content

feat: Allow admins to pay with any business bank account they have access to#83638

Merged
Gonals merged 29 commits intoExpensify:mainfrom
samranahm:82853/allow-to-pay-with-any-account
Mar 12, 2026
Merged

feat: Allow admins to pay with any business bank account they have access to#83638
Gonals merged 29 commits intoExpensify:mainfrom
samranahm:82853/allow-to-pay-with-any-account

Conversation

@samranahm
Copy link
Contributor
@samranahm samranahm commented Feb 26, 2026

Explanation of Change

Fixed Issues

$ #82853
PROPOSAL: #82853 (comment)

Tests

Prerequisites

  • User is an admin on workspace.
  • Connect a Business Bank Account to workspace (accounts must be fully set up).
  • Invite some members on workspace.

**Test 01 - Single workspace **

  1. Open the Workspace chat as an workspace member.
  2. Submit an expense report (for example, $20) in the Workspace chat.
  3. As admin Approve the report and verify that the Pay button appears on the Report preview along with a dropdown button.
  4. Click the dropdown button and verify that two options appear:
    • Business Bank Account
    • Mark as paid
  5. Click Business Bank Account (for example, Alberta Bobbeth Charleson) and verify that report get paid successfully
  6. As member submit another report and admin approves it and open reports page > To-do > Pay
  7. Select the report and press green selected button and verify Pay button appear and don't have right chevron
  8. Press pay and verify report paid successfully thorough business bank account since last payment was with business bank account

Test 02 - Multiple workspaces

Prerequisites

  • User is an admin on 02+ workspace.
  • Connect a Business Bank Account to each of those workspaces (accounts must be fully set up).
  • Invite some members on workspace.
  1. Open the Workspace chat as an workspace member.
  2. Submit an expense report (for example, $20) in the Workspace chat.
  3. As admin Approve the report and verify that the Pay button appears on the Report preview along with a dropdown button.
  4. Press dropdown button and verify all the Business Bank Accounts admin are available for admin
  5. Select any account and verify report get successfully get paid
  6. Open the expense report and verify "paid with bank account 1234" message appear
  7. Verify last 4 digits in system message match with business bank account that used to pay the report
  8. Cancel the payment or as member submit another report
  9. Open Report page > Todo > Pay and select the available report > Press green selected button
  10. Verify Pay button available and has right chevron
  11. Press pay button and verify all Business Bank Accounts are available along with "Mark as paid" option
  12. Choose any Business bank Account and verify report paid successfully.
  • Verify that no errors appear in the JS console

Offline tests

QA Steps

Same as test
// 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 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 n 8000 ew 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.Native.mp4
Android: mWeb Chrome
Android.mWeb.Chrome.mp4
iOS: Native
IOS.Native.mp4
iOS: mWeb Safari
IOS.mWeb.Safari.mp4
MacOS: Chrome / Safari
macOS.Chrome.mp4

@codecov
Copy link
codecov bot commented Feb 27, 2026

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/PopoverMenu.tsx 81.86% <100.00%> (-0.10%) ⬇️
src/components/ProcessMoneyReportHoldMenu.tsx 0.00% <ø> (ø)
src/libs/ReportUtils.ts 76.85% <100.00%> (+0.06%) ⬆️
src/libs/actions/IOU/index.ts 72.78% <100.00%> (+0.01%) ⬆️
src/libs/actions/Search.ts 30.30% <66.66%> (-0.07%) ⬇️
...report/ContextMenu/BaseReportActionContextMenu.tsx 0.00% <0.00%> (ø)
...es/inbox/report/ContextMenu/ContextMenuActions.tsx 25.49% <0.00%> (ø)
src/pages/inbox/report/ReportActionItemMessage.tsx 51.35% <0.00%> (ø)
src/components/Search/SearchBulkActionsButton.tsx 2.94% <0.00%> (-0.09%) ⬇️
...stWithSections/Search/ActionCell/PayActionCell.tsx 0.00% <0.00%> (ø)
... and 6 more
... and 6 files with indirect coverage changes

@samranahm samranahm marked this pull request as ready for review February 27, 2026 22:52
@samranahm samranahm requested a review from a team as a code owner February 27, 2026 22:52
Copilot AI review requested due to automatic review settings February 27, 2026 22:52
@samranahm samranahm requested a review from a team as a code owner February 27, 2026 22:52
Copy link
Contributor
Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

Enables admins to pay expense reports using any business bank account they have access to (not just the workspace-linked one), and propagates the selected bank account through the pay + KYC flows down to the PayMoneyRequest API call.

Changes:

  • Add a shared helper to derive “valid business bank account” options and use it in the SettlementButton and bulk-pay flows.
  • Persist selected bank-account data through KYC in Search bulk actions and include the selected bankAccountID in payment payloads.
  • Extend PayMoneyRequest API params and IOU pay logic to support passing bankAccountID.

Reviewed changes

Copilot reviewed 12 out of 12 changed files in this pull request and generated 4 comments.

Show a summary per file
File Description
tests/unit/PaymentUtilsTest.ts Updates unit test wording for renamed input concept.
src/libs/actions/Search.ts Threads selected bank account additionalData through KYC for bulk pay selection.
src/libs/actions/IOU/index.ts Adds methodID input and forwards it as bankAccountID for VBBA payments.
src/libs/PaymentUtils.ts Adds getBusinessBankAccountOptions() and updates getActivePaymentType() to use it.
src/libs/API/parameters/PayMoneyRequestParams.ts Adds optional bankAccountID to PayMoneyRequest params.
src/hooks/useSearchBulkActions.ts Builds payment data with selected business bank account id for expense reports.
src/hooks/useBulkPayOptions.ts Builds bulk pay menu items that include all eligible business bank accounts.
src/components/SettlementButton/index.tsx Updates pay dropdown to show all eligible business bank accounts (with submenu when multiple).
src/components/SelectionListWithSections/Search/ActionCell/PayActionCell.tsx Includes bankAccountID in pay request for VBBA payments.
src/components/Search/types.ts Introduces BulkPaySelectionData shape for bulk-pay additional data.
src/components/Search/SearchBulkActionsButton.tsx Stores pending selected bank account data across KYC completion.
src/components/MoneyReportHeader.tsx Passes selected methodID into IOU pay request for VBBA payments.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copy link
@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

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: dac9cdb3ff

ℹ️ 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".

@ikevin127
Copy link
Contributor 8000

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 tests pass on all platforms & I tested again on:
    • Android: Native
    • Android: mWeb Chrome
    • iOS: Native
    • 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 the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
    • 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.js 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 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.
  • 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-hybrid.mp4
Android: mWeb Chrome
android-mweb.mp4
iOS: HybridApp
ios-hybrid.mov
iOS: mWeb Safari
ios-mweb.mov
MacOS: Chrome / Safari
web.mov

@ikevin127
Copy link
Contributor
ikevin127 commented Feb 28, 2026

🔴 MANUAL TESTING BLOCKER REGRESSIONS @samranahm

  1. The UI overflow issue mentioned in proposal review and agreed-upon by design was not resolved:
bug-1

Note for author on how to replicate this locally if you only have 2 BA options, is to apply this diff in order to duplicate the 2 accounts multiple times:

DIFF
diff --git a/src/components/SettlementButton/index.tsx b/src/components/SettlementButton/index.tsx
index 1323285b1cb..e25a1c3fda1 100644
--- a/src/components/SettlementButton/index.tsx
+++ b/src/components/SettlementButton/index.tsx
@@ -311,24 +311,25 @@ function SettlementButton({
                     });
                 }
             } else {
+                const xyx = businessBankAccountOptionList.map((account) => ({
+                    text: account.text,
+                    description: account.description,
+                    icon: account.icon,
+                    iconStyles: account.iconStyles,
+                    iconHeight: account.iconSize,
+                    iconWidth: account.iconSize,
+                    onSelected: () => {
+                        if (checkForNecessaryAction()) {
+                            return;
+                        }
+                        onPress(CONST.IOU.PAYMENT_TYPE.VBBA, true, account.methodID, CONST.PAYMENT_METHODS.BUSINESS_BANK_ACCOUNT);
+                    },
+                }))
                 buttonOptions.push({
                     text: translate('iou.settleBusiness', formattedAmount),
                     icon: icons.Building,
                     value: CONST.PAYMENT_METHODS.BUSINESS_BANK_ACCOUNT,
-                    subMenuItems: businessBankAccountOptionList.map((account) => ({
-                        text: account.text,
-                        description: account.description,
-                        icon: account.icon,
-                        iconStyles: account.iconStyles,
-                        iconHeight: account.iconSize,
-                        iconWidth: account.iconSize,
-                        onSelected: () => {
-                            if (checkForNecessaryAction()) {
-                                return;
-                            }
-                            onPress(CONST.IOU.PAYMENT_TYPE.VBBA, true, account.methodID, CONST.PAYMENT_METHODS.BUSINESS_BANK_ACCOUNT);
-                        },
-                    })),
+                    subMenuItems: [...xyx, ...xyx, ...xyx, ...xyx, ...xyx, ...xyx, ...xyx, ...xyx, ...xyx, ...xyx],
                 });
             }
         }

  1. The deposit and withdrawal accounts are the same. error on payment when selecting different account

Following the PRs test steps, this issue happens at step 6 which is failing (see video below).

❌ 6. Select one of the accounts and verify that the report is paid successfully.

bug-3.mov


Could be related to payment action not receiving the correct bank account ID from the UI selection.

Important

Should be resolved with the suggested fix from this comment.

  1. Bulk Pay button not showing right side carret with options when clicked (not reproducible on staging)

Following the PRs test steps, this issue happens at steps 9-10 which are failing (see video below on issue contrast between this PR and staging).

❌ 9. Open the Reports page, go to the To-do tab, click Pay, select all expenses, and press pay to bulk pay all the reports.
❌ 10. Select Pay and press pay as a business and verify that all valid business bank accounts appear in the list.

bug-2.mov


Notes:

Bulk Pay button not showing right side caret with options when clicked. This is because <ButtonWithDropdownMenu> hides the right-side caret when options.length === 1. Since the newly pushed BUSINESS_BANK_ACCOUNT payload utilizes a subMenuItems map instead of a top-level onSelected trigger, clicking the button fails to open the menu. You must either dynamically flatten businessBankAccountOptionList if no other root payout methods exist (Wallet/Elsewhere), or ensure this component behaves identically to the staging nested hierarchy.

// useBulkPayOptions.ts (Line 150)
bulkPayButtonOptions.push({
    text: translate('iou.settleBusiness', formattedAmount),
    icon: icons.Building,
    key: CONST.PAYMENT_METHODS.BUSINESS_BANK_ACCOUNT,
    subMenuItems: businessBankAccountOptionList.map(...) // <--- The Nested Items
});

Notice what is missing ? There is no onSelected parameter.

@ikevin127
Copy link
Contributor

🧪 Test Coverage Analysis

Author's Diff Coverage Added: 0%

Checking the tests/unit/PaymentUtilsTest.ts lines, the author successfully renamed the description strings of existing tests (latestBankItems -> businessBankAccountOptions) - but wrote exactly zero actual assertions validating the internals of getBusinessBankAccountOptions.

⚠️ Next Step Required: Add unit tests validating that getBusinessBankAccountOptions() explicitly drops partiallySetup and PERSONAL accounts, and strictly returns properly constructed BusinessBankAccountOption payloads.

@samranahm Besides the 3 bugs mentioned here which are blockers, all AI reviewer comments are also valid / blockers + a few from me found during code review.

🟢 I completed the PR Reviewer Checklist. Once all blocker issues are addressed please tag me and I'll test the PR again to verify everything works as expected 🙌

@samranahm
Copy link
Contributor Author

Thanks for the review @ikevin127! I’ll tag you once I’ve addressed all potential blockers and review comments.

Copy link
Contributor
@JmillsExpensify JmillsExpensify left a comment

Choose a reason for hiding this comment

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

Big fan of this PR! It's part of an existing product initiative, so approving. cc @joekaufmanexpensify in case you want to test more thoroughly.

@joekaufmanexpensify joekaufmanexpensify self-requested a review March 2, 2026 13:56
@joekaufmanexpensify
Copy link
Contributor

I am interested to test. Will do that in a bit!

@samranahm
Copy link
Contributor Author

Falling checks are not related to this PR.

@Gonals
Copy link
Contributor
Gonals commented Mar 9, 2026

@samranahm, there are some comflicts

@samranahm
Copy link
Contributor Author

@Gonals I've resolved the conflicts.

Gonals
Gonals previously approved these changes Mar 11, 2026
@Gonals
Copy link
Contributor
Gonals commented Mar 11, 2026

More conflicts 🤣

@samranahm
Copy link
Contributor Author

Resolving merge conflicts

@samranahm

This comment was marked as resolved.

@samranahm
Copy link
Contributor Author

@Gonals All yours

@Gonals Gonals merged commit d0cc2f3 into Expensify:main Mar 12, 2026
31 checks passed
@github-actions
Copy link
Contributor

🚧 @Gonals 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, and Web. Happy testing! 🧪🧪
Built from App PR #83638.

Android 🤖 iOS 🍎
❌ FAILED ❌ https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-ios-device-AdHoc-d0cc2f3-3d8daef-ae8b58dc5f8cb54e133be47276fdc45cb2f262bb/index.html
The QR code can't be generated, because the Android build failed iOS
Web 🕸️
https://83638.pr-testing.expensify.com
Web

👀 View the workflow run that generated this build 👀

@OSBotify
Copy link
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
Copy link
Contributor

🚀 Deployed to staging by https://github.com/Gonals in version: 9.3.37-0 🚀

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

@mitarachim
Copy link

Deploy Blocker #85159 was identified to be related to this PR.

@samranahm
Copy link
Contributor Author

Deploy Blocker #85159 was identified to be related to this PR.

No related to this PR. Issue still persist after reverting locally.

@jponikarchuk
Copy link

Deploy Blocker #85180 was identified to be related to this PR.

@jponikarchuk
Copy link

Deploy Blocker #85191 was identified to be related to this PR.

luacmartins added a commit that referenced this pull request Mar 13, 2026
…ith-any-account"

This reverts commit d0cc2f3, reversing
changes made to 3fec5bc.
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.

9 participants

0