Skip to content

Android hybrid - After completing the Plaid flow, standalone ND opens on Google Play store #56719

Closed

Description

@mitarachim

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.97-0
Reproducible in staging?: Yes
Reproducible in production?: Unable to check
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: No, reproducible on hybrid only
If this was caught during regression testing, add the test name, ID and link from TestRail: #56401
Email or phone of affected tester (no customers): applausetester+sj9032@applause.expensifail.com
Issue reported by: Applause Internal Team
Device used: Samsung Galaxy Z Fold 4 / Android 14
App Component: Workspace Settings

Action Performed:

  1. Launch hybrid app.
  2. Go to workspace settings > Workflows.
  3. Tap Connect bank account.
  4. Tap Log into your bank.
  5. Select Wells Fargo.
  6. Go through Plaid flow on the browser.

Expected Result:

After completing the Plaid flow, it will land in the app.

Actual Result:

After completing the Plaid flow, standalone ND opens on Google Play store

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug6740220_1739328806640.1739328615247_56401_Android.mp4

View all open jobs on GitHub

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    DeployBlockerIndicates it should block deploying the API
    DeployBlockerCashThis issue or pull request should block deployment
    on Feb 12, 2025
  2. melvin-bot commented on Feb 12, 2025

    @melvin-bot

    Triggered auto assignment to @stephanieelliott (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 Feb 12, 2025

    @melvin-bot

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

  4. melvin-bot commented on Feb 12, 2025

    @melvin-bot

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

  5. github-actions commented on Feb 12, 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. mitarachim commented on Feb 12, 2025

    @mitarachim
    Author

    issue not repro in STG with use staging server OFF .
    issue repro in STG with use staging server ON .

  7. mountiny commented on Feb 12, 2025

    @mountiny
    Contributor

    Testing revert of the getEnviroment PR here #56744 kicked off adhoc build @mitarachim can you please chekc on the build once ready?

    issue not repro in STG with use staging server OFF .

    I think you cannot user production API for this same as why you cannot connect in production app

  8. 10 remaining items

  9. Julesssss commented on Feb 12, 2025

    @Julesssss
    Contributor
  10. Julesssss commented on Feb 12, 2025

    @Julesssss
    Contributor

    I am confident that this change is not related to the current web-expensify and web-secure code on staging.

    @stitesExpensify I'm not so sure. With these reports it's potentially backend (perhaps from Tuesday's deploy)

  11. m-natarajan commented on Feb 12, 2025

    @m-natarajan

    We see this #52199 bug now

    Screenrecorder-2025-02-12-22-56-06-633.mp4
  12. Julesssss commented on Feb 12, 2025

    @Julesssss
    Contributor

    We see this #52199 bug now

    Thanks, that is expected because we reverted the code for that fix.

  13. Julesssss commented on Feb 12, 2025

    @Julesssss
    Contributor

    @m-natarajan to confirm, the bug within this issue is no longer occuring?

  14. jnowakow commented on Feb 18, 2025

    @jnowakow
    Contributor

    I think it wasn't caused by my changes from #56401 but by the code that is currently on main. Package passed to Plaid is always com.expensify.chat so after successful flow Plaid redirects to google play in order to install production ND. I think that the fix for the issue is to pass actual app id.
    Currently I'm blocked by Plaid so I'm not able to confirm this but it seems reasonable.

  15. jnowakow commented on Feb 18, 2025

    @jnowakow
    Contributor

    BTW on dev environment backend returns Plaid's production link

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.EngineeringReviewingHas a PR in reviewWeeklyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions