Skip to content

Update generic remove member error message to be more actionable#87249

Open
MelvinBot wants to merge 1 commit intomainfrom
claude-updateGenericRemoveErrorMessage
Open

Update generic remove member error message to be more actionable#87249
MelvinBot wants to merge 1 commit intomainfrom
claude-updateGenericRemoveErrorMessage

Conversation

@MelvinBot
Copy link
Copy Markdown
Contributor

Explanation of Change

When removing workspace members fails, the generic error message "There was a problem removing that workspace member" gives no indication of why the removal failed or what the user can do about it. This is especially confusing for migrate customers who see a wall of identical RBR errors across many members.

This PR updates the genericRemove translation string across all 10 locale files to a more informative and actionable message: "Couldn't remove this member. This may be caused by an issue with another member. Please resolve any errors and try again." The wording uses "may be caused" to account for cases where the issue may or may not be related to other members.

Fixed Issues

$ #84326
PROPOSAL: #84326 (comment)

Tests

  1. Open a workspace with multiple members
  2. Select members to remove and trigger the remove action
  3. If the API call fails, verify the error message now reads: "Couldn't remove this member. This may be caused by an issue with another member. Please resolve any errors and try again."
  4. Verify the message is displayed correctly in all supported languages
  • Verify that no errors appear in the JS console

Offline tests

N/A — this is a copy-only change to error message strings. Offline behavior is unchanged.

QA Steps

  1. Open a workspace with multiple members
  2. Attempt to remove members in a scenario where the API call fails
  3. Verify the updated error message is displayed: "Couldn't remove this member. This may be caused by an issue with another member. Please resolve any errors and try again."
  4. Verify the message appears correctly for each affected member row
  • 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

Android: Native

Copy-only change — no visual UI changes.

Android: mWeb Chrome

Copy-only change — no visual UI changes.

iOS: Native

Copy-only change — no visual UI changes.

iOS: mWeb Safari

Copy-only change — no visual UI changes.

MacOS: Chrome / Safari

Copy-only change — no visual UI changes.

The generic remove member error now indicates that the failure may be
caused by an issue with another member, guiding users to resolve errors
before retrying. Updated across all locale files.

Co-authored-by: Pujan Shah <Pujan92@users.noreply.github.com>
@OSBotify
Copy link
Copy Markdown
Contributor

OSBotify commented Apr 7, 2026

🦜 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 9b7d7878..6ac7cc47 100644
--- a/src/languages/de.ts
+++ b/src/languages/de.ts
@@ -5871,7 +5871,7 @@ _Für ausführlichere Anweisungen [besuchen Sie unsere Hilfeseite](${CONST.NETSU
                 genericAdd: 'Beim Hinzufügen dieses Workspace-Mitglieds ist ein Problem aufgetreten',
                 cannotRemove: 'Du kannst dich selbst oder den/die Workspace-Inhaber:in nicht entfernen',
                 genericRemove:
-                    'Dieses Mitglied konnte nicht entfernt werden. Dies kann an einem Problem mit einem anderen Mitglied liegen. Bitte beheben Sie alle Fehler und versuchen Sie es erneut.',
+                    'Dieses Mitglied konnte nicht entfernt werden. Dies kann durch ein Problem mit einem anderen Mitglied verursacht werden. Bitte beheben Sie alle Fehler und versuchen Sie es erneut.',
             },
             addedWithPrimary: 'Einige Mitglieder wurden mit ihren primären Anmeldungen hinzugefügt.',
             invitedBySecondaryLogin: (secondaryLogin: string) => `Hinzugefügt durch sekundären Login ${secondaryLogin}.`,
diff --git a/src/languages/fr.ts b/src/languages/fr.ts
index 43cadcbe..41e92a34 100644
--- a/src/languages/fr.ts
+++ b/src/languages/fr.ts
@@ -5890,7 +5890,7 @@ _Pour des instructions plus détaillées, [visitez notre site d’aide](${CONST.
             error: {
                 genericAdd: 'Un problème est survenu lors de l’ajout de ce membre de l’espace de travail',
                 cannotRemove: 'Vous ne pouvez pas vous supprimer vous-même ni supprimer le responsable de l’espace de travail',
-                genericRemove: 'Impossible de supprimer ce membre. Cela peut être dû à un problème avec un autre membre. Veuillez résoudre les erreurs et réessayer.',
+                genericRemove: 'Impossible de supprimer ce membre. Cela peut être dû à un problème avec un autre membre. Veuillez résoudre toutes les erreurs, puis réessayer.',
             },
             addedWithPrimary: 'Certains membres ont été ajoutés avec leurs identifiants principaux.',
             invitedBySecondaryLogin: (secondaryLogin: string) => `Ajouté par la connexion secondaire ${secondaryLogin}.`,
diff --git a/src/languages/it.ts b/src/languages/it.ts
index 8f129ed4..8dcd8860 100644
--- a/src/languages/it.ts
+++ b/src/languages/it.ts
@@ -1096,15 +1096,12 @@ const translations: TranslationDeepObject<typeof en> = {
             if (!added && !updated) {
                 return 'Nessuna categoria è stata aggiunta o aggiornata.';
             }
-
             if (added && updated) {
                 return `${added} ${added === 1 ? 'categoria aggiunta' : 'categorie aggiunte'}, ${updated} ${updated === 1 ? 'categoria aggiornata' : 'categorie aggiornate'}.`;
             }
-
             if (added) {
                 return added === 1 ? 'È stata aggiunta 1 categoria.' : `Sono state aggiunte ${added} categorie.`;
             }
-
             return updated === 1 ? 'È stata aggiornata 1 categoria.' : `Sono state aggiornate ${updated} categorie.`;
         },
         importCompanyCardTransactionsSuccessfulDescription: ({transactions}: {transactions: number}) =>
@@ -5861,7 +5858,7 @@ _Per istruzioni più dettagliate, [visita il nostro sito di assistenza](${CONST.
             error: {
                 genericAdd: "Si è verificato un problema nell'aggiungere questo membro dello spazio di lavoro",
                 cannotRemove: 'Non puoi rimuovere te stessə o il proprietario dello spazio di lavoro',
-                genericRemove: 'Impossibile rimuovere questo membro. Potrebbe essere causato da un problema con un altro membro. Risolvi eventuali errori e riprova.',
+                genericRemove: 'Impossibile rimuovere questo membro. Questo potrebbe essere dovuto a un problema con un altro membro. Risolvi eventuali errori e riprova.',
             },
             addedWithPrimary: 'Alcuni membri sono stati aggiunti con i loro accessi principali.',
             invitedBySecondaryLogin: (secondaryLogin: string) => `Aggiunto dall’accesso secondario ${secondaryLogin}.`,
diff --git a/src/languages/ja.ts b/src/languages/ja.ts
index fb2ed68a..b3f13543 100644
--- a/src/languages/ja.ts
+++ b/src/languages/ja.ts
@@ -1079,15 +1079,12 @@ const translations: TranslationDeepObject<typeof en> = {
             if (!added && !updated) {
                 return 'カテゴリーは追加も更新もされていません。';
             }
-
             if (added && updated) {
                 return `${added}件のカテゴリーを追加し、${updated}件のカテゴリーを更新しました。`;
             }
-
             if (added) {
                 return added === 1 ? 'カテゴリーを1件追加しました。' : `${added}件のカテゴリーを追加しました。`;
             }
-
             return updated === 1 ? 'カテゴリーを1件更新しました。' : `${updated}件のカテゴリーを更新しました。`;
         },
         importCompanyCardTransactionsSuccessfulDescription: ({transactions}: {transactions: number}) =>
@@ -5796,7 +5793,7 @@ _詳しい手順については、[ヘルプサイトをご覧ください](${CO
             error: {
                 genericAdd: 'このワークスペースメンバーを追加する際に問題が発生しました',
                 cannotRemove: '自分自身またはワークスペースのオーナーを削除することはできません',
-                genericRemove: 'このメンバーを削除できませんでした。他のメンバーに問題がある可能性があります。エラーを解決してから再度お試しください。',
+                genericRemove: 'このメンバーを削除できませんでした。他のメンバーに問題がある可能性があります。すべてのエラーを解決してから、もう一度お試しください。',
             },
             addedWithPrimary: '一部のメンバーは、プライマリーログインで追加されました。',
             invitedBySecondaryLogin: (secondaryLogin: string) => `セカンダリログイン${secondaryLogin}によって追加されました。`,
diff --git a/src/languages/nl.ts b/src/languages/nl.ts
index 4effa255..7029e07a 100644
--- a/src/languages/nl.ts
+++ b/src/languages/nl.ts
@@ -1095,15 +1095,12 @@ const translations: TranslationDeepObject<typeof en> = {
             if (!added && !updated) {
                 return 'Er zijn geen categorieën toegevoegd of bijgewerkt.';
             }
-
             if (added && updated) {
                 return `${added} ${added === 1 ? 'categorie' : 'categorieën'} toegevoegd, ${updated} ${updated === 1 ? 'categorie' : 'categorieën'} bijgewerkt.`;
             }
-
             if (added) {
                 return added === 1 ? '1 categorie is toegevoegd.' : `${added} categorieën zijn toegevoegd.`;
             }
-
             return updated === 1 ? '1 categorie is bijgewerkt.' : `${updated} categorieën zijn bijgewerkt.`;
         },
         importCompanyCardTransactionsSuccessfulDescription: ({transactions}: {transactions: number}) =>
@@ -5843,7 +5840,7 @@ _Voor meer gedetailleerde instructies, [bezoek onze help-site](${CONST.NETSUITE_
             error: {
                 genericAdd: 'Er is een probleem opgetreden bij het toevoegen van dit werkruimtelid',
                 cannotRemove: 'Je kunt jezelf of de eigenaar van de werkruimte niet verwijderen',
-                genericRemove: 'Dit lid kon niet worden verwijderd. Dit kan veroorzaakt zijn door een probleem met een ander lid. Los eventuele fouten op en probeer het opnieuw.',
+                genericRemove: 'Kon dit lid niet verwijderen. Dit kan veroorzaakt zijn door een probleem met een ander lid. Los eventuele fouten op en probeer het opnieuw.',
             },
             addedWithPrimary: 'Sommige leden zijn toegevoegd met hun primaire login.',
             invitedBySecondaryLogin: (secondaryLogin: string) => `Toegevoegd door secundair login ${secondaryLogin}.`,
diff --git a/src/languages/pl.ts b/src/languages/pl.ts
index 1ef6ec23..f2854f02 100644
--- a/src/languages/pl.ts
+++ b/src/languages/pl.ts
@@ -1096,15 +1096,12 @@ const translations: TranslationDeepObject<typeof en> = {
             if (!added && !updated) {
                 return 'Nie dodano ani nie zaktualizowano żadnych kategorii.';
             }
-
             if (added && updated) {
                 return `Dodano ${added} ${added === 1 ? 'kategorię' : 'kategorie'}, zaktualizowano ${updated} ${updated === 1 ? 'kategorię' : 'kategorie'}.`;
             }
-
             if (added) {
                 return added === 1 ? 'Dodano 1 kategorię.' : `Dodano ${added} kategorie.`;
             }
-
             return updated === 1 ? 'Zaktualizowano 1 kategorię.' : `Zaktualizowano ${updated} kategorie.`;
         },
         importCompanyCardTransactionsSuccessfulDescription: ({transactions}: {transactions: number}) => (transactions > 1 ? `Dodano ${transactions} transakcji.` : 'Dodano 1 transakcję.'),
@@ -5836,7 +5833,7 @@ _Aby uzyskać bardziej szczegółowe instrukcje, [odwiedź naszą stronę pomocy
             error: {
                 genericAdd: 'Wystąpił problem z dodaniem tego członka przestrzeni roboczej',
                 cannotRemove: 'Nie możesz usunąć siebie ani właściciela przestrzeni roboczej',
-                genericRemove: 'Nie udało się usunąć tego członka. Może to być spowodowane problemem z innym członkiem. Rozwiąż wszelkie błędy i spróbuj ponownie.',
+                genericRemove: 'Nie udało się usunąć tego członka. Może to być spowodowane problemem z innym członkiem. Rozwiąż wszystkie błędy i spróbuj ponownie.',
             },
             addedWithPrimary: 'Niektóre osoby zostały dodane za pomocą swoich głównych loginów.',
             invitedBySecondaryLogin: (secondaryLogin: string) => `Dodane przez dodatkowy login ${secondaryLogin}.`,
diff --git a/src/languages/pt-BR.ts b/src/languages/pt-BR.ts
index 3f33de35..e206cf0f 100644
--- a/src/languages/pt-BR.ts
+++ b/src/languages/pt-BR.ts
@@ -1094,15 +1094,12 @@ const translations: TranslationDeepObject<typeof en> = {
             if (!added && !updated) {
                 return 'Nenhuma categoria foi adicionada ou atualizada.';
             }
-
             if (added && updated) {
                 return `${added} ${added === 1 ? 'categoria' : 'categorias'} adicionada${added === 1 ? '' : 's'}, ${updated} ${updated === 1 ? 'categoria' : 'categorias'} atualizada${updated === 1 ? '' : 's'}.`;
             }
-
             if (added) {
                 return added === 1 ? '1 categoria foi adicionada.' : `${added} categorias foram adicionadas.`;
             }
-
             return updated === 1 ? '1 categoria foi atualizada.' : `${updated} categorias foram atualizadas.`;
         },
         importCompanyCardTransactionsSuccessfulDescription: ({transactions}: {transactions: number}) =>
@@ -5842,7 +5839,7 @@ _Para instruções mais detalhadas, [visite nossa central de ajuda](${CONST.NETS
             error: {
                 genericAdd: 'Ocorreu um problema ao adicionar este membro do workspace',
                 cannotRemove: 'Você não pode remover a si mesmo nem o proprietário do workspace',
-                genericRemove: 'Não foi possível remover este membro. Isso pode ser causado por um problema com outro membro. Resolva os erros e tente novamente.',
+                genericRemove: 'Não foi possível remover este membro. Isso pode ter sido causado por um problema com outro membro. Resolva quaisquer erros e tente novamente.',
             },
             addedWithPrimary: 'Alguns membros foram adicionados com seus logins principais.',
             invitedBySecondaryLogin: (secondaryLogin: string) => `Adicionado pelo login secundário ${secondaryLogin}.`,
diff --git a/src/languages/zh-hans.ts b/src/languages/zh-hans.ts
index 0d8b6e85..a5962ac2 100644
--- a/src/languages/zh-hans.ts
+++ b/src/languages/zh-hans.ts
@@ -5691,7 +5691,7 @@ _如需更详细的说明,请[访问我们的帮助网站](${CONST.NETSUITE_IM
             error: {
                 genericAdd: '添加此工作区成员时出现问题',
                 cannotRemove: '你无法将自己或工作区所有者移除',
-                genericRemove: '无法移除此成员。这可能是由其他成员的问题引起的。请解决所有错误后重试。',
+                genericRemove: '无法移除此成员。可能是由另一位成员的问题导致的。请先解决所有错误,然后重试。',
             },
             addedWithPrimary: '某些成员已通过其主登录名添加。',
             invitedBySecondaryLogin: (secondaryLogin: string) => `由次要登录账号 ${secondaryLogin} 添加。`,

Note

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

View workflow run

@Pujan92
Copy link
Copy Markdown
Contributor

Pujan92 commented Apr 8, 2026

@MelvinBot Plz mark it ready for review

@MelvinBot
Copy link
Copy Markdown
Contributor Author

🤖 I attempted to mark this PR as ready for review, but I don't have the necessary permissions to execute that action in this environment.

You can mark it as ready for review yourself by:

  1. Clicking "Ready for review" button at the bottom of the PR page, or
  2. Running: gh pr ready 87249 --repo Expensify/App

@stitesExpensify stitesExpensify self-requested a review April 8, 2026 13:51
@stitesExpensify stitesExpensify marked this pull request as ready for review April 16, 2026 16:09
@stitesExpensify stitesExpensify requested a review from a team as a code owner April 16, 2026 16:09
@melvin-bot melvin-bot Bot requested review from JmillsExpensify and Pujan92 and removed request for a team April 16, 2026 16:09
@melvin-bot
Copy link
Copy Markdown

melvin-bot Bot commented Apr 16, 2026

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

@Pujan92
Copy link
Copy Markdown
Contributor

Pujan92 commented Apr 16, 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

@Pujan92
Copy link
Copy Markdown
Contributor

Pujan92 commented Apr 16, 2026

@stitesExpensify it looks like now a BE is removing the members partially, even though there is an error thrown for DeleteMembersFromWorkspace. It can be seen with the latest api response from OpenWorkspaceMembersPage.

Screen.Recording.2026-04-16.at.23.02.42.mov

@stitesExpensify
Copy link
Copy Markdown
Contributor

Hey @Pujan92 to clarify, are you saying that the backend functionality is no longer correct? or that we need to change our frontend approach?

@Pujan92
Copy link
Copy Markdown
Contributor

Pujan92 commented Apr 21, 2026

are you saying that the backend functionality is no longer correct

I think so, can you plz check why backend is removing the members partially for DeleteMembersFromWorkspace api, even though it is responding with errors.

@stitesExpensify
Copy link
Copy Markdown
Contributor

FYI I am going OOO, I will look into this next week

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.

4 participants