My understanding is that an ionic 4.x app used angular routing out of the box and not the traditional ionic navigation where the nav controller is used. I believe that the nav controller can be used if lazy loading is not as well in apps where ionic is not used as the framework.
@reedrichards you nailed it, I marked the other one as a solution as it gave a clear snippet to use.
Not sure if there is a points system on this board but if so, sorry
I would also point out to future readers that this the zone to be added to the import and the constructor as the snippet clearly shows but I missed and spent another 5 minutes googling “why doesn’t zone exist” before concluding that I must update to the latest beta and then realising I was just blind and dumb for a second.
It seems to solve other issues as well as I had a delete function with a confirm alert and on the ok it would delete that item from the data but the ui wasn’t being refreshed so it was still in the list of cards. I did some research and actually didn’t expect this to work as the Angular docs say zone is for when you update the data that you don’t want Angular to monitor and update, but I wanted the opposite. It worked anyway.
Hopefully the docs will have some clearer usage examples and explanation of what / why zone is required by the time it comes out of beta
FYI everyone: The github issue has been closed as fixed.
I have just removed the ngzone wrapper on an app running Ionic4.RC3 and I’m not seeing the error in the console any more so it seems that it is resolved.
HI
I am still getting this issue when navigating from one tab to other. Where do I need to put ngzone.rung()? Conference app on github is not doing any ngZone.run(), why is it required , not sure. folloiwng are my ionic details