Async data not rendered in the initial load

Bug Report

What is the expected behavior?

When I load the application initially all data passed into my components (i.e. header, router-outlet, footer) is rendered. In this case I expect to see links generated from an api in the footer.

What is the current behavior?

More often than not, I see a commented out html line where I expect to see the async data. But right after I reload, I see the data. This is unacceptable because the sole reason for using Angular-Universal (SSR) is for SEO crawl.

What modules are related to this issue?

- [x ] aspnetcore-engine
- [ ] common
- [ ] express-engine
- [ ] hapi-engine
- [ ] module-map-ngfactory-loader

Minimal reproduction with instructions:

What is the use-case or motivation for changing an existing behavior?

SEO Crawl.

Environment:

@nguniversal versions

• aspnetcore-engine: aspnet-prerendering@3.0.1 (i think this is what you eman)
• common:
• express-engine:
• hapi-engine:
• module-map-ngfactory-loader: 5.0.0-beta.5

<!--
Output from: `ng --version`.
Angular CLI: 1.7.0
Node: 8.11.3
OS: win32 x64
Angular: 5.2.5
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, platform-server, router

@angular/cli: 1.7.0
@angular-devkit/build-optimizer: 0.3.1
@angular-devkit/core: 0.3.1
@angular-devkit/schematics: 0.3.1
@ngtools/json-schema: 1.2.0
@ngtools/webpack: 1.10.0
@schematics/angular: 0.3.1
@schematics/package-update: 0.3.1
typescript: 2.5.3
webpack: 3.11.0
If nothing, output from: `node --version` and `npm --version`.
  Windows (7/8/10). Linux (incl. distribution). macOS (El Capitan? Sierra?)
-->

Is there anything else we should know?

Project was created from asp.net core SDK 2.1.302. Leveraging TransferState.

[CaerusKaru]

In your example, change the SSR interceptor not to use Object.assign. Use request.clone({url: fullUrl}) instead.

[angular-automatic-lock-bot[bot]]

This issue has been automatically locked due to inactivity. Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}