question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

apollo_cache_inmemory_1.readQueryFromStore is not a function in browser

See original GitHub issue

Do you want to request a feature or report a bug? bug

What is the current behavior? I’m receiving an error message when trying to process an offline query

ERROR Error: Network error: apollo_cache_inmemory_1.readQueryFromStore is not a function
    at new ApolloError (ApolloError.js:37)
    at QueryManager.js:335
    at QueryManager.js:710
    at Array.forEach (<anonymous>)
    at QueryManager.js:709
    at Map.forEach (<anonymous>)
    at QueryManager.push../node_modules/aws-appsync/node_modules/apollo-client/core/QueryManager.js.QueryManager.broadcastQueries (QueryManager.js:704)
    at QueryManager.js:284
    at ZoneDelegate.push../node_modules/zone.js/dist/zone.js.ZoneDelegate.invoke (zone.js:388)
    at Object.onInvoke (core.js:3824)

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem. It happens from time to time, only when a query is executed and the store is offline, well, only when my code reaches method processOfflineQuery.

What is the expected behavior? Process the query.

Which versions and which environment (browser, react-native, nodejs) / OS are affected by this issue? Did this work in previous versions? I’m using, in a angular app in browser (chrome):

    "apollo-angular": "^1.5.0",
    "apollo-angular-link-http": "^1.4.0",
    "apollo-cache-inmemory": "^1.3.9",
    "apollo-client": "^2.4.3",
    "apollo-link-error": "^1.1.1",    
    "aws-appsync": "^1.4.0",

The store should be hydrated since I do it in app startup.

Thank you

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Reactions:4
  • Comments:16 (5 by maintainers)

github_iconTop GitHub Comments

3reactions
manueliglesiascommented, Nov 20, 2018

@jamesalexmorgan @e23z @luccamordente @iudelsmann

We just published a new version to npm, could you guys test with these:

  • aws-appsync-react@1.2.1
  • aws-appsync@1.5.0
1reaction
iudelsmanncommented, Nov 21, 2018

No more errors for me. Thank you very much!

Read more comments on GitHub >

github_iconTop Results From Across the Web

TypeError: "x" is not a function - JavaScript - MDN Web Docs
The JavaScript exception "is not a function" occurs when there was an attempt to call a value from a function, but the value...
Read more >
How to Handle JavaScript Uncaught TypeError: “x” is Not a ...
The Javascript TypeError: "x" is not a function occurs when calling a function on a value or object, which is not actually a...
Read more >
TypeError: console.log(...) is not a function - Stack Overflow
Explanation. It's trying to pass function(){} as an argument to the return value of console. log() which itself is not a function but...
Read more >
JavaScript: Uncaught TypeError: n is not a function
This error occurs if you try to execute a function that is not initialized or is not initialized correctly. This means that the...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found