Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TypeError: createOperationSelector is not a function #168

Closed
l3roken opened this issue Feb 4, 2019 · 8 comments
Closed

TypeError: createOperationSelector is not a function #168

l3roken opened this issue Feb 4, 2019 · 8 comments

Comments

@l3roken
Copy link

l3roken commented Feb 4, 2019

I am getting the following error and I can't seem to passed it:


Resolver.js:207 Uncaught (in promise) TypeError: createOperationSelector is not a function
    at http://home.devbox:42450/vendors~main.1d7887f6607d23311910.js:19212:65
    at Array.map (<anonymous>)
    at Resolver.updateQuerySubscriptions (http://home.devbox:42450/vendors~main.1d7887f6607d23311910.js:19198:38)
    at Resolver._callee$ (http://home.devbox:42450/vendors~main.1d7887f6607d23311910.js:19094:41)
    at tryCatch (http://home.devbox:42450/vendors~main.1d7887f6607d23311910.js:2296:40)
    at Generator.invoke [as _invoke] (http://home.devbox:42450/vendors~main.1d7887f6607d23311910.js:2530:22)
    at Generator.prototype.(anonymous function) [as next] (http://home.devbox:42450/vendors~main.1d7887f6607d23311910.js:2348:21)
    at resume (http://home.devbox:42450/vendors~main.1d7887f6607d23311910.js:1820:30)
    at http://home.devbox:42450/vendors~main.1d7887f6607d23311910.js:1813:11
    at new Promise (<anonymous>)

@taion
Copy link
Member

taion commented Feb 4, 2019

this is #159

@taion taion closed this as completed Feb 4, 2019
@l3roken
Copy link
Author

l3roken commented Feb 5, 2019

I downgraded to 1.70 and its working. Thanks

@taion
Copy link
Member

taion commented Feb 5, 2019

actually, if you use the alphas for the next release, we have relay v2 support now

@geyang
Copy link

geyang commented Feb 17, 2019

This issue is god-send!!

I'm running into the same issue. Upgrading to found-replay@next solved the issue (@next points to 0.4.0-alpha.4).

@smooth-opperator
Copy link

I've upgraded to v0.4.0-alpha.6, but now I'm just back to a previous error
TypeError: Cannot read property 'store' of undefined
seems to be coming from:

at renderElement (/node_modules/found-relay/lib/renderElement.js:44:16)
at /node_modules/found-relay/lib/Resolver.js:217:48

@taion
Copy link
Member

taion commented Apr 5, 2019

See discussion in 4Catalyzer/found#244. You need to make sure you're using a version of found that is compatible with your version of react-redux; either the v0.4.x alphas for React Redux v6.x, or the v0.3.x releases for React Redux v5.x.

@smooth-opperator
Copy link

that's the issue that brought me here ;-)
am using
"found": "v0.4.0-alpha.1",
"react-redux": "^6.0.1",

@taion
Copy link
Member

taion commented Apr 5, 2019

You need to be on at least alpha 7 to get a compat bugfix per https://github.com/4Catalyzer/found/releases/tag/v0.4.0-alpha.7.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants