Skip to content

Automatically launch E-card enrollment after changing workspace to supported currency - #100667

Open
chuckdries wants to merge 3 commits into
mainfrom
chuckdries/e-card-rhp
Open

Automatically launch E-card enrollment after changing workspace to supported currency#100667
chuckdries wants to merge 3 commits into
mainfrom
chuckdries/e-card-rhp

Conversation

@chuckdries

@chuckdries chuckdries commented Sep 8, 2026

Copy link
Copy Markdown
Contributor

Explanation of Change

Fixed Issues

If the user tries to enroll Expensify Card on a workspace with an unsupported currency, and they don't have access to link a feed from a different workspace, the current behavior is to prompt them to change their workspace currency. Then, when they do this, they must click the CTA again to launch the enrollment flow.

This PR adds a shouldStartExpensifyCardEnrollment parameter to the workspaces/:policyID/overview/currency route which will, when the user selects a supported Expensify card currency, automatically enter the bank account setup to being the enrollment flow.

This PR also adds an empty state to the feed list picker. If the user has access to an existing Expensify card workspace feed, but loses access to that feed while the picker is open, we now show an empty state rather than a blank panel.

$ #99723 (comment)
PROPOSAL:

Tests

Non-USD workspace, has no existing workspace feeds or eligible bank accounts

  1. Create a user who is an admin on a workspace whose currency is not USD, GBP or EUR.
  2. Enable the Expensify Card feature
  3. Go to workspace > Expensify Card and press Issue new card
  4. In the modal, press Update workspace currency
  5. Select USD, GBP, or EUR from the currency picker
  6. Confirm that, after a moment, you are taken to the "Add bank account" page

Non-USD workspace, has no existing workspace feeds, does have eligible bank account

  1. Start with a user who has a verified business bank account already set up for some reason
  2. Create a workspace whose currency is not USD, GBP or EUR
  3. Enable the Expensify Card feature
  4. Go to workspace > Expensify Card and press Issue new card
  5. In the modal, press Update workspace currency
  6. Select USD, GBP, or EUR from the currency picker
  7. Confirm that you are taken to the "Choose bank account" page

Non-USD workspace, has eligible feed, is removed as admin from existing feed

  1. Start with a user A who is an admin on a workspace A that already has Expensify Card configured on it
  2. Create a workspace B whose currency is not USD, GBP or EUR
  3. Enable the Expensify Card feature
  4. Go to workspace > Expensify Card and press Issue new card
  5. Confirm you are shown the other workspace in the RHP
  6. As another admin on workspace A in a different browser, remove user A's admin permission on workspace A
  7. Confirm that they see the empty illustration
  • 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
  • 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 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 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)
  • 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.
  • 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

Non-USD workspace, has no existing workspace feeds or eligible bank accounts
auto.start.e-card.new.VBA.enrollment.after.currency.change.mp4
Non-USD workspace, has no existing workspace feeds, does have eligible bank account
auto-start.e-card.enrollment.after.currency.change.mp4
Non-USD workspace, has eligible feed, is removed as admin from existing feed
e-card.select-feed.empty.state.mp4

@chuckdries chuckdries self-assigned this Sep 8, 2026
@chuckdries
chuckdries requested review from a team as code owners September 8, 2026 23:37
@melvin-bot
melvin-bot Bot requested a review from Julesssss September 8, 2026 23:37
@melvin-bot

melvin-bot Bot commented Sep 8, 2026

Copy link
Copy Markdown

@Julesssss 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 trjExpensify and removed request for a team September 8, 2026 23:37
@OSBotify

OSBotify commented Sep 8, 2026

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 8842d6c3..c7de4b27 100644
--- a/src/languages/de.ts
+++ b/src/languages/de.ts
@@ -6255,6 +6255,8 @@ _Für ausführlichere Anweisungen [besuchen Sie unsere Hilfeseite](${CONST.NETSU
             csvColumnType: 'Typ',
             csvColumnLimitType: 'Limittyp',
             csvColumnLimit: 'Limit',
+            noCardFeedsAvailable: 'Keine Kartenfeeds verfügbar',
+            noCardFeedsAvailableDescription: 'Für diesen Workspace sind keine Kartenfeeds verfügbar.',
         },
         categories: {
             deleteCategories: 'Kategorien löschen',
diff --git a/src/languages/el.ts b/src/languages/el.ts
index c5519502..893a82ae 100644
--- a/src/languages/el.ts
+++ b/src/languages/el.ts
@@ -6368,6 +6368,8 @@ _Για πιο αναλυτικές οδηγίες, [επισκεφθείτε τ
             statusActive: 'Ενεργό',
             statusInactive: 'Ανενεργό',
             remaining: 'Υπόλοιπο',
+            noCardFeedsAvailable: 'Δεν υπάρχουν διαθέσιμες ροές καρτών',
+            noCardFeedsAvailableDescription: 'Δεν υπάρχουν διαθέσιμες ροές καρτών για αυτόν τον χώρο εργασίας.',
         },
         categories: {
             deleteCategories: 'Διαγραφή κατηγοριών',
diff --git a/src/languages/es.ts b/src/languages/es.ts
index 98fcf61d..7d5d40cb 100644
--- a/src/languages/es.ts
+++ b/src/languages/es.ts
@@ -6126,6 +6126,8 @@ ${amount} para ${merchant} - ${date}`,
             oneMoreStepDescription: 'Parece que tenemos que verificar manualmente tu cuenta bancaria. Dirígete a Concierge, donde te esperan las instrucciones.',
             gotIt: 'Entendido',
             goToConcierge: 'Ir a Concierge',
+            noCardFeedsAvailable: 'No hay feeds de tarjetas disponibles',
+            noCardFeedsAvailableDescription: 'No hay feeds de tarjetas disponibles para este espacio de trabajo.',
         },
         categories: {
             deleteCategories: 'Eliminar categorías',
diff --git a/src/languages/fr.ts b/src/languages/fr.ts
index 8643d549..8a024958 100644
--- a/src/languages/fr.ts
+++ b/src/languages/fr.ts
@@ -6261,6 +6261,8 @@ _Pour des instructions plus détaillées, [visitez notre site d’aide](${CONST.
             csvColumnType: 'Type',
             csvColumnLimitType: 'Type de limite',
             csvColumnLimit: 'Limite',
+            noCardFeedsAvailable: 'Aucun flux de carte disponible',
+            noCardFeedsAvailableDescription: 'Aucun flux de carte n’est disponible pour cet espace de travail.',
         },
         categories: {
             deleteCategories: 'Supprimer des catégories',
diff --git a/src/languages/it.ts b/src/languages/it.ts
index bc3dfb63..93ffd3ba 100644
--- a/src/languages/it.ts
+++ b/src/languages/it.ts
@@ -6213,6 +6213,8 @@ _Per istruzioni più dettagliate, [visita il nostro sito di assistenza](${CONST.
             csvColumnType: 'Tipo',
             csvColumnLimitType: 'Tipo di limite',
             csvColumnLimit: 'Limite',
+            noCardFeedsAvailable: 'Nessun feed carta disponibile',
+            noCardFeedsAvailableDescription: 'Non sono disponibili flussi di carte per questo spazio di lavoro.',
         },
         categories: {
             deleteCategories: 'Elimina categorie',
diff --git a/src/languages/ja.ts b/src/languages/ja.ts
index 4c45895e..c1ae2521 100644
--- a/src/languages/ja.ts
+++ b/src/languages/ja.ts
@@ -6141,6 +6141,8 @@ _詳しい手順については、[ヘルプサイトをご覧ください](${CO
             csvColumnType: 'タイプ',
             csvColumnLimitType: '限度タイプ',
             csvColumnLimit: '限度額',
+            noCardFeedsAvailable: '利用できるカードフィードがありません',
+            noCardFeedsAvailableDescription: 'このワークスペースで利用できるカードフィードはありません。',
         },
         categories: {
             deleteCategories: 'カテゴリを削除',
diff --git a/src/languages/nl.ts b/src/languages/nl.ts
index c83c320f..3d91f0f9 100644
--- a/src/languages/nl.ts
+++ b/src/languages/nl.ts
@@ -6204,6 +6204,8 @@ _Voor meer gedetailleerde instructies, [bezoek onze help-site](${CONST.NETSUITE_
             csvColumnType: 'Type',
             csvColumnLimitType: 'Limiettype',
             csvColumnLimit: 'Limiet',
+            noCardFeedsAvailable: 'Geen kaartfeeds beschikbaar',
+            noCardFeedsAvailableDescription: 'Er zijn geen kaartfeeds beschikbaar voor deze workspace.',
         },
         categories: {
             deleteCategories: 'Categorieën verwijderen',
diff --git a/src/languages/pl.ts b/src/languages/pl.ts
index 6367f138..563c158e 100644
--- a/src/languages/pl.ts
+++ b/src/languages/pl.ts
@@ -6229,6 +6229,8 @@ _Aby uzyskać bardziej szczegółowe instrukcje, [odwiedź naszą stronę pomocy
             csvColumnType: 'Typ',
             csvColumnLimitType: 'Typ limitu',
             csvColumnLimit: 'Limit',
+            noCardFeedsAvailable: 'Brak dostępnych kanałów kart',
+            noCardFeedsAvailableDescription: 'Dla tego obszaru roboczego nie ma dostępnych żadnych kanałów kart.',
         },
         categories: {
             deleteCategories: 'Usuń kategorie',
diff --git a/src/languages/pt-BR.ts b/src/languages/pt-BR.ts
index c90c4510..344f3749 100644
--- a/src/languages/pt-BR.ts
+++ b/src/languages/pt-BR.ts
@@ -6204,6 +6204,8 @@ _Para instruções mais detalhadas, [visite nossa central de ajuda](${CONST.NETS
             csvColumnType: 'Tipo',
             csvColumnLimitType: 'Tipo de limite',
             csvColumnLimit: 'Limite',
+            noCardFeedsAvailable: 'Nenhum feed de cartão disponível',
+            noCardFeedsAvailableDescription: 'Não há feeds de cartão disponíveis para este workspace.',
         },
         categories: {
             deleteCategories: 'Excluir categorias',
diff --git a/src/languages/zh-hans.ts b/src/languages/zh-hans.ts
index 3e0c540c..ebf6b7b9 100644
--- a/src/languages/zh-hans.ts
+++ b/src/languages/zh-hans.ts
@@ -5998,6 +5998,8 @@ _如需更详细的说明,请[访问我们的帮助网站](${CONST.NETSUITE_IM
             csvColumnType: '类型',
             csvColumnLimitType: '限额类型',
             csvColumnLimit: '限额',
+            noCardFeedsAvailable: '没有可用的卡片流水',
+            noCardFeedsAvailableDescription: '此工作区暂无可用的卡片流水。',
         },
         categories: {
             deleteCategories: '删除类别',

Note

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

View workflow run

Comment thread src/pages/workspace/WorkspaceOverviewCurrencyPage.tsx Outdated
@codecov

codecov Bot commented Sep 8, 2026

Copy link
Copy Markdown

Codecov Report

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

Files with missing lines Coverage Δ
.../pages/workspace/WorkspaceOverviewCurrencyPage.tsx 84.21% <100.00%> (+84.21%) ⬆️
.../workspace/invoices/WorkspaceInvoiceVBASection.tsx 68.29% <ø> (ø)
.../workspace/workflows/tabs/WorkflowsPaymentsTab.tsx 75.53% <ø> (ø)
src/libs/CardUtils.ts 85.57% <85.71%> (+<0.01%) ⬆️
...nsifyCard/WorkspaceExpensifyCardPageEmptyState.tsx 0.00% <0.00%> (ø)
src/ROUTES.ts 28.05% <16.66%> (+0.16%) ⬆️
...ifyCard/WorkspaceExpensifyCardFeedSelectorPage.tsx 59.78% <64.28%> (+59.78%) ⬆️
... and 674 files with indirect coverage changes

@Eskalifer1

Copy link
Copy Markdown
Contributor

@codex 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: 2f77e541ba

ℹ️ 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 on lines +103 to +105
Navigation.navigate(
getExpensifyCardEnrollmentRoute(policy.id, policy.outputCurrency, isUkEuCurrencySupported, bankAccountList, supportedCountriesByCurrency, reimbursementAccount?.achData),
);

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 Clear stale card form before direct enrollment

When a workspace has no accessible feeds but does have an eligible bank account, this now navigates directly to WorkspaceExpensifyCardBankAccounts without calling clearIssueNewCardFormData(). Previously, the eligible-account path passed through the feed selector and cleared the global ISSUE_NEW_EXPENSIFY_CARD_FORM; the bank-account page's verified handler does not clear it before opening the issue-card flow. Consequently, after abandoning an issue-card form in another workspace, enrolling this workspace can reuse those stale form values. Clear the form before either newly direct enrollment path, or in the bank-account page before it launches the issue flow.

Useful? React with 👍 / 👎.

Comment on lines +250 to +256
<BlockingView
icon={illustrations.Telescope}
iconWidth={variables.emptyListIconWidth}
iconHeight={variables.emptyListIconHeight}
title={translate('workspace.expensifyCard.noCardFeedsAvailable')}
subtitle={translate('workspace.expensifyCard.noCardFeedsAvailableDescription')}
/>

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.

Should we add here addBottomSafeAreaPadding?

Comment on lines +249 to +283
let feedListContent = (
<BlockingView
icon={illustrations.Telescope}
iconWidth={variables.emptyListIconWidth}
iconHeight={variables.emptyListIconHeight}
title={translate('workspace.expensifyCard.noCardFeedsAvailable')}
subtitle={translate('workspace.expensifyCard.noCardFeedsAvailableDescription')}
/>
);
if (issueNewCardAndOtherFeedsFooter) {
feedListContent = (
<ScrollView
addBottomSafeAreaPadding
style={styles.flex1}
keyboardShouldPersistTaps="handled"
>
{issueNewCardAndOtherFeedsFooter}
</ScrollView>
);
}
if (primaryFeeds.length > 0) {
feedListContent = (
<SelectionList
ListItem={SingleSelectListItem}
onSelectRow={selectFeed}
data={primaryListData}
alternateNumberOfSupportedLines={2}
initiallyFocusedItemKey={lastSelectedExpensifyCardFeedID.toString()}
addBottomSafeAreaPadding
listFooterContent={issueNewCardAndOtherFeedsFooter}
onDismissError={onDismissError}
/>
);
}

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.

The three sequential reassignments read backwards: the case that actually wins (primaryFeeds.length > 0) is written last, so working out what renders means mentally running all three branches. Both the BlockingView and the ScrollView elements are also built on every render and then thrown away. A small renderFeedListContent() with early returns, in priority order, would say the same thing more directly.

Comment on lines +66 to +68
Navigation.navigate(
getExpensifyCardEnrollmentRoute(policy.id, item.currencyCode, isUkEuCurrencySupported, bankAccountList, supportedCountriesByCurrency, reimbursementAccount?.achData),
);

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.

The currency page stays on the stack here. getExpensifyCardEnrollmentRoute can return WORKSPACE_EXPENSIFY_CARD_BANK_ACCOUNT, which has no backTo and whose header calls a plain Navigation.goBack(), so backing out of the settlement account screen drops the user onto the currency picker they just used rather than the Expensify Card page. The isForcedToChangeCurrency branch a few lines below already handles this with forceReplace: true.

2026-09-09.12.59.54.mov

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

Let's also complete this Verify that no errors appear in the JS console

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

I was able to repro this strange behaviour with input suggestion:

2026-09-09.13.21.56.mov

I think it will be fixed with forceReplace(#100667 (comment))

@Eskalifer1

Copy link
Copy Markdown
Contributor

Reviewer Checklist

  • I have verified the author checklist is complete (all boxes are checked off).
  • I verified the correct issue is linked in the ### Fixed Issues section above
  • I verified testing steps are clear and they cover the changes made in this PR
    • I verified the steps for local testing are in the Tests section
    • I verified the steps for Staging and/or Production testing are in the QA steps section
    • I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
    • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
  • I checked that screenshots or videos are included for tests on all platforms
  • I included screenshots or videos for tests on all platforms
  • I verified that the composer does not automatically focus or open the keyboard on mobile unless explicitly intended. This includes checking that returning the app from the background does not unexpectedly open the keyboard.
  • I verified tests pass on all platforms & I tested again on:
    • Android: HybridApp
    • Android: mWeb Chrome
    • iOS: HybridApp
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
  • If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
  • I verified proper code patterns were followed (see Reviewing the code)
    • I verified that comments were added to code that is not self explanatory
    • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
    • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • I verified that this PR follows the guidelines as stated in the Review Guidelines
  • I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
  • If a new component is created I verified that:
    • A similar component doesn't exist in the codebase
    • All props are defined accurately
    • The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
    • The only data being stored in the state is data necessary for rendering and nothing else
    • The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
  • If a new CSS style is added I verified that:
    • A similar style doesn't already exist
    • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)
  • If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
  • If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
  • If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
  • If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
  • If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
    • I verified that all the inputs inside a form are aligned with each other.
    • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
  • For any bug fix or new feature in this PR, I verified that sufficient unit tests are included to prevent regressions in this flow.
  • If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
  • I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: HybridApp
100667-android-native-1.mov
100667-android-native-2.mov
100667-android-native-3.mov
Android: mWeb Chrome
100667-android-web-1.mov
100667-android-web-2.mov
100667-android-web-3.mov
iOS: HybridApp
100667-ios-native-1.mov
100667-ios-native-2.mov
100667-ios-native-3.mov
iOS: mWeb Safari
100667-ios-web-1.mov
100667-ios-web-2.mov
100667-ios-web-3.mov
MacOS: Chrome / Safari
100667-web-1.mov
100667-web-2.mov
100667-web-3.mov

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.

3 participants