[🐞] v2: useNavigate transition timeouts

[andrei9669]

Which component is affected?

Qwik City (routing)

Describe the bug

while using button with useNavigate The app sort of hangs.
it Runs all the tasks on the new route as if navigation has happened but the DOM update doesn't happen instantly and instead I get the following error in console:

Uncaught (in promise) TimeoutError: Transition was aborted because of timeout in DOM update

msedge_xt5Bc3Iy5H.mp4

Reproduction

https://github.com/andrei9669/qwik-navigation-repro

Steps to reproduce

• npm install
• npm run dev
• open the link for the app
• navigate using buttons

System Info

System:
    OS: Windows 11 10.0.26200
    CPU: (16) x64 AMD Ryzen 7 5800X 8-Core Processor             
    Memory: 9.43 GB / 31.90 GB
  Binaries:
    Node: 24.4.0 - C:\Users\andre\AppData\Local\Volta\tools\image\node\24.4.0\node.EXE
    npm: 11.4.2 - C:\Users\andre\AppData\Local\Volta\tools\image\node\24.4.0\npm.CMD
    pnpm: 10.14.0 - C:\Users\andre\AppData\Local\Volta\tools\image\pnpm\10.14.0\bin\pnpm.CMD
  Browsers:
    Edge: Chromium (140.0.3485.54), ChromiumDev (140.0.3456.0)
    Internet Explorer: 11.0.26100.1882
  npmPackages:
    typescript: 5.4.5 => 5.4.5 
    undici: * => 7.16.0 
    vite: 7.1.11 => 7.1.11

Additional Information

No response

[wmertens]

so the error is coming from the viewtransition that qwik router automatically adds, and it's because the navigation takes too long to complete.

And it probably takes too long because of a deadlock. In the navigate button handler, you return nav() and that probably causes the navigation to wait until the navigation succeeds.

When I remove the return from return nav(), it works fine.

@Varixo thoughts?

[rafael-xmr]

was also happening to me on 2.0.0-beta.14 and had disabled viewTransitions until making a repro, thanks for reporting first, can confirm removing all return nav() and () => nav() works now, it propagates so all it takes is clicking one and then every navigation button follows to fail afterwards, also happens in the repro

[andrei9669]

yes, by not returning nav() promise or by not awaiting the nav() promise it works as expected.