Mark, according to the migration guide, all client (subscriber) tokens and registrations will continue to work:
Note that client SDKs and GCM tokens will continue to work indefinitely. However, you won't be able to target the latest version of Google Play Services in your Android app unless you migrate to FCM.
So the currently rolled out App does not need an immediate update, and as we currently target play-services v15.0.1, we won't need to migrate to be able to roll out a new release until we need to switch to v16. I have just finished updating my build environment and will look into this nevertheless. On the server (publisher) side, the API also hasn't changed and will continue to be supported. All that is needed is changing the end point. I've just done and tested that on my server, and pushed the change: https://github.com/openvehicles/Open-Vehicle-Monitoring-System/commit/91d1b1... Please update your server accordingly. Regards, Michael Am 05.03.19 um 12:48 schrieb Michael Balzer:
I wasn't aware of the deadline. I'll check the migration.
Regards, Michael
Am 05.03.19 um 12:38 schrieb Mark Webb-Johnson:
Just found out that google is going to kill GCM (1st April 2019 - surely not a joke?). Presumably that will affect our Android push notifications.
Changes don’t seem excessive, and it seems we can still use our old GCM registrations so may be limited to server side for the moment?
@Michael are you aware of this issue?
Regards, Mark.
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
-- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26