[messaging] using navigator serviceWorker

[hiepxanh]

Checklist

base on this solution #1904 (comment)

• Issue number for this PR: Unhandled Promise rejection: this._next is not a function : Zone in @angular/fire/messaging #2299 Not receiving FCM messages #1904
• Docs included?: no
• Test units included?: no
• In a clean directory, yarn install, yarn test run successfully? yes

Description

fixing a bug because this.angularFireMessaging.messages not trigger new message any more

Code sample

nothing changes

[hiepxanh]

@yasinkocak I just push new code, that pass the Javis Test

[jamesdaniels]

Ah, yes, this should help. Approved. I'll play around with this a bit and then merge.

[jamesdaniels]

It also seems a fix is coming upstream firebase/firebase-js-sdk#3221

[hiepxanh]

perfect, I will update my PR once they complete that change @jamesdaniels

[khaledwalid]

@hiepxanh , can you Told me the right version of @angular/fire and firebasejs from gstatic because i have also the issue that when i'm not receiving an notification

[hiepxanh]

"firebase": "^7.14.5", and "@angular/fire": "^6.0.0", sir @khaledwalid

[hiepxanh]

it is imposible to fix this, some how big problem come from firebase-messaging-sw.js

some how my browser not update new version, so I try everything I can but still cannot receive notification in forground. Even update the latest @angular/fire or firebase (newest version with fix is Fix FCM rxjs Incompatibility
)

[hiepxanh]

After research, the last firebase version auto add the firebase-messsaging-sw.js file for me. But when I update the firebase in package.json the firebase-messsaging-sw.js is just not update automaticly with the new version. Solution:
I have to create my own firebase-messaging-sw.js that matching to current firebase version:

[hiepxanh]

Close since firebase release new version that fix this bug, I think we need to update the document, because I have serious trouble, the message in foreground is not fired if you have missmatch firebase version in firebase-messaging-sw.js