Skip to content

BA- Incomplete error message displayed for failed GIACT ownership verification #102368

Closed

Description

@applause-bot

If you haven’t already, check out our contributing guidelines for onboarding. To join our Slack channel, fill out this form.


Version Number: v9.4.94-0
Reproducible in staging?: Yes
Reproducible in production?: Unable to validate in Prod - Provide reasoning.
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #101909
Email or phone of affected tester (no customers): N/A
Issue reported by: Applause Internal Team
Bug source: Pull Request QA execution
Device used: Windows 10
App Component: Other

Action Performed:

Requires an account whose bank fails GIACT ownership verification (a bank that does not support Plaid, added manually).

  1. Sign in as that account.
  2. Go to Settings > Wallet > Add bank account and choose to enter bank details manually.
  3. Enter the routing and account numbers, complete the personal details step and submit.
  4. Verify the error shown is "Unable to verify bank account ownership. Please chat with Concierge for further assistance."
    Result: Generic error "An unexpected error occurred…" is displayed

Expected Result:

After failing GIACT error shown is "Unable to verify bank account ownership. Please chat with Concierge for further assistance."

Actual Result:

After failing GIACT error shown is "Unable to verify bank account ownership."

Workaround:

Unknown

Platforms:

  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome Safari

Screenshots/Videos

Bug7269656_1790366196502.bandicam_2026-09-25_14-46-55-568_-_Trim.1.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Julia Ponikarchuk
Bug ID: 7269656

Upwork Automation - Do Not Edit
Issue OwnerCurrent Issue Owner: @NicolasBonet

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Sep 27, 2026
  2. applause-bot commented on Sep 27, 2026

    @applause-bot
    Author

    While Applause doesn't embed attachments for this bug, here are the links for quick view:
    https://platform.applause.com/services/links/v1/external/727e713df529e3db57744d4dc8840df2bf161bcc1b610025d3e181eee5fdb3ec

  3. MelvinBot commented on Sep 27, 2026

    @MelvinBot
    Contributor

    Issue Analysis

    Root Cause: The App shows the ownership error exactly as the server sends it. The App does not contain the text "Unable to verify bank account ownership" at all, so it cannot drop the "Please chat with Concierge…" sentence. The server response is missing that sentence.

    This appears to be a backend/internal issue. A separate internal investigation is needed.

    Recommended Fix: No App change. An internal engineer with backend access should confirm what the server returns for this GIACT failure and add the Concierge sentence there if it's wanted. Otherwise, update the expected result in the QA steps.

    [Payment due @daledah] Surface the server's bank account ownership error instead of generic copy worked as intended: QA saw the server's error, not the generic "An unexpected error occurred…" fallback.

    Investigation details
    • The generic fallback is pinned to key 0, so the server error always wins: src/libs/actions/BankAccounts.ts:550-558.
    • getLatestErrorMessage returns the newest error string unchanged. It doesn't split or shorten it: src/libs/ErrorUtils.ts:86-103.
    • The confirmation step passes the string to DotIndicatorMessage, which renders the whole thing: src/components/SubStepForms/ConfirmationStep.tsx:94-99.
    • The full string with the Concierge sentence appears in the App only as a unit test fixture: tests/unit/BankAccountsTest.ts:80. The PR's manual test used a stubbed response, so the expected text was never checked against a real server response.
    • The issue contradicts itself. "Action Performed" says the generic error appeared. "Actual Result" says "Unable to verify bank account ownership." appeared. This analysis goes with "Actual Result". If the generic error does appear, please attach a screenshot.

    Next Steps: Please escalate to an internal engineer with backend access. Reply with @MelvinBot <your feedback> to refine this analysis.


    view run

  4. added
    ExternalAdded to denote the issue can be worked on by a contributor
    on Sep 27, 2026
  5. melvin-bot commented on Sep 27, 2026

    @melvin-bot

    Triggered auto assignment to Contributor-plus team member for initial proposal review - @ahmedGaber93 (External)

  6. changed the title [-]BA- Incomplete error message displayed for failed GIACT ownership verification[/-] [+][$175] BA- Incomplete error message displayed for failed GIACT ownership verification[/+] on Sep 27, 2026
  7. melvin-bot commented on Sep 27, 2026

    @melvin-bot
  8. self-assigned this
    on Sep 30, 2026
  9. NicolasBonet commented on Sep 30, 2026

    @NicolasBonet
    Contributor

    This is a backend change, so must be handled internally, as it's pretty straightforward and is causing issues in prod, I have moved along with it.

  10. changed the title [-][$175] BA- Incomplete error message displayed for failed GIACT ownership verification[/-] [+]BA- Incomplete error message displayed for failed GIACT ownership verification[/+] on Oct 1, 2026
  11. NicolasBonet commented on Oct 1, 2026

    @NicolasBonet
    Contributor

    Merged, so changing periodicity while we deploy.

  12. NicolasBonet commented on Oct 7, 2026

    @NicolasBonet
    Contributor

    This should be fixed now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

BugSomething is broken. Auto assigns a BugZero manager.ExternalAdded to denote the issue can be worked on by a contributorWeeklyKSv2

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions