Skip to content

Show pending BYOC transactions in NewDot#91231

Merged
amyevans merged 41 commits into
Expensify:mainfrom
daledah:fix/91098
Jul 9, 2026
Merged

Show pending BYOC transactions in NewDot#91231
amyevans merged 41 commits into
Expensify:mainfrom
daledah:fix/91098

Conversation

@daledah

@daledah daledah commented May 20, 2026

Copy link
Copy Markdown
Contributor

Explanation of Change

Show pending BYOC card transactions in NewDot UI

  • Extend pending indicator in TypeCell to all pending card transactions (not just Expensify Card)
  • Extend transaction/report view status bar to all pending card transactions
  • Extend report preview "Receipt · Pending" to all pending card transactions
  • Update delete confirmation modal copy for pending BYOC transactions

Fixed Issues

$ #91098
PROPOSAL:

Tests

Precondition: Log in with an account that has pending BYOC transactions.

Case 1 - Pending indicator in TypeCell

  1. Go to Spend page
  2. Locate the BYOC pending transaction.
  3. Verify that: the Type column shows a CreditCardHourglass icon

Case 2 - Report preview shows "Pending"

  1. Go to Inbox page
  2. Locate the BYOC pending transaction preview
  3. Verify that: Report preview shows "· Pending"

Case 3 - Delete confirmation modal copy for pending BYOC transactions

  1. Open a BYOC pending transaction and tap Delete.
  2. Verify that: the confirmation modal reads: "Are you sure that you want to delete this expense? It's pending and we may import it again if it posts." and modal title is "Delete pending expense"

Case 4 - Pending next steps message in expense detail view

  1. Open a BYOC pending transaction
  2. Verify that: the next steps message reads: "All transactions are pending. You can't submit this report until they post in a few days."

Case 5 - Approve button hidden

  1. Open a report where all transactions are BYOC pending.
  2. Submit this report
  3. Verify that: the Approve button is not shown as a primary action and in the secondary actions menu in the report header.

Case 6 - Delete confirmation copy for mixed pending/non-pending selection

  1. Go to the Spend page, enter selection mode.
  2. Select multiple expenses where some are BYOC pending and some are not.
  3. Tap Delete.
  4. Verify that: the confirmation prompt reads: "Are you sure that you want to delete these expenses? Some of them are pending and we may import them again if they post."

Case 7 - Submission blocking for all-pending transactions (BYOC)

  1. Open a report where all transactions are BYOC pending.
  2. Tap the Submit button.
  3. Verify that: a blocking modal appears (same behavior as Expensify Card pending), preventing submission.

8 - Delete confirmation copy for mixed pending/non-pending selection

  1. Go to the Spend page, enter selection mode.
  2. Select multiple expenses where some are BYOC pending and some are not.
  3. Tap Delete.
  4. Verify that the confirmation prompt reads: "Are you sure that you want to delete these expenses? Some of them are pending and we may import them again if they post."
  • 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 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
web.mov

@melvin-bot

melvin-bot Bot commented May 20, 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

@daledah

This comment was marked as outdated.

@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

}, [showConfirmModal, translate, caseID, iouTransactionID, shouldOpenSplitExpenseEditFlowOnDelete, navigateToTargetUrl, deleteTransaction]);

P3 Badge Add transaction dependency to delete-modal callback

Update the showDeleteModal callback dependencies to include iouTransaction (or a derived pending flag). The callback now branches on isPending(iouTransaction), but iouTransaction is not in the dependency array, so if Onyx updates the transaction status while this page stays mounted (for example, pending → posted after sync), the modal can show stale copy (deleteConfirmationPendingBYOC vs normal delete text) until another dependency changes.

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

@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 9d2181f9..2fb383fa 100644
--- a/src/languages/de.ts
+++ b/src/languages/de.ts
@@ -1669,6 +1669,7 @@ const translations: TranslationDeepObject<typeof en> = {
         },
         bulkDuplicateLimit: `Sie können bis zu ${CONST.SEARCH.BULK_DUPLICATE_LIMIT} Ausgaben gleichzeitig duplizieren. Bitte wählen Sie weniger Ausgaben aus und versuchen Sie es erneut.`,
         deleted: 'Gelöscht',
+        deleteConfirmationPendingBYOC: 'Möchten Sie diese Ausgabe wirklich löschen? Sie ist ausstehend und wir importieren sie möglicherweise erneut, sobald sie verbucht wird.',
     },
     transactionMerge: {
         listPage: {
diff --git a/src/languages/es.ts b/src/languages/es.ts
index 27db271a..7ffce518 100644
--- a/src/languages/es.ts
+++ b/src/languages/es.ts
@@ -1625,6 +1625,7 @@ const translations: TranslationDeepObject<typeof en> = {
             prompt: 'Habilita el seguimiento de impuestos en el espacio de trabajo para editar los detalles del gasto o eliminar el impuesto de este gasto.',
             confirmText: 'Eliminar impuesto',
         },
+        deleteConfirmationPendingBYOC: '¿Seguro que quieres eliminar este gasto? Está pendiente y es posible que lo volvamos a importar si se contabiliza.',
     },
     transactionMerge: {
         listPage: {
diff --git a/src/languages/fr.ts b/src/languages/fr.ts
index 76c7ab07..515a336a 100644
--- a/src/languages/fr.ts
+++ b/src/languages/fr.ts
@@ -1673,6 +1673,7 @@ const translations: TranslationDeepObject<typeof en> = {
         },
         bulkDuplicateLimit: `Vous pouvez dupliquer jusqu’à ${CONST.SEARCH.BULK_DUPLICATE_LIMIT} dépenses à la fois. Veuillez sélectionner moins de dépenses et réessayer.`,
         deleted: 'Supprimé',
+        deleteConfirmationPendingBYOC: 'Voulez-vous vraiment supprimer cette dépense ? Elle est en attente et nous pourrions l’importer à nouveau si elle est comptabilisée.',
     },
     transactionMerge: {
         listPage: {
diff --git a/src/languages/it.ts b/src/languages/it.ts
index f4e72a6a..a8d2dc05 100644
--- a/src/languages/it.ts
+++ b/src/languages/it.ts
@@ -1667,6 +1667,7 @@ const translations: TranslationDeepObject<typeof en> = {
         },
         bulkDuplicateLimit: `Puoi duplicare fino a ${CONST.SEARCH.BULK_DUPLICATE_LIMIT} spese alla volta. Seleziona meno spese e riprova.`,
         deleted: 'Eliminato',
+        deleteConfirmationPendingBYOC: 'Sei sicuro di voler eliminare questa spesa? È in sospeso e potremmo importarla di nuovo se viene contabilizzata.',
     },
     transactionMerge: {
         listPage: {
diff --git a/src/languages/ja.ts b/src/languages/ja.ts
index b2e0e4c5..218ccc44 100644
--- a/src/languages/ja.ts
+++ b/src/languages/ja.ts
@@ -1647,6 +1647,7 @@ const translations: TranslationDeepObject<typeof en> = {
         },
         bulkDuplicateLimit: `一度に複製できる経費は最大で ${CONST.SEARCH.BULK_DUPLICATE_LIMIT} 件です。経費の数を減らして、もう一度お試しください。`,
         deleted: '削除済み',
+        deleteConfirmationPendingBYOC: 'この経費を削除してもよろしいですか?現在保留中のため、処理が完了すると再度取り込まれる可能性があります。',
     },
     transactionMerge: {
         listPage: {
diff --git a/src/languages/nl.ts b/src/languages/nl.ts
index 8821e9ab..52d7d716 100644
--- a/src/languages/nl.ts
+++ b/src/languages/nl.ts
@@ -1662,6 +1662,7 @@ const translations: TranslationDeepObject<typeof en> = {
         },
         bulkDuplicateLimit: `Je kunt maximaal ${CONST.SEARCH.BULK_DUPLICATE_LIMIT} uitgaven tegelijk dupliceren. Selecteer minder uitgaven en probeer het opnieuw.`,
         deleted: 'Verwijderd',
+        deleteConfirmationPendingBYOC: 'Weet je zeker dat je deze uitgave wilt verwijderen? Hij is in behandeling en we kunnen hem opnieuw importeren als hij wordt geboekt.',
     },
     transactionMerge: {
         listPage: {
diff --git a/src/languages/pl.ts b/src/languages/pl.ts
index cefba7c6..36173d73 100644
--- a/src/languages/pl.ts
+++ b/src/languages/pl.ts
@@ -1663,6 +1663,7 @@ const translations: TranslationDeepObject<typeof en> = {
         },
         bulkDuplicateLimit: `Możesz jednocześnie zduplikować maksymalnie ${CONST.SEARCH.BULK_DUPLICATE_LIMIT} wydatków. Wybierz mniej wydatków i spróbuj ponownie.`,
         deleted: 'Usunięto',
+        deleteConfirmationPendingBYOC: 'Na pewno chcesz usunąć ten wydatek? Jest w toku i możemy go ponownie zaimportować, jeśli zostanie zaksięgowany.',
     },
     transactionMerge: {
         listPage: {
diff --git a/src/languages/pt-BR.ts b/src/languages/pt-BR.ts
index 55b2c640..09aa23d6 100644
--- a/src/languages/pt-BR.ts
+++ b/src/languages/pt-BR.ts
@@ -1660,6 +1660,7 @@ const translations: TranslationDeepObject<typeof en> = {
         },
         bulkDuplicateLimit: `Você pode duplicar até ${CONST.SEARCH.BULK_DUPLICATE_LIMIT} despesas por vez. Selecione menos despesas e tente novamente.`,
         deleted: 'Excluído',
+        deleteConfirmationPendingBYOC: 'Tem certeza de que quer excluir esta despesa? Ela está pendente e podemos importá-la novamente se for lançada.',
     },
     transactionMerge: {
         listPage: {
diff --git a/src/languages/zh-hans.ts b/src/languages/zh-hans.ts
index 6a2a77ba..0e9e8ebb 100644
--- a/src/languages/zh-hans.ts
+++ b/src/languages/zh-hans.ts
@@ -1613,6 +1613,7 @@ const translations: TranslationDeepObject<typeof en> = {
         taxDisabledAlert: {title: '税费已禁用', prompt: '请在工作区中启用税费跟踪,以便编辑此报销的详细信息或从该报销中删除税费。', confirmText: '删除税费'},
         bulkDuplicateLimit: `您一次最多可以复制 ${CONST.SEARCH.BULK_DUPLICATE_LIMIT} 笔报销。请减少选择的报销数量后重试。`,
         deleted: '已删除',
+        deleteConfirmationPendingBYOC: '您确定要删除这笔报销吗?它目前处于待处理状态,如果入账后,我们可能会再次导入。',
     },
     transactionMerge: {
         listPage: {

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 May 21, 2026

Copy link
Copy Markdown

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 Δ
...eportPreview/MoneyRequestReportPreviewProvider.tsx 92.10% <100.00%> (ø)
src/hooks/useExpenseActions.ts 0.00% <ø> (ø)
src/hooks/useSearchBulkActions.ts 53.84% <100.00%> (+0.39%) ⬆️
src/libs/ReportUtils.ts 86.35% <100.00%> (-0.07%) ⬇️
...eaderActions/MoneyReportHeaderSecondaryActions.tsx 0.67% <0.00%> (ø)
...oneyReportHeaderPrimaryAction/PayPrimaryAction.tsx 0.00% <0.00%> (ø)
src/components/MoneyRequestHeader.tsx 0.00% <0.00%> (ø)
.../components/MoneyRequestHeaderSecondaryActions.tsx 0.51% <0.00%> (-0.01%) ⬇️
src/hooks/useMoneyReportHeaderStatusBar.ts 0.00% <0.00%> (ø)
src/libs/TransactionUtils/index.ts 88.93% <90.90%> (+0.09%) ⬆️
... and 4 more
... and 14 files with indirect coverage changes

@daledah

This comment was marked as outdated.

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. Already looking forward to the next diff.

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

@sobitneupane

Copy link
Copy Markdown
Contributor

Extend pending indicator in TypeCell to all pending card transactions (not just Expensify Card)
Extend transaction/report view status bar to all pending card transactions
Extend report preview "Receipt · Pending" to all pending card transactions
Update delete confirmation modal copy for pending BYOC transactions

@daledah Could you please add Tests and QA steps for all the above cases?

@daledah

This comment was marked as outdated.

@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: 621e27789d

ℹ️ 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/hooks/useSelectionModeReportActions.ts Outdated
@daledah

This comment was marked as outdated.

@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: 2815c1f9d8

ℹ️ 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/hooks/useMoneyReportHeaderStatusBar.ts
@daledah

daledah commented May 23, 2026

Copy link
Copy Markdown
Contributor Author

@codex review

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. Nice work!

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

@github-actions

github-actions Bot commented Jul 6, 2026

Copy link
Copy Markdown
Contributor

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

@github-actions

This comment has been minimized.

@joekaufmanexpensify

Copy link
Copy Markdown
Contributor

BUG: deleting pending personal card expense doesn't work

This seems to be fixed now! Can't reproduce anymore on the new adhoc 🎉

2026-07-06_17-13-32.mp4

@melvin-bot
melvin-bot Bot requested a review from robertjchen July 7, 2026 12:22

@robertjchen robertjchen 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.

Nice!

@joekaufmanexpensify joekaufmanexpensify 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.

Working well from my perspective 👍

@amyevans amyevans 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.

Looks great!

@amyevans
amyevans merged commit 606d4c3 into Expensify:main Jul 9, 2026
38 of 39 checks passed
@github-actions

github-actions Bot commented Jul 9, 2026

Copy link
Copy Markdown
Contributor

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

@OSBotify

OSBotify commented Jul 9, 2026

Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/amyevans in version: 9.4.32-0 🚀

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

@m-natarajan

Copy link
Copy Markdown

@daledah @sobitneupane @joekaufmanexpensify Can this one please be tested internally because of the Precondition: Log in with an account that has pending BYOC transactions.

@joekaufmanexpensify

Copy link
Copy Markdown
Contributor

Yeah, I can do internal QA today.

@joekaufmanexpensify

Copy link
Copy Markdown
Contributor

Working well!

One very minor thing I noticed: when you open an unreported pending card transaction, the next step in the header still references all transactions being unable to submit a report, even though the transaction itself is unreported. This is a bit odd. It might be better to use a different next step header for this case. What do we think?

(This is not a blocker, so still checking off for QA. I figure we can handle this in a follow up).

image

@joekaufmanexpensify

Copy link
Copy Markdown
Contributor

checked off!

@amyevans

amyevans commented Jul 9, 2026

Copy link
Copy Markdown
Contributor

Oh good find, definitely agree that's a little odd. What do you think about this instead:

This transaction is pending. It may take a few days to post.

@joekaufmanexpensify

Copy link
Copy Markdown
Contributor

Whoops, I meant to suggest something in my message above, too. Largely agree with what you posted, but I think maybe we can tighten up the first sentence even further. What do you think about what we originally had in the design doc, which is this:

Transaction pending. It may take a few days to post.

@amyevans

amyevans commented Jul 9, 2026

Copy link
Copy Markdown
Contributor

Ah yes, I should've checked the doc 🤦‍♀️. Transaction pending. It may take a few days to post. is great 👍

@daledah could you open up a follow up PR with that tweak please?

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/grgia in version: 9.4.32-3 🚀

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

Bundle Size Analysis (Sentry):

@daledah

daledah commented Jul 11, 2026

Copy link
Copy Markdown
Contributor Author

@daledah could you open up a follow up PR with that tweak please?

@amyevans yes, i'll open the follow up PR soon

@daledah

daledah commented Jul 13, 2026

Copy link
Copy Markdown
Contributor Author

@amyevans @sobitneupane we have the follow up PR here

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.

10 participants