Skip to content

Add Accounting option to Expensify Card details + Update design - #96923

Merged
lakchote merged 19 commits into
Expensify:mainfrom
s77rt:rillet-card-details-accounting
Jul 27, 2026
Merged

lakchote merged 19 commits into
Expensify:mainfrom
s77rt:rillet-card-details-accounting

Conversation

@s77rt

@s77rt s77rt commented Jul 24, 2026

Copy link
Copy Markdown
Member

Explanation of Change

  • Added accounting option row to Expensify Card details
  • Updated accounting option row to match design

Fixed Issues

$ #95951
PROPOSAL:

Tests

  • Have a workspace connected to Rillet
  • Have assigned Expensify Card and Company card
  1. Go to any Expensify Card details
  2. Verify the Accounting option match the attached screenshot
Image
  1. Go to any Company Card details
  2. Verify the Accounting option match the attached screenshot
Image
Screen.Recording.2026-07-24.at.6.15.41.AM.mov
  • Verify that no errors appear in the JS console

Offline tests

Same as Tests

QA Steps

Same as Tests

  • 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

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

@melvin-bot

melvin-bot Bot commented Jul 24, 2026

Copy link
Copy Markdown

Hey, I noticed you changed src/languages/en.ts in a PR from a fork. For security reasons, translations are not generated automatically for PRs from forks.

If you want to automatically generate translations for other locales, an Expensify employee will have to:

  1. Look at the code and make sure there are no malicious changes.
  2. Run the Generate static translations GitHub workflow. If you have write access and the K2 extension, you can simply click: [this button]

Alternatively, if you are an external contributor, you can run the translation script locally with your own OpenAI API key. To learn more, try running:

npx ts-node ./scripts/generateTranslations.ts --help

Typically, you'd want to translate only what you changed by running npx ts-node ./scripts/generateTranslations.ts --compare-ref main

@s77rt
s77rt marked this pull request as ready for review July 24, 2026 05:49
@s77rt
s77rt requested review from a team as code owners July 24, 2026 05:49
@melvin-bot
melvin-bot Bot requested a review from truph01 July 24, 2026 05:49
@melvin-bot

melvin-bot Bot commented Jul 24, 2026

Copy link
Copy Markdown

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

@s77rt

s77rt commented Jul 24, 2026

Copy link
Copy Markdown
Member Author

@truph01 This one is based on #96845. Filter on latests commits for the actual changes here

@s77rt
s77rt requested a review from lakchote July 24, 2026 05:50
@s77rt

s77rt commented Jul 24, 2026

Copy link
Copy Markdown
Member Author

@lakchote Please run translate workflow #96923 (comment)

@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: 6a33ba83a1

ℹ️ 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 thread src/ROUTES.ts
Comment thread src/pages/workspace/expensifyCard/DynamicWorkspaceExpensifyCardDetailsPage.tsx Outdated
@lakchote

Copy link
Copy Markdown
Contributor

@lakchote Please run translate workflow #96923 (comment)

Done

@OSBotify

Copy link
Copy Markdown
Contributor

🦜 Polyglot Parrot! 🦜

Squawk! Looks like you added some shiny new English strings. Allow me to parrot them back to you in other tongues:

View the translation diff
diff --git a/src/languages/de.ts b/src/languages/de.ts
index 2b4c88ee9c3..7f775988246 100644
--- a/src/languages/de.ts
+++ b/src/languages/de.ts
@@ -529,6 +529,7 @@ const translations: TranslationDeepObject<typeof en> = {
         unableToDisplayChart: 'Diagram kann nicht angezeigt werden',
         webGLNotSupported: 'Ihr Browser unterstützt WebGL nicht. Bitte aktivieren Sie es oder wechseln Sie den Browser.',
         apiKey: 'API-Schlüssel',
+        exportsTo: 'Exportiert nach',
     },
     socials: {
         podcast: 'Folgen Sie uns auf Podcast',
diff --git a/src/languages/es.ts b/src/languages/es.ts
index 293750179f1..e2797936021 100644
--- a/src/languages/es.ts
+++ b/src/languages/es.ts
@@ -482,6 +482,7 @@ const translations: TranslationDeepObject<typeof en> = {
         tagGLCode: 'Etiquetar código GL',
         off: 'Desactivado',
         noResultsFoundSubtitle: 'Sin resultados. Intenta ajustar tus filtros o la búsqueda.',
+        exportsTo: 'Exporta a',
     },
     socials: {
         podcast: 'Síguenos en Podcast',
diff --git a/src/languages/fr.ts b/src/languages/fr.ts
index 86ad445d9ff..b1dc4fdc070 100644
--- a/src/languages/fr.ts
+++ b/src/languages/fr.ts
@@ -529,6 +529,7 @@ const translations: TranslationDeepObject<typeof en> = {
         unableToDisplayChart: 'Impossible d’afficher le graphique',
         webGLNotSupported: 'Votre navigateur ne prend pas en charge WebGL. Veuillez l’activer ou changer de navigateur.',
         apiKey: 'Clé API',
+        exportsTo: 'Exports vers',
     },
     socials: {
         podcast: 'Suivez-nous sur Podcast',
diff --git a/src/languages/it.ts b/src/languages/it.ts
index 1647e4c0e87..a7405122d41 100644
--- a/src/languages/it.ts
+++ b/src/languages/it.ts
@@ -529,6 +529,7 @@ const translations: TranslationDeepObject<typeof en> = {
         unableToDisplayChart: 'Impossibile visualizzare il grafico',
         webGLNotSupported: 'Il tuo browser non supporta WebGL. Abilitalo oppure passa a un altro browser.',
         apiKey: 'Chiave API',
+        exportsTo: 'Esporta in',
     },
     socials: {
         podcast: 'Seguici su Podcast',
diff --git a/src/languages/ja.ts b/src/languages/ja.ts
index 7a8dc0136b0..fe4f744eba8 100644
--- a/src/languages/ja.ts
+++ b/src/languages/ja.ts
@@ -528,6 +528,7 @@ const translations: TranslationDeepObject<typeof en> = {
         unableToDisplayChart: 'グラフを表示できません',
         webGLNotSupported: 'お使いのブラウザは WebGL に対応していません。有効にするか、別のブラウザに切り替えてください。',
         apiKey: 'API キー',
+        exportsTo: 'エクスポート先',
     },
     socials: {
         podcast: 'ポッドキャストでフォロー',
diff --git a/src/languages/nl.ts b/src/languages/nl.ts
index 43980fc8472..9ae033e07cc 100644
--- a/src/languages/nl.ts
+++ b/src/languages/nl.ts
@@ -528,6 +528,7 @@ const translations: TranslationDeepObject<typeof en> = {
         unableToDisplayChart: 'Grafiek kan niet worden weergegeven',
         webGLNotSupported: 'Je browser ondersteunt WebGL niet. Schakel het in of gebruik een andere browser.',
         apiKey: 'API-sleutel',
+        exportsTo: 'Exporteert naar',
     },
     socials: {
         podcast: 'Volg ons op Podcast',
diff --git a/src/languages/pl.ts b/src/languages/pl.ts
index 9b4bcdc9d1d..5816f9397b1 100644
--- a/src/languages/pl.ts
+++ b/src/languages/pl.ts
@@ -528,6 +528,7 @@ const translations: TranslationDeepObject<typeof en> = {
         unableToDisplayChart: 'Nie można wyświetlić wykresu',
         webGLNotSupported: 'Twoja przeglądarka nie obsługuje WebGL. Włącz ją albo zmień przeglądarkę.',
         apiKey: 'Klucz API',
+        exportsTo: 'Eksporty do',
     },
     socials: {
         podcast: 'Śledź nas na Podcast',
diff --git a/src/languages/pt-BR.ts b/src/languages/pt-BR.ts
index 4f1ee271622..e97fd30c4a5 100644
--- a/src/languages/pt-BR.ts
+++ b/src/languages/pt-BR.ts
@@ -527,6 +527,7 @@ const translations: TranslationDeepObject<typeof en> = {
         unableToDisplayChart: 'Não foi possível exibir o gráfico',
         webGLNotSupported: 'Seu navegador não é compatível com WebGL. Ative-o ou mude de navegador.',
         apiKey: 'Chave de API',
+        exportsTo: 'Exportações para',
     },
     socials: {
         podcast: 'Siga-nos no Podcast',
diff --git a/src/languages/zh-hans.ts b/src/languages/zh-hans.ts
index eed8b03bf3c..e32ea0b2c0d 100644
--- a/src/languages/zh-hans.ts
+++ b/src/languages/zh-hans.ts
@@ -524,6 +524,7 @@ const translations: TranslationDeepObject<typeof en> = {
         unableToDisplayChart: '无法显示图表',
         webGLNotSupported: '您的浏览器不支持 WebGL。请启用该功能或更换浏览器。',
         apiKey: 'API 密钥',
+        exportsTo: '导出到',
     },
     socials: {
         podcast: '在播客上关注我们',

Note

You can apply these changes to your branch by copying the patch to your clipboard, then running pbpaste | git apply 😉

View workflow run

@codecov

codecov Bot commented Jul 24, 2026

Copy link
Copy Markdown

Codecov Report

✅ Changes either increased or maintained existing code coverage, great job!

Files with missing lines Coverage Δ
src/ROUTES.ts 21.72% <0.00%> (ø)
src/libs/actions/CompanyCards.ts 7.88% <0.00%> (ø)
...unting/rillet/export/RilletCardAccountCardList.tsx 0.00% <0.00%> (ø)
src/pages/workspace/companyCards/utils.tsx 20.73% <0.00%> (ø)
...namicWorkspaceCompanyCardAccountSelectCardPage.tsx 0.00% <0.00%> (ø)
...nyCards/DynamicWorkspaceCompanyCardDetailsPage.tsx 0.00% <0.00%> (ø)
...yCard/DynamicWorkspaceExpensifyCardDetailsPage.tsx 0.00% <0.00%> (ø)
... and 6 files with indirect coverage changes

@s77rt

s77rt commented Jul 24, 2026

Copy link
Copy Markdown
Member Author

Addressed comments

BTW, I have updated the accounting option only for Rillet, the rest (e.g. Sage) are still as they are today. Should I update those as well if so with what copy? (should all have same copy Exports to ...?)

Screenshot 2026-07-24 at 7 43 19 PM Screenshot 2026-07-24 at 7 43 02 PM

Comment thread src/pages/workspace/companyCards/DynamicWorkspaceCompanyCardDetailsPage.tsx Outdated
@s77rt
s77rt requested a review from truph01 July 26, 2026 01:18
Comment thread src/ROUTES.ts
// The cardID param is optional because some entry screens e.g. `SCREENS.WORKSPACE.DYNAMIC_COMPANY_CARD_DETAILS`
// already has the cardID in their path and we don't want to double pass the cardID.
getRoute: (cardID?: string) => `edit/export${cardID ? `/${encodeURIComponent(cardID)}` : ''}` as const,
path: 'edit/export/:feed/:cardID',

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

@s77rt Why do we need to introduce :feed param here?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

@MelvinBot Could you explain the purpose of new :feed param?

@MelvinBot

Copy link
Copy Markdown
Contributor

The :feed param tells the export/account-select screen (DynamicWorkspaceCompanyCardAccountSelectCardPage) which feed the card belongs to. It needs the feed to load the card list (useCardsList(feed)), resolve the domainOrWorkspaceAccountID from cardFeeds?.[feed], and set the export account via getCompanyCardFeed(feed).

Why it's new here: previously the route was edit/export/:cardID? with no feed segment, and the screen was only reachable from Company Card entry screens whose own paths already carried :feed — so the dynamic route inherited the feed from the parent's params (and cardID could even be optional for the same reason). This PR adds DYNAMIC_EXPENSIFY_CARD_DETAILS as a new entry screen so the export screen is now shared by both Expensify Cards and Company Cards, which live under different feeds. Since the feed can no longer be reliably inherited across both entry points, it's now passed explicitly as :feed in the route path (and cardID is now required too).

@truph01

truph01 commented Jul 26, 2026

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
Screen.Recording.2026-07-26.at.18.43.18.mov
Android: mWeb Chrome
iOS: HybridApp
Screen.Recording.2026-07-26.at.18.42.21.mov
iOS: mWeb Safari
MacOS: Chrome / Safari
Screen.Recording.2026-07-26.at.18.14.02.mov

@lakchote

Copy link
Copy Markdown
Contributor

Addressed comments

BTW, I have updated the accounting option only for Rillet, the rest (e.g. Sage) are still as they are today. Should I update those as well if so with what copy? (should all have same copy Exports to ...?)

Screenshot 2026-07-24 at 7 43 19 PM Screenshot 2026-07-24 at 7 43 02 PM

I'd say yes @heyjennahay @JmillsExpensify you confirm?

@JmillsExpensify

Copy link
Copy Markdown
Contributor

Yes, we should update all the existing connections as well, though we might want to do that in a separate PR since we need to tackle all integrations, including QuickBooks Desktop too.

@lakchote

Copy link
Copy Markdown
Contributor

^ cc @s77rt we should do that as a follow-up

@lakchote lakchote left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

LGTM

@lakchote
lakchote merged commit e576d1f into Expensify:main Jul 27, 2026
36 of 40 checks passed
@OSBotify

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.

@github-actions

Copy link
Copy Markdown
Contributor

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

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/lakchote in version: 9.4.45-0 🚀

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

@MelvinBot

Copy link
Copy Markdown
Contributor

Help site review — no changes required

I reviewed this PR against the help site files under App/docs/articles and no updates are needed. I did not open a docs PR.

What this PR changes (user-facing):

  • Adds an Accounting section with an Exports to … row to the Expensify Card details page.
  • Restyles the existing accounting row on the Company Card details page (adds the connection icon + an "Exports to" prefix).

Why no docs change is required:

  • The underlying capability — assigning a per-card export account from the Card Details page — is already documented and remains accurate in Configure-Company-Card-Settings.md ("How to export to individual accounts"). This PR is a design/UI refinement of that flow — no documented step becomes incorrect.
  • The change is scoped to the Rillet accounting integration (per the PR test steps). Rillet is intentionally unlisted / upcoming — its only mention in the docs is an internal AgentZero reference explicitly marked "Not for public search indexing" (Unlisted/Upcoming-Integrations-And-Accounting.md). There is no public help article for Rillet to update, and it isn't yet part of the public help site.
  • No existing article describes the Expensify Card details page in a way that this restyle would contradict.

If Rillet (or per-Expensify-Card export accounts) later graduates to a publicly documented integration, that would be the point to add a dedicated help article — but nothing is required for this UI change.

@s77rt — since no docs changes are required, I didn't create a help site PR (so there's nothing to mark Ready for review). If you think a specific article should still be updated, let me know which one and I'll draft it.

@s77rt

s77rt commented Jul 27, 2026

Copy link
Copy Markdown
Member Author

^ cc @s77rt we should do that as a follow-up

Let's handle this on its own issue

@jponikarchuk

Copy link
Copy Markdown

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

@s77rt

s77rt commented Jul 28, 2026

Copy link
Copy Markdown
Member Author

That does not look related

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/marcaaron in version: 9.4.45-14 🚀

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

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants