Android - VBA - User could not add bank account using plaid option

[kavimuru]

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

---

Issue was found when executing #6319

Action Performed:

1. Launch the app and login with gmail
2. Go to workspace and tap "Connect to a bank"
3. Select the option " connect online with plaid"
4. Tap continue

Expected Result:

User taken to bank selection screen

Actual Result:

Redirected back to app

Workaround:

Unknown

Platform:

Where is this issue occurring?

• Android

Version Number: 1.1.16-6
Reproducible in staging?: Yes
Reproducible in production?: No
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos:
Issue was found when executing #6319

Screenrecorder-2021-11-23-23-26-26-93.mp4

Expensify/Expensify Issue URL:
Issue reported by: Applause
Slack conversation:

View all open jobs on GitHub

[OSBotify]

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

[MelvinBot]

Triggered auto assignment to @joelbettner (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

[isagoico]

Found this while we were retesting #6319 on Android (I don't think it's the culprit tho) this was definitely not reproducible when we started QA so we added the Deploy Blocker label.

[joelbettner]

@nickmurray47 @TomatoToaster after some discussion in this thread, it seems like you might have the best context for working on this. https://expensify.slack.com/archives/C03TQ48KC/p1637777522145000

I'm going to un-assign myself as I'm currently working on a daily, and I've got a doctor appt coming up soon that will take me OOO.

[marcaaron]

@kavimuru can we get tester email to look at logs and see if there's more information?

Also can we please re-test but on a fresh sign in and switch to staging server before starting the flow?

The video shown doesn't really reflect what a user would do so I want to make sure this is a real blocker and not a consequence of switching from the production server to staging server as shown. Users can't switch the secure endpoint like that unless they are one the staging version of the app.

[isagoico]

@marcaaron I just checked and I'm unable to reproduce this same issue again 🤔

In the morning (when reporting this) 3 members of the applause team were able to reproduce consistently on 3 different Android devices (including mine). One of the emails we used was:

1. utester29+50@gmail.com

Maybe it was a temporary issue on plaid side (?)

[marcaaron]

Ok thanks! Sounds like we can remove the blocker then.

[marcaaron]

Leaving this as a Daily so someone can investigate and look into the logs to see what happened here.

[mvtglobally]

Issue not reproducible during KI retests. (First week)

[MelvinBot]

Eep! 4 days overdue now. Issues have feelings too...

[MelvinBot]

6 days overdue. This is scarier than being forced to listen to Vogon poetry!

[MelvinBot]

10 days overdue. Is anyone even seeing these? Hello?

[MelvinBot]

12 days overdue. Walking. Toward. The. Light...

[MelvinBot]

This issue has not been updated in over 14 days. eroding to Weekly issue.

[mvtglobally]

Issue not reproducible during KI retests. (Second week)

[mvtglobally]

Team was getting slightly different issue this week. Not closing this issue this week

[marcaaron]

@mvtglobally can we create separate issues for this "Webpage not available" error? It looks new and different from the issue first reported here. Is it reproducible on production?

[mvtglobally]

Issue not reproducible during KI retests. (Fourth week)Closing
We did not encounter this "Webpage not available" error again @marcaaron. It might've been a temporary glitch. If team is able to repro it again, we will log a separate issue.