Skip to content

Update how DEW submit actions are displayed#83517

Merged
mollfpr merged 16 commits intomainfrom
francois-dew-auto-submit-error-from-concierge
Mar 2, 2026
Merged

Update how DEW submit actions are displayed#83517
mollfpr merged 16 commits intomainfrom
francois-dew-auto-submit-error-from-concierge

Conversation

@francoisl
Copy link
Contributor

@francoisl francoisl commented Feb 26, 2026

Explanation of Change

Update how submit errors are shown when a policy uses DEW, to better match the original design.

  • When a report fails to auto-submit (harvesting) or auto-approve, show Concierge as the actor of the action
  • Prepend the error reason generated by the backend with a failed to submit/approve prefix

Fixed Issues

$ https://github.com/Expensify/Expensify/issues/603317

Offline tests

N/A

QA Steps

Important

Sign in to one of following accounts to run QA:

Same as test steps below

Tests

Prerequisite: use an account with a workspace that has a test DEW implementation enabled

Setup:

  1. Create a report with at least one expense
  2. Click the Submit button
  3. Verify that a message shows in the report history saying failed to submit the report. Add at least one approver as an expense description and that the "actor" of the message is yourself
  4. Click on one of the expenses in the report, and set the email address of one of the admins of the policy as the description of the expense
  5. Rename the report auto AUTOAPPROVE_ERROR
  6. Click the submit button again
  7. Verify that a report action saying report routed to XYZ due to custom approval workflow coming from Concierge is added to the report
  8. Verify that a report action saying "failed to approve via workspace rules. This report cannot be approved" coming from Concierge is added to the report
  9. Rename the report to APPROVE_ERROR
  10. In another session, sign in to the admin's account
  11. Approve the report
  12. Verify that a report action saying failed to approve. This report cannot be approved coming from the admin (not Concierge) was added to the report
  • 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 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

MacOS: Chrome / Safari image image

@codecov
Copy link

codecov bot commented Feb 26, 2026

Codecov Report

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

Files with missing lines Coverage Δ
src/libs/ReportActionsUtils.ts 52.12% <100.00%> (+0.33%) ⬆️
src/pages/inbox/report/PureReportActionItem.tsx 55.04% <ø> (+0.16%) ⬆️
... and 15 files with indirect coverage changes

const wasSubmittedViaHarvesting = getOriginalMessage(action)?.harvesting ?? false;

let failedSubmitReason = getOriginalMessage(action)?.message ?? translate('iou.error.genericCreateFailureMessage');
failedSubmitReason = wasSubmittedViaHarvesting ? translate('iou.failedToAutoSubmitViaDEW', failedSubmitReason) : translate('iou.failedToSubmitViaDEW', failedSubmitReason);
Copy link
Contributor

Choose a reason for hiding this comment

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

NAB, but I prefer to not mutating variable, so we can rename the first one as const message and keep the 2nd one name.

Suggested change
failedSubmitReason = wasSubmittedViaHarvesting ? translate('iou.failedToAutoSubmitViaDEW', failedSubmitReason) : translate('iou.failedToSubmitViaDEW', failedSubmitReason);
const message = getOriginalMessage(action)?.message ?? translate('iou.error.genericCreateFailureMessage');
const failedSubmitReason = wasSubmittedViaHarvesting ? translate('iou.failedToAutoSubmitViaDEW', message) : translate('iou.failedToSubmitViaDEW', message);


children = (
<ReportActionItemBasicMessage>
<RenderHTML html={`<comment><muted-text>${failedSubmitReason}</muted-text></comment>`} />
Copy link
Contributor

Choose a reason for hiding this comment

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

Since we want to render this as HTML, we can move the logic to getReportActionMessageFragments and remove the rendering here.

function getReportActionMessageFragments(translate: LocalizedTranslate, action: ReportAction): Message[] {
if (isOldDotReportAction(action)) {
const oldDotMessage = getMessageOfOldDotReportAction(translate, action);
const html = isActionOfType(action, CONST.REPORT.ACTIONS.TYPE.SELECTED_FOR_RANDOM_AUDIT) ? Parser.replace(oldDotMessage) : oldDotMessage;
return [{text: oldDotMessage, html: `<muted-text>${html}</muted-text>`, type: 'COMMENT'}];
}
if (isActionOfType(action, CONST.REPORT.ACTIONS.TYPE.ROOM_CHANGE_LOG.UPDATE_ROOM_DESCRIPTION)) {
const message = getUpdateRoomDescriptionMessage(translate, action);
return [{text: message, html: `<muted-text>${message}</muted-text>`, type: 'COMMENT'}];
}
if (isActionOfType(action, CONST.REPORT.ACTIONS.TYPE.ROOM_CHANGE_LOG.UPDATE_ROOM_AVATAR)) {
const message = getRoomAvatarUpdatedMessage(translate, action);
return [{text: message, html: `<muted-text>${message}</muted-text>`, type: 'COMMENT'}];
}
if (isActionOfType(action, CONST.REPORT.ACTIONS.TYPE.POLICY_CHANGE_LOG.UPDATE_DESCRIPTION)) {
const message = getWorkspaceDescriptionUpdatedMessage(translate, action);
return [{text: message, html: `<muted-text>${message}</muted-text>`, type: 'COMMENT'}];
}
if (isActionOfType(action, CONST.REPORT.ACTIONS.TYPE.REIMBURSED)) {
const message = getReportActionMessageText(action);
return [{text: message, html: `<muted-text>${message}</muted-text>`, type: 'COMMENT'}];
}
if (isActionOfType(action, CONST.REPORT.ACTIONS.TYPE.RETRACTED)) {
const message = translate('iou.retracted');
return [{text: message, html: `<muted-text>${message}</muted-text>`, type: 'COMMENT'}];
}
if (isActionOfType(action, CONST.REPORT.ACTIONS.TYPE.REOPENED)) {
const message = translate('iou.reopened');
return [{text: message, html: `<muted-text>${message}</muted-text>`, type: 'COMMENT'}];
}
if (isActionOfType(action, CONST.REPORT.ACTIONS.TYPE.TRAVEL_UPDATE)) {
const message = getTravelUpdateMessage(translate, action);
return [{text: message, html: `<muted-text>${message}</muted-text>`, type: 'COMMENT'}];
}
if (isConciergeCategoryOptions(action) || isConciergeDescriptionOptions(action)) {
const message = getReportActionMessageText(action);
return [{text: message, html: message, type: 'COMMENT'}];
}
if (isActionOfType(action, CONST.REPORT.ACTIONS.TYPE.DYNAMIC_EXTERNAL_WORKFLOW_ROUTED)) {
const message = getDynamicExternalWorkflowRoutedMessage(action, translate);
return [{text: message, html: `<muted-text>${message}</muted-text>`, type: 'COMMENT'}];
}
const actionMessage = action.previousMessage ?? action.message;
if (Array.isArray(actionMessage)) {
return actionMessage.filter((item): item is Message => !!item);
}
return actionMessage ? [actionMessage] : [];
}

if (isDynamicExternalWorkflowSubmitFailedAction(action)) {
    const originalMessage = getOriginalMessage(action);
    const wasSubmittedViaHarvesting = originalMessage?.harvesting ?? false;
    const message = originalMessage?.message ?? translate('iou.error.genericCreateFailureMessage');
    const failedSubmitReason = wasSubmittedViaHarvesting ? translate('iou.failedToAutoSubmitViaDEW', message) : translate('iou.failedToSubmitViaDEW', message);
    return [{text: message, html: `<muted-text>${failedSubmitReason}</muted-text>`, type: 'COMMENT'}];
}


children = (
<ReportActionItemBasicMessage>
<RenderHTML html={`<comment><muted-text>${failedApproveReason}</muted-text></comment>`} />
Copy link
Contributor

Choose a reason for hiding this comment

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

Same as above

@bernhardoj
Copy link
Contributor

For the test step,

  1. There is no test step for the auto-submit
  2. For step 5, it should be AUTOAPPROVE_ERROR
  3. Before step 10, we should rename the report to APPROVE_ERROR

(recording for the checklist later)

web.mp4

@francoisl
Copy link
Contributor Author

Updated, also added some tests.

There is no test step for the auto-submit

Yeah, I don't think there's an easy way to test this part because harvesting can't be manually triggered, as far as I know (well, at least on purpose). The options for local testing are:

  • Hardcode the const wasSubmittedViaHarvesting to true, or
  • Give me a report ID and account email in Slack and I can trigger a harvesting for it

I'll do internal QA for that part

For step 5, it should be AUTOAPPROVE_ERROR
Before step 10, we should rename the report to APPROVE_ERROR

👍 I'll update the steps

@@ -1,5 +1,5 @@
import Parser from '@libs/Parser';
import getClipboardText from '@libs/Clipboard/getClipboardText';
import Parser from '@libs/Parser';
Copy link
Contributor Author

Choose a reason for hiding this comment

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

This change is unrelated to the PR, but the prettier step was failing from CI, I had to pull main and run npm run prettier to fix it.

@francoisl francoisl marked this pull request as ready for review February 26, 2026 19:06
@francoisl francoisl requested review from a team as code owners February 26, 2026 19:06
@melvin-bot melvin-bot bot requested review from huult and joekaufmanexpensify and removed request for a team February 26, 2026 19:06
@melvin-bot
Copy link

melvin-bot bot commented Feb 26, 2026

@huult 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 February 26, 2026 19:06
@francoisl francoisl removed the request for review from huult February 26, 2026 19:06
@francoisl
Copy link
Contributor Author

(@bernhardoj will do the C+ review on this because he already has context btw)

const wasSubmittedViaHarvesting = originalMessage?.harvesting ?? false;
const message = originalMessage?.message ?? translate('iou.error.genericCreateFailureMessage');
const failedSubmitReason = wasSubmittedViaHarvesting ? translate('iou.failedToAutoSubmitViaDEW', message) : translate('iou.failedToSubmitViaDEW', message);
return [{text: message, html: `<muted-text>${failedSubmitReason}</muted-text>`, type: 'COMMENT'}];
Copy link
Contributor

Choose a reason for hiding this comment

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

My bad, the text should be failedSubmitReason

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Ah I see, makes sense. In the end it didn't change anything because we only render the html text? I'll still edit though.

Copy link
Contributor

Choose a reason for hiding this comment

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

Yeah, it didn't change anything though.

const wasAutoApproveAction = originalMessage?.automaticAction ?? false;
const message = originalMessage?.message ?? translate('iou.error.genericCreateFailureMessage');
const failedApproveReason = wasAutoApproveAction ? translate('iou.failedToAutoApproveViaDEW', message) : translate('iou.failedToApproveViaDEW', message);
return [{text: message, html: `<muted-text>${failedApproveReason}</muted-text>`, type: 'COMMENT'}];
Copy link
Contributor

Choose a reason for hiding this comment

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

Same as above

@francoisl
Copy link
Contributor Author

Ok, updated!

@bernhardoj
Copy link
Contributor

bernhardoj commented Feb 27, 2026

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 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
    • 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 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)
  • 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
  • If a new component is created I verified that:
    • A similar component doesn't exist in the codebase
    • All props are defined accurately and each prop has a /** comment above it */
    • The file is named correctly
    • 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
    • For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
    • Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
    • All JSX used for rendering exists in the render method
    • 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 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 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.
  • 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
web.mp4

queuedToSubmitViaDEW: 'en cola para enviar a través del flujo de aprobación personalizado',
failedToAutoSubmitViaDEW: (reason: string) => `no ha podido enviar este informe mediante <a href="${CONST.SELECT_WORKFLOWS_HELP_URL}">retrasar envíos</a>. ${reason}`,
failedToSubmitViaDEW: (reason: string) => `no ha podido enviar este informe. ${reason}`,
failedToAutoApproveViaDEW: (reason: string) => `no ha podido aprobar mediante <a href="${CONST.CONFIGURE_EXPENSE_REPORT_RULES_HELP_URL}">workspace rules</a>. ${reason}`,
Copy link
Contributor

Choose a reason for hiding this comment

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

Before approving, have we confirmed the translation? Also, is it expected not translating the "workspace rules"?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Oh good catch for workspace rules, that's a bad copy/paste. I'm confirming the rest of the translation internally but let's not hold the PR on that, it's a minor thing we can adjust later if needed.

@francoisl francoisl force-pushed the francois-dew-auto-submit-error-from-concierge branch from 2fd3758 to 1562f06 Compare February 27, 2026 08:21
@francoisl
Copy link
Contributor Author

Updated again.

Copy link
Contributor

@bernhardoj bernhardoj left a comment

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 requested a review from mollfpr February 27, 2026 13:09
@melvin-bot
Copy link

melvin-bot bot commented Feb 27, 2026

@mollfpr 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
Copy link

melvin-bot bot commented Feb 27, 2026

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

An E/App issue has been created to issue payment here: #83681.

Conflicts:
    src/languages/de.ts
    src/languages/fr.ts
    src/languages/it.ts
    src/languages/ja.ts
    src/languages/nl.ts
    src/languages/pl.ts
    src/languages/pt-BR.ts
    src/languages/zh-hans.ts
@mollfpr mollfpr merged commit bf6f684 into main Mar 2, 2026
34 checks passed
@mollfpr mollfpr deleted the francois-dew-auto-submit-error-from-concierge branch March 2, 2026 14:19
@github-actions
Copy link
Contributor

github-actions bot commented Mar 2, 2026

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

@OSBotify
Copy link
Contributor

OSBotify commented Mar 2, 2026

✋ 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
Contributor

OSBotify commented Mar 2, 2026

🚀 Deployed to staging by https://github.com/mollfpr in version: 9.3.28-0 🚀

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

@lanitochka17
Copy link

This PR is failing because of issue ##84043

The issue is reproducible in: Web

@OSBotify
Copy link
Contributor

OSBotify commented Mar 4, 2026

🚀 Deployed to staging by https://github.com/mollfpr in version: 9.3.30-0 🚀

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

@OSBotify
Copy link
Contributor

OSBotify commented Mar 4, 2026

🚀 Deployed to production by https://github.com/blimpich in version: 9.3.30-3 🚀

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

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