augury icon indicating copy to clipboard operation
augury copied to clipboard

Augury not working with debugging web extension apps

Open kspearrin opened this issue 7 years ago • 6 comments

Augury version (required): 1.16.0 Angular version (required): 5.2.0 Date: OS: Windows 10

Demo test application: https://github.com/bitwarden/browser

Description of issue: Augury does not seem to work with Angular apps running in a (Chrome) web extension popup.

Steps to reproduce:

  1. Create a popup browser action that is an Angular app.
  2. Debug with dev tools.
  3. Switch to Augury tab. None of the Augury tabs shows any information about the running app.

image

Additional details:

  • App is packaged with webpack, running with JIT compilation, dev mode.
  • Chrome extensions run under the chrome-extension:// protocol so maybe that has something to do with it?

P.S. Sorry if this has been posted before. I did some search but wasn't want to locate anything.

kspearrin avatar Apr 13 '18 20:04 kspearrin

@kspearrin - Do you mind trying the latest version of Augury. We've made quite a few stabilization fixes since the release posted.

andrewthauer avatar Aug 16 '18 20:08 andrewthauer

@andrewthauer Yes, I just tested with Augury 1.19.1 and this is still an issue.

kspearrin avatar Aug 17 '18 04:08 kspearrin

@kspearrin - Without additional details as to the errors it's hard to say. The use case of debugging another Angular devtool with Augury seems a bit low. However, in theory this should work. But it looks like you have a fairly customized build setup, etc. so it could be a number of things going on. Happy to look at it when we get a chance.

In the meantime it might help if you where able to inspect the augury devtool window itself and see if there are any console errors showing up. You should be able to right click on the augury UI and click "inspect". This will pop up another inspector window which hopefully has some additional details.

andrewthauer avatar Aug 17 '18 13:08 andrewthauer

Not seeing anything of note when inspecting augury itself. Here's a screenshot:

image

kspearrin avatar Aug 17 '18 13:08 kspearrin

Yeah, that's odd. I would have expected to see something. Did you try reloading after you inspected? It's possible any actual errors only occur when your angular app first bootstraps.

andrewthauer avatar Aug 17 '18 13:08 andrewthauer

@andrewthauer Reloading my app after having the dev tools open didn't seem to change anything.

kspearrin avatar Aug 17 '18 13:08 kspearrin