Skip to content

Add 'Require company cards for all purchases' configuration#76728

Merged
Valforte merged 21 commits into
mainfrom
jsenyitko-add-company-cards-violation
Dec 15, 2025
Merged

Add 'Require company cards for all purchases' configuration#76728
Valforte merged 21 commits into
mainfrom
jsenyitko-add-company-cards-violation

Conversation

@JS00001

@JS00001 JS00001 commented Dec 4, 2025

Copy link
Copy Markdown
Contributor

Explanation of Change

Adds the 'Require Company Cards for All Purchases' violation, which requires members of a policy to use company cards for purchases (via a violation)

Fixed Issues

$ #76673

Tests

Create a policy
Enable workspace rules
Ensure that you cannot toggle the 'Require company cards for all purchases' option until you have a card feed
Connect a card feed
Ensure that you can now enable the 'Require company cards for all purchases' rule
Enable the rule

Create a cash expense - The expense should have a violation that cannot be dismissed: "Company card purchases required"
Create a card expense (or import some from the feed) - The expense should not have a violation
Create an expense by importing a personal card
Move the expense to a report on the policy
A violation should show up: "Company card purchases required"

Disable the rule in the workspace settings
All of the violations should disappear

  • Verify that no errors appear in the JS console

Offline tests

N/A

QA Steps

Same as tests

  • 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

Screen.Recording.2025-12-04.at.1.27.57.PM.mov

@JS00001 JS00001 changed the title reverts 9ff3341 Add 'Require company cards for all purchases' configuration Dec 4, 2025
@OSBotify

This comment has been minimized.

@OSBotify

This comment has been minimized.

@codecov

codecov Bot commented Dec 4, 2025

Copy link
Copy Markdown

Codecov Report

❌ Looks like you've decreased code coverage for some files. Please write tests to increase, or at least maintain, the existing level of code coverage. See our documentation here for how to interpret this table.

Files with missing lines Coverage Δ
src/CONST/index.ts 85.84% <ø> (ø)
src/libs/API/types.ts 100.00% <ø> (ø)
src/hooks/useViolations.ts 3.22% <0.00%> (-0.06%) ⬇️
src/libs/Violations/ViolationsUtils.ts 66.97% <0.00%> (-1.03%) ⬇️
...c/components/ReportActionItem/MoneyRequestView.tsx 0.51% <0.00%> (-0.01%) ⬇️
src/libs/actions/Policy/Policy.ts 33.96% <0.00%> (-0.17%) ⬇️
.../workspace/rules/IndividualExpenseRulesSection.tsx 0.00% <0.00%> (ø)
... and 7 files with indirect coverage changes

@OSBotify

This comment has been minimized.

@JS00001 JS00001 changed the title Add 'Require company cards for all purchases' configuration [HOLD AUTH 18561] Add 'Require company cards for all purchases' configuration Dec 4, 2025
@JS00001 JS00001 changed the title [HOLD AUTH 18561] Add 'Require company cards for all purchases' configuration [HOLD AUTH 18563] Add 'Require company cards for all purchases' configuration Dec 4, 2025
@JS00001 JS00001 requested a review from ikevin127 December 4, 2025 18:26
@OSBotify

This comment has been minimized.

@JS00001 JS00001 marked this pull request as ready for review December 4, 2025 18:49
@JS00001 JS00001 requested review from a team as code owners December 4, 2025 18:49
@melvin-bot melvin-bot Bot requested review from joekaufmanexpensify and luacmartins and removed request for a team December 4, 2025 18:49
@OSBotify

Copy link
Copy Markdown
Contributor

🦜 Polyglot Parrot! 🦜

Squawk! Looks like you added some shiny new English strings. Allow me to parrot them back to you in other tongues:

View the translation diff
diff --git a/src/languages/de.ts b/src/languages/de.ts
index b8c27ad0..270e78b2 100644
--- a/src/languages/de.ts
+++ b/src/languages/de.ts
@@ -6215,8 +6215,8 @@ Fordere Spesendetails wie Belege und Beschreibungen an, lege Limits und Standard
                 gambling: 'Glücksspiel',
                 tobacco: 'Tabak',
                 adultEntertainment: 'Unterhaltung für Erwachsene',
-                requireCompanyCard: 'Firmenkarten für alle Einkäufe erforderlich machen',
-                requireCompanyCardDescription: 'Kennzeichnen Sie alle Barausgaben, einschließlich Kilometer- und Tagegeldspesen.',
+                requireCompanyCard: 'Firmenkarten für alle Käufe erforderlich',
+                requireCompanyCardDescription: 'Markiere alle Barausgaben, einschließlich Kilometer- und Pauschalspesen.',
             },
             expenseReportRules: {
                 title: 'Fortgeschritten',
diff --git a/src/languages/fr.ts b/src/languages/fr.ts
index 4fe8a891..8e3aa643 100644
--- a/src/languages/fr.ts
+++ b/src/languages/fr.ts
@@ -6223,7 +6223,7 @@ Exigez des informations de dépense comme les reçus et les descriptions, défin
                 tobacco: 'Tabac',
                 adultEntertainment: 'Divertissement pour adultes',
                 requireCompanyCard: 'Exiger des cartes d’entreprise pour tous les achats',
-                requireCompanyCardDescription: 'Marquez toutes les dépenses payées en espèces, y compris les frais kilométriques et les indemnités journalières.',
+                requireCompanyCardDescription: 'Signalez toutes les dépenses en espèces, y compris les frais de kilométrage et les indemnités journalières.',
             },
             expenseReportRules: {
                 title: 'Avancé',
@@ -7343,7 +7343,7 @@ Exigez des informations de dépense comme les reçus et les descriptions, défin
         confirmDuplicatesInfo: `Les doublons que vous ne conservez pas seront mis de côté pour que l’expéditeur les supprime.`,
         hold: 'Cette dépense a été mise en attente',
         resolvedDuplicates: 'a résolu le doublon',
-        companyCardRequired: 'Achats avec carte d’entreprise requis',
+        companyCardRequired: 'Achats par carte d’entreprise requis',
     },
     reportViolations: {
         [CONST.REPORT_VIOLATIONS.FIELD_REQUIRED]: ({fieldName}: RequiredFieldParams) => `${fieldName} est requis`,
diff --git a/src/languages/it.ts b/src/languages/it.ts
index e893f814..78014bd2 100644
--- a/src/languages/it.ts
+++ b/src/languages/it.ts
@@ -6194,7 +6194,7 @@ Richiedi dettagli di spesa come ricevute e descrizioni, imposta limiti e valori
                 tobacco: 'Tabacco',
                 adultEntertainment: 'Intrattenimento per adulti',
                 requireCompanyCard: 'Richiedi carte aziendali per tutti gli acquisti',
-                requireCompanyCardDescription: 'Contrassegna tutte le spese in contanti, incluse le spese per chilometraggio e le diarie.',
+                requireCompanyCardDescription: 'Contrassegna tutte le spese in contanti, incluse le spese chilometriche e di diaria.',
             },
             expenseReportRules: {
                 title: 'Avanzato',
diff --git a/src/languages/ja.ts b/src/languages/ja.ts
index ed55c72d..6a5dd2dd 100644
--- a/src/languages/ja.ts
+++ b/src/languages/ja.ts
@@ -6157,7 +6157,7 @@ ${reportName}
                 tobacco: 'たばこ',
                 adultEntertainment: 'アダルトエンターテインメント',
                 requireCompanyCard: 'すべての購入に会社カードを必須にする',
-                requireCompanyCardDescription: 'マイレージや日当の経費を含む、すべての現金支出にフラグを付けます。',
+                requireCompanyCardDescription: '現金での支出(走行距離精算や日当経費を含む)をすべてフラグ付けします。',
             },
             expenseReportRules: {
                 title: '上級',
@@ -7265,7 +7265,7 @@ ${reportName}
         confirmDuplicatesInfo: `あなたが保持しない重複分は、申請者が削除できるように保留されます。`,
         hold: 'この経費は保留になっています',
         resolvedDuplicates: '重複を解決しました',
-        companyCardRequired: '法人カードでの購入が必須',
+        companyCardRequired: '会社カードでの購入が必須',
     },
     reportViolations: {
         [CONST.REPORT_VIOLATIONS.FIELD_REQUIRED]: ({fieldName}: RequiredFieldParams) => `${fieldName} は必須です`,
diff --git a/src/languages/nl.ts b/src/languages/nl.ts
index 9e08df96..7aaefada 100644
--- a/src/languages/nl.ts
+++ b/src/languages/nl.ts
@@ -6182,7 +6182,7 @@ Vraag verplichte uitgavedetails zoals bonnetjes en beschrijvingen, stel limieten
                 tobacco: 'Tabak',
                 adultEntertainment: 'Volwassenenentertainment',
                 requireCompanyCard: 'Bedrijfskaarten vereisen voor alle aankopen',
-                requireCompanyCardDescription: 'Markeer alle contante uitgaven, inclusief kilometer- en dagvergoedingen.',
+                requireCompanyCardDescription: 'Markeer alle uitgaven in contanten, inclusief kilometer- en dagvergoedingen.',
             },
             expenseReportRules: {
                 title: 'Geavanceerd',
@@ -7301,7 +7301,7 @@ Vraag verplichte uitgavedetails zoals bonnetjes en beschrijvingen, stel limieten
         confirmDuplicatesInfo: `De duplicaten die je niet behoudt, worden bewaard zodat de indiener ze kan verwijderen.`,
         hold: 'Deze uitgave is in de wacht gezet',
         resolvedDuplicates: 'het duplicaat opgelost',
-        companyCardRequired: 'Aankopen met bedrijfskaart verplicht',
+        companyCardRequired: 'Aankopen met bedrijfskaart vereist',
     },
     reportViolations: {
         [CONST.REPORT_VIOLATIONS.FIELD_REQUIRED]: ({fieldName}: RequiredFieldParams) => `${fieldName} is verplicht`,
diff --git a/src/languages/pl.ts b/src/languages/pl.ts
index cabd5b56..04028e15 100644
--- a/src/languages/pl.ts
+++ b/src/languages/pl.ts
@@ -6176,7 +6176,7 @@ Wymagaj szczegółów wydatków, takich jak paragony i opisy, ustawiaj limity i
                 tobacco: 'Tytoń',
                 adultEntertainment: 'Rozrywka dla dorosłych',
                 requireCompanyCard: 'Wymagaj kart firmowych dla wszystkich zakupów',
-                requireCompanyCardDescription: 'Oznacz wszystkie wydatki gotówkowe, w tym koszty za przejechane kilometry i diety.',
+                requireCompanyCardDescription: 'Oznacz wszystkie wydatki gotówkowe, w tym koszty za przejechane kilometry oraz należności ryczałtowe (per diem).',
             },
             expenseReportRules: {
                 title: 'Zaawansowany',
diff --git a/src/languages/pt-BR.ts b/src/languages/pt-BR.ts
index 9c2625eb..f984c101 100644
--- a/src/languages/pt-BR.ts
+++ b/src/languages/pt-BR.ts
@@ -6177,7 +6177,7 @@ Exija detalhes de despesas como recibos e descrições, defina limites e padrõe
                 tobacco: 'Tabaco',
                 adultEntertainment: 'Entretenimento adulto',
                 requireCompanyCard: 'Exigir cartões corporativos para todas as compras',
-                requireCompanyCardDescription: 'Sinalize todas as despesas em dinheiro, incluindo quilometragem e diárias.',
+                requireCompanyCardDescription: 'Classifique todas as despesas em dinheiro, incluindo quilometragem e despesas de diária.',
             },
             expenseReportRules: {
                 title: 'Avançado',
diff --git a/src/languages/zh-hans.ts b/src/languages/zh-hans.ts
index ca1eccf0..37503545 100644
--- a/src/languages/zh-hans.ts
+++ b/src/languages/zh-hans.ts
@@ -6063,8 +6063,8 @@ ${reportName}
                 gambling: '赌博',
                 tobacco: '烟草',
                 adultEntertainment: '成人娱乐',
-                requireCompanyCard: '所有购买均需使用公司卡',
-                requireCompanyCardDescription: '标记所有现金支出,包括里程和日津贴费用。',
+                requireCompanyCard: '所有消费都必须使用公司卡',
+                requireCompanyCardDescription: '标记所有现金支出,包括里程和每日补贴费用。',
             },
             expenseReportRules: {
                 title: '高级',

Note

You can apply these changes to your branch by copying the patch to your clipboard, then running pbpaste | git apply 😉

@JS00001

JS00001 commented Dec 11, 2025

Copy link
Copy Markdown
Contributor Author

BE PR is merged, waiting for deploy

@JS00001 JS00001 changed the title [HOLD AUTH 18563] Add 'Require company cards for all purchases' configuration Add 'Require company cards for all purchases' configuration Dec 12, 2025
@JS00001

JS00001 commented Dec 12, 2025

Copy link
Copy Markdown
Contributor Author

This should be good @ikevin127

@ikevin127

Copy link
Copy Markdown
Contributor

🔄 Checking...

@ikevin127

ikevin127 commented Dec 12, 2025

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 tests pass on all platforms & I tested again on:
    • Android: Native
    • Android: mWeb Chrome
    • iOS: Native
    • 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 the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
    • 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.js 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 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.
  • 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-hybrid.mp4
Android: mWeb Chrome
android-mweb.mp4
iOS: HybridApp
ios-hybrid.mov
iOS: mWeb Safari
ios-mweb.mov
MacOS: Chrome / Safari
web.mov

Comment thread src/libs/API/parameters/SetPolicyRequireCompanyCardsEnabled.ts Outdated

@ikevin127 ikevin127 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 - tests well while offline as well 👍

@JS00001 ⚠️ The only issue I found is related to the report preview not updating (adding or removing the FE error) until the actual report is open (OpenReport), this might be addressable from the FE if we check whether policy?.requireCompanyCardsEnabled is enabled or disabled, here's an example of this issue:

ios-hybrid.mov

@melvin-bot melvin-bot Bot requested a review from Valforte December 12, 2025 23:43
@melvin-bot

melvin-bot Bot commented Dec 12, 2025

Copy link
Copy Markdown

@Valforte 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]

luacmartins
luacmartins previously approved these changes Dec 13, 2025

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

TS check is failing

…github.com:Expensify/App into jsenyitko-add-company-cards-violation
@JS00001

JS00001 commented Dec 15, 2025

Copy link
Copy Markdown
Contributor Author

@ikevin127 I think that last issue is a case that isnt common enough to add extra logic for

The user would have to be:
The policy admin
Offline
Have expenses that break this rule
Navigate back to the reports page while offline

So I think we should leave the logic in its simplest version of just checking for the violation

@Valforte Valforte merged commit 2988dc6 into main Dec 15, 2025
36 checks passed
@Valforte Valforte deleted the jsenyitko-add-company-cards-violation branch December 15, 2025 14:13
@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/Valforte in version: 9.2.79-0 🚀

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

@jponikarchuk

Copy link
Copy Markdown

This PR failing because of a regression issue
This issue is reproducible in: All platforms

527467828-41ef34d5-f5bc-428a-ab2b-2abbb5d165d8.mp4

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/Valforte in version: 9.2.81-0 🚀

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

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/AndrewGable in version: 9.2.81-5 🚀

platform result
🖥 desktop 🖥 success ✅
🕸 web 🕸 success ✅
🤖 android 🤖 failure ❌
🍎 iOS 🍎 success ✅

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/AndrewGable in version: 9.2.81-5 🚀

platform result
🖥 desktop 🖥 success ✅
🕸 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.

8 participants