fireMessaging.tokenChanges emit wrong(not equeal) fcm token after fireMessaging.requestToken

[Okz1]

Version info

*Angular:17.3.3*

*Firebase:-*

*AngularFire:17.1.0*

*Other (e.g. Ionic/Cordova, Node, browser, operating system):browser*

How to reproduce these conditions

1) Create subscription on fireMessaging.tokenChanges, can be several 2) Run fireMessaging.requestToken 3) Compare fcm token from tokenChanges & requestToken

Currently, we have different results, also each new subscription generates a new fcm token + additional HTTP requests

Expected behavior

Same fcm tokens + only required numbers of HTTP requests

Actual behavior

Different fcm tokens

[google-oss-bot]

This issue does not seem to follow the issue template. Make sure you provide all the required information.