Open IuliiaHerets opened 2 weeks ago
Triggered auto assignment to @stephanieelliott (Bug
), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.
@stephanieelliott FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors
When pressing on "Continue" button in sign in modal, it calls:
The read API is only called if the networkRequestQueue's length in onyx is 0.
In case of this bug, before we click on "Continue", the networkRequestQueue's length in onyx greater than 0, so the Continue button seems to become unresponsive.
Add isDisabled={networkRequestQueue.length > 0}
to FormAlertWithSubmitButton will disable the Continue button when the networkRequestQueue's length is greater than 0.
We can also display additional messages such as "Some existing requests are running; cannot sign in now."
In this, we can call PersistedRequests.clear()
.
@stephanieelliott Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!
Job added to Upwork: https://www.upwork.com/jobs/~021837011332462278943
Triggered auto assignment to Contributor-plus team member for initial proposal review - @eVoloshchak (External
)
The continue button becomes unresponsive when trying to login via deep link.
The root cause of this problem is in the baseloginform component.
To address this issue the button click listener, validation logic and loading state should be checked.
NA
@eVoloshchak, @stephanieelliott Whoops! This issue is 2 days overdue. Let's get this updated quick!
Hey @eVoloshchak there are some proposals here, can you review when you get.a sec?
@eVoloshchak, @stephanieelliott Eep! 4 days overdue now. Issues have feelings too...
Hey @eVoloshchak there are some proposals here, can you review when you get.a sec?
Bump on this @eVoloshchak
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸
@eVoloshchak, @stephanieelliott Still overdue 6 days?! Let's take care of this!
Hey @eVoloshchak can you review please?
@eVoloshchak @stephanieelliott 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!
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: 9.0.34-2 Reproducible in staging?: Y Reproducible in production?: Y If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/4962361&group_by=cases:section_id&group_id=229066&group_order=asc Email or phone of affected tester (no customers): gocemate+a2133@gmail.com Issue reported by: Applause Internal Team
Action Performed:
Expected Result:
Continue button should response
Actual Result:
Continue button becomes unresponsive
Workaround:
Unknown
Platforms:
Screenshots/Videos
https://github.com/user-attachments/assets/06e418bd-b39e-423f-a7af-9411415c0e7a
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @eVoloshchak