useLazyQuery executes query twice the first time on 3.6.x

I have some code like this:

const [execute, { data, loading }] = useLazyQuery(query, {
  fetchPolicy: "network-only",
  nextFetchPolicy: "cache-first",
  notifyOnNetworkStatusChange: true,
});
const handleClick = () => execute({ variables: { something } });
return <button onClick={handleClick}>do it</button>;

I click the button (once) but see two queries in the network tab. If i click the button a second time, with new something, the query appears to only fire one more time, as expected

In my debugging, I found that this line is executing the query for the same variables and same options passed to useLazyQuery: https://github.com/apollographql/apollo-client/blob/76ad8a789a20a4962270649dfe5e5fbcfbf9c0fa/src/react/hooks/useQuery.ts#L215

for me, the second extra query has this:

currentWatchQueryOptions === {
  fetchPolicy: "standby"
  initialFetchPolicy: "network-only"
  nextFetchPolicy: "cache-first"
  notifyOnNetworkStatusChange: true
  query: {…}
  variables: { something }
};
// and
watchQueryOptions === {
  fetchPolicy: "network-only"
  nextFetchPolicy: "cache-first"
  notifyOnNetworkStatusChange: true
  query: {…}
  variables: { something }
}

Hopefully this is helpful and not just a red herring 😃

[dairyisscary]

amazing, seems to fix the issue in real app. thanks @benjamn!

[dairyisscary]

@benjamn https://github.com/dairyisscary/duplicate-lazy-query main branch has it

I struggled at first to reproduce it so I kept adding more and more of my configuration until I got it. it was the queryDeduplication: false on the Client constructor. sorry homie; completely forgot about this setting since its fire and forget. 😃

I’m less certain this is a bug now but i will say on apollo 3.4.17 this does not duplicate the network request twice even with queryDeduplication turned off (I’m two releases behind, I never got to 3.5). if it is not a bug, what would you recommend benjamn? there doesn’t appear to be a way to turn this on and off for an individual query – I would turn it off for this particular query if it were possible.