Closed peterp closed 3 years ago
Same as #5065. You should be able to fix this by upgrading apollo-server-lambda to 2.22 as well -- ie, keeping the two packages either both on 2.22 or both before.
(But yes, this is unintentional and next week I'll get out a version of core that doesn't have this problem.)
I believe that apollo-server-core
v2.22.2 is now more fully compatible with pre-v2.22 versions of integrations packages like apollo-server
, apollo-server-lambda
(especially), apollo-server-express
, etc.
I'm still having this "UnhandledPromiseRejectionWarning: Error: called start() with surprising state started at ApolloServer." error
@georgetye What versions of all apollo-server*
packages are you currently using in your app? (Specific version from lock file, not just top level constraint.)
@georgetye OK, doesn't look like it's the same version skew issue. I will need to see more context in your code; at least the file that creates and interacts with the ApolloServer
object (though ideally a full minimal reproduction that lets me run it for myself and see the issue).
We're seeing this error when trying to start the apollo-server-lambda in RedwoodJS.
Pinning the
apollo-server-core
to2.21.2
resolves the problem:2.22.0
and2.22.1
exhibit the same error.