Apollo-client-devtools: Latest update breaks Asana.com

Created on 15 Mar 2021  路  12Comments  路  Source: apollographql/apollo-client-devtools

Intended outcome:
I'm trying to visit an organisation in Asana.com.

Actual outcome:
The Asana dashboard does not load. The loading spinner keeps circulating between different Asana assets that are loaded (projects, inbox etc). When disabling the Apollo Chrome extension, the page loads. I can also access the page when re-enabling the extension.

How to reproduce the issue:

Desktop (please complete the following information):

  • OS: Windows 10
  • Browser Chrome
  • Browser version Version 89.0.4389.82 (Official Build) (64-bit)
  • Extension version 3.0.0

Possibly related to #455?

馃悶 bug

All 12 comments

Some console output:

[2021-03-15T15:47:18.240Z] Created early WebSocket with PageLoad shard specification
bundle.js:2 Uncaught TypeError: Cannot set property 'exports' of undefined
    at Object.<anonymous> (bundle.js:2)
    at Object.page_load_bundle_evaluation_failure_checker (bundle.js:2)
    at o (bundle.js:2)
    at Object.page_load_bundle_evaluation_failure_checker (bundle.js:2)
    at o (bundle.js:2)
    at bundle.js:2
    at bundle.js:2
start_session?path=%2F0%2Fhome%2F1199901208724637&query_string=&rparam=01807108763015184487&user_id=_id=&t=1615823238124&k=key_one&h=&release_revision=20210311_181458_b09cbd9598bedb2b021fbe939c388a2a1f8accd2&sync_cluster=prod:1 Uncaught ReferenceError: Deserializer is not defined
    at start_session:1
    at start_session:1

Thanks @ggravlingen - definitely sounds like the same problem.

Latest update also broke TargetProcess for people in my organization.

I can toggle this extension to break/fix Targetprocess's initial loading screen with full consistency.

Fixed in https://github.com/apollographql/apollo-client-devtools/pull/460, but re-opening until the new version is published.

Apollo Client Devtools 3.0.1 has been submitted for review; 馃it will be available shortly.

3.0.1 should be available now - let me know if this issue still occurs. Thanks!

Thanks for looking into this! I'm on 3.0.1 now and unfortunately, the error still persists. Same error in console as yesterday. Is there any more data I can retrieve on my end in order to help?

image

Same here, on version 3.0.1 and I couldn't use Asana until I disabled the extension.

3.0.2 has been submitted for review with a fix for this - thanks!

3.0.2 has been published and this issue appears to be fixed. Let us know otherwise. Thanks!

Just confirming that it works on 3.0.2. Thanks for your help!

Phew - thanks @ggravlingen and sorry about that!

Was this page helpful?
0 / 5 - 0 ratings