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

Ember Inspector reporting incorrect version number in Info Pane #628

Closed
seanmhoffman opened this issue Jan 18, 2017 · 4 comments
Closed

Comments

@seanmhoffman
Copy link

I've been having difficulties recently debugging an ember application that uses liquid-fire using the ember-inspector. Presently I am unable to view any nested components of a liquid-outlet. Did some Googling and came across a GitHub Issue which references that issue and was fixed in the most recent update, #428. However when trying to determine what version of the Inspector I am on I realized that the version number reported on Chrome's extension page and the version number that appears in the Inspector's info pane are completely different. Chrome says I have 2.0.4 installed but the inspector reports that its still on 1.10.0. I'm not sure which is the correct version, although I am not seeing the reported fixes for the issue Im experiencing with the version of the Inspector I am using currently.

@locks
Copy link
Contributor

locks commented Jan 19, 2017

@seanmhoffman what version of Ember is your application? The Inspector has an architecture where it loads a different Inspector depending on the version of Ember your application is using.
This was done so the Inspector can be updated more easily, and so one version doesn't have to support all versions of Ember, as that meant a lot of code just to check features and whatnot.

@locks
Copy link
Contributor

locks commented Feb 11, 2017

Closing due to inactivity. Please re-open if the above comment wasn't clear enough!

@locks locks closed this as completed Feb 11, 2017
@seanmhoffman
Copy link
Author

@locks Heh, sorry for the late response 😅
That did fix my issue though. I was able to upgrade to the newest version of Ember and the Inspector seemed to reflect that as well. I also had to force Chrome to update the extension because it wasn't pulling down the new version.

Thanks again!

@locks
Copy link
Contributor

locks commented Oct 18, 2017

Glad the issue was addressed! 😁

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants