location 'replace' not working

[somentelucas]

I'm doing a transition to the same state (different params) and I intend to NOT keep this transition in history, so I did

$state.go("state.name", {param: param}, {location: 'replace'});

But when I go back it still goes through all the previous states.

[somentelucas]

So, has anyone tried 'replace' and knows if that works?
Thanks

[nateabele]

Can you post a plunkr that demonstrates the issue?

[ovidiubuligan]

I am also seeing this behavior with release v0.2.8 (2014-01-16)

[c0bra]

Seeing this in v0.2.10

[JoshWillik]

Also seeing this is v0.2.10

Edit: Also seeing this is v0.2.11

[JoshWillik]

I'm withdrawing my endorsement of this issue. Trying to replicate the issue in Plunkr revealed a bug in my code that was no fault of ui-router.

[sergey-ivlev]

I see the same behavior.
from parent state I did
$state.go(".childState.id", $stateParams, {location: 'replace'}).
When I go back at first time, it work correctly (it return me to parent state), but if repeat this (route to child state and go back ) two or more times it goes through all states to the root state.

[christopherthielen]

Post a plunkr or this won't be addressed.

[FreakTheMighty]

I'm seeing the same thing. I'll see if I can't put replicate in plunkr. Funny, I just create a plunkr/issue for ember for their replace functionality.

[FreakTheMighty]

Here's a plunkr http://embed.plnkr.co/1mykz3/preview.

1. Starting on route 0
2. Click on the tab for route 1, the route redirects to sub route routet1.list with location set to 'replace'
3. Click the back button, it should skip route1 and return to route0

If I repeat the last two steps, the route will no longer go back to route 0.

Edit

I replaced $state.go with $state.transitionTo and it reliably breaks for me after navigating to route1 twice.

[FreakTheMighty]

Ping, are people able to see the issue with this plunkr?

[mrtho1]

I wasn't able to, but I am seeing this issue in my app. I'm using ui-router-extras future states, not sure if that has anything to do with it.

[andertun]

@FreakTheMighty I am able to see the issue in your plunkr.

[OverZealous]

In case someone else hits this: I discovered it was being caused by angular-permission for me. Due to the way it's designed, it actually intercepts every state change, and breaks any options being passed to $state.go or $state.transitionTo.

(Also: note that permissions is inherited, so to see that removing permissions fixes the issue, you may need to set data.permissions to false.)

[OverZealous]

As a follow up, I really don't see a practical solution to this issue unless ui-router passes options into the $stateChangeStart event (and others).

I think the event broadcasts should be updated to toState, toParams, fromState, fromParams, options, which will allow a transition even to be paused, inspected or modified, then refired exactly as it was originally if appropriate.

[danharper]

For anyone using Ionic, there's a separate issue with their Back button. There's a couple of quite hacks in this issue:

ionic-team/ionic-framework#1287

[astanb]

I agree with @OverZealous, there really needs to be a way to access the options passed to ui-sref-opts, I am currently stuck as I need to interrupt a state change and then continue later on, but there is no way for me to find out whether I passed any options with the state change.

[christopherthielen]

I'll accept a PR that adds options as param #5 to state events

[mkoczorowski]

@OverZealous Thanks!
adding data.permissions: false worked for me

[petetaxi-test]

I was getting the same error as @FreakTheMighty plunkr.

Found a simple, albeit hacky workaround - put a slight delay on the $state.go using $timeout e.g. 10ms so that it happens after the first state transition completes.

[nateabele]

options has been added to $stateChangeStart. Can we close this?

[stecd]

@nateabele and how do you solve this issue using options from $statechangeStart? And where can I find the documentation for that?

[johncant]

Sorry for adding noise, but $state.go("state.name", {param: param}, {location: 'replace'}); is replacing the current state with the new state for me, which is what I expected, so the back button then goes from the new state to the previous state, skipping the current state. Recommend closing, since there's been no plunkr/jsfiddle in over 18 months, and two people have eliminated angular-ui-router as the cause of their manifestation of this issue. :)

[Mirodil]

still not wokring +1

[keshavwork]

still not wokring +1

[doorty]

still not working ++

[fijimunkii]

$state.go('place.to.be', $stateParams, { location: 'replace' }) is working for me.

I think the issue most people run into here is passing { location: 'replace' } as the second argument instead of the third.

[abachuk]

still not working +++

[christopherthielen]

@keshavwork

still not wokring +1

@doorty

still not working ++

@abachuk

still not working +++

These comments are not helpful. Post a plunker demonstrating that it's not working. http://bit.ly/UIR-Plunk

As far as I can tell, {location: 'replace'} works like it's supposed to. Prove me wrong by posting a reproduction.

[inad9300]

Still not working ++++

I appreciate the effort you put on developing this open source tool, but please, if many people say this feature does not work, at least take the time to verify it properly, otherwise who is going to rely on it?

I modified your plunkr to show the case when it doesn't work: when you programmatically call go() with {location: 'replace'}, which I think is the most common use case (as oppose to embed the options on the HTML).

There you can see how states are pushed into the history despite the "replace" intention, and you can still go back to them: https://plnkr.co/edit/i3R8jaRS6TrMz3KKHT10?p=preview

[dkordik]

@inad9300 here's an updated plnkr with the state.go pieces split out from the template, and using { location: 'replace' } instead of replace: true.

Seems to work for both the buttons and the select box examples.
https://plnkr.co/edit/H5FWyXlEjjLlHtC1ZqHP?p=preview [edit: woops, had your link at first]

[inad9300]

My mistake, sorry. So apparently it works after all :) Thanks for taking the time!

[christopherthielen]

@inad9300 next time please be considerate of the amount of time OSS maintainers spend. Snarky comments like "Still not working ++++" make me reconsider my involvement in OSS.

"if many people say this feature does not work, at least take the time to verify it properly"

I couldn't reproduce the issue. I posted a WORKING EXAMPLE. Issues without reproductions are very frustrating. I appreciated that you posted the plunker though 👍

[emanuel-virca]

I had the same issue and after research i have realized i was wrongly understanding the concept of replace.
When using location.replace you are replacing (exclude from history) the current page (not the one navigating to) with the page you are navigation to. So in ui-router case, when using $state.go('place.to.be', $stateParams, { location: 'replace' }) it will actually replace the current state with the state 'place.to.be'.
In other words, if you want to navigate to a page R that just redirects to another page X make sure you are navigation from page R () by using $state.go('X', $stateParams, { location: 'replace' }) . This way R will be replaced with page X

[juliobguedes]

Has this problem been solved? I'm using ui-router v0.2.13 along another group of dependencies (which I unfortunately cannot post here) and I'm facing the problem 😢

What I have here is: I have a list of objects, and clicking in an object on the list redirects me to an intermediary screen with a state.go(). In this intermediary screen, I use location: 'replace' to replace with the final screen after some logic.

When I click the navigator button once it works and I go to the previous screen, but clicking twice keeps me on the previous screen after a redirecting...

My exact code is $state.go(finalScreen, finalParams, { location: 'replace' });

PS: Sorry for my bad english, it isn't my home language, and I'm not used to technical terms