New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Ionic v4-Beta.15] Navigation triggered outside Angular zone, did you forget to call ''? #16270

iAmAnkeeta opened this Issue Nov 8, 2018 · 1 comment


None yet
1 participant

iAmAnkeeta commented Nov 8, 2018

Bug Report

Ionic Info
Run ionic info from a terminal/cmd prompt and paste the output below.


   ionic (Ionic CLI)             : 4.3.0 (/Users/user/.nvm/versions/node/v10.13.0/lib/node_modules/ionic)
   Ionic Framework               : @ionic/angular 4.0.0-beta.15
   @angular-devkit/build-angular : 0.8.7
   @angular-devkit/schematics    : 0.8.7
   @angular/cli                  : 6.2.7
   @ionic/angular-toolkit        : 1.1.0


   cordova (Cordova CLI) : 8.1.2 (cordova-lib@8.1.1)
   Cordova Platforms     : android 7.1.1, ios 4.5.5
   Cordova Plugins       : cordova-plugin-ionic-keyboard 2.1.3, cordova-plugin-ionic-webview 2.2.0, (and 15 other plugins)


   Android SDK Tools : 26.1.1 (/Users/user/Library/Android/sdk/)
   ios-deploy        : 1.9.4
   ios-sim           : 7.0.0
   NodeJS            : v10.13.0 (/Users/user/.nvm/versions/node/v10.13.0/bin/node)
   npm               : 6.4.1
   OS                : macOS High Sierra
   Xcode             : Xcode 10.0 Build version 10A255```

Describe the Bug
Prior to beta 15 when working on beta 12, the app page was loading fine, didn't have to use ngZone to display the UI. After the upgrade with nothing change on the code, we are getting a white screen, and once you tap on the screen, the dom elements load. We are also seeing lot of Navigation triggered outside Angular zone, did you forget to call ''? warnings.

@ionitron-bot ionitron-bot bot added the triage label Nov 8, 2018


This comment has been minimized.

iAmAnkeeta commented Nov 19, 2018

I was seeing the warning when I was navigating to a page using Router from @angular/router

Once I added all the route to ngZone => self.router.navigate(['/route1'])), I stopped getting the warning.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment