Troubleshooting

If the inspector cannot detect an Ember application, you will see the following message:

Some of the reasons this happens:

• This is not an Ember application
• You are using an old Ember version ( < 1.0 ).
• You are using a protocol other than http or https. For file:// protocol, follow these steps.
• The Ember application is inside a sandboxed iframe with no url (if you are using Jsbin, follow these steps.

Due to the way Jsbin uses iframes, the inspector doesn't work with edit mode.

To use the inspector, switch to the "live preview" mode by clicking on the arrow circled below.

If you always have to reload the application after you open the inspector, that may mean your application's booted state is corrupted. This happens if you are calling advanceReadiness or deferReadiness after the application has already booted.

When you click on the Data tab, and see this message:

It means that you are either not using a data persistence library (such as Ember Data), or the library you're using does not support the Ember Inspector.

If you are the library's author, see this section on how to add Ember Inspector support.

You click on the Promises tab, and see this message:

This happens if you are using a version of Ember < 1.3.

If the Promises tab is working, but there are promises you can't find, it's probably because these Promises were created before the inspector is activated.

To start detecting promises the moment the app boots, click on the Reload button below:

Firefox addons need to go through a review process before every update. This causes the Firefox Ember Inspector to usually be one version behind.

Unfortunately we don't have control over this process, so if you need the latest inspector version, you will have to download and install the inspector manually from GitHub.