Adobe-CEP / Getting-Started-guides

Getting Started guides and samples for CEP extensions
Apache License 2.0
548 stars 92 forks source link

How to keep devtools connected after reloading my extension #31

Closed celeryclub closed 2 years ago

celeryclub commented 3 years ago

Submit an issue

Topic

This is an issue regarding:

Versions

Description of the issue

I'm working on a CEP extension and I have a question about debug workflows. I've followed the "Client-side debugging" doc, and everything is working as expected. https://github.com/Adobe-CEP/Getting-Started-guides/tree/master/Client-side%20Debugging#debugging-in-chrome

However, when I make a change to the extension and disable/re-enable it in the CC app to see my changes, my devtools connection is severed and I'm shown this message: "Debugging connection was closed. Reason: WebSocket disconnected". Then I have to go back to the previous page and click the link for my extension again.

Is there a workaround for this issue that would prevent my session from being disconnected every time I reload the extension? Or perhaps there's a way to reload the extension that doesn't involve disabling/re-enabling it within the CC app?

Thanks!

Proposed solution or attempted solutions that failed

n/a

Stamker commented 3 years ago

hi @celeryclub You can add a link with "location.reload()" code in your html file to reload the page, that will be reload the extension without losing the connection in your debug tool. for example: <a href="javascript:location.reload(true)">Refresh panel</a>

celeryclub commented 2 years ago

Thanks @Stamker! That does seem to work.