Skip to content
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

error[E005]: The response from Apollo Studio was malformed. Response body contains null value for "implementing_services" #570

Closed
gablaflamme opened this issue May 25, 2021 · 2 comments · Fixed by #571
Labels

Comments

@gablaflamme
Copy link

Description

When following the quickstart guide (https://www.apollographql.com/docs/federation/quickstart-pt-2/),
I ran into this error when trying to publish my first subgraph using this command:
rover subgraph publish <MY_OWN_GRAPH_NAME>
--routing-url https://rover.apollo.dev/quickstart/products/graphql
--schema ./products.graphql
--name products
which is basically the exact command in the quickstart guide. Here is the complete error I got from running this:

error[E005]: The response from Apollo Studio was malformed. Response body contains null value for "implementing_services"
This error was unexpected! Please submit an issue with any relevant details about what you were trying to do

I made it work by using "npx apollo publish" for my first subgraph instead. From there, rover started working for other subgraphs.

Steps to reproduce

Follow step-by-step the quickstart guide here https://www.apollographql.com/docs/federation/quickstart/

Expected result

The first subgraph should have been published successfully.

Actual result

error[E005]: The response from Apollo Studio was malformed. Response body contains null value for "implementing_services"

Environment

Version: 0.1.2
Install Location: /usr/local/share/.config/yarn/global/node_modules/binary-install/bin/rover
OS: Mac OS 11.2.3 [64-bit]
Shell: /bin/zsh

@gablaflamme gablaflamme added bug 🐞 triage issues and PRs that need to be triaged labels May 25, 2021
@EverlastingBugstopper
Copy link
Contributor

Thanks for submitting this @gablaflamme - will get a fix out for this today.

@EverlastingBugstopper
Copy link
Contributor

this fix is out in 0.1.3!

@abernix abernix removed the triage issues and PRs that need to be triaged label Jun 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants