Apollo-client-devtools: devtools keeps crashing

Created on 2 Oct 2019  路  10Comments  路  Source: apollographql/apollo-client-devtools

First time I open the devtools everything is fine, it just take sometime to load, but I can see my cache data. Sometimes if I make any change to my app and the browser reloads, then if I try to go to the cache it will automatically crash. Other times it just crash if I try to just move through the data.
I have to reload the chrome extension, close the inspector and re open it again.
I don't have much data in my dev env, so I don't think is related to that.

I wanna help to find what issue could be, is there any way to see logs or anything like that?

one difference I found is that after I write to the cache, my ROOT_QUERY changes

before

image

after

image

I'm on chrome Version 77.0.3865.90 (Official Build) (64-bit) and version 2.2.5 of the devtools

馃悶 bug

All 10 comments

I'm experiencing that exact same issue. Same Chrome version also.

+1

+1, when I refresh the page, I see connecting to Apollo Client message then crashes.

Any resolutions for this issue? My Apollo Devtools crashed when 'cache' button is clicked after the data is recieved from API. tabs work just fine so long as I don't click on the cache button to view cache! Please help.

I'm seeing this issue as well. For me it's new as of the latest Chrome update (83.0.4103.61). I'm on the latest appollo devtool client (2.3.0) and have the most recent apollo react packages.

I'm seeing the following when I debug the apollo devtools and then click on the cache tab:

12098devtools.js:1 TypeError: Cannot read property '__typename' of null
    at T (devtools.js:1)
    at Yi (devtools.js:1)
    at Io (devtools.js:1)
    at Ka (devtools.js:1)
    at za (devtools.js:1)
    at Cu (devtools.js:1)
    at Ou (devtools.js:1)
    at Pu (devtools.js:1)
    at On (devtools.js:1)

Thanks @eDubrovsky 馃憦 I'll keep my eye out for that release.

If anyone wants to test out this PR https://github.com/apollographql/apollo-client-devtools/pull/273, let me know if this fixes the issue!

2.3.1 fixed this for me (from source)! Do releases happen automatically at some point?

@threehams Glad it resolved the issue! Releases are a manual process but both the Firefox and Chrome extensions should be at 2.3.1 now.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

iki picture iki  路  7Comments

konsumer picture konsumer  路  7Comments

robclouth picture robclouth  路  5Comments

kissu picture kissu  路  4Comments

richburdon picture richburdon  路  4Comments