我也遇到了这个问题。我在这里制作了一个复制品 https://github.com/jamsjordn/angular-push-request-hard-reload-issue
由 ng new 和 ng add @angular/pwa 制作的样板

我们也在Angular v16上遇到了这个问题。进行了一些深入的调试，发现问题出在这段代码中：

const currentController = defer(() => of(serviceWorker.controller));
      const controllerWithChanges = concat(currentController, controllerChanges);

      this.worker = controllerWithChanges.pipe(filter((c): c is ServiceWorker => !!c));

      this.registration = <Observable<ServiceWorkerRegistration>>(
          this.worker.pipe(switchMap(() => serviceWorker.getRegistration())));

这里的问题是，当你从硬刷新进入应用程序时，currentController 会发出 null 。这与描述的规范一致。
然而，控制器为null并不一定意味着没有注册，没有注册的发出意味着没有发出pushManager,这导致SwPush.subscription和SwPush.requestSubscription不发出或解析任何内容，即使存在现有的订阅。
我建议的修复方法如下：

const currentController = defer(() => of(serviceWorker.controller));
      const controllerWithChanges = concat(currentController, controllerChanges);

      this.worker = controllerWithChanges.pipe(filter((c): c is ServiceWorker => !!c));

      this.registration = <Observable<ServiceWorkerRegistration>>(
          concat(
              currentController, 
              controllerChanges.pipe(
                  filter((c): c is ServiceWorker => !!c)
              )
          ).pipe(
              switchMap(() => serviceWorker.getRegistration()),
              filter((swr): swr is ServiceWorkerRegistration => !!swr)
          )
      );

这实际上使得即使当前控制器为null,也会尝试获取ServiceWorkerRegistration。虽然这个方法有效，但我唯一怀疑的是，我对Angular的服务工作实现了解不足，无法判断这是否会产生任何意外的副作用。如果有更了解的开发人员能提供帮助，将不胜感激！：)
在此期间，我制作了一个hacky方法，可以在注入swPush服务的组件/服务中使用此修复：

private fixSwPush(): void {
    if (!this.swPush.isEnabled) {
      return;
    }

    const serviceWorker: ServiceWorkerContainer | undefined = this.swPush?.['sw']?.['serviceWorker'];

    if (!serviceWorker) {
      return;
    }

    // Adapted from original code:
    // https://github.com/angular/angular/blob/c3b00959659ca20d3f798820dfcb4dee250a32ac/packages/service-worker/src/low_level.ts#L137
    const controllerChangeEvents = fromEvent(serviceWorker, 'controllerchange');
    const controllerChanges = controllerChangeEvents.pipe(map(() => serviceWorker.controller));
    const currentController = defer(() => of(serviceWorker.controller));

    const registration = concat(
      // The actual fix, here we don't do the falsy filtering for the currentController (as it is null on a hard refresh)
      currentController,
      controllerChanges.pipe(
        filter((c): c is ServiceWorker => !!c),
      )
    ).pipe(
      // Instead just try to get the ServiceWorkerRegistration here
      switchMap(() => serviceWorker.getRegistration()),
      // And filter out any falsy ServiceWorkerRegistration at the end
      filter((swr): swr is ServiceWorkerRegistration => !!swr)
    );

    // Adapted from original code:
    // https://github.com/angular/angular/blob/c3b00959659ca20d3f798820dfcb4dee250a32ac/packages/service-worker/src/push.ts#L151
    const pushManager = registration.pipe(map(registration => registration.pushManager));

    // Overwrite the original pushManager
    this.swPush['pushManager'] = pushManager;

    const workerDrivenSubscriptions = pushManager.pipe(switchMap(pm => pm.getSubscription()));

    // Overwrite the original subscriptionChanges
    (this.swPush.subscription as Observable<PushSubscription | null>) = merge(workerDrivenSubscriptions, (this.swPush['subscriptionChanges'] as Subject<PushSubscription | null>));

  }

并在其他任何事情之前(甚至字段初始化器)执行此操作：

@Injectable({
  providedIn: 'root'
})
export class WebPushService implements OnDestroy {

  // TODO: There is a problem with this not emitting after a hard reload https://github.com/angular/angular/issues/48702
  // this is a hacky way to fix this. At some point reevaluate this solution
  private readonly runThisFirst = this.fixSwPush();
  
  constructor(
    private readonly swPush: SwPush,
...

我希望这可以帮助那些陷入困境的人，也希望这个问题能在某个时候得到正确的解决(如果有什么我可以做的来帮助解决这个问题，请告诉我？)

请查看以下链接：

1. https://developer.chrome.com/docs/workbox/improving-development-experience#shift_and_reload
2. https://web.dev/articles/service-worker-lifecycle#shift-reload
   When a service worker is active, a forced refresh will also bypass the service worker entirely.