[Due for payment 2026-07-17] [$250] Certinia Setup - Missing PSA/SRP bundle installation link and version

[applause-bot]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Version Number: 9.4.20-0
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #94414
Email or phone of affected tester (no customers): applausetester+thowner@applause.expensifail.com
Issue reported by: Applause Internal Team
Bug source: Pull Request QA execution
Device used: Samsung a31
App Component: Other

Action Performed:

1. Open Expensify app
2. Go to Workspace settings
3. Navigate to Accounting
4. Start a new Certinia connection
5. Observe setup step 1 screen

Expected Result:

Setup step 1 should display the full PSA/SRP bundle installation instructions including:
Install PSA/SRP Expensify Bundle link
Version 1.3
Complete descriptive text

Actual Result:

On Android, setup step 1 only displays the section title “For PSA/SRP connection”.
The installation link and version information (1.3) are missing.
Web version correctly displays the full instructions including the bundle link and version.

Workaround:

Unknown

Platforms:

• Android: App
• Android: mWeb Chrome
• iOS: App
• iOS: mWeb Safari
• iOS: mWeb Chrome
• Windows: Chrome
• MacOS: Chrome Safari

Screenshots/Videos

Bug7191973_1782479538390.WhatsApp_Video_2026-06-26_at_9.07.23_AM.1.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Julia Ponikarchuk
Bug ID: 7191973

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~022070529995910133940
• Upwork Job ID: 2070529995910133940
• Last Price Increase: 2026-06-26

Issue Owner

Current Issue Owner: @thelullabyy

[applause-bot]

While Applause doesn't embed attachments for this bug, here are the links for quick view:
https://platform.applause.com/services/links/v1/external/4512cfbfe1cb70b4d56817fdcfe4f510ad7a7a159ce060adfe56c5ee6eba46a4

[aswin-s]

Proposal

Please re-state the problem that we are trying to solve in this issue.

When a user navigates to the Certinia setup prerequisites screen on Android or iOS, the PSA/SRP bundle section only shows the header "For PSA/SRP Connections:" but the installation link ("Install PSA/SRP Expensify Bundle (Version 1.3)") and its descriptive text are absent. The web version renders both sections correctly. The expected behavior is that both the PSA/SRP and FFA bundle sections display their full description and clickable installation link on all platforms.

What is the root cause of that problem?

In CertiniaPrerequisitesStep.tsx (lines 38–43), the PSA description is rendered via RenderHTML with an HTML string containing an <a href> anchor tag. On Android and iOS native, RenderHTML renders raw HTML into a native view, but anchor tags (<a>) are not natively interactive and may silently produce no output when the HTML parser encounters an unsupported or empty-rendering node — causing the entire description block to appear blank. The FFA section (lines 46–52) uses the same pattern but predates PR #94414, so any pre-existing workaround or rendering quirk was already established; the PSA section is newly introduced by #94414 and exposes this gap on native platforms.

What changes do you think we should make in order to solve the problem?

1. In src/pages/workspace/accounting/certinia/prerequisites/CertiniaPrerequisitesStep.tsx (lines 38–43), replace the RenderHTML block for installBundlePSADescription with a Text component containing a TextLink (or PressableWithoutFeedback + Linking.openURL) for the bundle URL, matching the pattern used by other setup steps that need a tappable link on native.
2. In the same file (lines 47–52), apply the same replacement to the FFA RenderHTML block for consistency and to prevent the same issue from manifesting there if RenderHTML behavior changes.
3. Update src/languages/en.ts, de.ts, es.ts, fr.ts (and any other locale files) installBundlePSADescription and installBundleFFADescription keys to return plain text + a separate href value rather than an HTML string, since the rendering component no longer uses HTML.
4. In src/CONST/index.ts (line 2862–2864), add the missing SANDBOX key to CERTINIA_FFA_BUNDLE_INSTALL_URL to match the structure of CERTINIA_PSA_BUNDLE_INSTALL_URL and avoid a potential undefined URL if sandbox mode is ever used for FFA.

What alternative solutions did you explore? (Optional)

Keep RenderHTML but wrap it in a platform check (Platform.OS === 'web') and fall back to a native-compatible link component on Android/iOS — this avoids touching the translation strings but adds platform branching that is harder to maintain.

[MobileMage]

Proposal

Please re-state the problem that we are trying to solve in this issue.

On the Certinia connection setup, step 1 ("Install the Expensify bundle") should render a "For PSA/SRP Connections:" header followed by descriptive text and an "Install PSA/SRP Expensify Bundle (Version 1.3)" link, plus the equivalent FFA block. On native (Android + iOS App) only the bold section headers render; the descriptive text, the link, and the version are all missing. Web/mWeb render everything correctly. This is a native-only rendering divergence in the bundle-install step.

What is the root cause of that problem?

The step renders two pieces per section: a <Text> header and a RenderHTML block that contains the description plus the anchor. The headers are plain <Text>, so they always show. The missing content all lives inside the RenderHTML calls:

App/src/pages/workspace/accounting/certinia/prerequisites/CertiniaPrerequisitesStep.tsx

Lines 37 to 43 in 873a5a0

	<Text style={[styles.textStrong, styles.mb2]}>{translate('workspace.certinia.prerequisites.installBundlePSAHeader')}</Text>
	<RenderHTML
	html={translate('workspace.certinia.prerequisites.installBundlePSADescription', {
	href: CONST.CERTINIA_PSA_BUNDLE_INSTALL_URL.PRODUCTION,
	version: CONST.CERTINIA_PSA_BUNDLE_VERSION,
	})}
	/>

The translation passed to RenderHTML is bare, phrasing-level HTML — raw text followed by an inline <a>, with no block-level wrapper:

`Install the Expensify bundle in Salesforce by clicking this link: <a href="${href}">Install PSA/SRP Expensify Bundle (Version ${version})</a>`

App/src/languages/en.ts

Lines 5141 to 5142 in 873a5a0

	installBundlePSADescription: ({href, version}: {href: string; version: string}) =>
	`Install the Expensify bundle in Salesforce by clicking this link: <a href="${href}">Install PSA/SRP Expensify Bundle (Version ${version})</a>`,

The HTML string itself is fine — running it through the RenderHTML pipeline (Parser.replace + the bracket/emoji/br cleanups) leaves the <a> intact byte-for-byte, and CERTINIA_PSA_BUNDLE_INSTALL_URL/CERTINIA_PSA_BUNDLE_VERSION are populated. The problem is the shape of the content. On native, RenderHTML mounts a RenderHTMLSource whose content model is resolved by react-native-render-html's TRenderEngine. When the root source is pure phrasing content (text + an inline anchor) with no enclosing block element, the native engine collapses it to an empty/zero-height render, so nothing shows beneath the header. On web the DOM renderer lays the inline run out regardless, which is exactly why web is unaffected while Android and iOS App both break.

Every other native RenderHTML instruction in this part of the app proves the convention: they always wrap the content in a block-level custom tag (and/or a styles.renderHTML parent view). QBD's setup error is <muted-text><centered-text>...<a>reach out to Concierge</a>...</centered-text></muted-text>, and the NetSuite token setup step wraps its description as <comment><muted-text>${Parser.replace(...)}</muted-text></comment>. The Certinia bundle strings are the only ones that hand RenderHTML a bare inline run with no block container, which is why they alone fail on native.

What changes do you think we should make in order to solve the problem?

Give the RenderHTML content a block-level root so the native engine renders it, matching the existing convention used by QBD and NetSuite. The cleanest fix is to wrap the two bundle description strings in a block custom tag in the language files — e.g. <muted-text> (which is already registered as a block element model in BaseHTMLEngineProvider) — so the inline text and anchor live inside a block node:

installBundlePSADescription: ({href, version}: {href: string; version: string}) =>
    `<muted-text>Install the Expensify bundle in Salesforce by clicking this link: <a href="${href}">Install PSA/SRP Expensify Bundle (Version ${version})</a></muted-text>`,

Apply the same wrap to installBundleFFADescription. This is safe because muted-text is an existing block content-model tag handled identically on web and native, so it fixes native without changing web output beyond the muted styling already used for instructional copy. Alternatively, wrapping the <RenderHTML> in a <View style={styles.renderHTML}> in CertiniaPrerequisitesStep.tsx (as QBD does) also gives the engine a sized block parent; doing both the tag wrap and the view wrap is the most robust. Since these strings are only consumed by this one step, the change has no other callers to regress.

What alternative solutions did you explore? (Optional)

Replacing RenderHTML with a Text + TextLink composition would avoid the HTML engine entirely, but it duplicates link/version logic the translations already encode and diverges from how the rest of the accounting setup pages render instructional links, so wrapping the existing HTML in a block tag is the smaller, convention-aligned fix.

[lorretheboy]

Proposal

What is the root cause of that problem?

The Certinia bundle description strings produce HTML whose root content is bare inline/phrasing content — plain text followed immediately by an inline <a>, with no block-level wrapper:

App/src/languages/en.ts

Lines 5141 to 5145 in 873a5a0

	installBundlePSADescription: ({href, version}: {href: string; version: string}) =>
	`Install the Expensify bundle in Salesforce by clicking this link: <a href="${href}">Install PSA/SRP Expensify Bundle (Version ${version})</a>`,
	installBundleFFAHeader: 'For FFA Connections:',
	installBundleFFADescription: ({href, version}: {href: string; version: string}) =>
	`Install the Expensify bundle in Salesforce by clicking this link: <a href="${href}">Install FFA Expensify Bundle (Version ${version})</a>`,

That string is fed straight into RenderHTML for each section:

App/src/pages/workspace/accounting/certinia/prerequisites/CertiniaPrerequisitesStep.tsx

Lines 36 to 53 in 873a5a0

	<View>
	<Text style={[styles.textStrong, styles.mb2]}>{translate('workspace.certinia.prerequisites.installBundlePSAHeader')}</Text>
	<RenderHTML
	html={translate('workspace.certinia.prerequisites.installBundlePSADescription', {
	href: CONST.CERTINIA_PSA_BUNDLE_INSTALL_URL.PRODUCTION,
	version: CONST.CERTINIA_PSA_BUNDLE_VERSION,
	})}
	/>
	</View>
	<View style={styles.mt5}>
	<Text style={[styles.textStrong, styles.mb2]}>{translate('workspace.certinia.prerequisites.installBundleFFAHeader')}</Text>
	<RenderHTML
	html={translate('workspace.certinia.prerequisites.installBundleFFADescription', {
	href: CONST.CERTINIA_FFA_BUNDLE_INSTALL_URL.PRODUCTION,
	version: CONST.CERTINIA_FFA_BUNDLE_VERSION,
	})}
	/>
	</View>

react-native-render-html on native does not render a source document whose top level is only phrasing content; with no block element at the root it produces no output, so on Android/iOS each RenderHTML block comes out empty and only the plain <Text> section headers remain. react-native-web tolerates the inline-only root and lays it out, which is why the link and version 1.3 appear correctly on web.

Every other place in the app that renders a link through RenderHTML wraps the content in a block-level tag, which is why those render on native — e.g. QBD wraps the anchor in <muted-text><centered-text>:

App/src/languages/en.ts

Lines 4767 to 4768 in 873a5a0

	setupErrorBody: (conciergeLink: string) =>
	`<muted-text><centered-text>The QuickBooks Desktop connection isn't working at the moment. Please try again later or <a href="${conciergeLink}">reach out to Concierge</a> if the problem persists.</centered-text></muted-text>`,

and the NetSuite token step wraps its description in <comment><muted-text>:

App/src/pages/workspace/accounting/netsuite/NetSuiteTokenInput/subPages/NetSuiteTokenSetupContent.tsx

Line 28 in 873a5a0

<RenderHTML html={`<comment><muted-text>${Parser.replace(translate(description))}</muted-text></comment>`} />

The Certinia strings are the only ones missing that wrapper.

What changes do you think we should make in order to solve the problem?

Give the rendered HTML a block-level root. The smallest change is to wrap each description in a block tag (e.g. <muted-text>) at the call site, so the fix applies to all languages at once:

App/src/pages/workspace/accounting/certinia/prerequisites/CertiniaPrerequisitesStep.tsx

Lines 38 to 43 in 873a5a0

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

i.e. pass html={${translate('workspace.certinia.prerequisites.installBundlePSADescription', {...})}} for the PSA block and the same for the FFA block. The native renderer then has a block root and shows the link and version; web is unaffected.

What alternative solutions did you explore? (Optional)

Add the wrapping block tag inside the translation strings themselves (installBundlePSADescription / installBundleFFADescription) across all src/languages/* files, matching the QBD setupErrorBody pattern. Same result, but touches every language file instead of one component.

Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job.

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @daledah (External)

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~022070529995910133940