title: Angular Universal requires initialNavigation=enabled which breaks APP_INITIALIZER and Guards
body: <p>While adding Angular Universal to our app, we had to set the <code>initialNavigation=&quot;enabled&quot;</code> flag on the router, in order to avoid flickering.</p>
  <p>Now this comes with 2 issues for us:</p>
  <ol>
  <li>we create routes dynamically, opening one of those routes now fails</li>
  <li>because the app does not wait for the <code>APP_INITIALIZER</code>s to load, routes that are guarded cannot be loaded, because the guard always assumes the user is unauthorized, because the check is happening in the <code>APP_INITIALIZER</code></li>
  </ol>
  <p>I found several Github issues about this (i.e. <a href="https://github.com/angular/universal/issues/1623" rel="nofollow noreferrer">https://github.com/angular/universal/issues/1623</a>) but none of them really provided a solution.</p>
  <p>How can I use <code>initialNavigation=&quot;enabled&quot;</code> while at the same time wait for the <code>APP_INITIALIZER</code>s to be executed?</p>
  <p><strong>edit (01/02/2021)</strong>: in Angular 11 the wording has changed and the option is now called <code>enabledBlocking</code>. The issue mentioned here however is not touched by this.</p>