Chrome 69 doesn't support Firebase SDK

firebase google-chrome firebase-realtime-database browser-support
corvus picture corvus · Sep 6, 2018 · Viewed 22.1k times · Source

Yesterday everything worked perfectly, this morning I noticed chrome is introducing a new interface, afterwards I checked the chrome version, it is now updated to v69. So far so good. I then ran my server which is linked to firebase. But I started getting this: 

09:46:30.598 index.esm.js?76ac:2069 Uncaught FirebaseError {code: "messaging/unsupported-browser", message: "Messaging: This browser doesn't support the API's …he firebase SDK. (messaging/unsupported-browser).", stack: "FirebaseError: Messaging: This browser doesn't sup….0.0.0:8000/index.js?d00bc69e0c69f561d4af:2672:1)"}code: "messaging/unsupported-browser"message: "Messaging: This browser doesn't support the API's required to use the firebase SDK. (messaging/unsupported-browser)."stack: "FirebaseError: Messaging: This browser doesn't support the API's required to use the firebase SDK. (messaging/unsupported-browser).
at Object.factoryMethod [as messaging] (webpack-internal:///311:2077:32)
at FirebaseAppImpl._getService (webpack-internal:///30:134:66)
at FirebaseAppImpl.(anonymous function) [as messaging] (webpack-internal:///30:323:31)
at Object.serviceNamespace [as messaging] (webpack-internal:///30:308:32)
at eval (webpack-internal:///66:51:36)
at Object.<anonymous> (http://0.0.0.0:8000/index.js?d00bc69e0c69f561d4af:1240:1)
at __webpack_require__ (http://0.0.0.0:8000/index.js?d00bc69e0c69f561d4af:708:30)
at fn (http://0.0.0.0:8000/index.js?d00bc69e0c69f561d4af:113:20)
at eval (webpack-internal:///286:55:11)
at Object.<anonymous> (http://0.0.0.0:8000/index.js?d00bc69e0c69f561d4af:2672:1)"__proto__: Error

Long error made short: Messaging: This browser doesn't support the API's required to use the firebase SDK

Downgrading to chrome 68 is a solution, but does anyone have a better idea?

EDIT:

System information: Pop!_OS 18.04 LTS Linux (64-bit)

Chrome version: 69.0.3497.81 (Official Build) (64-bit)

Node version: v10.9.0

EDIT:

The server works just fine while deployed to production, and firefox.

Answer

Moradnejad picture Moradnejad · Jun 22, 2019

This problem occurs when you are not using HTTPS or localhost. This is documented in the official documentations: source

The FCM SDK is supported only in pages served over HTTPS. This is due to its use of service workers, which are available only on HTTPS sites.

Of course, your problem was caused for using 0.0.0.0 instead of localhost which was correctly pointed out by Noureldean Swearky.

Related questions

How to handle notification when app in background in Firebase

Here is my manifest <service android:name=".fcm.PshycoFirebaseMessagingServices"> <intent-filter> <action android:name="com.google.firebase.MESSAGING_EVENT" /> </intent-filter> </service> <service android:name=".fcm.PshycoFirebaseInstanceIDService"> <intent-filter> &…

Read More
How can I send a Firebase Cloud Messaging notification without use the Firebase Console?

I'm starting with the new Google service for the notifications, Firebase Cloud Messaging. Thanks to this code https://github.com/firebase/quickstart-android/tree/master/messaging I was able to send notifications from my Firebase User Console to my Android device. …

Read More
Firebase (FCM) how to get token

It's my first time using FCM. I download a sample from firebase/quickstart-android and I install the FCM Quickstart. But I can't get any token from the log even hit the LOG TOKEN button in the app. Then I try …

Read More