<p dir="auto"><strong>I'm submitting a ...</strong>  (check one with "x")<br>
[x ] bug report =&gt; search github for a similar issue or PR before submitting</p>
<p dir="auto"><strong>Current behavior</strong><br>
Related to <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="158752959" data-permission-text="Title is private" data-url="https://github.com/angular/angular/issues/9047" data-hovercard-type="issue" data-hovercard-url="/angular/angular/issues/9047/hovercard" href="https://github.com/angular/angular/issues/9047">#9047</a>. AppConfig is loaded using APP_INITIALIZER. Before the returned promise has been resolved, the initializer for the requested route is already invoked. The initializer will fail if it requires settings from AppConfig</p>
<p dir="auto"><strong>Expected behavior</strong></p>

<p dir="auto">The route resolvers should be invoked after the APP_INITIALIZER promise(s) have been resolved</p>
<p dir="auto"><strong>Minimal reproduction of the problem with instructions</strong><br>
<a href="https://plnkr.co/edit/PbTGxQ2X1aKUVfUvJdcO?p=preview" rel="nofollow">https://plnkr.co/edit/PbTGxQ2X1aKUVfUvJdcO?p=preview</a></p>
<p dir="auto"><strong>What is the motivation / use case for changing the behavior?</strong><br>
Use API url from AppConfig in a resolver</p>
<p dir="auto"><strong>Please tell us about your environment:</strong><br>
Not relevant</p>
<ul dir="auto">
<li>
<p dir="auto"><strong>Angular version:</strong> 2.0.X<br>
2.4.8 (I have not tried downgrading but I thought is was working properly in 2.4.7)</p>
</li>
<li>
<p dir="auto"><strong>Browser:</strong> [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]<br>
Chrome but does not seem relevant</p>
</li>
<li>
<p dir="auto"><strong>Language:</strong> [all | TypeScript X.X | ES6/7 | ES5]<br>
Typescript</p>
</li>
</ul>
<p dir="auto"><strong>I'm submitting a ...</strong>  (check one with "x")</p>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="[x ] bug report 
[ ] feature request
[ ] support request"><pre class="notranslate"><code class="notranslate">[x ] bug report 
[ ] feature request
[ ] support request
</code></pre></div>
<p dir="auto"><strong>Current behavior</strong></p>

<p dir="auto">After update angular my application shows the loader and that's it, nothing happens.<br>
On version 2.4.7 the site works just fine.<br>
I have no errors on console. I have no clue what's causing this issue except the version change<br>
<strong>Expected behavior</strong></p>

<p dir="auto">The site should work just like it 2.4.7</p>
<p dir="auto"><strong>Minimal reproduction of the problem with instructions</strong></p>

<p dir="auto"><strong>What is the motivation / use case for changing the behavior?</strong></p>

<p dir="auto">Updating angular from 2.4.7 to 2.4.8</p>
<p dir="auto"><strong>Please tell us about your environment:</strong></p>

<p dir="auto">Windows 10,<br>
Webstorm 2016.3.3</p>
<ul dir="auto">
<li><strong>Angular version:</strong> 2.0.8</li>
</ul>

<ul dir="auto">
<li><strong>Browser:</strong> [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]</li>
</ul>

<p dir="auto">Chrome 56.0.2924.87 (Only one that was tested)</p>
<ul dir="auto">
<li><strong>Language:</strong> [all | TypeScript X.X | ES6/7 | ES5]<br>
TypeScript 2.1.6</li>
</ul>