Can't find NextIntlClientProvider after updating React

EliasVal commented 1 month ago

Description

When I upgrade to any React version newer than 19.0.0-rc-a7d1240c-20240731, I start getting Error: Failed to call "useTranslations" because the context from "NextIntlClientProvider" was not found. errors, even though there is a component in my react tree.

Verifications

[X] I've verified that the problem I'm experiencing isn't covered in the docs.
[X] I've searched for similar, existing issues on GitHub and Stack Overflow.
[X] I've compared my app to a working example to look for differences.

Mandatory reproduction URL

can't reproduce in url :/

Reproduction description

Steps to reproduce:

Update react a newer version than 19.0.0-rc-a7d1240c-20240731
See if it breaks

Expected behaviour

Normal project behaviour

EliasVal commented 1 month ago

Band-aid solution found:

I put another NextIntlClientProvider in my layout.tsx, currently my layout.tsx imports a "layout" component (since the project is part of a mono-repo), so now I have two NextIntlClientProvider components, and if I remove either, it breaks again.

github-actions[bot] commented 1 month ago

Thank you for your report!

Unfortunately, the reproduction is missing or incomplete, and as such we cannot investigate this issue. Please add a reproduction to the issue, otherwise it will be closed automatically.

Templates:

Creating a good bug report takes time.

To help us resolve the issue quickly, please simplify the reproduction as much as possible by removing any unnecessary code, files, and dependencies that are not directly related to the problem. The easier it is for us to see the issue, the faster we can help you.

Apart from the reproduction, make sure to include the precise steps on how to reproduce the issue, e.g.:

Open reproduction
Click on …
See error: …

Thank you for your understanding!

FAQ

**"I've included a reproduction, what is missing?"** This comment might have been added because your reproduction doesn't point to a destination where the issue can be reproduced. Please make sure that the latest changes were saved in the reproduction and that the link is correct.

github-actions[bot] commented 2 weeks ago

This issue has been automatically closed because it is currently not actionable and has become stale. If the problem persists, please create a new issue.

amannn / next-intl