Ember-inspector: Ember Inspector reporting incorrect version number in Info Pane

Created on 18 Jan 2017  路  4Comments  路  Source: emberjs/ember-inspector

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, https://github.com/emberjs/ember-inspector/pull/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.

Most helpful comment

@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.

All 4 comments

@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.

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

@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!

Glad the issue was addressed! 馃榿

Was this page helpful?
0 / 5 - 0 ratings