Skip to content

[Payment due @huult] [No QA] Hide redundant MARKEDREIMBURSED action when report has a sibling IOU pay action - #95015

Merged
roryabraham merged 8 commits into
mainfrom
claude-markedReimbursedSiblingPayCheck
Sep 24, 2026
Merged

roryabraham merged 8 commits into
mainfrom
claude-markedReimbursedSiblingPayCheck

Conversation

@MelvinBot

@MelvinBot MelvinBot commented Jun 30, 2026 •

Copy link
Copy Markdown
Contributor

Explanation of Change

NewDot renders the IOU pay action in place of the MARKEDREIMBURSED action, so the two should never both be displayed on the same report. The existing guard in shouldReportActionBeVisible hides MARKEDREIMBURSED only when the write-time originalMessage.isNewDot flag is set or the baked shouldShow is false.

Both of those signals are computed once, at write time, and persisted into the Onyx update. When a MARKEDREIMBURSED action is created outside a NewDot request (e.g. a background job, then served back via GetMissingOnyxMessages), isNewDot is unset and a stale shouldShow: true gets baked in — so neither condition fires and the row leaks through alongside the IOU pay action, producing the duplicate "marked as paid" message.

This change stops trusting the stale baked flags and instead derives the answer locally: a new hasSiblingPayReportAction helper checks whether the report already contains an IOU pay action, and MARKEDREIMBURSED is hidden when it does. This is scoped to MARKEDREIMBURSED only (not REIMBURSED), and is purely additive to the existing flag checks, so:

  • Repro case (MARKEDREIMBURSED + IOU pay on the same report) → sibling pay exists → hidden → duplicate fixed.
  • No-twin paths (ABA-file batch reimbursements, zero-amount paychecks, OldDot non-instant-submit reports) create MARKEDREIMBURSED with no IOU pay → sibling absent → still visible → no regression.

Fixed Issues

$ https://github.com/Expensify/Expensify/issues/636674
PROPOSAL: https://github.com/Expensify/Expensify/issues/636674#issuecomment-4617734150

Tests

Automated tests only.

  • Verify that no errors appear in the JS console

Offline tests

n/a

QA Steps

None.

  • 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

…tion

Co-authored-by: Rory Abraham <roryabraham@users.noreply.github.com>
@MelvinBot
MelvinBot requested a review from a team June 30, 2026 22:57
@roryabraham
roryabraham marked this pull request as ready for review September 16, 2026 06:25
@roryabraham
roryabraham requested a review from a team as a code owner September 16, 2026 06:25
@melvin-bot
melvin-bot Bot requested a review from DylanDylann September 16, 2026 06:25
@melvin-bot

melvin-bot Bot commented Sep 16, 2026

Copy link
Copy Markdown

@DylanDylann 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 September 16, 2026 06:25
@roryabraham roryabraham changed the title Hide redundant MARKEDREIMBURSED action when report has a sibling IOU pay action [No QA] Hide redundant MARKEDREIMBURSED action when report has a sibling IOU pay action Sep 16, 2026

@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: 3d73234aaf

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

Comment thread src/libs/ReportActionsUtils.ts Outdated
Comment on lines +1310 to +1311
if (isActionOfType(reportAction, CONST.REPORT.ACTIONS.TYPE.MARKED_REIMBURSED) && hasSiblingPayReportAction(reportAction)) {
return false;

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P1 Badge Recompute cached siblings when PAY arrives

When the MARKED_REIMBURSED action is loaded before its sibling PAY action, DERIVED.VISIBLE_REPORT_ACTIONS has already cached it as visible. The incremental computation in visibleReportActions.ts processes only the action IDs included in each update, so merging the PAY action never reevaluates the existing MARKED_REIMBURSED action; isReportActionVisible() then returns that stale cached true value without invoking this new check. This means the duplicate remains in exactly the late-arriving-action scenario the helper intends to handle, unless visibility for all relevant siblings is invalidated or recomputed when a PAY action arrives.

Useful? React with 👍 / 👎.

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.

Fixed in 30ce84b

Comment thread src/libs/ReportActionsUtils.ts Outdated
Comment on lines +1814 to +1817
// Once a PAY action is found, unrelated report updates cannot change the result. Don't cache misses since PAY may arrive later.
const hasPayAction = Object.values(getAllReportActions(reportID)).some((action) => isPayAction(action));
if (hasPayAction) {
reportsWithPayAction.add(reportID);

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Match the PAY action to the reimbursement event

A report can contain a historical PAY action that is not the twin of this MARKED_REIMBURSED action—for example, after a NewDot payment is canceled, cancelPayment() adds a REIMBURSEMENT_DEQUEUED action but retains the original PAY action, and the report can subsequently be marked reimbursed through an OldDot/no-twin path. Checking for any PAY action over the report's entire history hides that later legitimate audit entry, so this needs to correlate the actions or exclude canceled/failed payments rather than treating every lifetime PAY action as the replacement.

Useful? React with 👍 / 👎.

@roryabraham
roryabraham requested a review from a team as a code owner September 16, 2026 07:59
@melvin-bot

melvin-bot Bot commented Sep 16, 2026

Copy link
Copy Markdown

@FitseTLT @roryabraham One of you needs to 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 September 16, 2026 07:59
# Conflicts:
#	src/libs/actions/OnyxDerived/configs/visibleReportActions.ts
#	tests/unit/OnyxDerivedTest.tsx
@roryabraham

Copy link
Copy Markdown
Contributor

@codex review

@roryabraham

Copy link
Copy Markdown
Contributor

@MelvinBot review

@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: 8076e0fda5

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

Comment thread src/libs/ReportActionsUtils.ts Outdated
Comment on lines +1883 to +1885
const reportID = reportAction?.reportID;
if (!reportID || !reportAction?.reportActionID) {
return false;

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P1 Badge Pass the collection report ID into the sibling lookup

When a persisted report action omits its optional reportID and relies on the reportActions_<reportID> collection key, this early return makes the new sibling check a no-op. That shape is explicitly supported by callers, which already compute actionReportID = reportAction.reportID ?? reportID, and is used by existing Onyx fixtures; however, isReportActionVisible() drops that known ID before calling this helper. Consequently the background-job MARKED_REIMBURSED action described by this change can remain visible beside its PAY action unless the report ID is passed separately into the lookup.

Useful? React with 👍 / 👎.

@MelvinBot

Copy link
Copy Markdown
Contributor Author

🤖 Review: this works, but it's solving a harder problem than the one you have.

The linked issue's own conclusion is that MARKEDREIMBURSED should never render in NewDot — NewDot shows the IOU pay action instead, and CONST already labels it // OldDot Action. If that's true, the client fix is one line — hide MARKED_REIMBURSED unconditionally in the existing block at src/libs/ReportActionsUtils.ts:1364 — instead of 64 lines of payment-attempt state machine plus a module-level WeakMap plus a derived-cache opt-out.

The "no regression" argument that justifies the complexity doesn't hold. The PR keeps no-twin paths (ABA batches, zero-amount paychecks, OldDot non-instant-submit) visible. But shouldShow is computed from the request context, so on the OpenReport path it is already false for every MARKEDREIMBURSED a NewDot client fetches — twin or no twin. Those rows are already hidden today. What this PR preserves is visibility only on the stale-flag delivery path, which means the same action renders or doesn't depending on which API delivered it. That inconsistency is the bug.

Also: the root cause is server-side. This is a client-side compensation for a backend value that shouldn't have been baked at write time. Fixing it there is a smaller change, covers every client including app versions that never update, and is what the linked issue recommends. That needs an internal engineer — please confirm the server fix isn't the right call before landing this.

Additional findings if this approach is kept

1. shouldReportActionBeVisible is no longer a pure function of one action. It now reads the module-global allReportActions via getAllReportActions. That purity is exactly what the visibleReportActions derived value is built on, which is why the PR had to opt every MARKED_REIMBURSED out of it in visibleReportActions.ts:16. You now have two caches with different invalidation strategies (the derived value keyed on Onyx updates, the WeakMap keyed on object identity) covering one predicate. This also conflicts with the repo guidance to prefer pure functions taking data as params over direct Onyx reads.

I did verify the cache opt-out is safe: every consumer I checked (useReportActionsVisibility, useMoneyRequestReportVisibleActions, getSortedReportActionsForDisplay) goes through isReportActionVisible, which falls back to a runtime check when the ID is absent from the derived map. No consumer treats "absent" as "invisible".

2. The look-back after a PAY is unbounded. In hasSiblingPayReportAction, once hasPay is set it stays set until a REIMBURSEMENT_DEQUEUED, REIMBURSEMENT_ACH_CANCELED, or REIMBURSEMENT_ACH_BOUNCE. Retract, reopen, and unapprove are not boundaries, so a report paid in NewDot, then retracted/reopened, then genuinely marked reimbursed in OldDot would hide the later action. The symmetric pendingSiblings path has the same gap in reverse. If the helper is modelling "payment attempts", those transitions probably belong in isPaymentAttemptBoundary.

3. REIMBURSED has the identical staleness and is left untouched. The PR scopes to MARKED_REIMBURSED deliberately, but both sit in the same branch keyed on the same two stale flags. Worth saying explicitly why REIMBURSED can't hit this, or handling both.

4. Minor: the WeakMap never caches for unknown reports. getAllReportActions returns a fresh {} literal when the report isn't in the collection, so paySiblingCache.set() writes against a throwaway key on every call and the lookup always misses. Guard on an empty result before caching.

5. Cache invalidation itself is sound. Onyx's mergeObject returns a new object reference whenever a merge changes anything and the original reference when nothing changed, so keying the WeakMap on the report's ReportActions object does invalidate correctly. The sort order assumption also holds — getSortedReportActions defaults to ascending, which the loop depends on.

What I couldn't verify: I wasn't able to run the test suite in this environment, so the four new tests are reviewed by reading only. Tests says "automated tests only" and the QA section is empty, so nothing here has been exercised against a real duplicate-MARKEDREIMBURSED report.


Reply with @MelvinBot <your feedback> to refine this review.


view run

@roryabraham

Copy link
Copy Markdown
Contributor

@codex review

@roryabraham

Copy link
Copy Markdown
Contributor

@MelvinBot review

@mountiny
mountiny requested a review from huult September 18, 2026 09:12
@huult

huult commented Sep 19, 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

Screen.Recording.2026-09-19.at.18.43.37.mov
await window.Onyx.merge('reportActions_6805983650172779', {
  'fake1': {
    reportActionID: 'fake1',
    actionName: 'MARKEDREIMBURSED',
    reportID: '6805983650172779',
    created: '2026-09-06 04:11:01.000',
    person: [{type:'TEXT', style:'strong', text:'Test'}],
    message: [{type:'TEXT', style:'normal', text:'[TEST] marked reimbursed - sibling PAY'}],
    originalMessage: {}, 
  },
});

Comment thread src/libs/ReportActionsUtils.ts Resolved
@huult

huult commented Sep 21, 2026

Copy link
Copy Markdown
Contributor

@roryabraham could you check my comment?

@huult

huult commented Sep 23, 2026

Copy link
Copy Markdown
Contributor

@roryabraham Could you take a look when you have time?

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

LGTM.

@melvin-bot melvin-bot Bot changed the title [No QA] Hide redundant MARKEDREIMBURSED action when report has a sibling IOU pay action [Payment due @huult] [No QA] Hide redundant MARKEDREIMBURSED action when report has a sibling IOU pay action Sep 24, 2026
@melvin-bot

melvin-bot Bot commented Sep 24, 2026

Copy link
Copy Markdown

🎯 @huult, thanks for reviewing and testing this PR! 🎉

A payment issue will be created for your review once this PR is deployed to production.
E/E issue linked to the PR - https://www.github.com/Expensify/Expensify/issues/636674.

If payment is not needed (e.g., regression PR review fix etc), react with 👎 to this comment to prevent the payment issue from being created.

@roryabraham
roryabraham requested a review from a team September 24, 2026 15:54
@melvin-bot
melvin-bot Bot requested a review from nyomanjyotisa September 24, 2026 15:55
@melvin-bot

melvin-bot Bot commented Sep 24, 2026

Copy link
Copy Markdown

@nyomanjyotisa 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 September 24, 2026 15:55
@roryabraham
roryabraham removed the request for review from nyomanjyotisa September 24, 2026 16:16
@roryabraham
roryabraham merged commit b344410 into main Sep 24, 2026
50 of 55 checks passed
@roryabraham
roryabraham deleted the claude-markedReimbursedSiblingPayCheck branch September 24, 2026 16:18
@github-actions

Copy link
Copy Markdown
Contributor

🚧 roryabraham 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/roryabraham in version: 9.4.94-0 🚀

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

@MelvinBot

Copy link
Copy Markdown
Contributor Author

No help site changes are required for this PR, so I did not create a docs PR.

This PR fixes a bug where a report could show a duplicate "marked as paid" message in its history. The fix changes nothing users can see or configure. No feature names, settings, buttons, or workflows changed.

What I checked
  • The PR: It changes only ReportActionsUtils.ts, visibleReportActions.ts, and unit tests. It hides a leftover MARKEDREIMBURSED action when the report already has an IOU pay action.
  • The help site: I searched App/docs/articles for "marked as paid" and "marked as reimbursed." The matches describe the Marked as paid status in Understanding-Report-Statuses-and-Actions.md:20 and Using-Reports-in-New-Expensify.md:78. That status still works the same way. No article describes or works around the duplicate message.

view run

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/Julesssss in version: 9.4.94-0 🚀

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

Bundle Size Analysis (Sentry):

@melvin-bot

melvin-bot Bot commented Sep 28, 2026

Copy link
Copy Markdown

🤖 Payment issue created: #102453

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