apollo-client: bug: `useQuery` with a fetch policy of `standby` causes SSR to hang

I met this issue recently. However, it seems adding ssr: false in the options of useLazyQuery would mitigate this issue. Like: const [doQuery, { data }] = useLazyQuery(GQL_DOC, { ssr: false });

This is odd, since useLazyQuery should be skipped in SSR by nature. Could anyone check this?

Edit: v3.5.7 just released hours ago, and the situation still the same.

Edit2: I just found src/react/ssr/__tests__/useLazyQuery.test.tsx and this issue can be reproduced in test environment:

  it('should render', () => {
    const link = mockSingleLink({
      request: { query: CAR_QUERY },
      result: { data: CAR_RESULT_DATA }
    });

    const client = new ApolloClient({
      cache: new InMemoryCache(),
      link,
      ssrMode: true
    });

    const Component = () => {
      const [, { loading, called, data }] = useLazyQuery(CAR_QUERY); // this will cause render time out
      // const [, { loading, called, data }] = useLazyQuery(CAR_QUERY, { ssr: false }); // this will render

      expect(called).toEqual(false);
      expect(loading).toEqual(false);
      expect(data).toEqual(undefined);

      return null;
    };

    const app = (
      <ApolloProvider client={client}>
        <Component />
      </ApolloProvider>
    );

    return renderToStringWithData(app).then(markup => {
      console.log({ markup });
    });
  });

Edit 3: Checked v3.5.8, v3.6.0-beta.5, and main (43883b33e): all of them have the same behavior mentioned above.

We are also experiencing the same issues using the useLazyQuery on our SSR pages.

When on Netlify, the SSR fails that uses useLazyQuery and would return error decoding lambda response: invalid status code returned from lambda: 0.

Downgrading to v3.4.17 seems to fix the issue.

I have a PR that should solve this issue, but there is a possible workaround by setting ssr: false in the query options

I can confirm I am encountering the same bug: I had one place in the code where I was using useLazyQuery and the SSR would never complete, but when I commented out the useLazyQuery call it started working. This started happening after I upgraded from version 3.4.16 to 3.5.2. I’m rendering a React app on the server using Vite with frandiox/vite-ssr.

The same bug occurs on version Apollo Client version 3.5.5.

I can confirm the same issue When there’s a useLazyQuery on page, it hangs during SSR. All 3.5 versions affected up to 3.5.6. Returning to 3.4.17 makes it work again.

Same for me.

v3.4.17 everything works v3.5.0 useLazyQuery has issues with our SSR pages.

I am also experiencing the same issues using the useLazyQuery on our SSR pages.

v3.4.8 works well.

@hwillson I created a separate branch demonstrating the bug in my original repo here:

https://github.com/simplecommerce/meteor-graphql-app/tree/bug-usequery-fetchpolicy-standby

Make sure meteor is installed and execute meteor npm install and meteor run. It will run on port 3000.

The page won’t load.

If you go in this file: /imports/ui/Info.jsx and uncomment the fetchPolicy, it will load fine.

Not gonna lie, I love reproductions that use Meteor. 🎉 We’ll take a look - thanks!

@atarek12 @byronlanehill I just tried 3.6.6 (latest) on my repo and it seems to work fine, so whatever problem I had with the prior release 3.5.4 (i hadn’t checked for a while) is gone on my end, it could be another issue but still be related to this one I assume.