Skip to content

[HOLD] Show error when card limit is $0 during physical card ordering#87410

Open
Beamanator wants to merge 1 commit intomainfrom
fix/598396-card-limit-error-handling
Open

[HOLD] Show error when card limit is $0 during physical card ordering#87410
Beamanator wants to merge 1 commit intomainfrom
fix/598396-card-limit-error-handling

Conversation

@Beamanator
Copy link
Copy Markdown
Contributor

Explanation of Change

When a user attempts to order a physical Expensify card via SetPersonalDetailsAndShipExpensifyCards and the card has an invalid (zero) limit, the Auth backend currently silently swallows the "400 Card has an invalid limit" error and returns 200 OK. A companion Auth PR (fix the silent swallow) properly returns a 400 in this case.

This PR adds the frontend defense-in-depth: failureData in updatePersonalDetailsAndShipExpensifyCards that writes to ONYXKEYS.PRIVATE_PERSONAL_DETAILS.errors, and a new translation key cardPage.invalidCardLimit with a user-friendly message. The MissingPersonalDetailsMagicCodePage already reads privateDetailsErrors and displays it as a validateError — no structural UI changes needed.

Note: This PR should be held and merged after/with the companion Auth fix that makes the backend return a proper 400 for invalid card limits.

Fixed Issues

$ https://github.com/Expensify/Expensify/issues/598396
PROPOSAL:

Tests

  1. Navigate to the missing personal details flow and reach the magic code page
  2. Submit the form while the companion Auth fix is active and card limit is $0
  3. Verify the error message "Your card limit is $0. Please ask your workspace admin to set a non-zero spending limit, then try again." is displayed on the page
  4. Verify no JS console errors appear
  • Verify that no errors appear in the JS console

Offline tests

N/A — this error is only surfaced via an API response; offline behavior is unchanged (the API call never fires while offline).

QA Steps

  1. With the companion Auth fix deployed to staging, navigate to Settings > Wallet > Get physical card
  2. Attempt to submit the physical card ordering flow with a workspace where the card spending limit is $0
  3. Verify the error message "Your card limit is $0. Please ask your workspace admin to set a non-zero spending limit, then try again." is displayed
  4. Verify that increasing the card limit and retrying completes the flow successfully
  • 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

…onalDetailsAndShipExpensifyCards

When Auth returns a 400 for an invalid card limit, the app now surfaces a meaningful error
message via failureData writing to ONYXKEYS.PRIVATE_PERSONAL_DETAILS.errors, which
MissingPersonalDetailsMagicCodePage already displays as a validateError.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@Beamanator Beamanator requested review from a team as code owners April 8, 2026 17:26
@melvin-bot melvin-bot bot requested review from a team, ahmedGaber93 and heyjennahay and removed request for a team April 8, 2026 17:26
@melvin-bot
Copy link
Copy Markdown

melvin-bot bot commented Apr 8, 2026

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

@melvin-bot melvin-bot bot requested review from truph01 and removed request for a team April 8, 2026 17:26
@melvin-bot
Copy link
Copy Markdown

melvin-bot bot commented Apr 8, 2026

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

@OSBotify
Copy link
Copy Markdown
Contributor

OSBotify commented Apr 8, 2026

🦜 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 fc74a72e..cafe2ceb 100644
--- a/src/languages/de.ts
+++ b/src/languages/de.ts
@@ -2413,7 +2413,8 @@ ${amount} für ${merchant} – ${date}`,
         changeYourPin: 'Geben Sie eine neue PIN für Ihre Karte ein.',
         confirmYourChangedPin: 'Bestätigen Sie Ihre neue PIN.',
         pinMustBeFourDigits: 'Die PIN muss genau 4 Ziffern lang sein.',
-        invalidCardLimit: 'Your card limit is $0. Please ask your workspace admin to set a non-zero spending limit, then try again.',
+        invalidCardLimit:
+            'Ihr Kartenlimit beträgt 0 $. Bitte bitten Sie Ihre Workspace-Administratorin bzw. Ihren Workspace-Administrator, ein Limit größer als 0 festzulegen, und versuchen Sie es dann erneut.',
         invalidPin: 'Bitte wählen Sie eine sicherere PIN.',
         pinMismatch: 'PINs stimmen nicht überein. Bitte versuchen Sie es erneut.',
         revealPin: 'PIN anzeigen',
diff --git a/src/languages/fr.ts b/src/languages/fr.ts
index 45d89479..fe81b041 100644
--- a/src/languages/fr.ts
+++ b/src/languages/fr.ts
@@ -2420,7 +2420,7 @@ ${amount} pour ${merchant} - ${date}`,
         changeYourPin: 'Saisissez un nouveau code PIN pour votre carte.',
         confirmYourChangedPin: 'Confirmez votre nouveau code PIN.',
         pinMustBeFourDigits: 'Le code PIN doit comporter exactement 4 chiffres.',
-        invalidCardLimit: 'Your card limit is $0. Please ask your workspace admin to set a non-zero spending limit, then try again.',
+        invalidCardLimit: 'Votre limite de carte est de 0 $. Veuillez demander à l’administrateur de votre espace de travail de définir une limite de dépense non nulle, puis réessayez.',
         invalidPin: 'Veuillez choisir un code PIN plus sécurisé.',
         pinMismatch: 'Les codes PIN ne correspondent pas. Veuillez réessayer.',
         revealPin: 'Afficher le code PIN',
diff --git a/src/languages/it.ts b/src/languages/it.ts
index d77cbed5..00a42cd3 100644
--- a/src/languages/it.ts
+++ b/src/languages/it.ts
@@ -1096,15 +1096,12 @@ const translations: TranslationDeepObject<typeof en> = {
             if (!added && !updated) {
                 return 'Nessuna categoria è stata aggiunta o aggiornata.';
             }
-
             if (added && updated) {
                 return `${added} ${added === 1 ? 'categoria aggiunta' : 'categorie aggiunte'}, ${updated} ${updated === 1 ? 'categoria aggiornata' : 'categorie aggiornate'}.`;
             }
-
             if (added) {
                 return added === 1 ? 'È stata aggiunta 1 categoria.' : `Sono state aggiunte ${added} categorie.`;
             }
-
             return updated === 1 ? 'È stata aggiornata 1 categoria.' : `Sono state aggiornate ${updated} categorie.`;
         },
         importCompanyCardTransactionsSuccessfulDescription: ({transactions}: {transactions: number}) =>
@@ -2413,7 +2410,7 @@ ${amount} per ${merchant} - ${date}`,
         changeYourPin: 'Inserisci un nuovo PIN per la tua carta.',
         confirmYourChangedPin: 'Conferma il tuo nuovo PIN.',
         pinMustBeFourDigits: 'Il PIN deve essere composto da esattamente 4 cifre.',
-        invalidCardLimit: 'Your card limit is $0. Please ask your workspace admin to set a non-zero spending limit, then try again.',
+        invalidCardLimit: 'Il limite della tua carta è 0 $. Chiedi all’amministratore dello spazio di lavoro di impostare un limite di spesa diverso da zero, quindi riprova.',
         invalidPin: 'Scegli un PIN più sicuro.',
         pinMismatch: 'I PIN non corrispondono. Riprova.',
         revealPin: 'Mostra PIN',
diff --git a/src/languages/ja.ts b/src/languages/ja.ts
index f8e8ee49..6cd4223d 100644
--- a/src/languages/ja.ts
+++ b/src/languages/ja.ts
@@ -1079,15 +1079,12 @@ const translations: TranslationDeepObject<typeof en> = {
             if (!added && !updated) {
                 return 'カテゴリーは追加も更新もされていません。';
             }
-
             if (added && updated) {
                 return `${added}件のカテゴリーを追加し、${updated}件のカテゴリーを更新しました。`;
             }
-
             if (added) {
                 return added === 1 ? 'カテゴリーを1件追加しました。' : `${added}件のカテゴリーを追加しました。`;
             }
-
             return updated === 1 ? 'カテゴリーを1件更新しました。' : `${updated}件のカテゴリーを更新しました。`;
         },
         importCompanyCardTransactionsSuccessfulDescription: ({transactions}: {transactions: number}) =>
@@ -2388,7 +2385,7 @@ ${date} の ${merchant} への ${amount}`,
         changeYourPin: 'カードの新しい暗証番号を入力してください。',
         confirmYourChangedPin: '新しい暗証番号を確認してください。',
         pinMustBeFourDigits: 'PIN は 4 桁で入力してください。',
-        invalidCardLimit: 'Your card limit is $0. Please ask your workspace admin to set a non-zero spending limit, then try again.',
+        invalidCardLimit: 'お客さまのカード利用限度額は $0 です。ワークスペース管理者に、0 より大きい利用限度額の設定を依頼してから、もう一度お試しください。',
         invalidPin: 'より安全な暗証番号を選択してください。',
         pinMismatch: 'PIN が一致しません。もう一度お試しください。',
         revealPin: 'PIN を表示',
diff --git a/src/languages/nl.ts b/src/languages/nl.ts
index db9456f8..18027fe4 100644
--- a/src/languages/nl.ts
+++ b/src/languages/nl.ts
@@ -1095,15 +1095,12 @@ const translations: TranslationDeepObject<typeof en> = {
             if (!added && !updated) {
                 return 'Er zijn geen categorieën toegevoegd of bijgewerkt.';
             }
-
             if (added && updated) {
                 return `${added} ${added === 1 ? 'categorie' : 'categorieën'} toegevoegd, ${updated} ${updated === 1 ? 'categorie' : 'categorieën'} bijgewerkt.`;
             }
-
             if (added) {
                 return added === 1 ? '1 categorie is toegevoegd.' : `${added} categorieën zijn toegevoegd.`;
             }
-
             return updated === 1 ? '1 categorie is bijgewerkt.' : `${updated} categorieën zijn bijgewerkt.`;
         },
         importCompanyCardTransactionsSuccessfulDescription: ({transactions}: {transactions: number}) =>
@@ -2411,7 +2408,7 @@ ${amount} voor ${merchant} - ${date}`,
         changeYourPin: 'Voer een nieuwe pincode in voor je kaart.',
         confirmYourChangedPin: 'Bevestig je nieuwe pincode.',
         pinMustBeFourDigits: 'Pincode moet precies 4 cijfers bevatten.',
-        invalidCardLimit: 'Your card limit is $0. Please ask your workspace admin to set a non-zero spending limit, then try again.',
+        invalidCardLimit: 'Je kaartlimiet is $0. Vraag je workspace-beheerder om een bestedingslimiet hoger dan nul in te stellen en probeer het daarna opnieuw.',
         invalidPin: 'Kies alsjeblieft een veiligere pincode.',
         pinMismatch: 'Pincodes komen niet overeen. Probeer het opnieuw.',
         revealPin: 'Pincode weergeven',
diff --git a/src/languages/pl.ts b/src/languages/pl.ts
index 258e3a6c..b521f45f 100644
--- a/src/languages/pl.ts
+++ b/src/languages/pl.ts
@@ -1096,15 +1096,12 @@ const translations: TranslationDeepObject<typeof en> = {
             if (!added && !updated) {
                 return 'Nie dodano ani nie zaktualizowano żadnych kategorii.';
             }
-
             if (added && updated) {
                 return `Dodano ${added} ${added === 1 ? 'kategorię' : 'kategorie'}, zaktualizowano ${updated} ${updated === 1 ? 'kategorię' : 'kategorie'}.`;
             }
-
             if (added) {
                 return added === 1 ? 'Dodano 1 kategorię.' : `Dodano ${added} kategorie.`;
             }
-
             return updated === 1 ? 'Zaktualizowano 1 kategorię.' : `Zaktualizowano ${updated} kategorie.`;
         },
         importCompanyCardTransactionsSuccessfulDescription: ({transactions}: {transactions: number}) => (transactions > 1 ? `Dodano ${transactions} transakcji.` : 'Dodano 1 transakcję.'),
@@ -2406,7 +2403,7 @@ ${amount} dla ${merchant} - ${date}`,
         changeYourPin: 'Wprowadź nowy PIN do swojej karty.',
         confirmYourChangedPin: 'Potwierdź swój nowy PIN.',
         pinMustBeFourDigits: 'PIN musi mieć dokładnie 4 cyfry.',
-        invalidCardLimit: 'Your card limit is $0. Please ask your workspace admin to set a non-zero spending limit, then try again.',
+        invalidCardLimit: 'Limit twojej karty wynosi 0 USD. Poproś administratora przestrzeni roboczej o ustawienie niezerowego limitu wydatków, a następnie spróbuj ponownie.',
         invalidPin: 'Wybierz proszę bardziej bezpieczny PIN.',
         pinMismatch: 'Kody PIN nie są takie same. Spróbuj ponownie.',
         revealPin: 'Pokaż PIN',
diff --git a/src/languages/pt-BR.ts b/src/languages/pt-BR.ts
index df29e99a..24d8cd6a 100644
--- a/src/languages/pt-BR.ts
+++ b/src/languages/pt-BR.ts
@@ -1094,15 +1094,12 @@ const translations: TranslationDeepObject<typeof en> = {
             if (!added && !updated) {
                 return 'Nenhuma categoria foi adicionada ou atualizada.';
             }
-
             if (added && updated) {
                 return `${added} ${added === 1 ? 'categoria' : 'categorias'} adicionada${added === 1 ? '' : 's'}, ${updated} ${updated === 1 ? 'categoria' : 'categorias'} atualizada${updated === 1 ? '' : 's'}.`;
             }
-
             if (added) {
                 return added === 1 ? '1 categoria foi adicionada.' : `${added} categorias foram adicionadas.`;
             }
-
             return updated === 1 ? '1 categoria foi atualizada.' : `${updated} categorias foram atualizadas.`;
         },
         importCompanyCardTransactionsSuccessfulDescription: ({transactions}: {transactions: number}) =>
@@ -2404,7 +2401,7 @@ ${amount} para ${merchant} - ${date}`,
         changeYourPin: 'Digite um novo PIN para o seu cartão.',
         confirmYourChangedPin: 'Confirme seu novo PIN.',
         pinMustBeFourDigits: 'O PIN deve ter exatamente 4 dígitos.',
-        invalidCardLimit: 'Your card limit is $0. Please ask your workspace admin to set a non-zero spending limit, then try again.',
+        invalidCardLimit: 'O limite do seu cartão é de US$ 0. Peça ao administrador do seu workspace para definir um limite de gastos diferente de zero e tente novamente.',
         invalidPin: 'Escolha um PIN mais seguro.',
         pinMismatch: 'Os PINs não coincidem. Tente novamente.',
         revealPin: 'Revelar PIN',
diff --git a/src/languages/zh-hans.ts b/src/languages/zh-hans.ts
index b14a0109..44344e85 100644
--- a/src/languages/zh-hans.ts
+++ b/src/languages/zh-hans.ts
@@ -2336,7 +2336,7 @@ ${amount},商户:${merchant} - 日期:${date}`,
         changeYourPin: '为您的银行卡输入新 PIN 码。',
         confirmYourChangedPin: '确认您的新 PIN。',
         pinMustBeFourDigits: 'PIN 必须正好为 4 位数字。',
-        invalidCardLimit: 'Your card limit is $0. Please ask your workspace admin to set a non-zero spending limit, then try again.',
+        invalidCardLimit: '您的卡片额度为 $0。请联系您的工作区管理员设置一个非零消费额度,然后重试。',
         invalidPin: '请选择一个更安全的 PIN。',
         pinMismatch: 'PIN 不匹配。请重试。',
         revealPin: '显示 PIN',

Note

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

View workflow run

Copy link
Copy Markdown

@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: 59a2ff6fdc

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

onyxMethod: Onyx.METHOD.MERGE,
key: ONYXKEYS.PRIVATE_PERSONAL_DETAILS,
value: {
errors: ErrorUtils.getMicroSecondOnyxErrorWithTranslationKey('cardPage.invalidCardLimit'),
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Restrict card-limit error to invalid-limit responses

failureData now always writes cardPage.invalidCardLimit, but applyHTTPSOnyxUpdates() applies request.failureData for every non-200 response code, not just the invalid-limit case. That means unrelated failures in SetPersonalDetailsAndShipExpensifyCards (e.g., transient server/network errors or other backend validation failures) will incorrectly tell users their card limit is $0, masking the real issue and sending them to the wrong remediation path.

Useful? React with 👍 / 👎.

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.

2 participants