App directory server component no working when not wrapped about next-international HOT 7 CLOSED

Thanks for resolving, the issue. I experimented with server context on my side also, but setting headers is a better solutions. Thanks 👍

from next-international.

Hey, what's the error you're getting?

from next-international.

Sorry, i get the following Error: No locale set, make sure to use the I18nProviderServer component

https://github.com/titouv/next-international-repro-bug

Here is the link to the repro, the root path is failing with the previous errors but the root with async wrapper and the root with the non async wrapper works perfectly. Maybe there is something I don't understand about NextJS behavior

from next-international.

With further testing it appears the error also appears when navigating to a page, a simple reload removes the issue but the navigation make this error happen even though its wrapped

from next-international.

Seems in the repro and in the example from the repo (at least on my side), the getLocale function is run before the setLocale, which is thus problematic. If this can give an hint

from next-international.

Looks like cache isn't the ideal solution to save the current locale for a given session. I'll try to use server contexts instead.

from next-international.

I've published 0.5.2 which resolves the issue on my side. Could you try again and open another issue if needed? Thanks.

from next-international.