JS error and infinite loading when setting up a password for a new account.

[isagoico]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Action Performed:

1. Navigate to https://staging.new.expensify.com
2. In the email field, enter a email address for a new account >> Press continue
3. Go to mail copy link and change to staging.
4. Enter password to 2 fields

Expected Result:

User should be signed in

Actual Result:

Endless spinner is shown. Account isn't created. A JS error can be seen in console.

Workaround:

Unknown

Platform:

Where is this issue occurring?

• Web

Version Number: 1.1.4-0

Reproducible in staging?: yes
Reproducible in production?: Unknown (we were only able to reproduce once)

Logs: https://stackoverflow.com/c/expensify/questions/4856

Notes/Photos/Videos: Any additional supporting documentation
We were able to reproduce this issue only once but we were able to capture the JS error in console.

Bug5261381_endless_new.mp4

Expensify/Expensify Issue URL:

**Issue reported by:**Applause

View all open jobs on GitHub

[MelvinBot]

Triggered auto assignment to @stephanieelliott (AutoAssignerTriage), see https://stackoverflow.com/c/expensify/questions/4749 for more details.

[MelvinBot]

Triggered auto assignment to @Julesssss (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

[Julesssss]

I was unable to reproduce this today in 1.1.4-0 (Chrome + Safari). However, it sounds quite similar to this issue which is also unreliable.

I tried Chrome/Safari with no luck. @isagoico can you remember if this was always reproducible, or only occasionally?

[isagoico]

@Julesssss this was only reproducible once by a tester. Since we were able to capture the JS error I thought it could be valuable as an issue.

[Julesssss]

No worries, I only suggested this because we ignored a similar issue recently. I think for now it's okay to do the same here.

[isagoico]

@Julesssss We were able to reproduce this again on the current regression run

[Julesssss]

I just tested on staging and was unable to reproduce, but let's keep an eye on the issue.