<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
</head>
<body>
That's the strange part: I don't get any error, and I don't get a
timeout either. That's what I meant by "fails in a way we don't
handle".<br>
<br>
This is the only log entry on "apns processing", I get this once
after restarting the server as soon as the first APN is due for
delivery:<br>
<font face="monospace"><br>
2020-12-10 16:55:30.351530 +0100 info main: - - - msg apns
processing queue for gateway.sandbox.push.apple.com</font><br>
<br>
(still running server v2 due to lack of time)<br>
<br>
After that, no more apns processing – I guess because $apns_running
never gets reset.<br>
<br>
Any idea?<br>
<br>
Regards,<br>
Michael<br>
<br>
<br>
<div class="moz-cite-prefix">Am 14.12.20 um 07:17 schrieb Mark
Webb-Johnson:<br>
</div>
<blockquote type="cite"
cite="mid:FFACA9C0-DE7C-45A2-BD55-E6B8B0E40462@webb-johnson.net">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<div class=""><br class="">
</div>
Push notifications are still working ok for me. What is the error
you get back from the gateway?
<div class=""><br class="">
</div>
<div class="">We are using this protocol (see apns_send function):</div>
<div class=""><br class="">
</div>
<blockquote style="margin: 0 0 0 40px; border: none; padding:
0px;" class="">
<div class=""><a
href="https://developer.apple.com/library/archive/documentation/NetworkingInternet/Conceptual/RemoteNotificationsPG/BinaryProviderAPI.html"
class="" moz-do-not-send="true">https://developer.apple.com/library/archive/documentation/NetworkingInternet/Conceptual/RemoteNotificationsPG/BinaryProviderAPI.html</a></div>
</blockquote>
<div class="">
<div class=""><br class="">
</div>
<div class="">We need to convert to this one:</div>
<div class=""><br class="">
</div>
</div>
<blockquote style="margin: 0 0 0 40px; border: none; padding:
0px;" class="">
<div class="">
<div class=""><a
href="https://developer.apple.com/documentation/usernotifications/setting_up_a_remote_notification_server/sending_notification_requests_to_apns/"
class="" moz-do-not-send="true">https://developer.apple.com/documentation/usernotifications/setting_up_a_remote_notification_server/sending_notification_requests_to_apns/</a></div>
</div>
</blockquote>
<div class="">
<div class="">
<div><br class="">
</div>
<div>But have until the end of March 2021 to do it. The switch
is not complex, and is probably slightly easier for us. It
becomes just a simple http request, with pretty much the
same payload we currently use (in json format).</div>
<div><br class="">
</div>
<div>Regards, Mark.</div>
<div><br class="">
<blockquote type="cite" class="">
<div class="">On 11 Dec 2020, at 12:27 AM, Michael Balzer
<<a href="mailto:dexter@expeedo.de" class=""
moz-do-not-send="true">dexter@expeedo.de</a>>
wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div class="">
<div class="content-isolator__container">
<div class="protected-part">
<div class="protected-title">Signed PGP part</div>
<div class="protected-content">Mark,<br class="">
<br class="">
a user informed me he no longer gets any push
notifications to iOS.<br class="">
<br class="">
Looking into the logs, it seems the initial
connect to the gateway fails in a way the perl
code does not handle.<br class="">
<br class="">
I've found this in the Apple forums: <a
href="https://developer.apple.com/forums/thread/667248"
class="" moz-do-not-send="true">https://developer.apple.com/forums/thread/667248</a><br
class="">
<br class="">
It seems the protocol we use has been
deprecated, but it should continue to work until
March. Do you see a similar effect on your
server?<br class="">
<br class="">
Regards,<br class="">
Michael<br class="">
<br class="">
-- <br class="">
Michael Balzer * Helkenberger Weg 9 * D-58256
Ennepetal<br class="">
Fon 02333 / 833 5735 * Handy 0176 / 206 989 26<br
class="">
<br class="">
<br class="">
</div>
</div>
<br class="">
<iframe class="content-isolator__isolated-content"
sandbox="allow-scripts" scrolling="auto"
style="border:none;display:block;overflow:auto;"
data-src="data:text/html;charset=UTF-8;base64,PGlmcmFtZS1jb250ZW50IGRhdGEtaWZyYW1lLWhlaWdodD0idHJ1ZSI+X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX188QlI+T3Ztc0RldiBtYWlsaW5nIGxpc3Q8QlI+T3Ztc0RldkBsaXN0cy5vcGVudmVoaWNsZXMuY29tPEJSPmh0dHA6Ly9saXN0cy5vcGVudmVoaWNsZXMuY29tL21haWxtYW4vbGlzdGluZm8vb3Ztc2RldjxCUj48L2lmcmFtZS1jb250ZW50Pg=="
width="200" height="10"></iframe></div>
</div>
</div>
</blockquote>
</div>
<br class="">
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
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>
<br>
<pre class="moz-signature" cols="72">--
Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
Fon 02333 / 833 5735 * Handy 0176 / 206 989 26</pre>
</body>
</html>