Skip to content

Android - Onfido - Onfido screen content is not rendering properly #55859

Description

@vincdargento

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!


Version Number: 9.0.90-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: N/A
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Email or phone of affected tester (no customers): applausetester+bm452@applause.expensifail.com
Issue reported by: Applause Internal Team
Device used: Samsung Galaxy A13/Android 14
App Component: Other

Action Performed:

  1. Open the Expensify app
  2. Create workspace
  3. Go to workflow
  4. Try to connect to bank using the manual method (Routing Number: 011401533, Account Number: 1111222233331111)
  5. Reach the 3rd step, which is the Onfido validation.

Expected Result:

The content on the Onfido screen should be fully visible.

Actual Result:

The app does not crash on the Onfido screen, but most of the content is not visible—only number is displayed.

Workaround:

Unknown

Platforms:

  • Android: Standalone
  • Android: HybridApp
  • Android: mWeb Chrome
  • iOS: Standalone
  • iOS: HybridApp
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

bug.mp4

View all open jobs on GitHub

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    DeployBlockerCashThis issue or pull request should block deployment
    on Jan 28, 2025
  2. melvin-bot commented on Jan 28, 2025

    @melvin-bot

    Triggered auto assignment to @JmillsExpensify (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

  3. melvin-bot commented on Jan 28, 2025

    @melvin-bot

    Triggered auto assignment to @rlinoz (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

  4. melvin-bot commented on Jan 28, 2025

    @melvin-bot

    💬 A slack conversation has been started in #expensify-open-source

  5. github-actions commented on Jan 28, 2025

    @github-actions
    Contributor

    👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

    1. Identify the pull request that introduced this issue and revert it.
    2. Find someone who can quickly fix the issue.
    3. Fix the issue yourself.
  6. vincdargento commented on Jan 28, 2025

    @vincdargento
    Author

    @JmillsExpensify FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors.

  7. shubham1206agra commented on Jan 28, 2025

    @shubham1206agra
    Contributor

    I am looking into this. Seems super strange. cc @Ollyws

  8. rlinoz commented on Jan 28, 2025

    @rlinoz
    Contributor

    It only happens if the phone is set to dark mode

  9. 26 remaining items

  10. JmillsExpensify commented on Feb 17, 2025

    @JmillsExpensify
    Contributor

    Still working through the PR?

  11. moved this to Bugs and Follow Up Issues in #expensify-bugson Feb 17, 2025
  12. shubham1206agra commented on Feb 18, 2025

    @shubham1206agra
    Contributor

    @rlinoz Can you add retest label and close this issue?

  13. added
    retest-weeklyApply this label if you want this issue tested on a Weekly basis by Applause
    on Feb 18, 2025
  14. rlinoz commented on Feb 18, 2025

    @rlinoz
    Contributor

    Let's get one round of retest then we can close.

    Thanks for looking into this!

  15. added and removed on Feb 20, 2025
  16. shubham1206agra commented on Feb 25, 2025

    @shubham1206agra
    Contributor

    @vincdargento Bump for retest

  17. rlinoz commented on Feb 28, 2025

    @rlinoz
    Contributor

    Can't repro anymore, closing.

    Image

  18. moved this from Bugs and Follow Up Issues to Done in #expensify-bugson Feb 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.EngineeringWeeklyKSv2retest-weeklyApply this label if you want this issue tested on a Weekly basis by Applause

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions