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.
// make some http request data