Invariant Violation 17

We have this issue that we detect only on Sentry side. Hence I never encountered it myself during development so I have no idea how to reproduce but here is the error message:

Invariant Violation: Invariant Violation: 17 (see https://github.com/apollographql/invariant-packages)
  at new t (/static/js/20.3c6f5529.chunk.js:1:129014)
  at s (/static/js/20.3c6f5529.chunk.js:1:129219)
  at e.getQueryWithPreviousResult (/static/js/20.3c6f5529.chunk.js:1:525535)
  at t.updateQuery (/static/js/20.3c6f5529.chunk.js:1:502730)
  at None (/static/js/20.3c6f5529.chunk.js:1:501301)

Additional data that sentry provides are:

{
framesToPop: 1
}

Any googling around that didn’t help me find what can be the cause of that, but I’ll be happy if anyone can give me any idea about this one.

The only clue is that it happens when the user leaves the page with one particular Query out to any different route that unmounts component that uses such query. And it always the same one.

[benjamn]

What exact versions of the apollo-* packages are you using? It’s relatively straightforward to track down a specific invariant number given the published bundle, as explained in the README mentioned in the error message you pasted above.

[benjamn]

What version of apollo-client? My guess is that this refers to the invariant ingetQueryWithPreviousResult, judging just from the stack trace.

An invariant(condition, message) function call is an assertion that condition is truthy, which throws an exception at runtime (with the given message) if the condition is falsy. The nice thing about the http://npmjs.org/package/ts-invariant package is that we can strip long messages in the production build, which saves more bundle size than any other optimization (besides minification and gzip, of course). In production bundles, the messages are replaced with unique numbers (e.g. 17), which you can find in the production bundle by looking for invariant(..., 17) or new InvariantError(17). If you examine the surrounding code in a bundle like apollo-client/bundle.esm.js, you will find a version of the invariant or InvariantError with the original message intact. Alternatively, if you can reproduce the error in development, without setting process.env.NODE_ENV === "production", then the errors messages will be preserved.