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

[mitarachim]

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] 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): [email protected]
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

[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.

[melvin-bot]

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

[melvin-bot]

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

[github-actions]

👋 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.

[mitarachim]

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

[mountiny]

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

[mitarachim]

@mountiny noted , let me know once the build ready to use , thank you

[jnowakow]

I tested it on adhoc build and I'm getting the same effect @mountiny

[techievivek]

Interesting, so it means that the issue existed beforehand?

[jnowakow]

I think earlier it was reproducible on adhoc builds and not on staging. On staging environment was set to production so I think the url passed to Plaid was different

[jnowakow]

Especially since it's not reproducible when use staging server is OFF

[stitesExpensify]

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

[staszekscp]

I've discussed the issue with @jnowakow. Actually, is it possible that there is a wrong package name configured on the Plaid account? I've looked at the documentation, and it says that the redirect on Android is based on the package name, not URL - maybe there is something wrong there? https://plaid.com/docs/link/oauth/#android-sdk-react-native-android

[Julesssss]

Good shout. I'm checking internally for any Plaid console changes. @mountiny I agree with that PR being the likely candidate.

With it being a minor change perhaps I will merge the revert and CP to test it out.

[Julesssss]

Potentially related customer issue: https://expensify.slack.com/archives/CAS1DND4H/p1739302676966999

[Julesssss]

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)

[m-natarajan]

We see this #52199 bug now

Screenrecorder-2025-02-12-22-56-06-633.mp4

[Julesssss]

We see this #52199 bug now

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

[Julesssss]

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

[jnowakow]

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.

[jnowakow]

BTW on dev environment backend returns Plaid's production link