Compatibility with next intl

[spaquis]

Hey,
Thank you for your work on this subject.

I have a screen where I put the navigation guard, it works perfectly. But on this screen you can change the language of the application.
To do this, I use nextIntl with this:
router.push(${pathName}?${searchParams.toString()}, { locale: lang });

My strategy was to disable the guard before calling router.push and then re-enable it afterwards (the enableGuard state is placed in a context that wraps the whole page).
The problem is that after pushing the new router with the locale changes, the guard no longer works.

Can you help me.
Regards,

[ypresto]

Thank you for reporting!

It might be interfering with next-intl itself, as it seems creating custom router too.

Can you provide a reproduction repo? 🙏

[riccardolardi]

Also looking for a solution to allow usage with next-intl. If it was possible to check whether the router pathname change is a locale change or not and use that to bypass the navigation guard would work?

[ypresto]

bypass the navigation guard would work?

It does not work because our history intervention is to add index of history stack, so it is always active despite of enabled/disabled of the guard.