[$250] Room - Continue button becomes unresponsive when try to login via deep link

[IuliiaHerets]

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:

1. Logout of New Expensify if logged in
2. Navigate to the following link - https://staging.new.expensify.com/r/6776919265133947
3. Click on Join button
4. Add email address
5. Click Continue

Expected Result:

Continue button should response

Actual Result:

Continue button becomes unresponsive

Workaround:

Unknown

Platforms:

• Android: Native
• Android: mWeb Chrome
• iOS: Native
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Bug6602399_1726235926814.Recording__3933.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021837011332462278943
• Upwork Job ID: 1837011332462278943
• Last Price Increase: 2024-09-27

Issue Owner

Current Issue Owner: @eVoloshchak

[melvin-bot]

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.

[IuliiaHerets]

@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

[mkzie2]

Proposal

Please re-state the problem that we are trying to solve in this issue.

• Continue button becomes unresponsive

What is the root cause of that problem?

When pressing on "Continue" button in sign in modal, it calls:

App/src/libs/actions/Session/index.ts

Line 420 in 1e8d80e

API.read(READ_COMMANDS.BEGIN_SIGNIN, params, {optimisticData, successData, failureData});

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.

What changes do you think we should make in order to solve the problem?

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."

What alternative solutions did you explore? (Optional)

In this, we can call PersistedRequests.clear().

[melvin-bot]

@stephanieelliott Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~021837011332462278943

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @eVoloshchak (External)