my loading is forever "True"

am i the only one here facing this issue ? here my “dependencies”: { “@apollo/client”: “^3.6.2”, “graphql”: “^16.4.0”, “react”: “17.0.2”, “react-native”: “0.68.1” },

const client = new ApolloClient({ uri: ‘https://api.mocki.io/v2/c4d7a195/graphql’, cache: new InMemoryCache(), });

const GET_ME = gql query { users { id email name } };

const {data, loading, error} = useQuery(GET_ME); console.log({error, loading, data}); if (loading) return <Text>Loading…</Text>; if (error) return <Text>Error! ${error.message}</Text>;

RESULT : {error: undefined, loading: true, data: undefined}

please advise. thanks

[fknop]

I’m seing this issue with 3.6.9 (react 17)

[TkDodo]

Hi, react-query maintainer here 👋

It seems that we have similar problems with the following setup:

• react-native 0.68 or lower
• react 17
• a version of our library that uses the useSyncExternalStore shim via: import { useSyncExternalStore } from 'use-sync-external-store/shim/index.js' which is also what apollo-client is doing: https://github.com/apollographql/apollo-client/blob/95c8a1a8211302b07dddd0a5e6e67119111009d7/src/react/hooks/useQuery.ts#L10

and as far as I can see, the last “working version” was the one before you switched to uSES.

I can confirm that the shim works fine with react17 and react18 for the web. We’ve also narrowed down that in the above setup, the subscribe function from useSyncExternalStore is just never called, which is why no fetches are made (at least in react-query). Now the question is:

• is there a react-native version where this setup works? For example, has someone tried out 0.67 or lower versions? Just to narrow down if the issue has something to do with react-native versions.
• does it work with react-native 0.69-RC ? This seems to be the first version with react18, so the shim would not be used, but the native useSyncExternalStore from react would be taken, which should not have any issues.
• can we come up with a minimal reproduction of useSyncExternalStore (without apollo or react-query) that fails, which would point to an issue in the shim itself, so that we can reach out to the react team.