Skip to content

Conversation

@marcochavezf
Copy link
Contributor

Explanation of Change

This PR reverts the incorrect use of Onyx.connectWithoutView back to Onyx.connect in ModifiedExpenseMessage.ts.

The connectWithoutView variant was incorrectly used for allPolicyTags and currentUserLogin. Since the functions using these values (like getForReportAction) are called from UI components, they need the regular Onyx.connect to ensure proper re-rendering when the underlying data changes.

Using connectWithoutView in this context causes stale data issues because the UI won't update when the Onyx data changes.

Fixed Issues

Tests

  • Verify that no errors appear in the JS console
  1. Open an expense report with modified expense actions
  2. Verify the modified expense messages display correctly
  3. Edit an expense (e.g., change category or tag)
  4. Verify the modified expense message updates to reflect the change

Offline tests

N/A - This change doesn't affect offline behavior

QA Steps

// No QA needed - this is a revert of an incorrect pattern change

  • 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.

Screenshots/Videos

Android: Native

N/A - No UI changes

Android: mWeb Chrome

N/A - No UI changes

iOS: Native

N/A - No UI changes

iOS: mWeb Safari

N/A - No UI changes

MacOS: Chrome / Safari

N/A - No UI changes

@marcochavezf marcochavezf requested review from a team as code owners January 16, 2026 17:33
@melvin-bot melvin-bot bot requested review from JmillsExpensify and removed request for a team January 16, 2026 17:33
@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 f5c06678..e9524fd7 100644
--- a/src/languages/de.ts
+++ b/src/languages/de.ts
@@ -942,7 +942,7 @@ const translations: TranslationDeepObject<typeof en> = {
         yourSpace: 'Ihr Bereich',
         welcomeToRoom: ({roomName}: WelcomeToRoomParams) => `Willkommen bei ${roomName}!`,
         usePlusButton: ({additionalText}: UsePlusButtonParams) => `Verwende die +‑Taste, um eine Ausgabe zu ${additionalText}.`,
-        askConcierge: ' Ihr 24/7-KI-Spesenassistent ist hier, um zu helfen.',
+        askConcierge: 'Ihr 24/7 KI-Spesenassistent ist hier, um zu helfen.',
         conciergeSupport: 'Ihr 24/7-Spesenassistent',
         create: 'Erstellen',
         iouTypes: {
diff --git a/src/languages/fr.ts b/src/languages/fr.ts
index 31061223..7c666102 100644
--- a/src/languages/fr.ts
+++ b/src/languages/fr.ts
@@ -945,8 +945,8 @@ const translations: TranslationDeepObject<typeof en> = {
         yourSpace: 'Votre espace',
         welcomeToRoom: ({roomName}: WelcomeToRoomParams) => `Bienvenue dans ${roomName} !`,
         usePlusButton: ({additionalText}: UsePlusButtonParams) => `Utilisez le bouton + pour ${additionalText} une dépense.`,
-        askConcierge: ' Votre assistant de dépenses IA 24h/24 et 7j/7 est là pour vous aider.',
-        conciergeSupport: 'votre assistant de dépenses 24h/24 et 7j/7',
+        askConcierge: 'Votre assistant de notes de frais IA disponible 24h/24 et 7j/7 est là pour vous aider.',
+        conciergeSupport: 'votre assistant de notes de frais 24h/24 et 7j/7',
         create: 'Créer',
         iouTypes: {
             pay: 'payer',
diff --git a/src/languages/it.ts b/src/languages/it.ts
index 363ce9c4..99c3823b 100644
--- a/src/languages/it.ts
+++ b/src/languages/it.ts
@@ -942,7 +942,7 @@ const translations: TranslationDeepObject<typeof en> = {
         yourSpace: 'Il tuo spazio',
         welcomeToRoom: ({roomName}: WelcomeToRoomParams) => `Benvenuto in ${roomName}!`,
         usePlusButton: ({additionalText}: UsePlusButtonParams) => `Usa il pulsante + per ${additionalText} una spesa.`,
-        askConcierge: ' Il tuo assistente spese AI 24/7 è qui per aiutarti.',
+        askConcierge: 'Il tuo assistente spese IA disponibile 24/7 è qui per aiutarti.',
         conciergeSupport: 'il tuo assistente spese 24/7',
         create: 'Crea',
         iouTypes: {
diff --git a/src/languages/ja.ts b/src/languages/ja.ts
index 57270513..d370d588 100644
--- a/src/languages/ja.ts
+++ b/src/languages/ja.ts
@@ -940,8 +940,8 @@ const translations: TranslationDeepObject<typeof en> = {
         yourSpace: 'あなたのスペース',
         welcomeToRoom: ({roomName}: WelcomeToRoomParams) => `${roomName} へようこそ!`,
         usePlusButton: ({additionalText}: UsePlusButtonParams) => `「+」ボタンを使って経費を${additionalText}してください。`,
-        askConcierge: ' あなたの24時間365日対応のAI経費アシスタントがサポートします。',
-        conciergeSupport: 'あなたの24時間365日対応の経費アシスタント',
+        askConcierge: 'あなたの24時間365日対応のAI経費アシスタントがお手伝いします。',
+        conciergeSupport: '24時間年中無休の経費アシスタント',
         create: '作成',
         iouTypes: {
             pay: '支払う',
diff --git a/src/languages/nl.ts b/src/languages/nl.ts
index 7575a78b..1e00f230 100644
--- a/src/languages/nl.ts
+++ b/src/languages/nl.ts
@@ -942,8 +942,8 @@ const translations: TranslationDeepObject<typeof en> = {
         yourSpace: 'Je ruimte',
         welcomeToRoom: ({roomName}: WelcomeToRoomParams) => `Welkom bij ${roomName}!`,
         usePlusButton: ({additionalText}: UsePlusButtonParams) => `Gebruik de knop + om een uitgave te ${additionalText}.`,
-        askConcierge: ' Uw 24/7 AI-uitgavenassistent is er om u te helpen.',
-        conciergeSupport: 'uw 24/7-uitgavenassistent',
+        askConcierge: 'Je 24/7 AI-uitgavenassistent is hier om te helpen.',
+        conciergeSupport: 'je 24/7-uitgavenassistent',
         create: 'Maken',
         iouTypes: {
             pay: 'Betalen',
@@ -8003,7 +8003,6 @@ Hier is een *testbon* om je te laten zien hoe het werkt:`,
             confirm: 'Afstandstracking negeren',
         },
         zeroDistanceTripModal: {title: 'Kan geen uitgave aanmaken', prompt: 'Je kunt geen uitgave aanmaken met dezelfde begin- en eindlocatie.'},
-
         locationRequiredModal: {
             title: 'Locatietoegang vereist',
             prompt: 'Sta locatietoegang toe in de instellingen van je apparaat om GPS-afstandsregistratie te starten.',
diff --git a/src/languages/pl.ts b/src/languages/pl.ts
index a6c03567..7890acbd 100644
--- a/src/languages/pl.ts
+++ b/src/languages/pl.ts
@@ -941,8 +941,8 @@ const translations: TranslationDeepObject<typeof en> = {
         yourSpace: 'Twoja przestrzeń',
         welcomeToRoom: ({roomName}: WelcomeToRoomParams) => `Witamy w ${roomName}!`,
         usePlusButton: ({additionalText}: UsePlusButtonParams) => `Użyj przycisku +, aby ${additionalText} wydatek.`,
-        askConcierge: ' Twój całodobowy asystent wydatków AI jest tutaj, aby pomóc.',
-        conciergeSupport: 'twój całodobowy asystent wydatków',
+        askConcierge: 'Twój całodobowy asystent wydatków AI jest tutaj, aby pomóc.',
+        conciergeSupport: 'Twój całodobowy asystent wydatków',
         create: 'Utwórz',
         iouTypes: {
             pay: 'Zapłać',
@@ -7978,7 +7978,6 @@ Oto *paragon testowy*, który pokazuje, jak to działa:`,
             confirm: 'Odrzuć śledzenie dystansu',
         },
         zeroDistanceTripModal: {title: 'Nie można utworzyć wydatku', prompt: 'Nie możesz utworzyć wydatku z tym samym miejscem początkowym i końcowym.'},
-
         locationRequiredModal: {
             title: 'Wymagany dostęp do lokalizacji',
             prompt: 'Aby rozpocząć śledzenie dystansu GPS, zezwól na dostęp do lokalizacji w ustawieniach swojego urządzenia.',
diff --git a/src/languages/pt-BR.ts b/src/languages/pt-BR.ts
index 9d91f779..0a9a1699 100644
--- a/src/languages/pt-BR.ts
+++ b/src/languages/pt-BR.ts
@@ -941,7 +941,7 @@ const translations: TranslationDeepObject<typeof en> = {
         yourSpace: 'Seu espaço',
         welcomeToRoom: ({roomName}: WelcomeToRoomParams) => `Bem-vindo(a) a ${roomName}!`,
         usePlusButton: ({additionalText}: UsePlusButtonParams) => `Use o botão + para ${additionalText} uma despesa.`,
-        askConcierge: ' Seu assistente de despesas com IA 24/7 está aqui para ajudar.',
+        askConcierge: 'Seu assistente de despesas com IA 24/7 está aqui para ajudar.',
         conciergeSupport: 'seu assistente de despesas 24/7',
         create: 'Criar',
         iouTypes: {
@@ -7988,7 +7988,6 @@ Aqui está um *recibo de teste* para mostrar como funciona:`,
             confirm: 'Descartar rastreamento de distância',
         },
         zeroDistanceTripModal: {title: 'Não é possível criar a despesa', prompt: 'Você não pode criar uma despesa com o mesmo local de partida e de chegada.'},
-
         locationRequiredModal: {
             title: 'Acesso à localização necessário',
             prompt: 'Permita o acesso à localização nas configurações do seu dispositivo para iniciar o rastreamento de distância por GPS.',
diff --git a/src/languages/zh-hans.ts b/src/languages/zh-hans.ts
index f343287e..1782ebb2 100644
--- a/src/languages/zh-hans.ts
+++ b/src/languages/zh-hans.ts
@@ -933,8 +933,8 @@ const translations: TranslationDeepObject<typeof en> = {
         yourSpace: '您的空间',
         welcomeToRoom: ({roomName}: WelcomeToRoomParams) => `欢迎来到 ${roomName}!`,
         usePlusButton: ({additionalText}: UsePlusButtonParams) => `使用“+”按钮来${additionalText}一笔报销。`,
-        askConcierge: ' 您的 7×24 小时 AI 费用助手随时为您提供帮助。',
-        conciergeSupport: '您的 7×24 小时费用助手',
+        askConcierge: '您的 24/7 AI 报销助手随时为您提供帮助。',
+        conciergeSupport: '您全天候的报销助手',
         create: '创建',
         iouTypes: {
             pay: '支付',
@@ -7794,7 +7794,6 @@ ${reportName}
         stopGpsTrackingModal: {title: '停止 GPS 追踪', prompt: '你确定吗?这将结束你当前的旅程。', cancel: '恢复追踪', confirm: '停止 GPS 追踪'},
         discardDistanceTrackingModal: {title: '丢弃距离跟踪', prompt: '您确定吗?这将放弃您当前的流程,且无法撤销。', confirm: '丢弃距离跟踪'},
         zeroDistanceTripModal: {title: '无法创建报销', prompt: '你不能创建起点和终点相同的报销。'},
-
         locationRequiredModal: {title: '需要访问位置信息', prompt: '请在设备设置中允许位置访问以开始 GPS 距离跟踪。', allow: '允许'},
         androidBackgroundLocationRequiredModal: {title: '需要后台位置访问权限', prompt: '请在设备设置中允许应用使用“始终允许”位置访问权限,以开始 GPS 距离跟踪。'},
         preciseLocationRequiredModal: {title: '需要精确位置', prompt: '请在设备设置中启用“精确位置”以开始 GPS 距离跟踪。'},

Note

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

The functions using allPolicyTags and currentUserLogin are connected
to UI components, so they need the regular Onyx.connect to ensure
proper re-rendering when the underlying data changes.
@marcochavezf marcochavezf force-pushed the marcochavezf/fix-onyx-connect-modified-expense-message branch from b26f924 to ce2d75c Compare January 16, 2026 17:36
@situchan
Copy link
Contributor

Does this require C+ review?

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.

4 participants