TL;DR

The most likely fix involves modifying the proxy.ts or middleware.ts to correctly handle shallow route transitions and prevent navigating back to the previous route.

Guidance

• Review the proxy.ts or middleware.ts implementation to ensure it correctly rewrites the current route and handles shallow route transitions.
• Verify that the device parameter is being correctly derived from the user agent and updated during route transitions.
• Test the application with different route transition scenarios to identify the specific conditions that cause the issue.
• Consider updating the Next.js version to the latest available, as the issue may have been fixed in a later version.

Example

No specific code example can be provided without more information about the proxy.ts or middleware.ts implementation.

Notes

The issue seems to be related to the handling of shallow route transitions in Next.js, and the provided workaround no longer works in versions 15.5.x and later. The root cause of the issue is unclear, and further investigation is needed to determine the correct solution.

Recommendation

Apply a workaround by modifying the proxy.ts or middleware.ts to correctly handle shallow route transitions, as updating to a fixed version is not a clear option due to the uncertainty of the issue's cause.