Route Groups do not work within [locale]

[BearCooder]

Hello I have a strange issue. It seems that Route Groups do not work with next-intl?

My following structure:

app/
 [locale]/
  (dashboard)/
    customers/
      page.tsx
    summary/
      page.tsx
   layout.tsx

Now when I want to access the customers page on http://localhost:3000/customers or http://localhost:3000/summary I get a 404 not found error. I have to use http://localhost:3000/dashboard/customers to access the page. But when I try it without the [locale] then it works as expected and I can access http://localhost:3000/customers without dashboard. When I put it all back into [locale] folder it does not work again?

I am not sure what causes this issue? I looked at the documentation in next intl and couldnt find anything related to this.

[amannn]

I haven't worked with route groups so far, but if you can reproduce the bug in a Next.js-only app then you might want to submit this as a bug report in the Next.js repo.

[J4v4Scr1pt]

Same issue here when multiple root layouts.

[astronaute77]

I have the same problem, I think the issue is in setRequestLocale(locale); executed in the layout. If it is executed from a route group, the let locale = await requestLocale; in request.ts returns "undefined"

[pbortnick]

Strongly suggest including a route group example in the docs 🙏

[amannn]

As a side note here, the Next.js team is working on rootParams, an API that next-intl will benefit of greatly, allowing to get rid of await requestLocale in favor of a built-in feature in Next.js. It's also expected to work with route groups, with multiple root layouts.

I hope to have more to share on this soon, once the API is available on the stable channel of Next.js!

[Yanick64]

Is there any update on the route group part?
Someone else went for a different approach?

Types seems incorrectly typed/missing groups within the defineRouting.