Skip to content

[CP Staging] fix: restore Connections tab param scoping and the accounting help link - #105735

Merged
lakchote merged 10 commits into
Expensify:mainfrom
Krishna2323:krishna2323/fix-connections-launch-regressions
Nov 3, 2026
Merged

lakchote merged 10 commits into
Expensify:mainfrom
Krishna2323:krishna2323/fix-connections-launch-regressions

Conversation

@Krishna2323

@Krishna2323 Krishna2323 commented Nov 3, 2026 •

Copy link
Copy Markdown
Contributor

Explanation of Change

Fixes three deploy blockers caused by #105137.

#105713: Begin on "Connect to QuickBooks Online" opens the Workspaces tab (HybridApp)

Cause:

  • The Begin link opens connections?tab=accounting.
  • On focus, the Connections page cleared tab with the global Navigation.setParams, which changes whichever route is focused at that moment.
  • After an app restart, the page mounts while the navigation from Home is still running. The clear hits the wrong route and the app lands on the Workspaces tab.

Fix:

  • Clear tab with the screen's own navigation.setParams, which only changes the Connections route.
  • Do the same for the connect-flow params (newConnectionName and the others an upgrade or setup flow returns with), which had the same global call.
  • The Workflows page had the same bug earlier.

#105722: No tooltip on a cut-off connection status

Cause: the card shows the status message on one line next to the badge and the Fix or Configure button. Long messages like "Cannot sync due to broken connection" get cut off with no way to read them.

Fix:

  • Render the message with TextWithTooltip, which shows the full text on hover only when it's cut off. Native renders plain text, so mobile is unchanged.
  • Pass the title and status message as the card's accessibility label, since the message no longer comes from MenuItem's description.

#105690: Not here after syncing Gusto and pressing Back

Cause:

Fix:

  • The results wait only for a modal opening on top (willAlertModalBecomeVisibleSelector, as MoneyRequestReportTransactionsNavigation does inside an RHP). They now open on top of the panel as soon as the sync finishes.
  • Only a focused screen tracks a sync. A screen covered when the sync finishes leaves the results to the screen on top. Connections no longer opens them a second time.
  • All three panels go back to ROUTES.WORKSPACE_CONNECTIONS explicitly, as they did before Launch unified Connections: remove the beta and the pages it replaced #105137.
  • The Members, Workflows, Rules and Home links open the Connections page on the matching tab instead of a panel. The panels only open from Connections again, so their Back always returns to the page underneath. Before Launch unified Connections: remove the beta and the pages it replaced #105137, those links also opened a full workspace page (the old HR or Accounting page).

Fixed Issues

$ #105713
$ #105722
$ #105690
$ #105786

PROPOSAL: N/A, deploy blocker fix

Tests

Begin link (#105713)

  1. Create a new account. In onboarding, choose "Manage my team's expenses" and pick QuickBooks Online.
  2. On Home, tap Begin on "Connect to QuickBooks Online".
  3. Verify Connections opens with the Accounting tab selected.
  4. Go back to Home. Kill the app and reopen it.
  5. Tap Begin again.
  6. Verify Connections opens again with the Accounting tab selected, not the Workspaces tab.

Status tooltip (#105722)

  1. Go to Workspace settings > Connections and connect Sage Intacct with wrong credentials.
  2. Hover the cut-off "Cannot sync due to broken..." text on the Sage Intacct card.
  3. Verify a tooltip shows the full message.
  4. Widen the window until the message fits. Verify no tooltip shows on hover.
  5. With a screen reader on, focus the Sage Intacct card. Verify it reads the name and the status message.

Gusto sync results (#105690)

  1. Use a workspace connected to Gusto. Go to Connections and click Configure on the Gusto card.
  2. Open the three-dots menu, choose Sync now, and wait for the sync to finish.
  3. Verify the sync results screen opens on top of the Gusto panel.
  4. Press back on the results screen. Verify the Gusto panel shows.
  5. Press the panel's back arrow. Verify Connections shows, with no second results screen and no Not here.
  6. Repeat steps 1-3, then press the browser's back button twice. Verify you end on Connections.
  7. Start a Gusto sync from the panel, then close the panel before it finishes. Wait for the sync to finish. Verify no results screen opens on Connections.

Back from other panels (#105690)

  1. Open a connected accounting integration's panel and press back. Verify Connections shows.
  2. Open the Receipt partners panel and press back. Verify Connections shows.

Links into Connections (#105690)

  1. With Gusto connected, go to Members and click "Configure HR sync". Verify Connections opens on the HR & People tab with the Gusto card at the top.
  2. On a narrow layout, press back. Verify you return to Members.
  3. Go to Workflows and click the link to the HR connection's settings. Verify Connections opens on the HR & People tab.
  4. With an accounting integration connected, go to Rules and open a rule that needs categories or taxes turned on. Choose to manage the settings. Verify Connections opens on the Accounting tab.
  5. On Home, tap Fix on a broken connection. Verify Connections opens on the matching tab with the broken card at the top.
  • Verify that no errors appear in the JS console

Offline tests

  1. Go offline.
  2. Open any connected integration's panel and press back. Verify Connections shows.
  3. Go to Members and click "Configure HR sync". Verify Connections opens on the HR & People tab.

QA Steps

Same as tests. The Begin link test and the Home Fix step only apply to iOS and Android. The tooltip test only applies to web and desktop.

  • 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
    • MacOS: Desktop
  • 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
Begin.link.mp4
iOS: mWeb Safari
MacOS: Chrome / Safari
Gusto_RHP_BUG.mp4
toltip.mp4

Clear the linked tab on the route of the Connections screen itself, so it cannot rewrite another route while Begin is still navigating (Expensify#105713). Bring back the "Chat with your account executive" link that the old Accounting page showed (Expensify#105711).

Signed-off-by: krishna2323 <belivethatkg@gmail.com>
@melvin-bot

melvin-bot Bot commented Nov 3, 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 bun ./scripts/generateTranslations.ts --help

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

@codecov

codecov Bot commented Nov 3, 2026 •

Copy link
Copy Markdown

Codecov Report

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

Files with missing lines Coverage Δ
src/hooks/useMergeSyncResultsPage.ts 97.61% <100.00%> (+0.11%) ⬆️
src/libs/WorkflowUtils.ts 94.45% <ø> (ø)
...orkspace/connections/ConnectionsAccountingPage.tsx 95.91% <100.00%> (+2.04%) ⬆️
...workspace/connections/WorkspaceConnectionsPage.tsx 95.83% <100.00%> (+0.02%) ⬆️
...c/pages/workspace/rules/RulesRequireFieldsPage.tsx 79.00% <100.00%> (ø)
...mponents/Rule/RuleCategoriesDisabledEmptyState.tsx 0.00% <0.00%> (ø)
...rc/components/Rule/RuleTaxesDisabledEmptyState.tsx 0.00% <0.00%> (ø)
src/pages/workspace/WorkspaceMembersPage.tsx 79.14% <0.00%> (ø)
...workspace/connections/ConnectionsMergePageBase.tsx 87.03% <0.00%> (ø)
...ace/connections/ConnectionsReceiptPartnersPage.tsx 84.44% <0.00%> (ø)
... and 2 more
... and 45 files with indirect coverage changes

The badge and button leave little room for the status message on the Connections card, so show it with TextWithTooltip (Expensify#105722).

Signed-off-by: krishna2323 <belivethatkg@gmail.com>
A plain goBack from the Gusto panel after a sync landed on a full-page Not here (Expensify#105690). Go back to the Connections route explicitly, as the HR, Accounting and Receipt partners panels did before the launch.

Signed-off-by: krishna2323 <belivethatkg@gmail.com>
The connect-flow params were cleared with the global setParams, which can change another route while a navigation is still running, the same as the tab param in Expensify#105713. Clear them on the Connections screen route instead.

Signed-off-by: krishna2323 <belivethatkg@gmail.com>
The HR, Recruiting and Accounting panels go back to Connections, which is wrong when Members, Workflows, Rules or Home opened them directly. Point those links at the matching Connections tab, as they led to a full workspace page before the launch.

Signed-off-by: krishna2323 <belivethatkg@gmail.com>
@Krishna2323
Krishna2323 marked this pull request as ready for review November 3, 2026 09:15
@Krishna2323
Krishna2323 requested review from a team as code owners November 3, 2026 09:16
@melvin-bot
melvin-bot Bot requested review from situchan and removed request for a team November 3, 2026 09:16
@melvin-bot

melvin-bot Bot commented Nov 3, 2026

Copy link
Copy Markdown

@situchan 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 dylanexpensify and removed request for a team November 3, 2026 09:16
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Nov 3, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-11-03T10:52:46.825338Z 2835ff8 Manual request
ℹ️ About Codex in GitHub

Your team has set up Codex to 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" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

…help link

Signed-off-by: krishna2323 <belivethatkg@gmail.com>

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 64a6f7f95d

ℹ️ About Codex in GitHub

Your team has set up Codex to 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 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Signed-off-by: krishna2323 <belivethatkg@gmail.com>
@situchan

situchan commented Nov 3, 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 any copy / text that was added to the app 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 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
    • 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
    • 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 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 the PR adds or modifies the UI:
    • I asked an AI agent to review the changes for accessibility issues and addressed its findings.
    • I tested with a screen reader (VoiceOver on macOS) and verified all new/changed elements are reachable with a logical focus order.
    • I verified all new/changed elements have meaningful accessible names and roles.
    • I verified state changes are announced (e.g. checked/unchecked, expanded/collapsed, selected).
  • 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
Android: mWeb Chrome
iOS: HybridApp
iOS: mWeb Safari
MacOS: Chrome / Safari
105713.mov
105713.mp4
105722.mov
105735.mov

@situchan

situchan commented Nov 3, 2026

Copy link
Copy Markdown
Contributor

#105690 was fixed too?

dylanexpensify
dylanexpensify previously approved these changes Nov 3, 2026

@dylanexpensify dylanexpensify 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.

Good from product POV

The results waited for MODAL.isVisible to clear, which never happens while an RHP is open, so they only opened after the panel closed. Wait only for a modal opening on top, and let only a focused screen track a sync so Connections under the panel does not open them again (Expensify#105690).

Signed-off-by: krishna2323 <belivethatkg@gmail.com>
…nfirms it

Signed-off-by: krishna2323 <belivethatkg@gmail.com>
@Krishna2323

Copy link
Copy Markdown
Contributor Author

#105690 was fixed too?

@situchan fixed now.

@Krishna2323

Copy link
Copy Markdown
Contributor Author

@MelvinBot review
@codex review

@MelvinBot

Copy link
Copy Markdown
Contributor

Review

The fixes look correct for the three linked blockers. I found one plausible regression in the sync-results hook and one small accessibility loss. CI is green apart from the approval check.

1. Results can open twice when a sync starts before the panel opens (plausible)

src/hooks/useMergeSyncResultsPage.ts:69-78 only blocks a screen that was covered for the whole sync. Example:

  1. A Gusto sync starts while Connections is focused, for example right after connecting. Connections sets didWatchSyncRunRef to true.
  2. While it runs, you click the card to open the HR panel. The panel's listener also starts watching the sync.
  3. The sync finishes. The panel opens the results now that isVisible no longer holds them back. Connections is not focused, so it skips the result but keeps didWatchSyncRunRef set to true.
  4. You close the results and the panel. Connections gets focus, still sees JOB_DONE with a result, and opens the results again.

Before this PR, step 3 didn't happen because the panel never opened the results. Consider clearing didWatchSyncRunRef when JOB_DONE arrives while the screen is unfocused. Also add a test for a screen that is covered partway through the sync. The current test only covers a screen that is covered for the whole sync.

2. Screen readers no longer read the status message (minor)

ConnectionCard.tsx:98-118 moves the message from description to descriptionAddon. MenuItem builds its default label from title and description (MenuItem.tsx:627). The card now reads only "Sage Intacct" instead of "Sage Intacct, Cannot sync due to broken connection". To fix it, pass accessibilityLabel={[title, status?.message].filter(Boolean).join(', ')}.

3. Nit: The PR description says "Fixes four deploy blockers", but it lists three.

Checked and fine
  • Switch to willAlertModalBecomeVisibleSelector: BaseModal keeps the flag true until the modal starts to hide. Confirm modals and popovers still hold the results back, and an open RHP no longer does.
  • Screen-scoped navigation.setParams: This clears tab and the connect-flow params on the Connections route only, which fixes the HybridApp Begin bug. The tests now mock the screen's setParams.
  • TextWithTooltip layout: On web, BaseTooltip adds no wrapper view, so flex1 keeps working inside MenuItem's row. The style matches MenuItem's own description style.
  • Panel back buttons: Navigation.goBack(ROUTES.WORKSPACE_CONNECTIONS.getRoute(policyID)) is correct now that Members, Workflows, Rules, and Home open Connections on a tab. Only DebugTabView still links to the panels directly, and it is a debug tool.

view run

…card label

A screen covered partway through a sync now lets the screen on top show its results instead of opening them again on refocus. The Connections card label includes the status message again, now that it renders as an addon.

Signed-off-by: krishna2323 <belivethatkg@gmail.com>
@Krishna2323

Copy link
Copy Markdown
Contributor Author

@MelvinBot Thanks, both fixed.

  1. A screen that gets a finished sync while covered now drops its watch, so only the screen on top opens the results. I added a test for a screen covered partway through the sync.
  2. The card passes [title, status?.message] as its accessibility label, the same format MenuItem builds by default.
  3. Updated the description.

@MelvinBot

Copy link
Copy Markdown
Contributor

Thanks. I checked 2869ecaa, and all three points are resolved:

  1. Duplicate results: useMergeSyncResultsPage.ts:81-84 clears the watch when a finished sync arrives while the screen is covered. When Connections gets focus again, it opens nothing. The new test covers this order of events.
  2. Accessibility label: ConnectionCard.tsx:91-92 matches MenuItem's default format. It reads only the title when there is no message.
  3. Description: It now says three deploy blockers.

One trade-off, not a blocker: a screen covered by something other than a sync-results listener now skips the results. For example, Members with a member's details panel open would skip them. That seems fine, because the results belong to whatever is showing when the sync finishes.

Jest and perf tests were still running when I checked.


view run

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. Nice work!

Reviewed commit: 2835ff8b56

ℹ️ About Codex in GitHub

Your team has set up Codex to 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 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

@Krishna2323

Copy link
Copy Markdown
Contributor Author

@situchan any updates on this?

@situchan

situchan commented Nov 3, 2026

Copy link
Copy Markdown
Contributor

How were you able to test #105690? Any test credentials for Gusto?

@Krishna2323

Copy link
Copy Markdown
Contributor Author

How were you able to test #105690? Any test credentials for Gusto?

I created a new account for testing.

@melvin-bot
melvin-bot Bot requested a review from lakchote November 3, 2026 14:32
@lakchote lakchote changed the title fix: restore Connections tab param scoping and the accounting help link [CP Staging] fix: restore Connections tab param scoping and the accounting help link Nov 3, 2026

@lakchote lakchote 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.

Thanks @Krishna2323, looks good. NAB: it looks like if you open another page from the HR panel while a sync runs, the results won't open when you go back, since both covered screens drop them now. Can you check that in a follow-up?

@lakchote
lakchote merged commit ab3ccbd into Expensify:main Nov 3, 2026
39 of 41 checks passed
@github-actions

github-actions Bot commented Nov 3, 2026

Copy link
Copy Markdown
Contributor

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

@OSBotify

OSBotify commented Nov 3, 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.

@github-actions

github-actions Bot commented Nov 3, 2026

Copy link
Copy Markdown
Contributor

OSBotify pushed a commit that referenced this pull request Nov 3, 2026
…ns-launch-regressions

[CP Staging] fix: restore Connections tab param scoping and the accounting help link

(cherry picked from commit ab3ccbd)

(cherry-picked to staging by lakchote)
@OSBotify OSBotify added the CP Staging marks PRs that have been CP'd to staging label Nov 3, 2026
@OSBotify OSBotify mentioned this pull request Nov 3, 2026
75 tasks done
@OSBotify

OSBotify commented Nov 3, 2026

Copy link
Copy Markdown
Contributor

🚀 Cherry-picked to staging by https://github.com/lakchote in version: 9.5.28-6 🚀

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

@MelvinBot

Copy link
Copy Markdown
Contributor

No help site update needed: this PR fixes three deploy-blocker bugs (wrong landing tab, a missing tooltip on cut-off status text, and Back buttons that led to Not here), and no existing article sentence becomes incorrect.


view run

@OSBotify

OSBotify commented Nov 3, 2026

Copy link
Copy Markdown
Contributor

🚀 Cherry-picked to staging by https://github.com/lakchote in version: 9.5.30-0 🚀

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

@OSBotify

OSBotify commented Nov 3, 2026

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/blimpich in version: 9.5.30-0 🚀

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

CP Staging marks PRs that have been CP'd to staging

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants