Skip to content

Fix Certinia setup step 1 bundle links not rendering on native#94856

Merged
yuwenmemon merged 8 commits into
Expensify:mainfrom
ShridharGoel:fix/94711-certinia-bundle-link-native
Jul 8, 2026
Merged

Fix Certinia setup step 1 bundle links not rendering on native#94856
yuwenmemon merged 8 commits into
Expensify:mainfrom
ShridharGoel:fix/94711-certinia-bundle-link-native

Conversation

@ShridharGoel

@ShridharGoel ShridharGoel commented Jun 29, 2026

Copy link
Copy Markdown
Contributor

Explanation of Change

On the Certinia setup step 1 ("Install the Expensify bundle"), the PSA/SRP and FFA sections each render a bold header plus a description with an install link through RenderHTML. On native (Android/iOS) only the headers showed — the description text, the install link, and the version were missing. Web rendered everything correctly.

The two description strings are bare inline HTML (text followed by an <a> link) with no block-level wrapper. react-native-render-html won't lay out top-level inline content that has no block parent, so on native the whole block rendered empty. On web the browser lays out the inline content anyway, which is why web was unaffected.

The fix wraps each description in a <p> block element at the call site. This gives the native renderer a block root so the text, link, and version render. <p> keeps the normal text color and has zero margins, so the web appearance is unchanged. Wrapping at the call site fixes all locales without editing the translation strings, and matches how other accounting setup pages feed "text + link" copy through RenderHTML (e.g. NetSuite, QBD).

Fixed Issues

$ #94711
PROPOSAL:

Tests

  1. On the Android or iOS native app, open a workspace and go to More features > enable Accounting > open Accounting.
  2. Start a new Certinia connection.
  3. On setup step 1 ("Install the Expensify bundle"), verify the For PSA/SRP Connections: section shows its description text and the link Install PSA/SRP Expensify Bundle (Version 1.3).
  4. Verify the For FFA Connections: section shows its description text and the link Install FFA Expensify Bundle (Version 1.4).
  5. Tap each link and verify it opens the correct Salesforce install page.
  6. On Web, verify both sections still render the same as before.
  7. Verify that no errors appear in the JS console.

Offline tests

  1. Turn off the network connection.
  2. Open Certinia setup step 1.
  3. Verify both descriptions, links, and versions still render (the content is static).

QA Steps

Same as tests.

  • Verify that no errors appear in the JS console

PR Author Checklist

  • I linked the correct issue in the ### Fixed Issues section above
  • I wrote clear testing steps that cover the changes made in this PR
    • I added steps for local testing in the Tests section
    • I added steps for the expected offline behavior in the Offline steps section
    • I added steps for Staging and/or Production testing in the QA steps section
    • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
    • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
    • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
  • I included screenshots or videos for tests on all platforms
  • I ran the tests on all platforms & verified they passed on:
    • Android: Native
    • Android: mWeb Chrome
    • iOS: Native
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
  • I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
  • I followed proper code patterns (see Reviewing the code)
    • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
    • I verified that comments were added to code that is not self explanatory
    • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
    • I verified any copy / text 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)
  • 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)
  • 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.
  • 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

iOS: Native Screenshot 2026-07-07 at 12 30 40 PM

@ShridharGoel
ShridharGoel marked this pull request as ready for review June 29, 2026 14:53
@ShridharGoel
ShridharGoel requested review from a team as code owners June 29, 2026 14:53
@melvin-bot
melvin-bot Bot requested review from thelullabyy and removed request for a team June 29, 2026 14:53
@melvin-bot

melvin-bot Bot commented Jun 29, 2026

Copy link
Copy Markdown

@thelullabyy 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 trjExpensify and removed request for a team June 29, 2026 14:53
@thelullabyy

thelullabyy commented Jun 30, 2026

Copy link
Copy Markdown
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 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 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)
  • 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)
  • 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.
  • 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 image
Android: mWeb Chrome image
iOS: HybridApp image
iOS: mWeb Safari Screenshot 2026-07-02 at 03 12 42
MacOS: Chrome / Safari Screenshot 2026-07-02 at 03 10 37

@thelullabyy

Copy link
Copy Markdown
Contributor

@ShridharGoel Type check failed

@thelullabyy

Copy link
Copy Markdown
Contributor

@ShridharGoel Please add recordings as well

@melvin-bot

melvin-bot Bot commented Jun 30, 2026

Copy link
Copy Markdown

Hey, I noticed you changed src/languages/en.ts in a PR from a fork. For security reasons, translations are not generated automatically for PRs from forks.

If you want to automatically generate translations for other locales, an Expensify employee will have to:

  1. Look at the code and make sure there are no malicious changes.
  2. Run the Generate static translations GitHub workflow. If you have write access and the K2 extension, you can simply click: [this button]

Alternatively, if you are an external contributor, you can run the translation script locally with your own OpenAI API key. To learn more, try running:

npx ts-node ./scripts/generateTranslations.ts --help

Typically, you'd want to translate only what you changed by running npx ts-node ./scripts/generateTranslations.ts --compare-ref main

@OSBotify

Copy link
Copy Markdown
Contributor

🦜 Polyglot Parrot! 🦜

Squawk! Looks like you added some shiny new English strings. Allow me to parrot them back to you in other tongues:

View the translation diff
diff --git a/src/languages/de.ts b/src/languages/de.ts
index a53c7407..b170e2de 100644
--- a/src/languages/de.ts
+++ b/src/languages/de.ts
@@ -5048,7 +5048,7 @@ ${amount} für ${merchant} – ${date}`,
                     `<p>Installieren Sie das Expensify-Paket in Salesforce, indem Sie auf diesen Link klicken: <a href="${href}">PSA/SRP Expensify Bundle installieren (Version ${version})</a></p>`,
                 installBundleFFAHeader: 'Für FFA-Verbindungen:',
                 installBundleFFADescription: ({href, version}: {href: string; version: string}) =>
-                    `<p>Installieren Sie das Expensify-Paket in Salesforce, indem Sie auf diesen Link klicken: <a href="${href}">FFA-Expensify-Paket installieren (Version ${version})</a></p>`,
+                    `<p>Installieren Sie das Expensify-Bundle in Salesforce, indem Sie auf diesen Link klicken: <a href="${href}">FFA Expensify-Bundle installieren (Version ${version})</a></p>`,
                 installBundleConfirm: 'Ich habe das Paket installiert',
                 setupContacts: 'Benutzer und Kontakte einrichten',
                 setupContactsBullet1:
diff --git a/src/languages/es.ts b/src/languages/es.ts
index 07dcb890..69108066 100644
--- a/src/languages/es.ts
+++ b/src/languages/es.ts
@@ -4926,10 +4926,10 @@ ${amount} para ${merchant} - ${date}`,
                 installBundle: 'Instala el paquete de Expensify',
                 installBundlePSAHeader: 'Para conexiones PSA/SRP:',
                 installBundlePSADescription: ({href, version}: {href: string; version: string}) =>
-                    `<p>Instala el paquete de Expensify en Salesforce haciendo clic en este enlace: <a href="${href}">Instalar paquete Expensify PSA/SRP (Versión ${version})</a></p>`,
+                    `<p>Instala el paquete de Expensify en Salesforce haciendo clic en este enlace: <a href="${href}">Instalar paquete PSA/SRP de Expensify (Versión ${version})</a></p>`,
                 installBundleFFAHeader: 'Para conexiones FFA:',
                 installBundleFFADescription: ({href, version}: {href: string; version: string}) =>
-                    `<p>Instala el paquete de Expensify en Salesforce haciendo clic en este enlace: <a href="${href}">Instalar el paquete de Expensify para FFA (versión ${version})</a></p>`,
+                    `<p>Instala el paquete de Expensify en Salesforce haciendo clic en este enlace: <a href="${href}">Instalar paquete FFA Expensify (Versión ${version})</a></p>`,
                 installBundleConfirm: 'He instalado el paquete',
                 setupContacts: 'Configura usuario y contactos',
                 setupContactsBullet1:
diff --git a/src/languages/fr.ts b/src/languages/fr.ts
index 82654b73..345259dc 100644
--- a/src/languages/fr.ts
+++ b/src/languages/fr.ts
@@ -5057,10 +5057,10 @@ ${amount} pour ${merchant} - ${date}`,
                 installBundle: 'Installer le module Expensify',
                 installBundlePSAHeader: 'Pour les connexions PSA/SRP :',
                 installBundlePSADescription: ({href, version}: {href: string; version: string}) =>
-                    `<p>Installez le bundle Expensify dans Salesforce en cliquant sur ce lien : <a href="${href}">Installer le bundle Expensify PSA/SRP (version ${version})</a></p>`,
+                    `<p>Installez le bundle Expensify dans Salesforce en cliquant sur ce lien : <a href="${href}">Installer le bundle Expensify PSA/SRP (version ${version})</a></p>`,
                 installBundleFFAHeader: 'Pour les connexions FFA :',
                 installBundleFFADescription: ({href, version}: {href: string; version: string}) =>
-                    `<p>Installez le bundle Expensify dans Salesforce en cliquant sur ce lien : <a href="${href}">Installer le bundle Expensify pour FFA (version ${version})</a></p>`,
+                    `<p>Installez le bundle Expensify dans Salesforce en cliquant sur ce lien : <a href="${href}">Installer le bundle FFA Expensify (version ${version})</a></p>`,
                 installBundleConfirm: 'J’ai installé le paquet',
                 setupContacts: 'Configurer l’utilisateur et les contacts',
                 setupContactsBullet1:
diff --git a/src/languages/it.ts b/src/languages/it.ts
index e0305a4c..5339192a 100644
--- a/src/languages/it.ts
+++ b/src/languages/it.ts
@@ -5030,10 +5030,10 @@ ${amount} per ${merchant} - ${date}`,
                 installBundle: 'Installa il bundle Expensify',
                 installBundlePSAHeader: 'Per le connessioni PSA/SRP:',
                 installBundlePSADescription: ({href, version}: {href: string; version: string}) =>
-                    `<p>Installa il bundle Expensify in Salesforce cliccando su questo link: <a href="${href}">Installa il bundle PSA/SRP Expensify (versione ${version})</a></p>`,
+                    `<p>Installa il bundle Expensify in Salesforce cliccando su questo link: <a href="${href}">Installa il bundle PSA/SRP Expensify (Versione ${version})</a></p>`,
                 installBundleFFAHeader: 'Per le connessioni FFA:',
                 installBundleFFADescription: ({href, version}: {href: string; version: string}) =>
-                    `<p>Installa il bundle Expensify in Salesforce facendo clic su questo link: <a href="${href}">Installa il bundle Expensify per FFA (versione ${version})</a></p>`,
+                    `<p>Installa il bundle Expensify in Salesforce cliccando su questo link: <a href="${href}">Installa FFA Expensify Bundle (Versione ${version})</a></p>`,
                 installBundleConfirm: 'Ho installato il pacchetto',
                 setupContacts: 'Configura utente e contatti',
                 setupContactsBullet1:
diff --git a/src/languages/ja.ts b/src/languages/ja.ts
index 15bf9cba..060338dc 100644
--- a/src/languages/ja.ts
+++ b/src/languages/ja.ts
@@ -4983,10 +4983,10 @@ ${integrationName === CONST.ONBOARDING_ACCOUNTING_MAPPING.other ? 'あなたの'
                 installBundle: 'Expensify バンドルをインストールします',
                 installBundlePSAHeader: 'PSA/SRP 接続の場合:',
                 installBundlePSADescription: ({href, version}: {href: string; version: string}) =>
-                    `<p>このリンクをクリックして Salesforce に Expensify バンドルをインストールしてください:<a href="${href}">PSA/SRP Expensify バンドル(バージョン ${version})をインストール</a></p>`,
+                    `<p>このリンクをクリックして Salesforce に Expensify バンドルをインストールします : <a href="${href}">PSA/SRP Expensify バンドル(バージョン ${version})をインストール</a></p>`,
                 installBundleFFAHeader: 'FFA 接続用:',
                 installBundleFFADescription: ({href, version}: {href: string; version: string}) =>
-                    `<p>このリンクをクリックして、Salesforce に Expensify バンドルをインストールしてください:<a href="${href}">FFA 用 Expensify バンドルをインストール(バージョン ${version})</a></p>`,
+                    `<p>このリンクをクリックして、Salesforce に Expensify バンドルをインストールします: <a href="${href}">FFA Expensify バンドルをインストール(バージョン ${version})</a></p>`,
                 installBundleConfirm: 'バンドルをインストールしました',
                 setupContacts: 'ユーザーと連絡先を設定',
                 setupContactsBullet1:
diff --git a/src/languages/nl.ts b/src/languages/nl.ts
index 45687347..77e3cda8 100644
--- a/src/languages/nl.ts
+++ b/src/languages/nl.ts
@@ -5020,10 +5020,10 @@ ${amount} voor ${merchant} - ${date}`,
                 installBundle: 'Installeer het Expensify-pakket',
                 installBundlePSAHeader: 'Voor PSA/SRP-koppelingen:',
                 installBundlePSADescription: ({href, version}: {href: string; version: string}) =>
-                    `<p>Installeer de Expensify-bundel in Salesforce door op deze link te klikken: <a href="${href}">Installeer PSA/SRP Expensify-bundel (versie ${version})</a></p>`,
+                    `<p>Installeer het Expensify-pakket in Salesforce door op deze link te klikken: <a href="${href}">Installeer PSA/SRP Expensify-pakket (versie ${version})</a></p>`,
                 installBundleFFAHeader: 'Voor FFA-verbindingen:',
                 installBundleFFADescription: ({href, version}: {href: string; version: string}) =>
-                    `<p>Installeer de Expensify-bundel in Salesforce door op deze link te klikken: <a href="${href}">Expensify-bundel voor FFA installeren (versie ${version})</a></p>`,
+                    `<p>Installeer de Expensify-bundel in Salesforce door op deze link te klikken: <a href="${href}">Installeer FFA Expensify-bundel (versie ${version})</a></p>`,
                 installBundleConfirm: 'Ik heb de bundel geïnstalleerd',
                 setupContacts: 'Gebruiker en contacten instellen',
                 setupContactsBullet1:
diff --git a/src/languages/pl.ts b/src/languages/pl.ts
index 0664cd4c..2a7f88b6 100644
--- a/src/languages/pl.ts
+++ b/src/languages/pl.ts
@@ -5016,7 +5016,7 @@ ${amount} dla ${merchant} - ${date}`,
                     `<p>Zainstaluj pakiet Expensify w Salesforce, klikając ten link: <a href="${href}">Zainstaluj pakiet PSA/SRP Expensify (wersja ${version})</a></p>`,
                 installBundleFFAHeader: 'Dla połączeń FFA:',
                 installBundleFFADescription: ({href, version}: {href: string; version: string}) =>
-                    `<p>Zainstaluj pakiet Expensify w Salesforce, klikając ten link: <a href="${href}">Zainstaluj pakiet Expensify dla FFA (wersja ${version})</a></p>`,
+                    `<p>Zainstaluj pakiet Expensify w Salesforce, klikając ten link: <a href="${href}">Zainstaluj pakiet FFA Expensify (wersja ${version})</a></p>`,
                 installBundleConfirm: 'Zainstalowałem pakiet',
                 setupContacts: 'Skonfiguruj użytkownika i kontakty',
                 setupContactsBullet1:
diff --git a/src/languages/pt-BR.ts b/src/languages/pt-BR.ts
index dea936b8..1ac4c45e 100644
--- a/src/languages/pt-BR.ts
+++ b/src/languages/pt-BR.ts
@@ -5011,10 +5011,10 @@ ${amount} para ${merchant} - ${date}`,
                 installBundle: 'Instalar o pacote do Expensify',
                 installBundlePSAHeader: 'Para conexões PSA/SRP:',
                 installBundlePSADescription: ({href, version}: {href: string; version: string}) =>
-                    `<p>Instale o pacote Expensify no Salesforce clicando neste link: <a href="${href}">Instalar pacote PSA/SRP Expensify (versão ${version})</a></p>`,
+                    `<p>Instale o pacote do Expensify no Salesforce clicando neste link: <a href="${href}">Instalar Pacote PSA/SRP Expensify (Versão ${version})</a></p>`,
                 installBundleFFAHeader: 'Para conexões FFA:',
                 installBundleFFADescription: ({href, version}: {href: string; version: string}) =>
-                    `<p>Instale o pacote do Expensify no Salesforce clicando neste link: <a href="${href}">Instalar o pacote do Expensify para FFA (versão ${version})</a></p>`,
+                    `<p>Instale o pacote do Expensify no Salesforce clicando neste link: <a href="${href}">Instalar Pacote FFA Expensify (Versão ${version})</a></p>`,
                 installBundleConfirm: 'Eu instalei o pacote',
                 setupContacts: 'Configurar usuário e contatos',
                 setupContactsBullet1:
diff --git a/src/languages/zh-hans.ts b/src/languages/zh-hans.ts
index 3345524e..82d3f96d 100644
--- a/src/languages/zh-hans.ts
+++ b/src/languages/zh-hans.ts
@@ -4884,10 +4884,10 @@ ${amount},商户:${merchant} - 日期:${date}`,
                 installBundle: '安装 Expensify 捆绑包',
                 installBundlePSAHeader: '用于 PSA/SRP 连接:',
                 installBundlePSADescription: ({href, version}: {href: string; version: string}) =>
-                    `<p>通过点击此链接在 Salesforce 中安装 Expensify 包:<a href="${href}">安装 PSA/SRP Expensify 包(版本 ${version})</a></p>`,
+                    `<p>在 Salesforce 中安装 Expensify 包,请点击此链接:<a href="${href}">安装 PSA/SRP Expensify 包(版本 ${version})</a></p>`,
                 installBundleFFAHeader: '对于 FFA 连接:',
                 installBundleFFADescription: ({href, version}: {href: string; version: string}) =>
-                    `<p>通过点击此链接在 Salesforce 中安装 Expensify 组件包:<a href="${href}">安装 FFA Expensify 组件包(版本 ${version})</a></p>`,
+                    `<p>在 Salesforce 中安装 Expensify 捆绑包,请点击此链接:<a href="${href}">安装 FFA Expensify 捆绑包(版本 ${version})</a></p>`,
                 installBundleConfirm: '我已安装此捆绑包',
                 setupContacts: '设置用户和联系人',
                 setupContactsBullet1: '如果 Certinia 中尚未为你创建用户和联系人,请为自己分别创建一个用户和一个联系人,并确保其电子邮箱与你在 Expensify 中的主要邮箱一致。',

Note

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

View workflow run

@github-actions

Copy link
Copy Markdown
Contributor

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

@github-actions

This comment has been minimized.

trjExpensify
trjExpensify previously approved these changes Jun 30, 2026

@trjExpensify trjExpensify left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Bug fix for Certinia rollout. So close to getting this released! 👍

@thelullabyy

Copy link
Copy Markdown
Contributor

@ShridharGoel It doesn't fix on native app

image

@thelullabyy

Copy link
Copy Markdown
Contributor

@MelvinBot could you please check this bug? #94856 (comment)

@MelvinBot

Copy link
Copy Markdown
Contributor

Issue Analysis

Root cause: Wrapping the strings in <p> isn't enough to make RenderHTML lay out top-level "text + link" content on native. The established pattern in this codebase for exactly this case (NetSuite/QBD) wraps the content in a <comment> tag — a custom block element model registered in the HTML engine with intrinsic-width styling (whiteSpace: 'pre') — not a plain <p>.

RenderHTML here is rendered without an onLinkPress, so it falls through to a bare <RenderHTMLSource> (src/components/RenderHTML.tsx:89-99) that inherits the app-wide provider. That provider applies alignItemsStart to the block root (BaseHTMLEngineProvider.tsx:239). A plain <p> block (no registered model, no width styling) collapses on native under Yoga, so the text/link don't show — while web lays it out regardless. <comment> avoids this because it's registered as a block with whiteSpace: 'pre' (BaseHTMLEngineProvider.tsx:97-108).

Recommended fix: Match the proven NetSuite/QBD pattern — wrap the description in <comment> instead of <p>. Cleanest is to do it at the call site and keep the translation strings as bare text + <a> (revert the 10 language-file <p> edits):

<RenderHTML
    html={`<comment>${translate('workspace.certinia.prerequisites.installBundlePSADescription', {
        href: CONST.CERTINIA_PSA_BUNDLE_INSTALL_URL.PRODUCTION,
        version: CONST.CERTINIA_PSA_BUNDLE_VERSION,
    })}</comment>`}
/>

(Alternatively, swap <p><comment> inside the strings, but wrapping at the call site avoids touching all 10 locale files and mirrors NetSuite exactly — see NetSuiteImportMappingPage.tsx:65.)

Investigation details
  • Call site: CertiniaPrerequisitesStep.tsx:38-52 passes the translated string straight to <RenderHTML html={...} /> with no onLinkPress.
  • ExpensiMark is not the culprit: RenderHTML runs the string through Parser.replace(..., {shouldEscapeText: false, filterRules: ['emoji']}) (RenderHTML.tsx:50). With only the emoji rule active and no emoji present, the <p>/<a> pass through unchanged — so the markup does reach the renderer; the problem is layout, not parsing.
  • The differentiator between working (<comment>) and broken (<p>) is that <comment> is a registered custom block model with width-giving styles, whereas <p> is a plain block that collapses under the provider's alignItemsStart on native.
  • Note: I confirmed the mechanism by tracing the code, but wasn't able to run it on an Android/iOS device — worth verifying the <comment> change renders correctly on native before merging.

Next Steps: Reply with @MelvinBot implement this to have me revert the <p> edits and apply the <comment> fix, or @MelvinBot <your feedback> to refine this analysis.

@github-actions

github-actions Bot commented Jul 2, 2026

Copy link
Copy Markdown
Contributor

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

@github-actions

This comment has been minimized.

@ShridharGoel ShridharGoel mentioned this pull request Jul 3, 2026
Closed
@ShridharGoel
ShridharGoel requested a review from thelullabyy July 4, 2026 09:37
@trjExpensify

Copy link
Copy Markdown
Contributor

@thelullabyy can you review this today? It's the only blocker left to release.

@thelullabyy

Copy link
Copy Markdown
Contributor
image

@ShridharGoel It still doesn't work to me. Could you please test again and add all required recording/evidences before request another review. Thanks

@thelullabyy

Copy link
Copy Markdown
Contributor

Stop routing this static label + link through RenderHTML and render it with the app's first-class components, which is the standard Expensify pattern for "sentence + link" and is immune to the phrasing-root pitfall on every platform.

@MelvinBot Do you think solution above will work? As the current approach doesn't work to me, there is still no text on android and ios app

image

@MelvinBot

Copy link
Copy Markdown
Contributor

⚠️ Something went wrong. This may be a transient issue — try again. If it persists, check status.anthropic.com.

Run details

@ShridharGoel

Copy link
Copy Markdown
Contributor Author

Updated

@codecov

codecov Bot commented Jul 7, 2026

Copy link
Copy Markdown

Codecov Report

✅ Changes either increased or maintained existing code coverage, great job!

Files with missing lines Coverage Δ
...rtinia/prerequisites/CertiniaPrerequisitesStep.tsx 0.00% <0.00%> (ø)
... and 10 files with indirect coverage changes

@thelullabyy

Copy link
Copy Markdown
Contributor

@codex review

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. Keep it up!

Reviewed commit: 20366e69d1

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

@yuwenmemon

Copy link
Copy Markdown
Contributor

@ShridharGoel you have conflicts

@yuwenmemon
yuwenmemon self-requested a review July 7, 2026 20:10
@thelullabyy

Copy link
Copy Markdown
Contributor

Yeah, code LGTM, I have tested all platforms! Let's fix the conflicts so I can approve @ShridharGoel

@yuwenmemon

Copy link
Copy Markdown
Contributor

@ShridharGoel bump!

@ShridharGoel

Copy link
Copy Markdown
Contributor Author

Done

@yuwenmemon
yuwenmemon merged commit 92303dd into Expensify:main Jul 8, 2026
35 checks passed
@github-actions

github-actions Bot commented Jul 8, 2026

Copy link
Copy Markdown
Contributor

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

@OSBotify

OSBotify commented Jul 8, 2026

Copy link
Copy Markdown
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

OSBotify commented Jul 9, 2026

Copy link
Copy Markdown
Contributor

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

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

@MelvinBot

Copy link
Copy Markdown
Contributor

🤖 Help site review: no changes required.

This PR is a native-only rendering bug fix. It wraps the two Certinia setup step 1 description strings (PSA/SRP and FFA) in a <p> block so react-native-render-html lays out the inline text + install link on Android/iOS. Web already rendered correctly.

Why no docs update is needed:

  • No user-facing content changed — the same descriptions, the same Install PSA/SRP / FFA Expensify Bundle links, and the same versions (1.3 / 1.4) were always intended to display; they were simply not rendering on native.
  • No feature name, tab, label, setting, or setup step was added or renamed.
  • The existing help article Connect-To-Certinia.md already documents the "Install the Expensify bundle in Certinia" step with both the PSA/SRP and FFA installer links, and it remains accurate after this change.

Since the help site already reflects the correct behavior and this PR only restores rendering of existing content, no draft help site PR was created.

@ShridharGoel, please confirm this assessment — if you believe a help site update is warranted, let me know and I'll create a draft PR. (No linked help site PR exists, since none was required.)

@OSBotify

Copy link
Copy Markdown
Contributor

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

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

Bundle Size Analysis (Sentry):

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