setTimeout in interceptor causes error with/in EventReplay about angular

[Fluccioni]

I have currently the same TypeError, but I'm not sure it has something to do with the use of setTimeout.

I came across this comment in the initEventReplay function saying we may encounter undefined reading 'ngContracts'.

If it is the case, therefore the const container will be undefined too and the error will be thrown on the invocation of getJsactionData.

// TODO: Upstream this back into event-dispatch.
function getJsactionData(container) {
    return container._ejsa;
}

const initEventReplay = (eventDelegation, injector) => {
    const appId = injector.get(APP_ID);
    // This is set in packages/platform-server/src/utils.ts
    // Note: globalThis[CONTRACT_PROPERTY] may be undefined in case Event Replay feature
    // is enabled, but there are no events configured in an application.
    const container = globalThis[CONTRACT_PROPERTY]?.[appId];
    const earlyJsactionData = getJsactionData(container);
    ...

The problem seems to be the bundle jsaction contract script not correctly inlined during the html generation, which might be the case while using the "old" browser builder instead of esbuild from what I saw

[AndrewKushnir]

Thanks for reporting this issue. I was able to reproduce it for cases when there are no events registered in an application, but Event Replay feature is enabled. I've created PR #56509 with the fix.

The problem seems to be the bundle jsaction contract script not correctly inlined during the html generation, which might be the case while using the "old" browser builder instead of esbuild from what I saw

@Fluccioni the mentioned PR would likely resolve that problem as well (there will be no JS exceptions), but we may consider adding some logic to detect those cases and add a warning. Could you please create a minimal repro (in a form of GitHub repository), so that we can perform further investigation to see if we can detect those cases?