-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Due for payment 2025-02-27] [Due for payment 2025-02-19] Hybrid - Bank Account - Plaid flow is not pointing to Sandbox environment #52199
Comments
Triggered auto assignment to @VictoriaExpensify ( |
Thanks for this issue, I assume this is because the HybridApp staging environment checker continues to not work. |
@AndrewGable, @VictoriaExpensify Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
@AndrewGable @VictoriaExpensify this issue was created 2 weeks ago. Are we close to a solution? Let's make sure we're treating this as a top priority. Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks! |
Oh I'm not sure how I missed this in my queue.
@AndrewGable it sounds like this is going to be fixed elsewhere, is that right? In which case, is there anything we need to do with this issue? |
Bump on the above @AndrewGable |
@flaviadefaria I still think #migrate is the best fit for this issue. If you disagree can you please let me know where you think it should go? Roadmap for reference. |
We don't need to do anything in this issue, but it's fine to stay open until we fix it. |
If this is an issue currently happening in ND then it should go in #retain. |
This was merged, but then reverted for blockers. We will continue working on it 🦾 |
@jnowakow what are the next steps here, this issue was highlighted as happening in production, can you please work on this one with priority? thank you! |
I'll try to figure out what link is passed to Plaid because it seems the only what we pass configuration to it it from App |
Skipping the payment summary for this issue since all the assignees are employees or vendors. If this is incorrect, please manually add the payment summary SO. |
@AndrewGable @mountiny @VictoriaExpensify |
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results. If a regression has occurred and you are the assigned CM follow the instructions here. If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future. |
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results. If a regression has occurred and you are the assigned CM follow the instructions here. If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future. |
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results. If a regression has occurred and you are the assigned CM follow the instructions here. If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future. |
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results. If a regression has occurred and you are the assigned CM follow the instructions here. If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future. |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.2-1 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2025-02-27. 🎊 For reference, here are some details about the assignees on this issue:
|
@ZhenjaHorbach @VictoriaExpensify @ZhenjaHorbach The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button] |
Payment Summary
BugZero Checklist (@VictoriaExpensify)
|
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 reported by: Applause - Internal team
Slack conversation (hyperlinked to channel name): #qa
Action Performed:
Expected Result:
Plaid should point to the Sandbox environment to be able to test it.
Actual Result:
Plaid is pointing to the prod environment.
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
View all open jobs on GitHub
Issue Owner
Current Issue Owner: @VictoriaExpensifyThe text was updated successfully, but these errors were encountered: