Running FCM on IP stops Angular rendering

I need to sometimes run my app on IP for mobile testing etc, and this used to work fine in Angular 16 since firebase would just ignore IPs but now, since Angular 20, I get:

TypeError: Cannot read properties of undefined (reading 'addEventListener')

eventually failing with

FirebaseError: Messaging: This browser doesn't support the API's required to use the Firebase SDK. (messaging/unsupported-browser).

But not before it halts the whole app and stops it rendering.

This should just not do anything when it detect a none 127.0.0.1 IP as it did before, seems like there has been a regression bug somewhere.

Specifically the issue provider is:

provideMessaging(() => getMessaging()),

Start at the provideMessaging(() => getMessaging()) entry point and reproduce the issue while serving the app on a non-127.0.0.1 IP. Trace the initialization failure that leads to the unsupported-browser error; done means the app continues rendering without Firebase Messaging halting it in that environment.

Written by the indexing model from the issue text.