Skip to content

migrate money request part 2 - #95930

Merged
mjasikowski merged 15 commits into
Expensify:mainfrom
huult:83858-migrate-money-request-part-2-v6
Jul 24, 2026
Merged

mjasikowski merged 15 commits into
Expensify:mainfrom
huult:83858-migrate-money-request-part-2-v6

Conversation

@huult

@huult huult commented Jul 13, 2026

Copy link
Copy Markdown
Contributor

Explanation of Change

Fixed Issues

$ #83858
PROPOSAL:

Tests

Same QA step

  • Verify that no errors appear in the JS console

Offline tests

QA Steps

Pre-requisites

  • A paid/Collect workspace with Tax enabled (≥2 tax rates) and Categories enabled (≥2 categories).
  • A second account on a free plan (no paid workspace) to trigger the Upgrade flow.

MONEY_REQUEST_STEP_TAX_RATE

  1. Open the Expensify app.
  2. Open any workspace chat.
  3. Start the Create Expense flow.
  4. On the confirmation step, tap Tax rate.
  5. Navigate back.
  6. Verify that the Tax rate page step and returns to the confirmation step correctly.

MONEY_REQUEST_STEP_TAX_AMOUNT

  1. Open the Expensify app.
  2. Open any workspace chat.
  3. Start the Create Expense flow.
  4. On the confirmation step, tap Tax amount.
  5. Navigate back.
  6. Verify that the Tax amount step opens and returns to the confirmation step correctly.

MONEY_REQUEST_ATTENDEE

Precondition:

  • In the workspace settings, enable Rules and turn on Attendee Tracking
  1. Open the Expensify app.
  2. Open any workspace chat.
  3. Start the Create Expense flow.
  4. On the confirmation step, tap Attendee.
  5. Navigate back.
  6. Verify that the Attendee step opens and returns to the confirmation step correctly.
  • 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 verified there are no new alerts related to the canBeMissing param for useOnyx
  • I followed proper code patterns (see Reviewing the code)
    • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
    • I verified that comments were added to code that is not self explanatory
    • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
    • I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
      • If any non-english text was added/modified, I used JaimeGPT to get English > Spanish translation. I then posted it in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
    • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
    • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
    • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
    • I verified the JSDocs style guidelines (in STYLE.md) were followed
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • I followed the guidelines as stated in the Review Guidelines
  • I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
  • I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
  • I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
  • I verified that if a function's arguments changed that all usages have also been updated correctly
  • If any new file was added I verified that:
    • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
  • If a new CSS style is added I verified that:
    • A similar style doesn't already exist
    • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))
  • If new assets were added or existing ones were modified, I verified that:
    • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
    • The assets load correctly across all supported platforms.
  • If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
  • If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
  • If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
  • If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
  • If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
    • I verified that all the inputs inside a form are aligned with each other.
    • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
  • If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
  • I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
  • If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native
Android: mWeb Chrome
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari
Screen.Recording.2026-07-13.at.16.32.38.mov

@huult
huult requested review from a team as code owners July 13, 2026 09:33
@melvin-bot
melvin-bot Bot requested review from joekaufmanexpensify and suneox and removed request for a team July 13, 2026 09:33
@melvin-bot

melvin-bot Bot commented Jul 13, 2026

Copy link
Copy Markdown

@suneox 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 removed the request for review from a team July 13, 2026 09:33
@codecov

codecov Bot commented Jul 13, 2026 •

Copy link
Copy Markdown

@joekaufmanexpensify

Copy link
Copy Markdown
Contributor

No product review needed.

@joekaufmanexpensify
joekaufmanexpensify removed their request for review July 13, 2026 21:33
@suneox

suneox commented Jul 17, 2026

Copy link
Copy Markdown
Contributor

Manual test cases based on current code change & previous PR regression


DYNAMIC_ROUTES.MONEY_REQUEST_STEP_TAX_RATE — select tax rate on confirmation / edit expense

Case TR-01 — Confirmation → Tax rate → back

Target: TaxFields.tsx:142

Precondition: Paid workspace with Tax enabled (≥2 rates); on a workspace chat.

Steps:

  1. Sign in with a paid workspace + Tax enabled account.
  2. Open a workspace chat.
  3. Tap + → Create expense → Manual.
  4. Enter an amount (e.g. $100) → tap Next (confirmation).
  5. Verify the Tax rate row is visible.
  6. Tap Tax rate → verify the TaxPicker opens (no "Hmm... it's not here").
  7. Select a different rate → tap Back.
  8. Verify it returns to confirmation with the updated tax rate.

Expected: URL is <confirmationPath>/taxRate?action=…&iouType=…&transactionID=…&reportID=…; Back strips the suffix + query correctly.


Case TR-02 — Expense RHP → edit Tax rate (RHP must stay open)

Target: MoneyRequestView.tsx:1414

Precondition: Expense report with an editable taxed manual expense.

Steps:

  1. Sign in → Reports → open an expense report with a taxed expense.
  2. Tap the expense → open expense detail in RHP.
  3. Tap the Tax rate row.
  4. Verify the TaxPicker opens in the RHP.
  5. Change the rate → save/back.
  6. Verify the RHP stays open and the tax row updates.

Expected: Back returns to the expense detail in the RHP (panel does not close).


Case TR-03 — Refresh / deep-link with taxRate suffix → restore stack

Steps:

  1. Do TR-02 up to the TaxPicker open in the RHP (URL has /taxRate?...).
  2. Refresh the page (F5 on web).
  3. Verify: the TaxPicker RHP re-mounts, the background blur persists, and the full-screen report underneath restores correctly.
  4. Tap Back → verify it returns to the expense detail (no NotFound, not Home).

Case TR-DB-93255 — ⚠️ REGRESSION: Tax rate must not show "not here" from any origin

Precondition: betas: ["newManualExpenseFlow"], policy Tax enabled.

Steps:

  1. Path A — Confirmation (create) → tap Tax rate → verify no NotFound.
  2. Path B — Expense report RHP → tap Tax rate → verify no NotFound.
  3. Path C — Central report view (open transaction inline) → Tax rate → verify no NotFound.
  4. Refresh the URL with the suffix on each path → verify correct restore.

Expected: all three origins mount DynamicIOURequestStepTaxRatePage, no NotFound fallback.


DYNAMIC_ROUTES.MONEY_REQUEST_STEP_TAX_AMOUNT — enter tax amount

Case TA-01 — Confirmation → Tax amount (menu path, beta OFF)

Target: TaxFields.tsx:181

Precondition: betas: [] (beta OFF so the MenuItem path runs, not the inline form), policy Tax enabled.

Steps:

  1. Sign in → workspace chat → create a manual expense → reach confirmation.
  2. Verify Tax amount is a MenuItem (not an inline input).
  3. Tap Tax amount → enter a valid amount → save.
  4. Verify it returns to confirmation with the updated amount.

Expected: page mounts via the taxAmount?... suffix; after save it always navigateBack() to confirmation (the page is now always treated as editing).


Case TA-02 — Expense RHP → edit Tax amount

Target: MoneyRequestView.tsx:1446

Steps:

  1. Open an expense in the report RHP (tax enabled, editable).
  2. Tap Tax amount → change the value → save.
  3. Verify the RHP stays open and the row updates.

Case TA-DB-93236 — ⚠️ REGRESSION: over-limit tax amount must show error

Precondition: betas: [], policy Tax enabled.

Steps:

  1. Path A — Confirmation → Tax amount → enter an amount above the max (per rate) → save.
  2. Verify the invalidTaxAmount error is shown and it is not saved.
  3. Path B (beta ON) — enter an over-limit value on the inline field → submit the expense → verify a brick-road error and the expense is blocked.

Case TA-04 — Refresh with taxAmount suffix → restore

Steps:

  1. Do TA-02 until the tax amount page is open in the RHP (URL has /taxAmount?...).
  2. Refresh → verify the page restores, the blur persists, and Back returns to the expense detail.

DYNAMIC_ROUTES.MONEY_REQUEST_ATTENDEE — select attendees (route from the reverted blockers — test hardest)

Case ATT-01 — Confirmation → Attendees → back

Target: AttendeeField.tsx:79

Precondition: Control workspace with Attendee tracking ON; ≥1 other member to add.

Steps:

  1. Sign in to a Control workspace, attendee tracking ON.
  2. Workspace chat → create an expense → reach confirmation → verify the Attendees row is visible.
  3. Tap Attendees → add an attendee → Save → verify it returns to confirmation.

Case ATT-02 — Expense RHP → edit Attendees

Target: MoneyRequestView.tsx:1487

Steps:

  1. Expense report RHP → an expense with attendees → tap Attendees → modify → Save.
  2. Verify the RHP stays open and the attendee list updates.

Case ATT-DB-94554 — 🔴 REGRESSION (IN SCOPE): refresh Attendees RHP → background blur must persist

This is deploy blocker #94554 that caused the revert of the original PR. Attendee is still in this PR, so this must be verified as fixed.

Target: MoneyRequestView.tsx:1487 + getMatchingFullScreenRoute.

Precondition: Expense report with an editable expense that has attendees; test on Web/Chrome (to refresh).

Steps:

  1. Sign in → Reports → open an expense report with an expense.
  2. Tap the expense → tap Attendees → verify the Attendees RHP opens (with a background blur dimming the report behind it).
  3. Copy the URL (has /attendees?...) — Refresh (F5).
  4. After refresh, verify:
    • The Attendees RHP re-mounts.
    • The background blur still persists (the report behind is dimmed, not blank / not un-blurred).
    • The full-screen report underneath restores correctly.
  5. Tap Back → verify it returns to the expense detail (no NotFound, not Home / report list).

Expected (PASS): blur persists + full stack restores.
⚠️ If the blur disappears / the background turns blank after refresh → this reproduces #94554 → not mergeable (capture a screenshot as evidence).


Case ATT-DB-93253 — ⚠️ REGRESSION: saving attendees with no changes must NOT close the RHP

Steps:

  1. Open an expense in the Report RHP (confirm the RHP is open).
  2. Tap Attendees → do not change anything → tap Save immediately.
  3. PASS: back to the expense detail in the RHP, panel does not close.
  4. FAIL: the RHP closes / navigates to the report list.
  5. Repeat: open attendees → wait 2s → Save (tests the stale backPath ref).

Expected: the panel stays, and the back path is computed correctly even with no changes.

@suneox

suneox commented Jul 18, 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 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
    • 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 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
Android: mWeb Chrome
iOS: HybridApp
iOS: mWeb Safari
MacOS: Chrome / Safari
CleanShot.2026-07-18.at.18.35.14.1.mp4
CleanShot.2026-07-18.at.18.29.54.1.mp4
CleanShot.2026-07-18.at.18.27.15.1.mp4

DYNAMIC_ROUTES.MONEY_REQUEST_STEP_TAX_RATE — select tax rate on confirmation / edit expense

Case TR-01 — Confirmation → Tax rate → back TR-01-1-before-confirmation-tax-row TR-01-2-entry-tax-rate-dynamic-page TR-01-3-after-back-confirmation
Case TR-02 — Expense RHP → edit Tax rate (RHP must stay open) TR-02-1-before-expense-detail-tax-row TR-02-2-entry-tax-rate-dynamic-page TR-02-3-after-back-expense-detail
Case TR-03 — Refresh / deep-link with taxRate suffix → restore stack TR-03-1-before-tax-rate-open-prerefresh TR-03-2-entry-tax-rate-restored-postrefresh TR-03-3-after-back-expense-detail
Case TR-DB-93255 — ⚠️ REGRESSION: Tax rate must not show "not here" from any origin TR-DB-93255-1-before-rhp-origin-taxrate-renders TR-DB-93255-2-entry-confirmation-origin-taxrate-renders

DYNAMIC_ROUTES.MONEY_REQUEST_STEP_TAX_AMOUNT — enter tax amount

Case TA-01 — Confirmation → Tax amount (menu path, beta OFF) TA-01-1-before-confirmation-tax-amount-row TA-01-2-entry-tax-amount-dynamic-page TA-01-3-after-back-confirmation
Case TA-02 — Expense RHP → edit Tax amount TA-02-1-before-expense-detail-tax-amount-row TA-02-2-entry-tax-amount-dynamic-page TA-02-3-after-back-expense-detail
Case TA-DB-93236 — ⚠️ REGRESSION: over-limit tax amount must show error TA-DB-93236-1-before-expense-detail-tax-amount TA-DB-93236-2-entry-tax-amount-overlimit
Case TA-04 — Refresh with taxAmount suffix → restore TA-04-1-before-tax-amount-open-prerefresh TA-04-2-entry-tax-amount-restored-postrefresh TA-04-3-after-back-expense-detail

DYNAMIC_ROUTES.MONEY_REQUEST_ATTENDEE — select attendees (route from the reverted blockers — test hardest)

Case ATT-01 — Confirmation → Attendees → back ATT-01-1-before-confirmation-screen ATT-01-2-entry-confirmation-attendees-route
Case ATT-02 — Expense RHP → edit Attendees ATT-02-1-before-expense-detail-attendees-row ATT-02-2-entry-attendees-dynamic-page ATT-02-3-after-back-back-destination
Case ATT-DB-94554 — 🔴 REGRESSION (IN SCOPE): refresh Attendees RHP → background blur must persist

This is deploy blocker #94554 that caused the revert of the original PR. Attendee is still in this PR, so this must be verified as fixed.

ATT-DB-94554-1-before-attendees-open-prerefresh ATT-DB-94554-2-entry-attendees-restored-postrefresh
Case ATT-DB-93253 — ⚠️ REGRESSION: saving attendees with no changes must NOT close the RHP ATT-DB-93253-1-before-attendees-page-nochange ATT-DB-93253-2-after-save-save-destination

@suneox

suneox commented Jul 18, 2026

Copy link
Copy Markdown
Contributor

@huult We should support sharing routes for both MONEY_REQUEST_STEP_TAX_RATE and MONEY_REQUEST_STEP_TAX_AMOUNT.

CleanShot.2026-07-18.at.18.54.24.1.mp4

@huult

huult commented Jul 20, 2026

Copy link
Copy Markdown
Contributor Author

@suneox it's done

@suneox

suneox commented Jul 23, 2026

Copy link
Copy Markdown
Contributor

Confirmed, the remaining issue has been fixed

Share on native platform
CleanShot.2026-07-23.at.14.02.01.1.mp4

@melvin-bot
melvin-bot Bot requested a review from mjasikowski July 23, 2026 07:08

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

@huult This PR is missing compatibility configuration for OldRoutes.ts

CleanShot.2026-07-23.at.14.10.20.1.mp4
Suggestion fix
  // Money request tax/attendees routes migrated to dynamic routes (PR #95930)
  // Old flat path: /<action>/<iouType>/taxRate/<transactionID>/<reportID>
  // New dynamic: /r/<reportID>/taxRate?action=...&iouType=...&transactionID=...&reportID=...
  '/*/*/taxRate/*/*': '/r/$4/taxRate?action=$1&iouType=$2&transactionID=$3&reportID=$4',
  '/*/*/taxAmount/*/*': '/r/$4/taxAmount?action=$1&iouType=$2&transactionID=$3&reportID=$4',
  '/*/*/attendees/*/*': '/r/$4/attendees?action=$1&iouType=$2&transactionID=$3&reportID=$4',

@huult

huult commented Jul 23, 2026

Copy link
Copy Markdown
Contributor Author

Thanks! I'll update it once I finish migrating the transaction duplicate flow. I expect it to be done within the next hour.

@huult

huult commented Jul 23, 2026 •

Copy link
Copy Markdown
Contributor Author
Screen.Recording.2026-07-23.at.17.59.43.mov

@suneox It's done. Could you re-test it?

@mjasikowski
mjasikowski merged commit 8e88bfd into Expensify:main Jul 24, 2026
34 checks passed
@github-actions

Copy link
Copy Markdown
Contributor

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

@OSBotify

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

Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/mjasikowski in version: 9.4.45-0 🚀

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

@MelvinBot

Copy link
Copy Markdown
Contributor

🤖 I reviewed the changes in this PR against Expensify's help site content under App/docs/articles.

No help site changes are required, so I have not created a draft docs PR.

Why: This PR is a purely internal navigation/routing migration for the Tax rate, Tax amount, and Attendee steps of the expense creation flow. It swaps the backTo-parameter routes for dynamic routes (createDynamicRoute / entryScreens) and updates the related screen constants and types. There are:

  • No new or changed user-facing features
  • No new UI text, labels, buttons, or copy (src/languages/* is untouched)
  • No change to how these steps behave for the end user — the QA steps only verify that forward/back navigation still works exactly as before

Help site articles document user-facing product behavior, and none of that changes here, so there's nothing to update.

If I've misjudged the scope — for example if this is expected to alter a documented flow — reply with @MelvinBot <details> and I'll take another pass.

@huult, please confirm you agree no help site updates are needed here. If you believe a docs change is warranted, let me know what user-facing behavior changed and I'll draft the help site PR.

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/marcaaron in version: 9.4.45-14 🚀

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.

7 participants