问题背景

某客户使用了第三方的Authentication service来实现Spartacus用户的登录机制： 使用token，调用另一个API，获取user信息。

We found out that the problem was caused by using this.windowAdapter.getWindow().sessionStorage.* without previously checking if the sessionStorage is actually available. In SSR it was undefined.

If you wrap all the calls in an if (this.windowAdapter.getWindow().sessionStorage) {...} the PLP pages are being SSRed correctly.

As an additional, browser’s storage (sessionStorage, localStorage) API is not available in SSR, therefore code defensively.

自开发的用户认证：

sessionStorage和localStorage都无法在SSR模式下工作。 This is the reason of SSR not working on the pages where these objects are being used.

If window or localStorage objects are required to be used with SSR then include the library @ng-toolkit/universal .

An example of using window and localStorage objects with SSR can be referred at this article

最佳实践

最好不要在SSR模式下进行用户认证(user Authentication)相关的逻辑：

解决方案

I can suggest you to try to inject the @Inject(PLATFORM_ID) protected platform: any (from @angular/core) to your custom-login.component.ts, and then check if the platform is a browser or a server with isPlatformBrowser() or isPlatformServer() ( both coming from @angular/common).