I am running this error too, and I am using npm instead of yarn.
Looking in the networking error stack I noticed: following error
"message": "Cannot use GraphQLSchema \"[object GraphQLSchema]\" from another module or realm.\n\nEnsure that there is only one instance of \"graphql\" in the node_modules\ndirectory. If different versions of \"graphql\" are the dependencies of other\nrelied on modules, use \"resolutions\" to ensure only one version is installed.\n\nhttps://yarnpkg.com/en/docs/selective-version-resolutions\n\nDuplicate \"graphql\" modules cannot be used at the same time since different\nversions may have different capabilities and behavior. The data from one\nversion used in the function from another could produce confusing and\nspurious results."
Cannot use GraphQLSchema “[object GraphQLSchema]” from another module or realm.
Ensure that there is only one instance of “graphql” in the node_modules
directory. If different versions of “graphql” are the dependencies of other
relied on modules, use “resolutions” to ensure only one version is installed.
Duplicate “graphql” modules cannot be used at the same time since different
versions may have different capabilities and behavior. The data from one
version used in the function from another could produce confusing and
I looked in the package-lock.json and noticed that react-native references
eslint-plugin-relay for some reason and it comes with new graphql version.
There is following PR open to update the graphql version in the developer tools: https://github.com/expo/expo-cli/pull/2286 which should fix this issue.
Note: I suspect that it works with yarn because yarn handles this conflicting dependencies slighty different.