<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><br></div><div>I found an issue with the developer build of push notifications under iOS. It was not a code problem - just the wrong certificate specified for code signing. I also found that the PUSH certificates were not installed on the production <a href="http://tmc.openvehicles.com">tmc.openvehicles.com</a> server (64.111.70.40).</div><div><br></div><div>So, two questions:</div><div><br></div><div><ol class="MailOutline"><li>For those of you using the iOS TestFlight release against <a href="http://www.openvehicles.com">www.openvehicles.com</a> server, do PUSH notifications work for you? Do you get a notification of charge complete/done when you are not running the App? A simple way to test is to send an SMS to your car "HELLO WORLD" - you should get a PUSH notification back with the content of the unrecognised SMS. Can you test this, and let me know if it is ok?<br><br></li><li>For those you using the iOS TestFlight release against <a href="http://tmc.openvehicles.com">tmc.openvehicles.com</a>, can you test PUSH notifications now, to see if they work? A simple way to test is to send an SMS to your car "HELLO WORLD" - you should get a PUSH notification back with the content of the unrecognised SMS. Can you test this, and let me know if it is ok?</li></ol></div><div><br></div><div><br></div><div>We're getting ready for production now, and need to cross the T's and dot the I's.</div><div><br></div><div>Regards, Mark.</div><div><br></div></body></html>