Gmscore: Firebase Cloud Messaging

[ale5000-git]

Is this supported? If no, please add it.

Firebase Cloud Messaging (FCM) is the new version of GCM. It inherits the reliable and scalable GCM infrastructure, plus new features

Info are here.

[RMcNeely]

So does this mean they're decoupling GCM from GMS?

On Feb 16, 2017 3:51 PM, "ale5000" [e-mail] wrote:

Is this supported? If no, please add it.

Firebase Cloud Messaging (FCM) is the new version of GCM. It inherits the
reliable and scalable GCM infrastructure, plus new features

Info are here https://developers.google.com/cloud-messaging/.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/microg/android_packages_apps_GmsCore/issues/313, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ACrSHt9QnFmomilWCHn-9sLnVXffzJxbks5rdLbPgaJpZM4MDhxh
.

[mar-v-in]

FCM shouldn't require changes in GmsCore. On Android, FCM is just a new API around GCM. I don't know how it is realized on other platforms, but that's OT here.

[ale5000-git]

For the new API to appears on Android doesn't it need to be supported in GmsCore?

[jfrederickson]

@mar-v-in's comment made it sound like FCM doesn't require changes in microG (am I understanding that correctly?) but an application I use that just switched from GCM to FCM is no longer able to register my device.

<yannick> i have a bug report from a nexus 5 device.
<yannick> Have a look to  GCMHelper logs
<yannick> D/GCMHelper: ## getRegistrationToken(): null
<yannick> means that the FCM registration fails.
<yannick> The latest Google play version works only with the official ROMs.
<yannick> MicroG does not seem compliant with FCM.

[mar-v-in]

@jfrederickson which app is that?

[jfrederickson]

Riot: https://github.com/vector-im/riot-android

Looks like this is where they switched over to FCM: https://github.com/vector-im/riot-android/commit/15bba9dce4a96e49fd4bd5132e2f60b57bdf1059

[tostercx]

Have there been any news / workarounds for this? My bank's 2FA (com.smart_id) seems to be half-broken, I think it's due to FCM :<

E FirebaseInstanceId: Token retrieval failed: SERVICE_NOT_AVAILABLE

[tostercx]

I have no idea what changed but the latest version seems to have fixed it for me!

Probably this? https://github.com/microg/android_packages_apps_GmsCore/commit/9e0ee103a145564b1b33158a6b83697021d7ea9e

[chris42]

Please see #439

[farfromrefug]

I am a developer and was fighting to get my app to work with microg.
I was constantly hit with SERVICE_NOT_AVAILABLE errors.
I then used that code with my app id and google json file and it worked!
So what was different?
I figured it out. It is the version of com.google.firebase:firebase-messaging you use to build your app.
Using 19.0.1 will work with microg. But then updating to 20.1.5, uninstall/build/run and you will get a SERVICE_NOT_AVAILABLE error!

So i would guess that something changed which makes it not work anymore. We need to find what. Now it also means that any app using com.google.firebase:firebase-messaging later that 20.0.0 (which i would guess is the breaking point), wont work at all with microg!

[godfuture]

So i would guess that something changed which makes it not work anymore. We need to find what. Now it also means that any app using com.google.firebase:firebase-messaging later that 20.0.0 (which i would guess is the breaking point), wont work at all with microg!

Same here. My banking app offered digital cards which is an alternative to Google Pay. But I get issues during registration. I found out that the "firebase messaging id" is missing. Most likely microg is missing latest API elements. Unfortunately I do not know firebase version used in the banking app.

[danielfrankcom]

Unfortunately the Fastmail app also seems to encounter a similar SERVICE_NOT_AVAILABLE after a fresh microG install.