Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

'Loading...' after Canary update? #394

Closed
tycho01 opened this issue May 14, 2016 · 6 comments
Closed

'Loading...' after Canary update? #394

tycho01 opened this issue May 14, 2016 · 6 comments
Assignees
Labels

Comments

@tycho01
Copy link

@tycho01 tycho01 commented May 14, 2016

I just updated my Chrome Canary version to 52.0.2735.0 (64-bit), and it appears Augury is stuck on 'Loading...' for me now. I can't exclude other causes yet, but was wondering if anyone else had experienced something similar. If not, I'm clueless atm and this can be closed.

@tycho01

This comment has been minimized.

Copy link
Author

@tycho01 tycho01 commented May 16, 2016

@igor-ka: Sorry, I'm a bit confused as to what you meant by response. Could you elaborate please?
I'm still experiencing this issue; neither browser restarts nor Augury reinstalls appear to be fixing it for me so far.

@igor-ka

This comment has been minimized.

Copy link

@igor-ka igor-ka commented May 16, 2016

@tycho01 sorry for the confusing response :)

We will investigate this issue, as we need to figure out if this is a Chrome Canary issue (which seems to work for us) or if this is something else.

It would be great if you could tell us which version of angular2 you are using as well. We will be releasing a version that supports RC1 very soon. Otherwise, I we only support the beta for now.

PS. Also your app needs to run in dev mode for Augury to work

@st-clair-clarke

This comment has been minimized.

Copy link

@st-clair-clarke st-clair-clarke commented May 16, 2016

I am experiencing the same problem with Canary (latest version) too. No such problem with Chrome.

@sumitarora

This comment has been minimized.

Copy link
Member

@sumitarora sumitarora commented May 16, 2016

@tycho01 @st-clair-clarke In the latest update of the chrome window.postMessage has been deprecated this is the reason why it's not working see the message below. We will investigate if it's possible to support both the versions with the next Augury Release

'window.postMessage(message, transferables, targetOrigin)' is deprecated and will be removed in M54, around October 2016. Please use 'window.postMessage(message, targetOrigin, transferables)' instead. See https://www.chromestatus.com/features/5719033043222528 for more details.

@tycho01

This comment has been minimized.

Copy link
Author

@tycho01 tycho01 commented May 17, 2016

Thank you for the update. Interestingly, I had been using Augury with ng2 RC1 in production mode. Only after the Canary update did I start experiencing issues. But this sounds hopeful; until resolved I'll try stable Chrome then. :)

@clbond clbond added in progress and removed ready labels Jun 13, 2016
@clbond clbond self-assigned this Jun 13, 2016
@clbond

This comment has been minimized.

Copy link
Contributor

@clbond clbond commented Jun 13, 2016

It turns out this had nothing to do with the postMessage API being changed. It was a result of our recursive node-item component not working in Chrome Canary. First I determined that the promise being returned by bootstrap() was never resolved or rejected. Then I did some extensive debugging of runtime_compiler.js and was able to determine that ultimately the promise that was hanging the application was associated with node-info. From there, I took out the recursive reference in [directives] and in the .html file and it completely resolved the issue, and the application was able to start correctly. Then with some trial and error, I noticed that changing the component from using templateUrl to template actually resolves the problem. So there is something about the interplay of templateUrl and recursive components which does not work on Chrome Canary. It's not clear whether this is a Chrome bug or an Angular 2 bug, but nonetheless the issue is fixed by this PR: #425

clbond added a commit that referenced this issue Jun 14, 2016
#394: Fix Augury hanging on load on Chrome Canary
@sumitarora sumitarora closed this Jun 23, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
5 participants
You can’t perform that action at this time.