-
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 2023-03-13] Login - The magic code page is displayed first, followed by the successful login page #15188
Comments
Triggered auto assignment to @johncschuster ( |
Bug0 Triage Checklist (Main S/O)
|
Job added to Upwork: https://www.upwork.com/jobs/~01d8fc2ede25c6905c |
Triggered auto assignment to Contributor Plus for review of internal employee PR - @thesahindia ( |
@johncschuster, @cristipaval, @thesahindia Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
This is in review, waiting for @deetergp's review |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.2.78-0 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 2023-03-13. 🎊 After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.
As a reminder, here are the bonuses/penalties that should be applied for any External 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:
|
Hey @thesahindia ! You were right! I am working on a follow-up PR which handles the use case when the sign in with the link fails. And I see now what you were raising here. The intermediary screen still appears on devices with limited resources. The new state gets delayed. I am fixing this in the follow-up PR. This is my fault, no penalty for you. cc @johncschuster |
I think this one got delayed due to ECX 🤔 |
Melvin, again. |
Pinged @johncschuster internally. He's taking care of this today. |
Upwork is being a bit of a PITA. I'm working on getting a different job put together so I can get this sorted. Standby! |
Ok, Upwork is really not working for me. I've raised the question in Slack, and am also speaking to my Talent Specialist to see if I can get this fixed. |
Coming back to this today 💪 |
@johncschuster have we issued payment here? Can we close this out? |
Ugh no. I'm still having trouble with Upwork. I'm walking through it with Dylan right now so I can get this out the door. |
Well, Dylan fixed it embarrassingly fast 🤦♂️ Huzzah! |
@thesahindia Dylan has just invited you to this job. Can you accept this invite? I'll get it paid out right away! https://www.upwork.com/ab/applicants/1640296870359920640/job-details |
Applied, thanks! |
Fantastic! I've just sent the offer! Let me know when you've accepted so I can get the payment sent out. |
@johncschuster, @cristipaval, @thesahindia Eep! 4 days overdue now. Issues have feelings too... |
I have accepted the offer. Thanks! |
@cristipaval @johncschuster just bumping this issue - anything further that we need to do here to get this closed out? |
I think @johncschuster has to perform the payment and hen we close it out. |
It looks like John is OOO. I'll ask someone else to take care of this payment. |
I've paid this. Sorry for the delay @thesahindia! |
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 found when executing PR #14443
Action Performed:
Expected Result:
The successful login page is displayed
Actual Result:
The magic code page is displayed first, followed by the successful login page
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number: 1.2.72.0
Reproducible in staging?: Yes
Reproducible in production?: No (new feature)
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
Notes/Photos/Videos: Any additional supporting documentation
Bug5939323_14443_Web_no_2fa.mp4
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: