Skip to content

Add the consolidated domain billing to the DomainAdminsSettingsPage.tsx#77526

Merged
mountiny merged 24 commits intoExpensify:mainfrom
software-mansion-labs:war-in/domains/add-consolidated-domain-billing
Dec 22, 2025
Merged

Add the consolidated domain billing to the DomainAdminsSettingsPage.tsx#77526
mountiny merged 24 commits intoExpensify:mainfrom
software-mansion-labs:war-in/domains/add-consolidated-domain-billing

Conversation

@war-in
Copy link
Contributor

@war-in war-in commented Dec 12, 2025

Explanation of Change

PR adds Consolidated domain billing toggle to the admin settings

Fixed Issues

$ #77745
PROPOSAL:

Tests

  1. Go to /domain/domainAccountID/admins
  2. Click on settings, verify that Consolidated domain billing toggle is there
  3. Switch the toggle
  4. Set technicalContactEmail to null in onyx and verify that the toggle is locked
Onyx.merge('sharedNVP_private_domain_member_774', {settings: {technicalContactEmail: null}})

At the moment of writing, Vit's VM is not working properly and request is failing (that's why toggle goes back to the previous value)

Offline tests

QA Steps

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
Android: mWeb Chrome
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari
Screen.Recording.2025-12-15.at.19.40.32.mov

@melvin-bot
Copy link

melvin-bot bot commented Dec 12, 2025

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

@codecov
Copy link

codecov bot commented Dec 12, 2025

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 Δ
src/libs/API/types.ts 100.00% <ø> (ø)
src/selectors/Domain.ts 78.94% <100.00%> (+1.16%) ⬆️
src/pages/domain/Admins/DomainAdminsPage.tsx 0.00% <0.00%> (ø)
...ages/domain/Admins/DomainAddPrimaryContactPage.tsx 0.00% <0.00%> (ø)
src/pages/domain/DomainInitialPage.tsx 0.00% <0.00%> (ø)
src/libs/actions/Domain.ts 9.45% <0.00%> (-1.31%) ⬇️
...c/pages/domain/Admins/DomainAdminsSettingsPage.tsx 0.00% <0.00%> (ø)
... and 70 files with indirect coverage changes

@war-in war-in changed the title Add the consolidated domain billing to the DomainAdminsSettingsPage.tsx [HOLD] Add the consolidated domain billing to the DomainAdminsSettingsPage.tsx Dec 12, 2025
…mains/add-consolidated-domain-billing

# Conflicts:
#	src/libs/API/parameters/index.ts
#	src/libs/API/types.ts
#	src/libs/actions/Domain.ts
#	src/pages/domain/Admins/DomainAdminsSettingsPage.tsx
…o war-in/domains/add-consolidated-domain-billing

# Conflicts:
#	src/libs/actions/Domain.ts
#	src/pages/domain/Admins/DomainAdminsSettingsPage.tsx
@war-in war-in changed the title [HOLD] Add the consolidated domain billing to the DomainAdminsSettingsPage.tsx Add the consolidated domain billing to the DomainAdminsSettingsPage.tsx Dec 17, 2025
@war-in war-in marked this pull request as ready for review December 17, 2025 13:34
@war-in war-in requested review from a team as code owners December 17, 2025 13:34
@ZhenjaHorbach
Copy link
Contributor

I think it's better to reset the issue after reopening the screen
As we usually do on SAML domains flow

2025-12-17.14.38.07.mov

@war-in
Copy link
Contributor Author

war-in commented Dec 17, 2025

I think it's better to reset the issue after reopening the screen
As we usually do on SAML domains flow

Hmm, now I'm not sure which is the correct flow because in other parts of the app we don't reset errors

Screen.Recording.2025-12-17.at.14.42.01.mov

@ZhenjaHorbach
Copy link
Contributor

Also, I suppose it's better to reset this error optimistically
When we try to update this value in offline mode

2025-12-17.14.41.39.mov

@war-in
Copy link
Contributor Author

war-in commented Dec 17, 2025

Also, I suppose it's better to reset this error optimistically
When we try to update this value in offline mode

definitely, updated!

@ZhenjaHorbach
Copy link
Contributor

I think it's better to reset the issue after reopening the screen
As we usually do on SAML domains flow

Hmm, now I'm not sure which is the correct flow because in other parts of the app we don't reset errors

Screen.Recording.2025-12-17.at.14.42.01.mov

Hmmm, interesting
Okay then
Let's skip then 😄

@OSBotify

This comment has been minimized.

@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 50a39062..156240b7 100644
--- a/src/languages/de.ts
+++ b/src/languages/de.ts
@@ -7969,7 +7969,17 @@ Hier ist ein *Testbeleg*, um dir zu zeigen, wie es funktioniert:`,
             subtitle: 'Erzwingen Sie für Mitglieder Ihrer Domain die Anmeldung per Single Sign-On, schränken Sie die Erstellung von Workspaces ein und vieles mehr.',
             enable: 'Aktivieren',
         },
-        admins: {title: 'Admins', findAdmin: 'Admin finden', primaryContact: 'Hauptansprechpartner', addPrimaryContact: 'Primären Kontakt hinzufügen', settings: 'Einstellungen'},
+        admins: {
+            title: 'Admins',
+            findAdmin: 'Admin finden',
+            primaryContact: 'Hauptansprechpartner',
+            addPrimaryContact: 'Primären Kontakt hinzufügen',
+            settings: 'Einstellungen',
+            consolidatedDomainBilling: 'Konsolidierte Domain-Abrechnung',
+            consolidatedDomainBillingDescription: (domainName: string) =>
+                `Wenn diese Option aktiviert ist, bezahlt der Hauptansprechpartner für alle Workspaces, die Mitgliedern von <strong>${domainName}</strong> gehören, und erhält alle Rechnungsbelege.`,
+            consolidatedDomainBillingError: 'Die konsolidierte Domain-Abrechnung konnte nicht geändert werden. Bitte versuche es später erneut.',
+        },
     },
 };
 // IMPORTANT: This line is manually replaced in generate translation files by scripts/generateTranslations.ts,
diff --git a/src/languages/fr.ts b/src/languages/fr.ts
index b9a86aa3..138e1f37 100644
--- a/src/languages/fr.ts
+++ b/src/languages/fr.ts
@@ -7974,7 +7974,17 @@ Voici un *reçu test* pour vous montrer comment cela fonctionne :`,
             subtitle: "Exiger que les membres de votre domaine se connectent via l'authentification unique, restreindre la création d'espaces de travail, et plus encore.",
             enable: 'Activer',
         },
-        admins: {title: 'Admins', findAdmin: 'Trouver un admin', primaryContact: 'Contact principal', addPrimaryContact: 'Ajouter un contact principal', settings: 'Paramètres'},
+        admins: {
+            title: 'Admins',
+            findAdmin: 'Trouver un admin',
+            primaryContact: 'Contact principal',
+            addPrimaryContact: 'Ajouter un contact principal',
+            settings: 'Paramètres',
+            consolidatedDomainBilling: 'Facturation consolidée du domaine',
+            consolidatedDomainBillingDescription: (domainName: string) =>
+                `Lorsque cette option est activée, le contact principal paiera pour tous les espaces de travail appartenant aux membres de <strong>${domainName}</strong> et recevra tous les reçus de facturation.`,
+            consolidatedDomainBillingError: 'La facturation de domaine consolidée n’a pas pu être modifiée. Veuillez réessayer plus tard.',
+        },
     },
 };
 // IMPORTANT: This line is manually replaced in generate translation files by scripts/generateTranslations.ts,
diff --git a/src/languages/it.ts b/src/languages/it.ts
index 75cf826e..93619eed 100644
--- a/src/languages/it.ts
+++ b/src/languages/it.ts
@@ -7956,6 +7956,10 @@ Ecco una *ricevuta di prova* per mostrarti come funziona:`,
             primaryContact: 'Contatto principale',
             addPrimaryContact: 'Aggiungi contatto principale',
             settings: 'Impostazioni',
+            consolidatedDomainBilling: 'Fatturazione consolidata del dominio',
+            consolidatedDomainBillingDescription: (domainName: string) =>
+                `Quando abilitata, il contatto principale pagherà per tutti gli spazi di lavoro di proprietà dei membri di <strong>${domainName}</strong> e riceverà tutte le ricevute di fatturazione.`,
+            consolidatedDomainBillingError: 'La fatturazione dominio consolidata non può essere modificata. Riprova più tardi.',
         },
     },
 };
diff --git a/src/languages/ja.ts b/src/languages/ja.ts
index 685a7cda..cbd0da52 100644
--- a/src/languages/ja.ts
+++ b/src/languages/ja.ts
@@ -7889,7 +7889,17 @@ Expensify の使い方をお見せするための*テストレシート*がこ
             subtitle: 'ドメインのメンバーにシングルサインオンでのログインを必須化し、ワークスペースの作成を制限するなど、さらに多くのことができます。',
             enable: '有効にする',
         },
-        admins: {title: '管理者', findAdmin: '管理者を検索', primaryContact: '主要連絡先', addPrimaryContact: '主要連絡先を追加', settings: '設定'},
+        admins: {
+            title: '管理者',
+            findAdmin: '管理者を検索',
+            primaryContact: '主要連絡先',
+            addPrimaryContact: '主要連絡先を追加',
+            settings: '設定',
+            consolidatedDomainBilling: '統合ドメイン請求',
+            consolidatedDomainBillingDescription: (domainName: string) =>
+                `有効にすると、<strong>${domainName}</strong> メンバーが所有するすべてのワークスペースの支払いを代表連絡先が行い、すべての請求書の領収書を受け取ります。`,
+            consolidatedDomainBillingError: '統合ドメイン請求を変更できませんでした。後でもう一度お試しください。',
+        },
     },
 };
 // IMPORTANT: This line is manually replaced in generate translation files by scripts/generateTranslations.ts,
diff --git a/src/languages/nl.ts b/src/languages/nl.ts
index 695fd9ec..e9a9c933 100644
--- a/src/languages/nl.ts
+++ b/src/languages/nl.ts
@@ -7942,6 +7942,10 @@ Hier is een *testbon* om je te laten zien hoe het werkt:`,
             primaryContact: 'Primair contactpersoon',
             addPrimaryContact: 'Primair contactpersoon toevoegen',
             settings: 'Instellingen',
+            consolidatedDomainBilling: 'Geconsolideerde domeinfacturering',
+            consolidatedDomainBillingDescription: (domainName: string) =>
+                `Indien ingeschakeld, betaalt de primaire contactpersoon voor alle werkruimten die eigendom zijn van leden van <strong>${domainName}</strong> en ontvangt hij/zij alle factuurbewijzen.`,
+            consolidatedDomainBillingError: 'Geconsolideerde domeinfacturering kon niet worden gewijzigd. Probeer het later opnieuw.',
         },
     },
 };
diff --git a/src/languages/pl.ts b/src/languages/pl.ts
index 0aebd058..3e5ce18c 100644
--- a/src/languages/pl.ts
+++ b/src/languages/pl.ts
@@ -7921,7 +7921,17 @@ Oto *paragon testowy*, który pokazuje, jak to działa:`,
             subtitle: 'Wymagaj, aby członkowie Twojej domeny logowali się przez Single Sign-On (SSO), ograniczaj tworzenie obszarów roboczych i nie tylko.',
             enable: 'Włącz',
         },
-        admins: {title: 'Administratorzy', findAdmin: 'Znajdź administratora', primaryContact: 'Główny kontakt', addPrimaryContact: 'Dodaj główny kontakt', settings: 'Ustawienia'},
+        admins: {
+            title: 'Administratorzy',
+            findAdmin: 'Znajdź administratora',
+            primaryContact: 'Główny kontakt',
+            addPrimaryContact: 'Dodaj główny kontakt',
+            settings: 'Ustawienia',
+            consolidatedDomainBilling: 'Skonsolidowane rozliczanie domen',
+            consolidatedDomainBillingDescription: (domainName: string) =>
+                `Gdy ta opcja jest włączona, główny kontakt będzie opłacać wszystkie przestrzenie robocze należące do członków <strong>${domainName}</strong> i otrzymywać wszystkie potwierdzenia rozliczeń.`,
+            consolidatedDomainBillingError: 'Nie udało się zmienić zbiorczego rozliczania domeny. Spróbuj ponownie później.',
+        },
     },
 };
 // IMPORTANT: This line is manually replaced in generate translation files by scripts/generateTranslations.ts,
diff --git a/src/languages/pt-BR.ts b/src/languages/pt-BR.ts
index 5dd8a001..3c2d07e9 100644
--- a/src/languages/pt-BR.ts
+++ b/src/languages/pt-BR.ts
@@ -7934,6 +7934,10 @@ Aqui está um *recibo de teste* para mostrar como funciona:`,
             primaryContact: 'Contato principal',
             addPrimaryContact: 'Adicionar contato principal',
             settings: 'Configurações',
+            consolidatedDomainBilling: 'Cobrança consolidada de domínio',
+            consolidatedDomainBillingDescription: (domainName: string) =>
+                `Quando ativado, o contato principal pagará por todos os espaços de trabalho pertencentes aos membros de <strong>${domainName}</strong> e receberá todos os recibos de cobrança.`,
+            consolidatedDomainBillingError: 'A cobrança de domínio consolidada não pôde ser alterada. Tente novamente mais tarde.',
         },
     },
 };
diff --git a/src/languages/zh-hans.ts b/src/languages/zh-hans.ts
index 58777d34..4817beda 100644
--- a/src/languages/zh-hans.ts
+++ b/src/languages/zh-hans.ts
@@ -7754,7 +7754,16 @@ ${reportName}
         addDomain: {title: '添加域', subtitle: '请输入您想访问的私有域名(例如:expensify.com)。', domainName: '域名', newDomain: '新域名'},
         domainAdded: {title: '已添加域名', description: '接下来,您需要验证域名的所有权并调整您的安全设置。', configure: '配置'},
         enhancedSecurity: {title: '增强的安全性', subtitle: '要求您域内的成员使用单点登录登录、限制工作区创建等。', enable: '启用'},
-        admins: {title: '管理员', findAdmin: '查找管理员', primaryContact: '主要联系人', addPrimaryContact: '添加主要联系人', settings: '设置'},
+        admins: {
+            title: '管理员',
+            findAdmin: '查找管理员',
+            primaryContact: '主要联系人',
+            addPrimaryContact: '添加主要联系人',
+            settings: '设置',
+            consolidatedDomainBilling: '合并域名结算',
+            consolidatedDomainBillingDescription: (domainName: string) => `启用后,主要联系人将为<strong>${domainName}</strong>成员拥有的所有工作区付款,并接收所有账单收据。`,
+            consolidatedDomainBillingError: '无法更改合并域账单。请稍后重试。',
+        },
     },
 };
 // IMPORTANT: This line is manually replaced in generate translation files by scripts/generateTranslations.ts,

Note

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

@ZhenjaHorbach
Copy link
Contributor

But overall changes look good!

@situchan
If you want you can check this PR also!

@war-in
Copy link
Contributor Author

war-in commented Dec 19, 2025

But sometimes the toogle changes state to incorrect after returning from offline mode

That only happens for an even number of toggles. Let's consider this situation

  • billing is disabled (false in onyx)
  • go offline
  • toggle once (failure data for billing is false, the original value)
  • toggle second time (failure data is true, the current optimistic value)
  • go online
  • first failure data is applied, and then the second
  • so we end with true where the original value was false

I think that should start working as expected once the OpenDomainInitialPage start return the useTechnicalContactBillingCard

I added useNetwork({onReconnect: fetchDomainData}); to DomainInitialPage to load the data after reconnect

@ZhenjaHorbach
Copy link
Contributor

But sometimes the toogle changes state to incorrect after returning from offline mode

That only happens for an even number of toggles. Let's consider this situation

  • billing is disabled (false in onyx)
  • go offline
  • toggle once (failure data for billing is false, the original value)
  • toggle second time (failure data is true, the current optimistic value)
  • go online
  • first failure data is applied, and then the second
  • so we end with true where the original value was false

I think that should start working as expected once the OpenDomainInitialPage start return the useTechnicalContactBillingCard

I added useNetwork({onReconnect: fetchDomainData}); to DomainInitialPage to load the data after reconnect

Sounds good
Thanks!

@melvin-bot melvin-bot bot requested a review from JS00001 December 21, 2025 19:25
@ZhenjaHorbach
Copy link
Contributor

LGTM!

settings: 'Einstellungen',
consolidatedDomainBilling: 'Konsolidierte Domain-Abrechnung',
consolidatedDomainBillingDescription: (domainName: string) =>
`Wenn diese Option aktiviert ist, bezahlt der Hauptansprechpartner für alle Workspaces, die Mitgliedern von <strong>${domainName}</strong> gehören, und erhält alle Rechnungsbelege.`,
Copy link
Contributor

Choose a reason for hiding this comment

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

<strong> was removed in English. If that's the correct fix, can we apply same to all other languages?

Copy link
Contributor Author

@war-in war-in Dec 22, 2025

Choose a reason for hiding this comment

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

@situchan that was a mistake. I fixed it in the last commit - f8492e8

Comment on lines +83 to +85
<View style={[styles.flexRow, styles.renderHTML, styles.mt1]}>
<RenderHTML html={translate('domain.admins.consolidatedDomainBillingDescription', domain?.email ? Str.extractEmailDomain(domain.email) : '')} />
</View>
Copy link
Contributor

Choose a reason for hiding this comment

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

This should be retested. I think engineers are OOO but @war-in do you know any ngrok available at the moment?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Not really :/ I tested it on my account where I have a domain and it worked fine without ngrok

Copy link
Contributor Author

Choose a reason for hiding this comment

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

also, you can just mock the data

Copy link
Contributor

Choose a reason for hiding this comment

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

Mind sharing mock data? So I can test further PRs without ngrok

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I have something like that

Onyx.merge('domain_20998357', {
    expensify_adminPermissions_1: "1353644",
    expensify_adminPermissions_2: "1999782",
    expensify_adminPermissions_3: "12831710",
    expensify_adminPermissions_4: "12831943",
    expensify_adminPermissions_5: "16530855",
    expensify_adminPermissions_6: "21010971",

    expensify_adminPermissions_7: "21011234",
    expensify_adminPermissions_8: "21011890",
    expensify_adminPermissions_9: "21012567",
    expensify_adminPermissions_10: "21013321",
    expensify_adminPermissions_11: "21014482",
    expensify_adminPermissions_12: "21015509",
    expensify_adminPermissions_13: "21016224",
    expensify_adminPermissions_14: "21017356",
    expensify_adminPermissions_15: "21018477",
    expensify_adminPermissions_16: "21019588",
    expensify_adminPermissions_17: "21020745",
    expensify_adminPermissions_18: "21021893",
    expensify_adminPermissions_19: "21022941",
    expensify_adminPermissions_20: "21024012"
});

do you have a domain? Or should I add you to mine?

Copy link
Contributor

Choose a reason for hiding this comment

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

Copy link
Contributor

Choose a reason for hiding this comment

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

should I add you to mine?

yes please
situchandrashil7+77526@gmail.com

Copy link
Contributor Author

Choose a reason for hiding this comment

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

added!

@situchan
Copy link
Contributor

RBR message is cut off on iOS. Does this happen on main (other places of the app)?

Screenshot 2025-12-22 at 7 02 27 PM

@war-in
Copy link
Contributor Author

war-in commented Dec 22, 2025

@situchan it looks the same on the workspace workflows page
image

Copy link
Contributor

@situchan situchan left a comment

Choose a reason for hiding this comment

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

renderHTML looks good on both web and native

web:

Image

iOS:

Image

Android:

Screenshot 2025-12-22 at 7 49 37 PM

JS00001
JS00001 previously approved these changes Dec 22, 2025
Copy link
Contributor

@mountiny mountiny left a comment

Choose a reason for hiding this comment

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

Looks good, lets rename the param

mountiny
mountiny previously approved these changes Dec 22, 2025
Copy link
Contributor

@mountiny mountiny left a comment

Choose a reason for hiding this comment

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

Thank you

@mountiny
Copy link
Contributor

@war-in for clean up, the error message should come from the BE once we have that in place but the way we render this error should be better, we should add classic padding for the error here
image
and it should wrap

@mountiny mountiny merged commit 39ea123 into Expensify:main Dec 22, 2025
31 checks passed
@OSBotify
Copy link
Contributor

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

@OSBotify
Copy link
Contributor

🚀 Deployed to staging by https://github.com/mountiny in version: 9.2.86-0 🚀

platform result
🖥 desktop 🖥 success ✅
🕸 web 🕸 success ✅
🤖 android 🤖 failure ❌
🍎 iOS 🍎 success ✅

@OSBotify
Copy link
Contributor

🚀 Deployed to production by https://github.com/marcaaron in version: 9.2.86-4 🚀

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

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.

6 participants