Firebase support bounty

This is a bounty to promote development interest and find a solution to the many apps that fail because of the migration from GCM (Google Cloud Messaging) to FCM (Firebase Cloud Messaging)

https://www.bountysource.com/issues/51518216-gcm-fcm-update-needed-for-push-messaging

Follow the conversation in the latest pages of MicroG XDA thread and on GitHub:

https://forum.xda-developers.com/android/apps-games/app-microg-gmscore-floss-play-services-t3217616

https://github.com/microg


The Deprecation of GCM for FCM
by @ Shadow53
https://shadow53.com/post/whats-new-pussycat/#the-deprecation-of-gcm-for-fcm

"Users of MicroG on Android Oreo will notice that their apps using Google for notifications are no longer receiving them. This is because of Google pushing Firebase Cloud Messaging (FCM) as a replacement for Google Cloud Messaging (GCM) for notifications. MicroG currently only has support for the older GCM protocol, so apps using the newer FCM cannot register for notifications.

Some people have found that installing older versions of the app will cause it to register via GCM, then an update will continue using GCM. The problem of lacking support for FCM still remains.

A solution to this problem is to just not use apps that require Play Services at all, and request that developers of apps you use requiring Play Services implement an alternate method of pushing notifications.

This doesn’t work if you need a certain app that still requires Play Services, and certainly won’t work if trying to convince someone to switch to using MicroG. So, we need to get FCM implemented. Open Source enthusiasts will suggest that I do it if I think it needs to be done - I would, and I may in the future, but not any time soon. I have too many projects already that need to be worked on. So here’s hoping someone else is able to get something working…"


#bounty #firebase #fcm

https://www.bountysource.com/issues/51518216-gcm-fcm-update-needed-for-push-messaging

chris42:
Just to help a few people trying to figure out if push messaging is working or not, please check the following:

✅ you are using newest microg version 0.2.5-12879 running (ale5000 installer is updated and should be very helpful)
✅ you deactivated battery optimization for microg
✅ you activated google device registration
✅ you get all the green checkmarks in microg diagnostics
✅ you made sure nothing is blocking network traffic to mtalk.google.com (e.g. afwall, adaway, ...)
✅ you deleted the app you have troubles with and installed it fresh after updating to microg 0.2.5-12879
✅ you have not used backup solutions, like oandbackup, titaniumbackup, ... to restore app data
✅ you can also use the push notification tester to check. I just tried it and it works.

To verify incoming messages, look in you logs and search for "GmsGcmMcsInput". You should see the heartbeat and Incoming messages. In the incoming messages there should be a category stating your apps package. This should be messages your receive via push. (@mar-v-in I hope this is correct?!)


#firebase #fcm #bounty

How Tutanota replaced Google’s FCM with their own notification system

https://f-droid.org/en/2018/09/03/replacing-gcm-in-tutanota.html


#tutanota #email #fcm #firebase

OpenPush - A Free, Decentralized Push Messaging Framework for Android

Push messages are an essential part of connected mobile devices. They are also one of the critical missing pieces in the open source Android ecosystem. Until now, free Android apps would either need to implement their own push notification system, do without any push messaging or use the proprietary Google Cloud Messaging service.

OpenPush is a self-hosted, free alternative push messaging implementation which can either run alongside or as a replacement to FCM.

👉🏼 Read more:
https://f-droid.org/en/2020/02/03/openpush-talk.html


📡 @NoGoolag
#openpush #push #fcm #gcm #notifications #opensource #microg

FCM/push messaging troubleshooting

Go to microG settings > Google Cloud Messaging and check if the app is connected.

if no:

- Log in your Google account

- Try wiping data for the app

- Before restoring a backup, first restore the app only (without data) and start it to register the app. After that you can restore the data.

- If on NanoDroid, use this command for all apps or for a given appname (e.g. com.nianticlabs.pokemongo)
-- nutl -r
or
-- nutl -r [appname]

If yes:

- Ensure you don't have an adblocker blocking the domain mtalk.google.com

If you can't get any app to register for Google Cloud Messaging, try dialing this:

*#*#2432546#*#*
or
*#*#CHECKIN#*#*


From: https://gitlab.com/Nanolx/NanoDroid/tree/master#issues


📡 @NoGoolag
#push #fcm #gcm #fix #problems

Signal messenger:
Government circumvention doesn’t work without Google services in Qatar

https://community.signalusers.org/t/government-circumvention-doesnt-work-without-google-services-in-qatar/13886


#signal #Google #services #gcm #fcm #gov #qatar #censorship

Microsoft Teams users are getting the same mysterious 'FCM Messages' notifications that plagued Hangouts

Could be due to a vulnerability in Google's push notification servers

Just a few days ago, Hangouts users saw a number of mysterious "FCM Messages" test notifications, and now Microsoft Teams is exhibiting the same issue. The two incidents are likely linked, as they're connected to a recently published vulnerability in Google's push notification service Firebase Cloud Messaging (hence "FCM Messages"). Ultimately, the messages appear to be harmless (if annoying) for users, so you don't need to worry about the safety of your account or phone.

https://www.androidpolice.com/2020/08/27/microsoft-teams-users-are-getting-the-same-mysterious-fcm-messages-notifications-that-plagued-hangouts/

#Microsoft #Teams #Google #FCM #vulnerability

Apple and Google Monitor Notifications. We Need #Push Notification Alternatives

https://tuta.com/blog/open-source-email-fdroid

Comments

#gcm #fcm #firebase