You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Due for payment 2026-07-01] [$75] Android & iOS - Agents - "Create agents to handle your workflow.." sentence is missing #93638
Version Number: 9.4.8-0 Reproducible in staging?: Yes Reproducible in production?: No If this was caught during regression testing, add the test name, ID and link from BrowserStack:#93446 Email or phone of affected tester (no customers):jsodinjosdjsoinjsiojs@gmail.com Issue reported by: Applause Internal Team Bug source: Exploratory - Significant User Experience Deterioration Device used: iPhone 15 Pro Max / iOS 26.5 App Component: User Settings
Action Performed:
Launch Expensify app.
Go to Account > Agents.
Create an agent.
Expected Result:
"Create agents to handle your workflow.." sentence will appear above the agent list.
Actual Result:
"Create agents to handle your workflow.." sentence is missing.
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:
Identify the pull request that introduced this issue and revert it.
Root cause:PR #92326 ("Link to the Custom Agents help article from the Agents page") changed the Agents page subtitle from a plain <Text> into an HTML string rendered via <RenderHTML>, and that HTML output does not render on native (iOS/Android app). This PR is in staging but not production, which is why the bug reproduces on staging only.
Not the linked PR #93446 — that PR only touched the Edit/Add agent form pages (EditPromptPage, AddAgentRulePage, EditAgentRulePage), not the Agents list page. The deploy-blocker auto-assignment is based on "recently merged a PR," not on root cause.
Recommended action (deploy blocker):
Fastest unblock: revert PR #92326. It changed two working plain-text subtitles into RenderHTML that breaks on native.
Proper fix (if keeping the "Learn more" link): make the subtitle render on native. The call site at AgentsPage.tsx:148 calls <RenderHTML html={...} />without an onLinkPress prop. Per RenderHTML.tsx:78-88, when onLinkPress is omitted it renders a bare RenderHTMLSource (no local config provider). Passing onLinkPress (and verifying on a native build) is the likely fix and matches how RenderHTML is used elsewhere for linked content.
Evidence
Production vs. staging diff (via gh api .../contents/...?ref=production):
agentsPage.subtitle string
render
production (works)
Create agents to handle your workflow. Skip the manual work and get hours back in your day.
Why the whole sentence vanishes (not just the link): the subtitle <View> and the <FlatList> are siblings under the same hasAgents conditional, so the list rendering while the text is absent rules out a data/empty-state issue — it's a native RenderHTML rendering failure for this string. The HTML uses the custom <muted-text> block element (defined in BaseHTMLEngineProvider.tsx); without the local RenderHTMLConfigProvider (only mounted when onLinkPress is passed) the native output is empty.
Confidence: High on the cause (PR #92326, staging-only, Text → RenderHTML). Medium on the exact native mechanism / sufficiency of the onLinkPress fix — I confirmed via the prod-vs-staging code diff but did not reproduce on a native build. A native repro (or testing the page with onLinkPress wired up) would confirm the fix.
Next Steps: Reply with @MelvinBot implement this to create a draft PR with the fix (or a revert of #92326), or @MelvinBot <feedback> to refine this analysis.
[Contributor] The offending PR and associated issue have been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
Link to the comment on the PR: NA
Link to the comment on the Issue
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.
Link to discussion: NA
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
Test:
Launch Expensify app.
Go to Account > Agents.
Create an agent.
Verify "Agents handle your workflows for you, so you get hours back in your day. Learn more." sentence will appear above the agent list.
Activity
applause-bot commentedon Jun 15, 2026
While Applause doesn't embed attachments for this bug, here are the links for quick view:
https://platform.applause.com/services/links/v1/external/d6129b081f06e43a919d0f10f41e939015dea687ff469e59c978512444d35a0e
https://platform.applause.com/services/links/v1/external/7bfc405fc57fba1398669e6954dafe930444dbf59e89ed60e6b4184e83643dc8
melvin-bot commentedon Jun 15, 2026
You have been assigned to this deploy blocker because you recently merged this PR: #93446
melvin-bot commentedon Jun 15, 2026
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Jun 15, 2026
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:
NicolasBonet commentedon Jun 15, 2026
@MelvinBot investigate, demoting this from been a blocker
MelvinBot commentedon Jun 15, 2026
Issue Analysis
Root cause: PR #92326 ("Link to the Custom Agents help article from the Agents page") changed the Agents page subtitle from a plain
<Text>into an HTML string rendered via<RenderHTML>, and that HTML output does not render on native (iOS/Android app). This PR is in staging but not production, which is why the bug reproduces on staging only.Not the linked PR #93446 — that PR only touched the Edit/Add agent form pages (
EditPromptPage,AddAgentRulePage,EditAgentRulePage), not the Agents list page. The deploy-blocker auto-assignment is based on "recently merged a PR," not on root cause.Recommended action (deploy blocker):
RenderHTMLthat breaks on native.AgentsPage.tsx:148calls<RenderHTML html={...} />without anonLinkPressprop. PerRenderHTML.tsx:78-88, whenonLinkPressis omitted it renders a bareRenderHTMLSource(no local config provider). PassingonLinkPress(and verifying on a native build) is the likely fix and matches howRenderHTMLis used elsewhere for linked content.Evidence
Production vs. staging diff (via
gh api .../contents/...?ref=production):agentsPage.subtitlestringCreate agents to handle your workflow. Skip the manual work and get hours back in your day.<Text style={[styles.textSupporting,…]}>{translate('agentsPage.subtitle')}</Text><muted-text>Create agents…day. <a href="${CUSTOM_AGENTS_HELP_URL}">Learn more</a>.</muted-text><View style={[styles.renderHTML,…]}><RenderHTML html={translate('agentsPage.subtitle')} /></View>en.ts:2896AgentsPage.tsx:145-149AgentsPage.tsxstill shows the old<Text>version, confirming it has not yet shipped to production.Why the whole sentence vanishes (not just the link): the subtitle
<View>and the<FlatList>are siblings under the samehasAgentsconditional, so the list rendering while the text is absent rules out a data/empty-state issue — it's a nativeRenderHTMLrendering failure for this string. The HTML uses the custom<muted-text>block element (defined inBaseHTMLEngineProvider.tsx); without the localRenderHTMLConfigProvider(only mounted whenonLinkPressis passed) the native output is empty.Confidence: High on the cause (PR #92326, staging-only,
Text→RenderHTML). Medium on the exact native mechanism / sufficiency of theonLinkPressfix — I confirmed via the prod-vs-staging code diff but did not reproduce on a native build. A native repro (or testing the page withonLinkPresswired up) would confirm the fix.Next Steps: Reply with
@MelvinBot implement thisto create a draft PR with the fix (or a revert of #92326), or@MelvinBot <feedback>to refine this analysis.69 remaining items
thelullabyy commentedon Jun 24, 2026
BugZero Checklist:
[Contributor] The offending PR and associated issue have been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
Link to the comment on the PR: NA
Link to the comment on the Issue
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.
Link to discussion: NA
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
Test:
Do we agree 👍 or 👎
Zapier Logs
Run ID: 00040eee-23c3-a6c6-0aa5-155ecfe8a8b4melvin-bot commentedon Jun 30, 2026
Triggered auto assignment to @mallenexpensify (
Awaiting Payment)mallenexpensify commentedon Jul 2, 2026
Payment Summary
Contributor: @lorretheboy paid $75 via Upwork
Contributor+: @thelullabyy paid $75 via Upwork.
@lorretheboy can you please accept the job below? Please reply here and tag me once you have.
https://www.upwork.com/jobs/~022066661999298746571
lorretheboy commentedon Jul 2, 2026
@mallenexpensify I accepted the job. Thx
thelullabyy commentedon Jul 2, 2026
@mallenexpensify I think you mentioned wrong person btw, I am due for payment here instead of @DylanDylann
mallenexpensify commentedon Jul 3, 2026
@lorretheboy paid, summary updated above. Thx. Same with @thelullabyy