Apollo-client-devtools: Devtools backend.js error on version 2.3.2

Created on 29 Oct 2020  路  10Comments  路  Source: apollographql/apollo-client-devtools

I've been trying to open the Apollo Client DevTools on localhost:3000 and I keep getting this error. It did not use to happen on previous versions. Is anybody getting the same issue?

apollo-client-error

Most helpful comment

Good news! I was able to get a reproduction and a fix is coming. https://github.com/apollographql/apollo-client-devtools/pull/307 If you are able to check out the associated PR and confirm this fixes the error, that would be awesome!

All 10 comments

@wesbragagt Oh, thanks for reporting this. I'll see if I can reproduce this error - I _think_ I have an idea of what might happening.

@wesbragagt What version of Apollo Client are you using?

I'm hitting the same error FYI - Apollo client version 3.1.3

This started happening for me when updating from 2.3.1 to 2.3.2.

@apollo/[email protected]

Same for us, also started to happen on 2.3.2.

I have the same issue. I use "@apollo/client": "3.2.5",

Is anyone able to submit a small, runnable reproduction? It would be super helpful as I'm unable to reproduce this issue.

A temporary workaround to manually revert back to v2.3.1:

  1. Clone this repo
  2. Checkout the previous release tag: git checkout v2.3.1
  3. Install deps: npm ci
  4. Build the extension: npm run build
  5. Install the build output as an extension in Chrome

    1. ensure the "real" extension is uninstalled

    2. Nav to chrome://extensions/

    3. Switch on "Developer mode" in the top right corner

    4. Click the "Load unpacked" button in the top left corner

    5. Select the output file (it will be in the .../shells/webextension folder wherever you have cloned the repo)

  6. Thank the dev team here for fantastic automation and a well-managed project that makes this possible 馃帀

Good news! I was able to get a reproduction and a fix is coming. https://github.com/apollographql/apollo-client-devtools/pull/307 If you are able to check out the associated PR and confirm this fixes the error, that would be awesome!

Version 2.3.3 is released with a fix for this issue!

Was this page helpful?
0 / 5 - 0 ratings

Related issues

jeffdesign picture jeffdesign  路  5Comments

glauberfc picture glauberfc  路  5Comments

meyer picture meyer  路  3Comments

richburdon picture richburdon  路  4Comments

nanandn picture nanandn  路  4Comments