Augury not showing properties for a component

[walrus95]

Augury version (required): 1.16.0
Angular version (required): 4.4.3
Date: 5/16/18
OS: Windows 10

Description of issue:
I load my web application and open it up in Augury. Augury will only occasionally show the properties for a component and their values, and sometimes after having to click around at random a ton. It's simply unreliable, big time. Just now I have been trying to get it to show me something useful for half an hour with no luck. Today is decided to take the day off, apparently, as it did yesterday too.

Great idea for a tool. When it works, it's helpful. Most days though, it's on vacation, which makes it more trouble than it's worth. If you could get it working consistently, it would be a huge asset for Angular development.

I have found that the Firefox version is much more response. It get bogged down easily in Chrome.

It works a little bit better than the old betarang, but not by much. I never got betarang to work at all.

Steps to reproduce:

1. Use it on an Application of any complexity, and you'll see what I'm talking about.

Additional details:
Get funding from Google to Make Augury Great Again.

[andrewthauer]

@walrus95 - @santiago-elustondo published an Augury Canary build that fixed a similar issue that many people have been having. If you wouldn't mind, could you install the canary build and see if this resolves your issue?

[walrus95]

Welp, one of my components is showing its state in Augury with Augury Canary, but only one, and it's not the one I need to inspect. I would say Canary gets you about 5% of the way there, so it's an improvement, a small improvement though.

Got a Canary for FireFox?

[walrus95]

Update: After a little coaxing, I managed to get Canary to actually show me the state of the component in which I'm interested. Go Canary! Now if we just had a FireFox Canary life would be good. (The Augury for Chrome runs slow, but FF Augury is nice and snappy.)

[santiago-elustondo]

What coaxing was necessary?

[santiago-elustondo]

Thanks for your input, @walrus95
We will continue to investigate this issue, please let us know if you find any new information, or if you can help us replicate the issue.
We don't currently have a Canary for FF, but we will hopefully release one soon. We only released onto the addon store very recently.

[walrus95]

@santiago-elustondo Thank you! I had to click around the component tree a bit to get the properties for the component in which I'm interested to show up, but then I tried it again just now and the proprieties showed up right away without the need to click around first. Unfortunately, it then crashed the Chrome tab right after. I find the FF version much more stable. I have never had Augury crash on FF.

[santiago-elustondo]

Version 1.16.2 released on FireFox just now, which brings the official FireFox and Chrome versions up-to-date with the Canary Build.

[tkstang]

This is still a problem for me even with the canary build 1.19.3