Bug report: Calling navigate more than once causes 404 error

[Bastian]

When calling the navigate functions multiple times immediately after the initial rendering in a useEffect hook, the website shows a 404 error even though the route exists. This does not happen, if the calls to navigate are delayed.

This is very likely to happen in dev mode with strict mode enabled, since then React executes the useEffect hook twice. I do not know how to do this with your test template, so to simulate a similar behavior I just called the navigate function twice.

I did not have this problem with Remix v2. Correction: It also happens with Remix 2.15.2 and all feature flags enabled. But it used to work in older (2.11.1) Remix versions without feature flags. I don't know when exactly it broke.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 612b20c

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[remix-cla-bot]

Hi @Bastian,

Welcome, and thank you for contributing to React Router!

Before we consider your pull request, we ask that you sign our Contributor License Agreement (CLA). We require this only once.

You may review the CLA and sign it by adding your name to contributors.yml.

Once the CLA is signed, the CLA Signed label will be added to the pull request.

If you have already signed the CLA and received this response in error, or if you have any questions, please contact us at [email protected].

Thanks!

- The Remix team

[remix-cla-bot]

Thank you for signing the Contributor License Agreement. Let's get this merged! 🥳