Intermittent connection issues when first opening dev tools

[jerelmiller]

We've had a couple issues opened now (#1244, #1239) where users report an issue connecting to the client at first. After a refresh, the issue seems resolved.

I've now experienced myself now a few times now and think this might be a symptom of another underlying issues with the devtools communication. I think there is room for further improvement.

Unfortunately this one is a bit hard to track down as it only happens the first time before you can access logs from the devtools panel, then it seems to work reliably after connecting for the first time. I'm opening this issue to track this so that we can continue to make the devtools communication more bullet proof.

[jerelmiller]

Another comment regarding potential issues: #1244 (comment)

Perhaps this could be due to the ugprade of the extension while devtools is open? This might invalidate the extension and prevent messages from properly connecting in the background script. Perhaps we need to build some more resiliency into the message passing between the devtools and content scripts from the background script if something disconnects (message queue perhaps?).

[jerelmiller]

Another one: #1316

[paddyobrien]

I found that I need to go to the chrome task manager, kill the service work associated with the apollo inspector and restart dev tools.

[UlyssesInvictus]

I found that I need to go to the chrome task manager, kill the service work associated with the apollo inspector and restart dev tools.

Just confirming that this worked for me as well. On 4.12.3 of the dev tools.

[jerelmiller]

I have a suspicion that its related to background updates of the devtools. This is not handled well at all right now and from the surface it just appears to hang forever. That and we don't handle connections that may have dropped from the devtools to the background script due to inactivity.

I'm exploring both of these situations right now and hope to have a PR up sometime soon to make this work a little better.

Thanks for your patience and letting me know at least we have an (annoying) workaround in the meantime.