-
Notifications
You must be signed in to change notification settings - Fork 36
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
Error: could not identify unique query #386
Comments
I just commented in the forum, but let's continue the conversation here: We cannot stream queries from the server to the client that contain only client-local fields. Also keep in mind that |
So what's the solution here? How can I make sure to stream these queries only on the client? |
I'm afraid, you probably won't be able to use Even if we could solve the "data of multiple users is getting mixed up" problem, every future render on the server would not know what data the user has set in the browser, so it would render "initial data" again. If you can ensure that all of this will only be accessed in the browser (keep in mind that Next.js SSRs your Client Component, too!), I would recommend skipping Apollo Client here and calling That said, this is a very strong if. You probably would have to avoid rendering whole subtrees of your app on the server, with something like
and then conditionally rendering children or not. |
Hello, we recently updated to "@apollo/experimental-nextjs-app-support"; We need this to run server queries.
The problem is that now our global store queries are throwing the error below when on first page visit/refresh.
Versions
This is the error we're getting
Below is how we've setup the apollo wrapper
Here's the query that's erroring out (one of them, all global store queries are erroring out)
Here's how it's all defined
The text was updated successfully, but these errors were encountered: