fix: requires validate when opening bank account #49230

daledah · 2024-09-15T20:49:44Z

Details

Fixed Issues

$ #48041
PROPOSAL: #48041 (comment)

Tests

Login with a new Account
Go to settings > wallet
Verify that: Add bank account button is not disabled
Click on Add bank account button
Verify that: Validation modal appears
Click on Enable wallet button
Verify that: Add bank account button is not disabled
Click on Add bank account button
Verify that: Validation modal appears

Verify that no errors appear in the JS console

Offline tests

QA Steps

Login with a new Account
Go to settings > wallet
Verify that: Add bank account button is not disabled
Click on Add bank account button
Verify that: Validation modal appears
Click on Enable wallet button
Verify that: Add bank account button is not disabled
Click on Add bank account button
Verify that: Validation modal appears

Verify that no errors appear in the JS console

PR Author Checklist

Screenshots/Videos

Android: Native

Screen.Recording.2024-09-18.at.18.10.51.mov

Android: mWeb Chrome

Screen.Recording.2024-09-18.at.18.12.56.mov

iOS: Native

Screen.Recording.2024-09-18.at.23.29.02.mov

iOS: mWeb Safari

Screen.Recording.2024-09-18.at.23.30.55.mov

MacOS: Chrome / Safari

Screen.Recording.2024-09-18.at.17.48.10.mov

MacOS: Desktop

Screen.Recording.2024-09-18.at.23.31.26.mov

melvin-bot · 2024-09-18T10:47:47Z

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

daledah · 2024-09-18T16:46:29Z

@hungvu193 I used the ValidateCodeForm that you added in #48628. Just one question: Why do we auto-remove the error when we have one in here:

App/src/components/ValidateCodeActionModal/ValidateCodeForm/BaseValidateCodeForm.tsx

Lines 131 to 137 in 8d19726

    
           useEffect(() => { 
        
               if (!validateError) { 
        
                   return; 
        
               } 
        
               clearError(); 
        
               // eslint-disable-next-line react-compiler/react-compiler, react-hooks/exhaustive-deps 
        
           }, [clearError, validateError]);

I see that in other places, we show the error after the modal is closed, but why don't we show the error directly in the form, so the user don't have to open the modal again?

hungvu193 · 2024-09-19T02:36:19Z

I see that in other places, we show the error after the modal is closed, but why don't we show the error directly in the form, so the user don't have to open the modal again?

Yeah, we have a plan to change that behavior in here, we should clear the error when modal is closed.

daledah · 2024-09-19T07:16:41Z

@jjcoffee According to #49230 (comment), should we hold until #49270 is resolved until we can continue on this one? cc @hungvu193

jjcoffee · 2024-09-19T07:28:08Z

should we hold until #49270 is resolved

@daledah Thanks for bringing that up! I don't think we need to hold on that since it doesn't affect the overall fix here.

jjcoffee · 2024-09-19T08:18:23Z

@daledah Didn't we agree to use ValidateCodeActionModal?

daledah · 2024-09-19T09:40:09Z

@jjcoffee I tried using ValidateCodeActionModal in this commit but it ended up causing a lot of unexpected bugs, so I had to come back to the original solution.

jjcoffee · 2024-09-19T11:57:52Z

@daledah Following the flow Enable wallet -> Add bank account, I think I'd expect that once the validate code is entered we are immediately navigated to the next step, rather than having to click Add bank account again.

jjcoffee · 2024-09-19T11:57:57Z

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
- MacOS: Desktop
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 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: Native

android-app-2024-09-19_14.15.23.mp4

Android: mWeb Chrome

android-chrome-2024-09-19_14.17.18.mp4

iOS: Native

ios-app-2024-09-19_14.01.39.mp4

iOS: mWeb Safari

ios-safari-2024-09-19_13.55.34.mp4

MacOS: Chrome / Safari

desktop-chrome-2024-09-19_14.04.03.mp4

MacOS: Desktop

desktop-app-2024-09-19_14.12.43.mp4

src/SCREENS.ts

jjcoffee · 2024-09-19T12:27:19Z

Tagging @Expensify/design to take a look! Do we need to tag anyone else to review the copy?

jjcoffee · 2024-09-19T12:29:30Z

Minor bug: Refreshing after opening the validate modal via Enable wallet and then tapping the back button doesn't take us back to the Enable wallet page.

desktop-chrome-enable-wallet-2024-09-19_14.29.11.mp4

jjcoffee · 2024-09-19T12:36:00Z

src/pages/AddPersonalBankAccountPage.tsx

@@ -52,7 +53,7 @@ function AddPersonalBankAccountPage({personalBankAccount, plaidData}: AddPersona
            } else if (shouldContinue && onSuccessFallbackRoute) {
                PaymentMethods.continueSetup(onSuccessFallbackRoute);
            } else {
-                Navigation.goBack();
+                Navigation.navigate(ROUTES.SETTINGS_WALLET);


I'm not sure I understand this change, can you explain?

shawnborton · 2024-09-19T12:58:26Z

Looks pretty good to me 👍

shawnborton · 2024-09-20T05:40:47Z

Could have sworn I saw @dannymcclain leave some feedback in another PR that we could use some more spacing between the inputs and the "Didn't receive a code?" line:

Does that sound right?

daledah · 2024-09-20T06:27:48Z

@jjcoffee I think the behavior in #49230 (comment) is expected, when we reload the page, the following logic is triggered, as isFirstRouteInNavigator becomes true

App/src/libs/Navigation/Navigation.ts

Lines 226 to 229 in 6510ae4

    
           if (shouldEnforceFallback || (isFirstRouteInNavigator && fallbackRoute)) { 
        
               navigate(fallbackRoute, CONST.NAVIGATION.TYPE.UP); 
        
               return; 
        
           }

jjcoffee · 2024-09-20T07:22:23Z

@jjcoffee I think the behavior in #49230 (comment) is expected, when we reload the page, the following logic is triggered, as isFirstRouteInNavigator becomes true

@daledah Hmm it doesn't happen when tapping Add bank account directly from the settings screen though, so there's some inconsistency there. Can you think of a way of handling it?

daledah · 2024-09-20T11:00:22Z

@daledah Hmm it doesn't happen when tapping Add bank account directly from the settings screen though, so there's some inconsistency there. Can you think of a way of handling it?

@jjcoffee Can you share a screenshot for this? For me both places has the same behavior: The screen navigates to wallet page after a reload.

jjcoffee · 2024-09-20T11:23:06Z

@daledah Ah yeah sorry I think I got confused with something else - the Add bank account flow only has one step so it's a bit different. I still think it's worth fixing, if it's possible.

dannymcclain · 2024-09-20T13:19:48Z

Could have sworn I saw @dannymcclain leave some feedback in another PR that we could use some more spacing between the inputs and the "Didn't receive a code?" line
Does that sound right?

Yes I did indeed! I think a gap of 20px between the input lines and the Didn’t receive a magic code? line feels better. I also still don't understand why the Verify button isn't a footer button like almost all our other big buttons in RHPs. I feel like I'd expect this screen to look like this:

shawnborton · 2024-09-20T13:35:32Z

Yeah that looks great! I agree, let's do that.

dubielzyk-expensify · 2024-09-23T07:09:28Z

Agree bottom positioning of the button looks better :)

daledah · 2024-09-24T06:12:03Z

@shawnborton I updated, looks pretty good now.

dubielzyk-expensify · 2024-09-24T09:27:52Z

That looks good to me. If @dannymcclain gives it the thumbs up, then I think we're good here

jjcoffee · 2024-09-24T09:53:49Z

@daledah Is this issue resolved?

daledah · 2024-09-24T12:20:56Z

@jjcoffee I updated. Almost forgot about that! Thanks for the reminder!

Screen.Recording.2024-09-24.at.19.20.10.mov

jjcoffee · 2024-09-24T12:32:30Z

@daledah Thanks! There's still a brief flash of the first step however, anything you can do about that?

daledah · 2024-09-25T04:58:32Z

@jjcoffee I don't think we can work around this, as the logic uses asynchronous Onyx data to display components. Maybe we can delay the action, so the steps will show up a little bit later, like this:

Screen.Recording.2024-09-25.at.11.57.34.mov

What do you think?

daledah · 2024-09-25T05:13:52Z

@jjcoffee #49230 (comment) This happens in wallet page even without opening the RHP, which caused by WalletEmptyState here being displayed as shouldShowEmptyState here is true before Onyx data was loaded.

Screen.Recording.2024-09-25.at.12.14.48.mov

jjcoffee · 2024-09-25T09:18:17Z

I don't think we can work around this, as the logic uses asynchronous Onyx data to display components.

Hmm, testing locally I actually don't see the brief flash. I guess we could also just immediately load the validation page when tapping Enable wallet, rather than after tapping Add bank account once the Enable wallet modal opens (it's actually maybe more frustrating that way!). I don't know if @Expensify/design would have any objections?

daledah added 6 commits September 16, 2024 03:47

fix: requires validate when opening bank account

85c7680

Merge branch 'main' into fix/48041

a7c1e49

fix: add Verify account page

f7310b1

Merge branch 'main' into fix/48041

fc2bd89

fix: navigate when add bank account

a5b24fe

fix: request code on open page

56327f6

daledah marked this pull request as ready for review September 18, 2024 10:47

daledah requested a review from a team as a code owner September 18, 2024 10:47

melvin-bot bot requested a review from jjcoffee September 18, 2024 10:47

melvin-bot bot removed the request for review from a team September 18, 2024 10:47

daledah marked this pull request as draft September 18, 2024 11:04

fix: change fallback route

b0fc0d7

daledah marked this pull request as ready for review September 18, 2024 16:40

This comment was marked as resolved.

Sign in to view

jjcoffee reviewed Sep 19, 2024

View reviewed changes

src/SCREENS.ts Show resolved Hide resolved

jjcoffee reviewed Sep 19, 2024

View reviewed changes

Merge branch 'main' into fix/48041

88aa696

fix: redirect to chat page when reload

d9882a3

cretadn22 mentioned this pull request Sep 20, 2024

[$250] Web - Pay - Not here page opens when Gmail user Pay with Expensify #49523

Open

6 tasks

fix: ui

e579824

getusha mentioned this pull request Sep 24, 2024

[$250] Use new ValidateCodeActionModal component in as many places as possible #49270

Open

fix: refactor withOnyx

bcfdcf4

This comment was marked as off-topic.

Sign in to view

feat: enable payment when navigate back

47e815f

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

fix: requires validate when opening bank account #49230

fix: requires validate when opening bank account #49230

daledah commented Sep 15, 2024 •

edited

Loading

melvin-bot bot commented Sep 18, 2024

daledah commented Sep 18, 2024

hungvu193 commented Sep 19, 2024

daledah commented Sep 19, 2024

jjcoffee commented Sep 19, 2024

jjcoffee commented Sep 19, 2024

daledah commented Sep 19, 2024 •

edited

Loading

jjcoffee commented Sep 19, 2024

jjcoffee commented Sep 19, 2024 •

edited

Loading

This comment was marked as resolved.

jjcoffee commented Sep 19, 2024 •

edited

Loading

jjcoffee commented Sep 19, 2024

jjcoffee Sep 19, 2024

shawnborton commented Sep 19, 2024

shawnborton commented Sep 20, 2024

daledah commented Sep 20, 2024

jjcoffee commented Sep 20, 2024

daledah commented Sep 20, 2024

jjcoffee commented Sep 20, 2024

dannymcclain commented Sep 20, 2024

shawnborton commented Sep 20, 2024

dubielzyk-expensify commented Sep 23, 2024

daledah commented Sep 24, 2024

dubielzyk-expensify commented Sep 24, 2024

This comment was marked as off-topic.

jjcoffee commented Sep 24, 2024

daledah commented Sep 24, 2024

jjcoffee commented Sep 24, 2024

daledah commented Sep 25, 2024

daledah commented Sep 25, 2024 •

edited

Loading

jjcoffee commented Sep 25, 2024

fix: requires validate when opening bank account #49230

Are you sure you want to change the base?

fix: requires validate when opening bank account #49230

Conversation

daledah commented Sep 15, 2024 • edited Loading

Details

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

melvin-bot bot commented Sep 18, 2024

daledah commented Sep 18, 2024

hungvu193 commented Sep 19, 2024

daledah commented Sep 19, 2024

jjcoffee commented Sep 19, 2024

jjcoffee commented Sep 19, 2024

daledah commented Sep 19, 2024 • edited Loading

jjcoffee commented Sep 19, 2024

jjcoffee commented Sep 19, 2024 • edited Loading

Reviewer Checklist

Screenshots/Videos

This comment was marked as resolved.

jjcoffee commented Sep 19, 2024 • edited Loading

jjcoffee commented Sep 19, 2024

jjcoffee Sep 19, 2024

Choose a reason for hiding this comment

shawnborton commented Sep 19, 2024

shawnborton commented Sep 20, 2024

daledah commented Sep 20, 2024

jjcoffee commented Sep 20, 2024

daledah commented Sep 20, 2024

jjcoffee commented Sep 20, 2024

dannymcclain commented Sep 20, 2024

shawnborton commented Sep 20, 2024

dubielzyk-expensify commented Sep 23, 2024

daledah commented Sep 24, 2024

dubielzyk-expensify commented Sep 24, 2024

This comment was marked as off-topic.

jjcoffee commented Sep 24, 2024

daledah commented Sep 24, 2024

jjcoffee commented Sep 24, 2024

daledah commented Sep 25, 2024

daledah commented Sep 25, 2024 • edited Loading

jjcoffee commented Sep 25, 2024

daledah commented Sep 15, 2024 •

edited

Loading

daledah commented Sep 19, 2024 •

edited

Loading

jjcoffee commented Sep 19, 2024 •

edited

Loading

jjcoffee commented Sep 19, 2024 •

edited

Loading

daledah commented Sep 25, 2024 •

edited

Loading