Related to: https://github.com/driftyco/ionic/issues/3941 and The “back” navigation button visible when using resolve in state configuration
When resolving data before showing view takes more than 300ms the view fails to clear history and shows back button instead.
This is a production critical bug for me! Is see that this bug has been around for ages, is there still no fix or work around?
At the moment, resolves work against how Ionic handles history and navigation. As resolves can be pretty ambiguous on when they start/end, there’s no reliable way to catch them and then apply the proper next view options needed.
As we’ve stated on that issue,
The risks of hacking things together is too great. Plus Ionic also provide the viewLifecycle events you can use instead.
.constroller('SecondView', function($scope){
$scope.$on('$ionicView.beforeEnter', function(){
// make some http request data
})
})