Calling writeQuery does not update the props

[scottmcpherson]

Intended outcome:
writeQuery should refresh the props data. You can see here that when a user logs in, this function gets called with the user. I'm trying to call writeQuery() to update the currentUser.

I've also tried calling writeQuery directly on the client and store, but no luck.

Actual outcome:
writeQuery does not refresh the props data

How to reproduce the issue:
You can clone this repo to see the issue: https://github.com/scottmcpherson/react-graphql-apollo-semanticui-starter and checking out commit 3be17f74071dc347164d1ac825c8503bc075ee8b

Version
"apollo-boost": "0.1.10",
"react-apollo": "2.1.9",

[scottmcpherson]

I got around this for the time being by calling refetch on the query. It's not ideal, but it does the trick

[captDaylight]

@scottmcpherson I've been struggling with the same issue.

I have a query GET_USER on page load to see if the user is logged in. If not, the header show log in/sign up... if so it shows log out. If the user is not logged in, then goes to the login page I tried doing something like this:

<Mutation
  mutation={LOGIN}
  variables={{ email, password }}
  update={(cache, { data }) => {
    cache.writeQuery({
      query: GET_USER,
      data: { user: data.login }
    });
  }}
> 
  // ... form

here are the queries that correspond:

import gql from 'graphql-tag';

export const GET_USER = gql`
  {
    user {
      id
      name
      email
      __typename
    }
  }
`;

export const LOGIN = gql`
  mutation LoginMutation($email: String!, $password: String!) {
    login(email: $email, password: $password) {
      id
      name
      email
      __typename
    }
  }
`;

However, when I log in successfully, that update does not update the query (as far as I can tell, assuming that the header should switch over to the logged out state as it's referencing the same query). The data that I have coming back after login in data.login is exactly the same format as my GET_USER query.

I'm going to try to refetch from the server for now too but this feels redundant as you said...

[captDaylight]

This thread is about refetching the user after log in, but fundamentally that feels like a redundant call.

[rosskevin]

possibly duplicate of #2099

[rosskevin]

#2099 is a mutate without writeQuery, but notes are there. Specifically, the writeQuery bug I just proved to be upstream in apollographql/apollo-client#2415 (comment)

I'm leaving this open because it is another permutation of what I think is the same upstream bug.

[rosskevin]

I proved the bug upstream is not a bug, so back to looking at other cases to find it.

[danilobuerger]

@scottmcpherson I don't think this has anything to do with writeQuery. When the site initially loads, it will fetch the CurrentUser query. The server returns:

{"data":{"currentUser":null},"errors":[{"message":"Invalid token","locations":[{"line":2,"column":3}],"path":["currentUser"],"extensions":{"code":"UNAUTHENTICATED","exception":{"stacktrace":[...]}}}]}

Since this is an error, the query isn't cached and is not observable. So then when you call writeQuery with the data the query is not "refetched" as nothing is triggering it as its not observable.

[danilobuerger]

The only thing you have to do to get it working is:

diff --git a/server/data/resolvers.js b/server/data/resolvers.js
index b349a89..066f137 100644
--- a/server/data/resolvers.js
+++ b/server/data/resolvers.js
@@ -9,7 +9,7 @@ const resolvers = {
   Query: {
     currentUser: async (root, {}, { user }) => {
       if (!user) {
-        throw new AuthenticationError('Invalid token')
+        return null
       }
       const loginInUser = await User.findOne({ where: { id: user.id } })
       return loginInUser

[rosskevin]

Thanks for digging in @danilobuerger. I'm closing given that solution/information.