Why ui-view doesn't work into components template?

[tamtakoe]

http://plnkr.co/edit/SKYVVGWw2GqABPoQHg8E?p=preview

[kukac7]

@tamtakoe missing $urlRouterProvider.otherwise('/');
http://plnkr.co/edit/EtfH7yyh4pFOuxssUAYV?p=preview

[tamtakoe]

@kukac7 I have updated my plnkr (added otherwise and templateUrl). It works good but only in plnkr. On local server it doesn't work. This is problem in templateUrl

[kukac7]

@tamtakoe there's nothing wrong with it, works well.
i do not know that there is a local development environment set for you, but for me there is no problem.

[eddiemonge]

If it doesn't work locally but does work elsewhere then I would examine your local setup to see whats different. Closing as this doesn't seem like a ui-router issue.

[tamtakoe]

@eddiemonge, @kukac7 This problem occurs because of $location service. See example:
http://plnkr.co/edit/kXcik8znN5HMp6ohRuMA?p=preview

If you remove problem service, app will works good

[eddiemonge]

That looks like a core angular problem

[eddiemonge]

It doesn't matter what you put into the run argument list, even nothing in there breaks it.

[tamtakoe]

I created an issue in angular repository angular/angular.js#14201

Investigate this problem, please. In what place and what time it appear. I or Angular team can not do it effectively, because we are not ui-router specialists.

[Narretz]

This might be a problem similar to angular/angular.js#1213 (A fix for this was merged, but it's not in a release yet). But the exact problem is different. With uiRoute, injecting location breaks the state update. I would say that this is a uiRouter bug.

[tamtakoe]

It works if you add $state near $location dependency http://plnkr.co/edit/GlZgwMSJjuSt0AVjT2zc?p=preview

[gkalpak]

This was indeed an issue very similar to the one pointed out by @Narretz.
This seems to have been fixed in v1.0.0alpha0: updated plnkr

[gkalpak]

This is the original commit that fixed this if anyone is curious: 46cf53d

[tamtakoe]

👍

[christopherthielen]

Thanks all. For others, the @tamtakoe workaround is simple:
app.run(['$state', function($state) {}]);

[christopherthielen]

Fixed in de3a04a
released as 0.3.0

[mickaeltr]

Hi @christopherthielen,

I am working on a legacy project with Angular 1.5 and ui-router 0.2. I am trying to upgrade it progressively to newer versions. Upgrading to ui-router 0.3 or 0.4 breaks the history.back() behaviour (if I go from state1 to state2 to state3 then back, it goes back to state1 instead of state2).

I figured out that replacing .constant("$state.runtime", { autoinject: true })
by .constant("$state.runtime", { autoinject: false }) fixes it.

Any idea? Many thanks

[christopherthielen]

@mickaeltr Not sure. I don't think the constant $state.runtime is used by either ui-router or angularjs. I suspect your app might have custom code that uses that value?

[mickaeltr]

@christopherthielen More precisely, my problem actually comes from $injector.get('$state'); (in the run block), which is executed when $state.runtime.autoinject is true. Sorry for my bad explanation!

[christopherthielen]

As for the back button, I'd try the latest version 1.0.10

[mickaeltr]

I'd like that but upgrading ui-router from 0.x to 1.x requires quite some work. So for now we'll have to stick to 0.2.18. Thanks @christopherthielen