<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Cool. I have update the <a href="http://api.openvehicles.com" class="">api.openvehicles.com</a> server.<div class=""><br class=""></div><div class="">Regards, Mark.<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On 9 Mar 2019, at 7:19 PM, Michael Balzer <<a href="mailto:dexter@expeedo.de" class="">dexter@expeedo.de</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" class="">
<div text="#000000" bgcolor="#FFFFFF" class="">
Mark,<br class="">
<br class="">
according to the migration guide, all client (subscriber) tokens and
registrations will continue to work:<br class="">
<br class="">
<blockquote type="cite" class="">
<section class="expandable" id="deprecationtime" style="box-sizing: inherit; position: relative;"><p class="exw-expanded-content" style="box-sizing: inherit;
margin: 16px 0px; padding: 0px; display: block;">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.</p>
</section>
</blockquote>
<br class="">
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.<br class="">
<br class="">
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.<br class="">
<br class="">
I've just done and tested that on my server, and pushed the change:<br class="">
<a class="moz-txt-link-freetext" href="https://github.com/openvehicles/Open-Vehicle-Monitoring-System/commit/91d1b12a81781b82bd2ce7ab451d129677f5d685">https://github.com/openvehicles/Open-Vehicle-Monitoring-System/commit/91d1b12a81781b82bd2ce7ab451d129677f5d685</a><br class="">
<br class="">
Please update your server accordingly.<br class="">
<br class="">
Regards,<br class="">
Michael<br class="">
<br class="">
<br class="">
<div class="moz-cite-prefix">Am 05.03.19 um 12:48 schrieb Michael
Balzer:<br class="">
</div>
<blockquote type="cite" cite="mid:e7327b32-c574-dad9-e490-726e11bd6212@expeedo.de" class="">
<pre class="moz-quote-pre" wrap="">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:
</pre>
<blockquote type="cite" class="">
<pre class="moz-quote-pre" wrap="">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
<a class="moz-txt-link-abbreviated" href="mailto:OvmsDev@lists.openvehicles.com">OvmsDev@lists.openvehicles.com</a>
<a class="moz-txt-link-freetext" href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a>
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
</pre>
</blockquote>
<br class="">
<pre class="moz-signature" cols="160">--
Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
</pre>
</div>
_______________________________________________<br class="">OvmsDev mailing list<br class=""><a href="mailto:OvmsDev@lists.openvehicles.com" class="">OvmsDev@lists.openvehicles.com</a><br class="">http://lists.openvehicles.com/mailman/listinfo/ovmsdev<br class=""></div></blockquote></div><br class=""></div></body></html>