useMutation data is always undefined, only works in onCompleted

Intended outcome: I am using the below mutation to update a tile object. The data in the onCompleted callback is correctly returning the updated data object. The data I’m returning in my wrapper is always undefined now. This seems to have recently changed and I’m not sure why

const useUpdateTile = () => {
  const [mutation, { data, loading, error }] = useMutation(UPDATE_TILE, {
    errorPolicy: 'all',
    onCompleted: (data) => {
      console.log('LOG: mutation updateTile completed', data);
    },
  });

  console.log('LOG: mutation updateTile', data);

  return {
    updateTile: (input) => {
      mutation({
        variables: {
          input,
        },
      });
    },
    loading,
    error,
    data: data?.updateTile || {},
  };
};

Actual outcome:

I expect the data returned from the useMutation to contain the updated data object instead of being undefined. This was recently working as intended.

How to reproduce the issue: Haven’t been able to replicate in a codesandbox environment, it must be some other factor. https://codesandbox.io/s/competent-visvesvaraya-ifzp9?file=/src/App.js

Versions

System:
    OS: macOS 10.15.6
  Binaries:
    Node: 12.18.3 - ~/.nvm/versions/node/v12.18.3/bin/node
    npm: 6.14.10 - ~/mycode/node_modules/.bin/npm
  Browsers:
    Chrome: 85.0.4183.102
    Firefox: 68.11.0
    Safari: 13.1.2
  npmPackages:
    @apollo/client: 3.3.6 => 3.3.6 

[brainkim]

Closing because it seems like this has been fixed at some point by some person 😶

[dylanwulf]

@sfratini The change in that PR is available in v3.3.16: https://github.com/apollographql/apollo-client/blob/main/CHANGELOG.md#apollo-client-3316