Parallel/Intercepting routes causing route to freeze when navigating from window
Unanswered
Blanc de Hotot posted this in #help-forum
Blanc de HototOP
Hello everyone,
I’ve encountered an unusual bug in our application that I hope to get some insights on. The issue occurs under specific circumstances when switching between different Desktops (MacOs) when I am on the intercepted route projects/@drawer/(.)specific/[id]
Here’s a more detailed description:
1. The bug is triggered when I navigate away from our application’s browser window to another window on my system when I am on the intercepted route projects/@drawer/(.)specific/[id] from projects/status/[slug].
2. After spending going into another window and doing something there and then coming back (5 sek later) and closing the @drawer and being on the /projects/status/[slug] route, the following routes dont work any more /projects/status/[slug] and projects/specific/[id]
3. Interestingly, I can still navigate to other routes such as /projects/items/item, resources/, schedules/, etc.
4. However, once I’ve navigated away from /projects/status/[slug], I cannot return to /projects/status/[slug] until I refresh the application or stay away from that route
5. After refreshing the application, everything returns to normal, and I can navigate freely again.
I tested this in Safari, Edge, and Firefox browsers.
I am using the newest Next Js 13.5.4, but the error has occurred for some time, and even when I was on older versions all 13+ though.
This is a perplexing issue, and any insights or suggestions would be greatly appreciated. Has anyone else encountered this or have any idea why this might be happening?
I will be monitoring this thread closely and will answer quickly any questions
I’ve encountered an unusual bug in our application that I hope to get some insights on. The issue occurs under specific circumstances when switching between different Desktops (MacOs) when I am on the intercepted route projects/@drawer/(.)specific/[id]
Here’s a more detailed description:
1. The bug is triggered when I navigate away from our application’s browser window to another window on my system when I am on the intercepted route projects/@drawer/(.)specific/[id] from projects/status/[slug].
2. After spending going into another window and doing something there and then coming back (5 sek later) and closing the @drawer and being on the /projects/status/[slug] route, the following routes dont work any more /projects/status/[slug] and projects/specific/[id]
3. Interestingly, I can still navigate to other routes such as /projects/items/item, resources/, schedules/, etc.
4. However, once I’ve navigated away from /projects/status/[slug], I cannot return to /projects/status/[slug] until I refresh the application or stay away from that route
5. After refreshing the application, everything returns to normal, and I can navigate freely again.
I tested this in Safari, Edge, and Firefox browsers.
I am using the newest Next Js 13.5.4, but the error has occurred for some time, and even when I was on older versions all 13+ though.
This is a perplexing issue, and any insights or suggestions would be greatly appreciated. Has anyone else encountered this or have any idea why this might be happening?
I will be monitoring this thread closely and will answer quickly any questions