[server@2.12.0] APQ registration causes "addProtobufError called before startTiming!"
See original GitHub issueI’m using apollo-server-lambda
to serve a GraphQL Application in an AWS Lambda and apollo-client
with apollo-link-persisted-queries
so I can benefit from “persisted queries” feature
Upgrading 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 extension
Here is a query exemple
{"operationName":"Themes","variables":{},"extensions":{"persistedQuery":{"version":1,"sha256Hash":"abc5e6f7d2b18d51853698b172c002b7866af0cab36178a6867b8f0f92a61a60"}}}
And here is the server response
{"errors":[{"message":"[internal apollo-server error] addProtobufError called before startTiming!","extensions":{"code":"INTERNAL_SERVER_ERROR"}}]}
Rollbacking apollo-server-lambda
to 2.11.0
fixed the issue
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (5 by maintainers)
Top Results From Across the Web
No results found
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
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.