Fix: Unable to confirm on double check Personal info page, error appears

[tienifr]

Details

This PR shows detailed error from Onfido if possible instead of the generic one.

Fixed Issues

$ #38201
PROPOSAL: #38201 (comment)

Tests

1. Go to Workspace > Bank account > Connect manually.
2. Select Connect manually.
3. Enter 011401533 and 1111222233331111 for Routing number and Account number.
4. Enter First and Last for first name and last name.
5. Enter random data on the rest of the fields.
6. On double check Personal info, press Confirm.
7. Verify no error shows

• Verify that no errors appear in the JS console

Offline tests

NA

QA Steps

1. Go to Workspace > Bank account > Connect manually.
2. Select Connect manually.
3. Enter 011401533 and 1111222233331111 for Routing number and Account number.
4. Enter First and Last for first name and last name.
5. Enter random data on the rest of the fields.
6. On double check Personal info, press Confirm.
7. Verify no error shows

• 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 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 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
    • If any non-english text was added/modified, I verified the translation was requested/reviewed 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.js 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 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.

Screenshots/Videos

Android: Native

Screen.Recording.2024-03-27.at.12.14.34-compressed.mov

Android: mWeb Chrome

Screen.Recording.2024-03-27.at.12.15.55-compressed.mov

iOS: Native

Screen.Recording.2024-03-27.at.12.08.02-compressed.mov

iOS: mWeb Safari

Screen.Recording.2024-03-27.at.12.08.39-compressed.mov

MacOS: Chrome / Safari

Screen.Recording.2024-03-27.at.03.06.57-compressed.mov

MacOS: Desktop

Screen.Recording.2024-03-27.at.03.06.57-compressed.mov

[melvin-bot]

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

[tienifr]

@s77rt Do you have any hint how to reproduce Onfido error on dev?

[s77rt]

@tienifr No not really as I was not able to reproduce on dev, not sure why. Were you able to see what errors Onfido returns? Were the error messages based on user selected language?

[tienifr]

Were you able to see what errors Onfido returns?

I couldn't.

Were the error messages based on user selected language?

No, it's always in English.

I did try some validation errors but they are all catched by our BE.

[s77rt]

Something is confusing, how did you find out that error messages are in English if you were not able to see any error?

[s77rt]

@tienifr ^

[tienifr]

Check today.

[s77rt]

Any updates here?

[tienifr]

@s77rt I found the root problem of this:

The Content-Security-Policy set in the backend is lacking https://sdk.onfido.com/v14/Onfido.is endpoint:

This happens on both staging and production. This is very critical since access to Onfido SDK is no longer working. And this requires a fix the backend. There's a suggested solution by Onfido here. It has nothing to do with the personal data.

[tienifr]

About the error returned by Onfido, I cannot really find any way to reproduce an Onfido error in Expensify dev. I tried their sample app here and set the language to Spanish/Chinese but the error message is always in English:

[s77rt]

Their error message is generic too. It's not worth using over ours. We'd be just losing translation this way.

[tienifr]

@s77rt There're more errors here but they seem to be related to BE configuration. The fields property contains the detailed error for each field, we can opt in to show that instead of the generic message (if there be).

[s77rt]

That would be better. Order: onfido field error message > onfido error message > generic error message

[tienifr]

@s77rt fields error only appears in validation_error which we will never get because Onfido is only responsible for veryfing user's document and face, it does not take user's personal data into account. And if there was any error, Onfido would show its own error notification like this:

I think we only need to show Onfido error message. But the errors here are all BE-related so I don't think we can reproduce them. The root cause of this issue is here. Otherwise we can close this PR.

[s77rt]

I think closing makes sense in this case