Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Using navigate() function with a state change doesn't rerender the page

See original GitHub issue

Description

Calling the same page with a state change navigate('/page', { state: { newState }}) doesn’t cause the page to rerender. Downgrading gatsby to version 2.24.69 fix the issue and the page is rerendered correctly.

Steps to reproduce

I’ve create a minimal reproduction that show the problem: https://github.com/doscio/gatsby-navigate-issue

The index page has a button that navigate to /counter page. On that page, everytime the button Increase counter is pressed, the counter should increase it’s value, but this is not appening on gatsby version 2.24.85.

Versions prior to 2.24.70 works without problem:

Run npm install gatsby@2.24.69
Run gatsby develop

Everytime I click Increase counter the counter is updating correctly.

Expected result

Everytime the button Increase counter is pressed the counter value should update it’s value.

Actual result

Nothing appens when i click the button Increase counter. If i refresh the page manually (F5) the counter show the correct value.

Environment

  System:
    OS: Windows Server 2016 10.0.14393
    CPU: (8) x64 Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz
  Binaries:
    Node: 14.4.0 - C:\Program Files\nodejs\node.EXE
    npm: 6.14.8 - C:\Program Files\nodejs\npm.CMD
  Languages:
    Python: 3.9.0
  Browsers: {}
  npmPackages:
    gatsby: ^2.24.85 => 2.24.85
  npmGlobalPackages:
    gatsby-cli: 2.12.109