Skip to content

Conversation

@mountiny
Copy link
Contributor

@mountiny mountiny commented Jan 30, 2026

Explanation of Change

This PR implements Release 4 of the NewDot Home page Time Sensitive section, adding two new widgets:

  1. Fix Company Card Connection - Shows when an admin has a workspace with broken company card connections (import errors)
  2. Fix Accounting Connection - Shows when an admin has a workspace with broken/stale accounting integrations (QuickBooks, Xero, NetSuite, etc.)

Key changes:

  • Added FixCompanyCardConnection widget component that displays broken company card connections with a "Fix" CTA navigating to workspace company cards settings
  • Added FixAccountingConnection widget component that displays broken accounting connections with a "Fix" CTA navigating to workspace accounting settings
  • Updated BaseWidgetItem to support isDanger prop for danger-styled (coral) buttons
  • Added selector using activeAdminPoliciesSelector to filter policies where the user is an admin
  • Used existing useCardFeedErrors hook and hasSynchronizationErrorMessage function to detect broken connections
  • Each broken connection/workspace shows as a separate row in the Time Sensitive section

Priority order (from design doc):

  • Potential card fraud (Release 3)
  • Broken company card connections ← Added in this PR
  • Broken accounting connections ← Added in this PR
  • Early adoption discount (50% or 25%)
  • Expensify card shipping (Release 3)
  • Expensify card activation (Release 3)

Fixed Issues

$ #79970
PROPOSAL:

Tests

Prerequisite: Have a workspace with accounting integration set up

  1. Break the accounting integration connection
  2. Verify that you can see the Fix option on the home page as the admin
  3. Sign in as a member on that workspace
  4. Verify you do not see that time-sensitive widget
  5. As admin, click the Fix
  6. Verify you had been navigated to the Accounting page in the workspace settings
image
  1. Log in as an admin of a workspace that has a broken accounting connection (e.g., QuickBooks with sync error)
  2. Navigate to the Home page
  3. Verify the "Time sensitive" section appears with a "Fix [Integration Name] connection" widget
  4. Verify the widget shows "Workspace > Connections" subtitle
  5. Verify the icon has a coral/salmon background color
  6. Verify the "Fix" button is coral colored (not green)
  7. Click "Fix" and verify it navigates to the workspace accounting settings page
  8. Repeat steps 1-7 for a workspace with a broken company card connection
  9. Verify company card widget shows "Workspace > Company cards" subtitle and navigates correctly
  10. Verify that if multiple broken connections exist across workspaces, each shows as a separate row
  • Verify that no errors appear in the JS console
image

Offline tests

N/A

QA Steps

  1. Log in as an admin of a workspace with a broken accounting integration
  2. Navigate to Home page
  3. Verify "Time sensitive" section shows the broken connection widget with coral styling
  4. Tap "Fix" and verify navigation to workspace accounting settings
  5. Repeat for broken company card connections
  6. Verify multiple broken connections show as separate rows

// 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 verified there are no new alerts related to the canBeMissing param for useOnyx
  • 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.
  • I verified that similar component doesn't exist in the codebase
  • I verified that all props are defined accurately and each prop has a /** comment above it */
  • I verified that each file is named correctly
  • I verified that each component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
  • I verified that the only data being stored in component state is data necessary for rendering and nothing else
  • In component if we are not using the full Onyx data that we loaded, I've added the proper selector in order to ensure the component only re-renders when the data it is using changes
  • 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)
  • I verified that component 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)
  • I verified that all JSX used for rendering exists in the render method
  • I verified that each 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

Screenshots/Videos

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

@mountiny mountiny self-assigned this Jan 30, 2026
@OSBotify

This comment has been minimized.

@OSBotify

This comment has been minimized.

@OSBotify

This comment has been minimized.

@codecov
Copy link

codecov bot commented Jan 30, 2026

@OSBotify

This comment has been minimized.

@github-actions
Copy link
Contributor

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


function FixAccountingConnection({connectionName, policyID}: FixAccountingConnectionProps) {
const {translate} = useLocalize();
const icons = useMemoizedLazyExpensifyIcons(['Exclamation'] as const);
Copy link
Contributor

Choose a reason for hiding this comment

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

I suppose it should work without as const


function FixCompanyCardConnection({card, policyID}: FixCompanyCardConnectionProps) {
const {translate} = useLocalize();
const icons = useMemoizedLazyExpensifyIcons(['Connect'] as const);
Copy link
Contributor

@ZhenjaHorbach ZhenjaHorbach Jan 30, 2026

Choose a reason for hiding this comment

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

It should work without as const

@github-actions

This comment has been minimized.

if (!shouldShowDiscount || !discountInfo) {
return null;
// Determine which offer to show based on discount type (they are mutually exclusive)
const shouldShow50off = shouldShowDiscount && discountInfo?.discountType === 50;
Copy link
Contributor

@ZhenjaHorbach ZhenjaHorbach Jan 30, 2026

Choose a reason for hiding this comment

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

It's better to wait until we merge this PR
And then use useTimeSensitiveOffers here

@OSBotify

This comment has been minimized.

@mountiny mountiny requested a review from grgia January 30, 2026 20:28
@mountiny mountiny marked this pull request as ready for review January 30, 2026 20:28
@mountiny mountiny requested review from a team as code owners January 30, 2026 20:28
@melvin-bot melvin-bot bot requested a review from ZhenjaHorbach January 30, 2026 20:28
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: e4b4426a41

ℹ️ 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 on lines 80 to 82
// Check if there's a sync in progress for this policy
const syncProgress = connectionSyncProgress?.[`${ONYXKEYS.COLLECTION.POLICY_CONNECTION_SYNC_PROGRESS}${policy.id}`];
const isSyncInProgress = !!syncProgress?.stageInProgress;

Choose a reason for hiding this comment

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

P2 Badge Use real sync-in-progress check to avoid hiding errors

Using !!syncProgress?.stageInProgress treats any stored sync-progress record as “in progress,” but hasSynchronizationErrorMessage returns false when a sync is in progress. policyConnectionSyncProgress entries can linger with stageInProgress = JOB_DONE or an old timestamp; isConnectionInProgress explicitly filters those cases. With the current check, a failed sync can be permanently suppressed and the broken accounting widget never appears after a stale/finished sync. This should mirror the isConnectionInProgress logic used elsewhere to respect the timeout and JOB_DONE handling.

Useful? React with 👍 / 👎.

@OSBotify
Copy link
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 ece661c4..74f8e043 100644
--- a/src/languages/de.ts
+++ b/src/languages/de.ts
@@ -8307,10 +8307,10 @@ Hier ist ein *Testbeleg*, um dir zu zeigen, wie es funktioniert:`,
             offer25off: {title: 'Erhalten Sie 25 % Rabatt auf Ihr erstes Jahr!', subtitle: ({days}: {days: number}) => `${days} ${days === 1 ? 'Tag' : 'Tage'} verbleiben`},
             ctaFix: 'Beheben',
             fixCompanyCardConnection: {
-                title: ({feedName}: {feedName: string}) => (feedName ? `${feedName}-Firmenkartenverbindung reparieren` : 'Firmenkartenverbindung reparieren'),
-                subtitle: 'Workspace > Firmenkarten',
+                title: ({feedName}: {feedName: string}) => (feedName ? `${feedName}-Firmenkartenverbindung reparieren` : 'Verbindung der Firmenkarte reparieren'),
+                subtitle: 'Arbeitsbereich > Firmenkarten',
             },
-            fixAccountingConnection: {title: ({integrationName}: {integrationName: string}) => `${integrationName}-Verbindung reparieren`, subtitle: 'Workspace > Buchhaltung'},
+            fixAccountingConnection: {title: ({integrationName}: {integrationName: string}) => `${integrationName}-Verbindung reparieren`, subtitle: 'Arbeitsbereich > Buchhaltung'},
             addShippingAddress: {title: 'Wir benötigen Ihre Versandadresse', subtitle: 'Gib eine Adresse an, um deine Expensify Card zu erhalten.', cta: 'Adresse hinzufügen'},
             activateCard: {title: 'Aktiviere deine Expensify Card', subtitle: 'Bestätige deine Karte und beginne mit dem Ausgeben.', cta: 'Aktivieren'},
         },
diff --git a/src/languages/fr.ts b/src/languages/fr.ts
index adf3be15..bec022e4 100644
--- a/src/languages/fr.ts
+++ b/src/languages/fr.ts
@@ -8313,7 +8313,7 @@ Voici un *reçu test* pour vous montrer comment cela fonctionne :`,
             offer25off: {title: 'Obtenez 25 % de réduction sur votre première année !', subtitle: ({days}: {days: number}) => `${days} ${days === 1 ? 'jour' : 'jours'} restants`},
             ctaFix: 'Corriger',
             fixCompanyCardConnection: {
-                title: ({feedName}: {feedName: string}) => (feedName ? `Corriger la connexion de la carte professionnelle ${feedName}` : 'Corriger la connexion de la carte professionnelle'),
+                title: ({feedName}: {feedName: string}) => (feedName ? `Réparer la connexion de carte d’entreprise ${feedName}` : 'Corriger la connexion de la carte d’entreprise'),
                 subtitle: 'Espace de travail > Cartes d’entreprise',
             },
             fixAccountingConnection: {title: ({integrationName}: {integrationName: string}) => `Réparer la connexion ${integrationName}`, subtitle: 'Espace de travail > Comptabilité'},
diff --git a/src/languages/it.ts b/src/languages/it.ts
index a40ea2a4..49086c48 100644
--- a/src/languages/it.ts
+++ b/src/languages/it.ts
@@ -8293,10 +8293,10 @@ Ecco una *ricevuta di prova* per mostrarti come funziona:`,
             offer25off: {title: 'Ottieni il 25% di sconto sul tuo primo anno!', subtitle: ({days}: {days: number}) => `${days} ${days === 1 ? 'giorno' : 'giorni'} rimanenti`},
             ctaFix: 'Correggi',
             fixCompanyCardConnection: {
-                title: ({feedName}: {feedName: string}) => (feedName ? `Correggi la connessione della carta aziendale ${feedName}` : 'Correggi la connessione della carta aziendale'),
+                title: ({feedName}: {feedName: string}) => (feedName ? `Correggi la connessione della carta aziendale ${feedName}` : 'Correggi connessione carta aziendale'),
                 subtitle: 'Spazio di lavoro > Carte aziendali',
             },
-            fixAccountingConnection: {title: ({integrationName}: {integrationName: string}) => `Correggi la connessione ${integrationName}`, subtitle: 'Workspace > Contabilità'},
+            fixAccountingConnection: {title: ({integrationName}: {integrationName: string}) => `Correggi la connessione ${integrationName}`, subtitle: 'Area di lavoro > Contabilità'},
             addShippingAddress: {title: 'Abbiamo bisogno del tuo indirizzo di spedizione', subtitle: 'Fornisci un indirizzo per ricevere la tua Expensify Card.', cta: 'Aggiungi indirizzo'},
             activateCard: {title: 'Attiva la tua Expensify Card', subtitle: 'Convalida la tua carta e inizia a spendere.', cta: 'Attiva'},
         },
diff --git a/src/languages/nl.ts b/src/languages/nl.ts
index 13afbc28..843de5b5 100644
--- a/src/languages/nl.ts
+++ b/src/languages/nl.ts
@@ -8269,10 +8269,10 @@ Hier is een *testbon* om je te laten zien hoe het werkt:`,
             offer25off: {title: 'Krijg 25% korting op je eerste jaar!', subtitle: ({days}: {days: number}) => `Nog ${days} ${days === 1 ? 'dag' : 'dagen'} resterend`},
             ctaFix: 'Oplossen',
             fixCompanyCardConnection: {
-                title: ({feedName}: {feedName: string}) => (feedName ? `Verbinding voor ${feedName}-bedrijfskaart herstellen` : 'Verbinding voor bedrijfskaart herstellen'),
-                subtitle: 'Werkruimte > Bedrijfskaarten',
+                title: ({feedName}: {feedName: string}) => (feedName ? `Verbinding voor bedrijfskaart ${feedName} herstellen` : 'Verbinding bedrijfskaart repareren'),
+                subtitle: 'Workspace > Bedrijfskaarten',
             },
-            fixAccountingConnection: {title: ({integrationName}: {integrationName: string}) => `${integrationName}-verbinding herstellen`, subtitle: 'Werkruimte > Boekhouding'},
+            fixAccountingConnection: {title: ({integrationName}: {integrationName: string}) => `${integrationName}-verbinding repareren`, subtitle: 'Werkruimte > Boekhouding'},
             addShippingAddress: {title: 'We hebben je verzendadres nodig', subtitle: 'Voer een adres in om je Expensify Card te ontvangen.', cta: 'Adres toevoegen'},
             activateCard: {title: 'Activeer je Expensify Card', subtitle: 'Valideer je kaart en begin met uitgeven.', cta: 'Activeren'},
         },
diff --git a/src/languages/pl.ts b/src/languages/pl.ts
index e2b2256f..63b2fbd3 100644
--- a/src/languages/pl.ts
+++ b/src/languages/pl.ts
@@ -8253,10 +8253,10 @@ Oto *paragon testowy*, który pokazuje, jak to działa:`,
             offer25off: {title: 'Uzyskaj 25% zniżki na pierwszy rok!', subtitle: ({days}: {days: number}) => `Pozostało ${days} ${days === 1 ? 'dzień' : 'dni'}`},
             ctaFix: 'Napraw',
             fixCompanyCardConnection: {
-                title: ({feedName}: {feedName: string}) => (feedName ? `Napraw połączenie firmowej karty ${feedName}` : 'Napraw połączenie firmowej karty'),
+                title: ({feedName}: {feedName: string}) => (feedName ? `Napraw połączenie firmowej karty ${feedName}` : 'Napraw połączenie karty firmowej'),
                 subtitle: 'Workspace > Karty firmowe',
             },
-            fixAccountingConnection: {title: ({integrationName}: {integrationName: string}) => `Napraw połączenie ${integrationName}`, subtitle: 'Obszar roboczy > Księgowość'},
+            fixAccountingConnection: {title: ({integrationName}: {integrationName: string}) => `Napraw połączenie z ${integrationName}`, subtitle: 'Workspace > Księgowość'},
             addShippingAddress: {title: 'Potrzebujemy Twojego adresu do wysyłki', subtitle: 'Podaj adres, na który mamy wysłać Twoją kartę Expensify.', cta: 'Dodaj adres'},
             activateCard: {title: 'Aktywuj swoją kartę Expensify', subtitle: 'Zweryfikuj swoją kartę i zacznij wydawać.', cta: 'Aktywuj'},
         },
diff --git a/src/languages/pt-BR.ts b/src/languages/pt-BR.ts
index 02f2cba0..c49e8805 100644
--- a/src/languages/pt-BR.ts
+++ b/src/languages/pt-BR.ts
@@ -8264,9 +8264,9 @@ Aqui está um *recibo de teste* para mostrar como funciona:`,
             ctaFix: 'Corrigir',
             fixCompanyCardConnection: {
                 title: ({feedName}: {feedName: string}) => (feedName ? `Corrigir conexão do cartão corporativo ${feedName}` : 'Corrigir conexão do cartão corporativo'),
-                subtitle: 'Workspace > Cartões corporativos',
+                subtitle: 'Espaço de trabalho > Cartões corporativos',
             },
-            fixAccountingConnection: {title: ({integrationName}: {integrationName: string}) => `Corrigir conexão com ${integrationName}`, subtitle: 'Workspace > Contabilidade'},
+            fixAccountingConnection: {title: ({integrationName}: {integrationName: string}) => `Corrigir conexão do ${integrationName}`, subtitle: 'Workspace > Contabilidade'},
             addShippingAddress: {title: 'Precisamos do seu endereço de entrega', subtitle: 'Forneça um endereço para receber seu Expensify Card.', cta: 'Adicionar endereço'},
             activateCard: {title: 'Ative seu Cartão Expensify', subtitle: 'Valide seu cartão e comece a gastar.', cta: 'Ativar'},
         },

Note

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

View workflow run

@ZhenjaHorbach
Copy link
Contributor

ZhenjaHorbach commented Jan 30, 2026

Strange
I have a connection to Sage issue
But don't have the section

2026-01-30.21.48.53.mov

@mountiny
Copy link
Contributor Author

@ZhenjaHorbach can you share the policy data for that policy and connection? I am using standardized approach from what I know so I agree that is weird

@ZhenjaHorbach
Copy link
Contributor

Sure

{
    "isFromFullPolicy": false,
    "id": "833FF0601CD04E7A",
    "name": "Y's Workspace 1",
    "role": "admin",
    "type": "corporate",
    "owner": "zhenja3033+0350@gmail.com",
    "created": "2026-01-30 20:45:42",
    "ownerAccountID": 17827541,
    "ownerLastDayFreeTrial": "2024-08-01 18:18:13",
    "outputCurrency": "PLN",
    "avatarURL": "",
    "employeeList": {
        "zhenja3033+0350@gmail.com": {
            "email": "zhenja3033+0350@gmail.com",
            "forwardsTo": "",
            "role": "admin",
            "submitsTo": "zhenja3033+0350@gmail.com"
        }
    },
    "isPolicyExpenseChatEnabled": true,
    "lastModified": 1769806076710169,
    "chatReportIDAnnounce": "0",
    "chatReportIDAdmins": "6188732992864815",
    "autoReporting": true,
    "autoReimbursement": {
        "limit": 0
    },
    "areCategoriesEnabled": true,
    "areTagsEnabled": true,
    "areDistanceRatesEnabled": false,
    "arePerDiemRatesEnabled": false,
    "areWorkflowsEnabled": true,
    "areConnectionsEnabled": true,
    "areInvoicesEnabled": false,
    "areExpensifyCardsEnabled": false,
    "areCompanyCardsEnabled": true,
    "tax": {
        "trackingEnabled": false
    },
    "areRulesEnabled": false,
    "eReceipts": false,
    "shouldShowCustomReportTitleOption": false,
    "shouldShowAutoApprovalOptions": false,
    "shouldShowAutoReimbursementLimitOption": false,
    "maxExpenseAmountNoReceipt": 10000000000,
    "maxExpenseAmountNoItemizedReceipt": 10000000000,
    "maxExpenseAmount": 10000000000,
    "maxExpenseAge": 10000000000,
    "approvalMode": "BASIC",
    "invoice": {
        "markUp": 0
    },
    "workspaceAccountID": 21249124,
    "address": [],
    "approver": "zhenja3033+0350@gmail.com",
    "areInvoiceFieldsEnabled": false,
    "areReportFieldsEnabled": false,
    "autoReimbursementLimit": 0,
    "autoReportingFrequency": "immediate",
    "autoReportingOffset": 1,
    "clientID": "",
    "customUnits": {
        "3A4CCAFA32974": {
            "attributes": {
                "taxEnabled": false,
                "unit": "mi"
            },
            "customUnitID": "3A4CCAFA32974",
            "defaultCategory": "Car",
            "enabled": true,
            "name": "Distance",
            "rates": {
                "B781581431232": {
                    "attributes": [],
                    "currency": "PLN",
                    "customUnitRateID": "B781581431232",
                    "enabled": true,
                    "index": 0,
                    "name": "Default Rate",
                    "rate": 72.5,
                    "subRates": []
                }
            }
        }
    },
    "defaultBillable": false,
    "defaultReimbursable": true,
    "disabledFields": {
        "defaultBillable": true,
        "reimbursable": false
    },
    "exportLayouts": [],
    "fieldList": {
        "text_title": {
            "defaultValue": "{report:type} {report:startdate}",
            "deletable": true,
            "disabledOptions": [],
            "externalIDs": [],
            "fieldID": "text_title",
            "isTax": false,
            "keys": [],
            "name": "title",
            "orderWeight": 0,
            "target": "expense",
            "type": "formula",
            "values": []
        }
    },
    "glCodes": true,
    "harvesting": {
        "enabled": false
    },
    "hasMultipleTagLists": false,
    "isAttendeeTrackingEnabled": false,
    "isTravelEnabled": false,
    "mccGroup": {
        "airlines": {
            "category": "Travel",
            "groupID": "airlines"
        },
        "commuter": {
            "category": "Car",
            "groupID": "commuter"
        },
        "gas": {
            "category": "Car",
            "groupID": "gas"
        },
        "goods": {
            "category": "Materials",
            "groupID": "goods"
        },
        "groceries": {
            "category": "Meals and Entertainment",
            "groupID": "groceries"
        },
        "hotel": {
            "category": "Travel",
            "groupID": "hotel"
        },
        "mail": {
            "category": "Office Supplies",
            "groupID": "mail"
        },
        "meals": {
            "category": "Meals and Entertainment",
            "groupID": "meals"
        },
        "rental": {
            "category": "Travel",
            "groupID": "rental"
        },
        "services": {
            "category": "Professional Services",
            "groupID": "services"
        },
        "taxi": {
            "category": "Travel",
            "groupID": "taxi"
        },
        "uncategorized": {
            "category": "Other",
            "groupID": "uncategorized"
        },
        "utilities": {
            "category": "Utilities",
            "groupID": "utilities"
        }
    },
    "preventSelfApproval": false,
    "prohibitedExpenses": {
        "adultEntertainment": true,
        "alcohol": false,
        "gambling": true,
        "hotelIncidentals": false,
        "tobacco": false
    },
    "reimbursementChoice": "reimburseManual",
    "requiresCategory": true,
    "requiresTag": false,
    "rules": [],
    "technicalContact": "zhenja3033+0350@gmail.com",
    "units": {
        "time": {
            "enabled": false,
            "rate": 50
        }
    },
    "connections": {
        "intacct": {
            "config": {
                "credentials": {
                    "companyID": "",
                    "password": "3ohUaNKJMNPyLo4Fh3Qawg==;JWI+Q5t/qJ7A4rDX0nSAUA==;jZ6JediYwNnjhFlcCfJxQj7qtXXxO1kXc8EQ+SE0X7Do/dTRS3wkQfwhjdbkIIWZN/kc7bSQu42RJAs8gwxeOA==",
                    "userID": ""
                },
                "export": {
                    "exportDate": "LAST_EXPENSE",
                    "exporter": "zhenja3033+0350@gmail.com",
                    "nonReimbursable": "CREDIT_CARD_CHARGE",
                    "nonReimbursableAccount": "",
                    "reimbursable": "EXPENSE_REPORT"
                },
                "importEmployees": false,
                "isConfigured": false,
                "mappings": {
                    "classes": "DEFAULT",
                    "customers": "NONE",
                    "departments": "DEFAULT",
                    "locations": "DEFAULT",
                    "projects": "TAG"
                },
                "sync": {
                    "reimbursementAccountID": "",
                    "syncReimbursedReports": true
                },
                "tax": {
                    "syncTax": false,
                    "taxSolutionID": ""
                }
            },
            "data": {
                "bankAccounts": [],
                "creditCards": [],
                "entities": [],
                "vendors": []
            },
            "lastSync": {
                "errorDate": "2026-01-30T20:48:22+0000",
                "errorMessage": "Session initialization error",
                "isAuthenticationError": true,
                "isConnected": false,
                "isSuccessful": false,
                "source": "",
                "successfulDate": ""
            }
        }
    },
    "exporter": "zhenja3033+0350@gmail.com",
    "policyID": "833FF0601CD04E7A",
    "reimburser": "zhenja3033+0350@gmail.com"
}
Снимок экрана 2026-01-30 в 22 01 32

@ZhenjaHorbach
Copy link
Contributor

ZhenjaHorbach commented Jan 30, 2026

Looks like the problem with const isSyncInProgress = !!syncProgress?.stageInProgress;

const isSyncInProgress = !!syncProgress?.stageInProgress;

Which return true for this policy

As result, we ignore errors in this policy here

https://github.com/Expensify/App/blob/db53228f760be1c39b148d65dce8b485b6697acd/src/libs/actions/connections/index.ts#L256-#L258

Actually, do we really need isSyncInProgress?
Since, in any case, we will have errors only after synchronization

@mountiny
Copy link
Contributor Author

Do you still get that after the latest push?

@ZhenjaHorbach
Copy link
Contributor

Now is good!

Снимок экрана 2026-01-30 в 22 20 24

@ZhenjaHorbach
Copy link
Contributor

ZhenjaHorbach commented Jan 30, 2026

Maybe we should update designs and add workspace names for section items?
Since it is a little unclear which workspaces we are having errors in

Снимок экрана 2026-01-30 в 22 25 12

@ZhenjaHorbach
Copy link
Contributor

ZhenjaHorbach commented Jan 30, 2026

And should we improve navigation on the mobile apps to navigate to the previous screen after opening Accounting screen ? (not to Workspace details screen only)

2026-01-30.22.30.56.mov

@ZhenjaHorbach
Copy link
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 there are no new alerts related to the canBeMissing param for useOnyx
  • 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 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.ts 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 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.
  • 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
2026-01-30.22.29.26.mov
Android: mWeb Chrome
2026-01-30.22.31.09.mov
iOS: HybridApp
2026-01-30.22.29.26.mov
iOS: mWeb Safari
2026-01-30.22.31.09.mov
MacOS: Chrome / Safari
2026-01-30.22.21.03.mov

@ZhenjaHorbach
Copy link
Contributor

But overall changes look good!

@mountiny
Copy link
Contributor Author

Maybe we should update designs and add workspace names for section items?
Since it is a little unclear which workspaces we are having errors in

Good feedback, I think that is out of scope here, but we could consider @JmillsExpensify @Expensify/design

@dannymcclain
Copy link
Contributor

Yeah I kinda like that idea. Maybe instead of Workspace > Accounting it could just be {workSpaceName} > Accounting (i.e. Danny's Donuts > Accounting)?

@mountiny
Copy link
Contributor Author

And should we improve navigation on the mobile apps to navigate to the previous screen after opening Accounting screen ? (not to Workspace details screen only)

I think that is expected navigation using the UP button

using the browser history back will take you back as you mentioned

@melvin-bot melvin-bot bot requested a review from chuckdries January 30, 2026 23:27
@melvin-bot
Copy link

melvin-bot bot commented Jan 30, 2026

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

@github-actions
Copy link
Contributor

🚧 @mountiny 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 #80974.

Android 🤖 iOS 🍎
⏩ SKIPPED ⏩ ⏩ SKIPPED ⏩
The build for Android was skipped The build for iOS was skipped
Web 🕸️
https://80974.pr-testing.expensify.com
Web

👀 View the workflow run that generated this build 👀

@shawnborton
Copy link
Contributor

Maybe instead of Workspace > Accounting it could just be {workSpaceName} > Accounting (i.e. Danny's Donuts > Accounting)?

Definitely agree with that!

@shawnborton
Copy link
Contributor

Although cc @JmillsExpensify because I thought we decided to ditch the second line and just use one liners for all of these?

@mountiny
Copy link
Contributor Author

mountiny commented Feb 2, 2026

I do like adding the workspace name there for clarity when admin has multiple workspaces. We can add it in follow up cc @adamgrzybowski @WojtekBoman for visibility

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.

7 participants