Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't find NextIntlClientProvider after updating React #1233

Closed
3 tasks done
EliasVal opened this issue Aug 4, 2024 · 3 comments
Closed
3 tasks done

Can't find NextIntlClientProvider after updating React #1233

EliasVal opened this issue Aug 4, 2024 · 3 comments
Labels
bug Something isn't working reproduction-missing Stale unconfirmed Needs triage.

Comments

@EliasVal
Copy link

EliasVal commented Aug 4, 2024

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

  • I've verified that the problem I'm experiencing isn't covered in the docs.
  • I've searched for similar, existing issues on GitHub and Stack Overflow.
  • 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:

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

Expected behaviour

Normal project behaviour

@EliasVal EliasVal added bug Something isn't working unconfirmed Needs triage. labels Aug 4, 2024
@EliasVal
Copy link
Author

EliasVal commented Aug 5, 2024

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.

Copy link

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.:

  1. Open reproduction
  2. Click on …
  3. 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.

Copy link

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.

@github-actions github-actions bot added the Stale label Aug 29, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Aug 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working reproduction-missing Stale unconfirmed Needs triage.
Projects
None yet
Development

No branches or pull requests

2 participants