-
Notifications
You must be signed in to change notification settings - Fork 2k
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
[[email protected]] APQ registration causes "addProtobufError called before startTiming!" #3978
Comments
Thanks for the report @vanwalj. Can you please provide a reproduction? We'll start looking into this today but anything helps. |
Seems related to #3627, which recently seems to have resurfaced #3627 (comment) and was still present in |
Looking into this now! |
I tried to reproduce this, deploying all the way to Lambda using However, I was unable to re-create this using To move forward, we'll need much more precise reproduction steps (e.g. is this via |
Thank you @trevor-scheer and @abernix for your investigations, I will try this week to isolate the problem on my side so we can reproduce it, I'll keep you updated! Thanks again! |
Happy to re-open this if you're able to provide a reproduction, but I'm going to close it for now. |
I'm using
apollo-server-lambda
to serve a GraphQL Application in an AWS Lambda andapollo-client
withapollo-link-persisted-queries
so I can benefit from "persisted queries" featureUpgrading to
2.12.0
broke the persisted queries requests, the server is now returning a 500 error whenever a client make a request using the persisted query extensionHere is a query exemple
And here is the server response
Rollbacking
apollo-server-lambda
to2.11.0
fixed the issueThe text was updated successfully, but these errors were encountered: