You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Android - VBA - User could not add bank account using plaid option #6457
👋 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:
Identify the pull request that introduced this issue and revert it.
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.
@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.
@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:
@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?
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.
Activity
OSBotify commentedon Nov 24, 2021
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open
StagingDeployCashdeploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:MelvinBot commentedon Nov 24, 2021
Triggered auto assignment to @joelbettner (
Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.isagoico commentedon Nov 24, 2021
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 commentedon Nov 24, 2021
@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 commentedon Nov 24, 2021
@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 commentedon Nov 24, 2021
@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:
Maybe it was a temporary issue on plaid side (?)
marcaaron commentedon Nov 24, 2021
Ok thanks! Sounds like we can remove the blocker then.
2 remaining items
mvtglobally commentedon Nov 29, 2021
Issue not reproducible during KI retests. (First week)
MelvinBot commentedon Nov 30, 2021
Eep! 4 days overdue now. Issues have feelings too...
MelvinBot commentedon Dec 2, 2021
6 days overdue. This is scarier than being forced to listen to Vogon poetry!
MelvinBot commentedon Dec 6, 2021
10 days overdue. Is anyone even seeing these? Hello?
MelvinBot commentedon Dec 8, 2021
12 days overdue. Walking. Toward. The. Light...
MelvinBot commentedon Dec 13, 2021
This issue has not been updated in over 14 days. eroding to Weekly issue.
mvtglobally commentedon Dec 14, 2021
Issue not reproducible during KI retests. (Second week)
mvtglobally commentedon Dec 21, 2021
Team was getting slightly different issue this week. Not closing this issue this week

marcaaron commentedon Dec 21, 2021
@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 commentedon Dec 28, 2021
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.