-
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
[HOLD for payment 2025-02-06] [HOLD for payment 2025-02-05] [HOLD for payment 2025-02-04] [$100] Migrate AuthScreens to useOnyx #49103
Comments
Triggered auto assignment to @zanyrenney ( |
Job added to Upwork: https://www.upwork.com/jobs/~021834281376353079480 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @c3024 ( |
Upwork job price has been updated to $100 |
Dibs |
Do we need to submit proposal? |
ProposalPlease re-state the problem that we are trying to solve in this issue.Migrate AuthScreens to useOnyx What is the root cause of that problem?This is an improvement What changes do you think we should make in order to solve the problem?Remove the withOnyx here and use
What alternative solutions did you explore? (Optional) |
@roryabraham @c3024 want to take a look at the proposals here please? |
It is a simple enough task. I think it is fine to give it to @BhuvaneshPatil if he has not been assigned any other 🎀 👀 🎀 C+ Reviewed |
Current assignee @roryabraham is eligible for the choreEngineerContributorManagement assigner, not assigning anyone new. |
Thanks @c3024 , |
Both @BhuvaneshPatil and @nkdengineer are now assigned to one other migration each, so I'm going to treat this one on a first-come-first-serve and give it to @BhuvaneshPatil |
📣 @c3024 🎉 An offer has been automatically sent to your Upwork account for the Reviewer role 🎉 Thanks for contributing to the Expensify app! |
📣 @BhuvaneshPatil 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app! Offer link |
@BhuvaneshPatil, @roryabraham, @zanyrenney, @c3024 Whoops! This issue is 2 days overdue. Let's get this updated quick! |
assigning this issue to @deetergp since he's been reviewing the PR(s) |
latest PR was merged then reverted just a few minutes ago |
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.89-8 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-04. 🎊 For reference, here are some details about the assignees on this issue:
|
@c3024 @zanyrenney @c3024 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] |
Melvin is incorrect as the last PR for this has been reverted, so it is not ready for payment. @blazejkustra @WojtekBoman @c3024 Do we have a plan for re-implementing this without causing a regression? |
I think @WojtekBoman is working on a fix, hopefully he will leave an update tomorrow 🙌 |
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.90-6 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-05. 🎊 For reference, here are some details about the assignees on this issue:
|
@c3024 @zanyrenney @c3024 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] |
I created a draft PR fixing this issue. It seems to work fine, but I know there are more sign in flows that should be checked thoroughly before I make it ready for review. Can we trigger builds for this PR and ask QA testers to check it? Screen.Recording.2025-01-29.at.17.16.54.mov |
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.91-2 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-06. 🎊 For reference, here are some details about the assignees on this issue:
|
@c3024 @zanyrenney @c3024 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] |
tomorrow! @c3024 please complete the checklist. |
The PR was reverted. A new PR #55966 is under works. |
Currently Held on #51942
Coming from https://expensify.slack.com/archives/C01GTK53T8Q/p1725973460005309?thread_ts=1725905735.105989&cid=C01GTK53T8Q
Migrate
src/libs/Navigation/AppNavigator/AuthScreens.tsx
to useuseOnyx
instead ofwithOnyx
.Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @zanyrenneyThe text was updated successfully, but these errors were encountered: