This bug still exists in Ionic 5. Any idea? It is related to this thread: Ionic 4 Route Reuse strategy
With a custom route reuse strategy, this could be fixed. But maybe somebody has an idea for another workaround?
This bug still exists in Ionic 5. Any idea? It is related to this thread: Ionic 4 Route Reuse strategy
With a custom route reuse strategy, this could be fixed. But maybe somebody has an idea for another workaround?