In my app, users are able to interact with a number of features without logging in, but some features require an account. When a user logs in, the app uses $state.go to reload the current view in order to update anything specific to that user. In general, this works very well. The problem comes in if a user logs in after navigating to a child view. The view is reloaded, but their history is not preserved so the back button goes away.
Any suggestions on a way to reload the current view while preserving the history stack?