fix: ensure create-password.js
doesn't attempt to change routes twice
#24874
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Multiple onboarding tests are flaky, failing with the error
TimeoutError: Waiting for element to be located By(css selector, [data-testid="recovery-phrase-reveal"])
The problem is that the test can get to the page where that selector is present, but then be re-routed back to the previous screen. This is due to a race condition.
in create-password.js there is this code:
and there is this also this code inside handleCreate():
What is happening is:
await createNewAccount(password);
resolves, and the user/test is rerouted to the "Secure Your Wallet" screen againThe fix is to prevent the
history.replace(ONBOARDING_SECURE_YOUR_WALLET_ROUTE)
call in theuseEffect
ifhandleCreate
has already started to create a new accountRelated issues
Fixes: #24608
Manual testing steps
e2e tests should pass
Pre-merge author checklist
Pre-merge reviewer checklist