-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
[HOLD for payment 2024-03-18] [$1000] Desktop - There is no turning back from the SSO provider #29825
Comments
Triggered auto assignment to @anmurali ( |
Job added to Upwork: https://www.upwork.com/jobs/~01b86a48a78c5400e9 |
Bug0 Triage Checklist (Main S/O)
|
Triggered auto assignment to Contributor-plus team member for initial proposal review - @0xmiroslav ( |
This will be handled as part of the SAML project - putting a hold on this issue for now |
@anmurali, @0xmiroslav Huh... This is 4 days overdue. Who can take care of this? |
@NikkiWines - can you link the issue you are referring to? And if it makes sense can you degrade this issue to a weekly or monthly? |
Sure, it's planned to be handled as part of polish for https://github.com/Expensify/Expensify/issues/294583 (internal link) - though actually I guess there's no reason it can't be handled externally now. The desktop UI is on production, if someone wants to simulate having a SAML enabled or required account on newDot to trigger the new flow, they'll just need to modify either of these lines to be |
Current assignee @anmurali is eligible for the NewFeature assigner, not assigning anyone new. |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
@anmurali @0xmiroslav this issue was created 2 weeks ago. Are we close to approving a proposal? If not, what's blocking us from getting this issue assigned? Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks! |
Thanks @davidgelhar , please keep updating daily since it's been almost a week. |
I determined that an additional change was necessary in order to get the PR working with the latest from main. Specifically, the newly-added "lastVisitedPath" Onyx key was preventing you from navigating back to the login page. That issue is also fixed in the (draft) PR #37283 Question: the PR form wants to include screenshots for all platforms, but this fix is specific to the web/desktop platforms. There is a related bug #36673 open for ios/android native. How do you want to handle that @mallenexpensify ? Is it ok to proceed with this as a fix for just the web/desktop bug, or do you want to try to solve it for all platforms? (I'd suggest keeping this task scoped to web/desktop and using the other bug to track the other platforms) |
@thienlnam I've applied for the new upwork job you created https://www.upwork.com/jobs/~01534a657243d6c5b8 but it is not showing as "accepted" yet. Does something need to happen manually becausre you had to create a new job? |
Something has to happen manually because it's your first job and the bot only sends automated Upwork offer after the first job since you're not in the system before that. Don't worry you'll get paid, the payment is usually handled 7 days (regression period) after the PR was deployed on production. |
Hired ya in Upwork @davidgelhar , apologies for the delay/hassle. Like @ikevin127 said, we have automation but it's not perfect. PR is waiting on review from @thienlnam |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.49-4 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 2024-03-18. 🎊 For reference, here are some details about the assignees on this issue:
|
BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
|
Payment Summary
BugZero Checklist (@anmurali)
|
@alitoshmatov can you complete the BZ checklist? |
Regression Test Proposal
Do we agree 👍 or 👎 |
@anmurali Checklist completed |
Contributor: @davidgelhar paid $1000 via Upwork TR GH - https://github.com/Expensify/Expensify/issues/380930 Thanks @alitoshmatov and @davidgelhar , happy to get this one fixed. |
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: 1.3.85-2
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
Issue found when executing PR #28372
Action Performed:
isSAMLEnabled
totrue
here.Expected Result:
There should be a Path back from the SSO provider portal (arrow or cross)
Actual Result:
There is no turning back from the SSO provider portal
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Android: Native
Android: mWeb Chrome
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari
MacOS: Desktop
2023-10-17.3.55.58.PM.mov
_._2023-10-17_._3.52.34_PM_.1.1.mov
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: