Augury not showing state for many components #1340
Comments
Hey, @tkstang Does the state tab show "no state to show", "loading state..." or any other message? Could you open a second inspector window, and tell me if you see any errors in the console? (hit option+command+i while looking at Augury's devtools panel) |
It shows "loading state..." for a few seconds and then switches to "no state to show." I'm not sure if I'm not quite understanding you correctly but hitting option+cmd+i while looking at augury is just going to close the inspector window. If you mean errors with the application there are no errors aside from a server error from a network request our back end that is down. Nothing with the application itself. If there is some way I'm missing to actually see any errors with augury itself perhaps I'm not quite following you. Also just to clarify I have had this issue for months, I was hoping it would be resolved by fixes that were presented as solutions for other open issues of the same problem. |
option+cmd+i while looking at augury should open a second inspector window, which inspects the first inspector window. |
I'm getting a bunch of this error
|
Ok, so we have another edge case affecting the serializer. We need to figure out why there is a syntax error in the generated serialized message. |
On Manjaro with :
I face a very similar issue, the message "No state to show" appear on some components but with a different error in the inspector :
|
Same issue, Angular 7.0.1 Augury 1.19.1 error -
|
I guess same as well, Angular 7.0.1, Augury 1.20.0
` |
So this category of issue seems to manifest itself in many different cases. Some which have been fixd and others not. It has to do with how the angular app details are serialized and sent to the devtools extension. This can be difficult to track down and replicate due to the nature of how it works and diverse set of things that need to be serialized/deserialized. As always a repo or sample to reproduce is the best way to track these issues down. Barring that can anyone provide some additional details about the types of components that are not showing state?
|
Sure! Thanks for the help! So i've done some digging and eventually ended up with Angular Fire as the main suspect. Steps to reproduce -
open
open
and BAAM! augury state view stops working. removing the injection fixes it. |
I can confirm, AngularFire is also beeing injected in my case. |
I am not using AngularFire, it is a rather large and complex app so it would take me quite some time to go through all of the components that do and do not show state and list their dependencies but I will try to do that in the next few days when I have a chance. Generally the components that show state seem to be small components without router. |
Thanks for the detailed feedback. This should help a great deal in tracking down this particular state issue. We've also seen some issues with router state, but thought we'd fixed those as well. Definitely more to go on now. Much appreciated! |
I've published a chrome canary build from the https://chrome.google.com/webstore/detail/augury-canary-build/leechohfifidanmkioncamdcibhmmcji?hl=en |
Works perfect! Thank you so much! |
I can confirm, state works :) |
Also confirming it works. State hasn't worked for me with Augury for months with none of the other fixes seeming to make a difference. So happy to report this one seems to have been successful. Thank you for all of your hard work and such a great tool! |
Does the augury-canary-build only work with chrome canary or regular chrome as well? Installed the extension in regular chrome and getting issues, the console for the extension is full of this error
|
@furier it should work on both. After being briefly fixed once again it was not working for me, same error and I found the solution to be to remove the core-js/es6/date polyfill from your polyfills file. This is a date polyfill for older IE browsers so you may just want to comment it out when you're doing development. You can see #1351 for further discussion. Hopefully that works for you as well! |
Great, and where is this file located? |
@furier You should have a polyfills.ts file in the root of your project |
D by |
Augury version (required): Canary build 1.19.3
Angular version (required): 6.0.7
Date: 9/10/18
OS: Mac OS High Sierra
I know this has been an on going issue that seems to have been a problem for many people, all previously opened issues were marked as resolved so I'm opening a new one. I'm using the most current canary build and many of my components still load and then indicate "no state to show" in the properties tab. Unfortunately I can't share a repository as the issue is with a private repo at my place of work. The application is rather complex, it seems that simpler smaller components will show state but most larger components do not. I have previously seen in other issues where there were mentions of things like components with router as a dependency working, components loaded with resolvers, etc. All of these issues are currently marked as resolved, however, and I am still experiencing the issue.
The text was updated successfully, but these errors were encountered: