I had the same issue several times, i has also been addressed on this list recently, this has to do with the APN certificates that you upload in Aerogear. You have 2 things to pay attention to : Make sure the Apple produced APN certificate that you upload in you aerogear IOS variant through the edit network option is still valid datewise Make sure this certificate is consistent with the Provisionning profile you have used to produce your app : APN certificate can be produced on apple developper site with production or development flavour. If you use a production provisionning profile for your app and a development APN certificate on aerogear, or vice versa, you will experience this issue of Apple network invalidating your token. Best, Yves Le 01/06/2016 08:55, Raghavendra a écrit :

On Thu, Jun 2, 2016 at 7:43 AM, Raghavendra <raghavendra.dabbir(a)gmail.com&gt; wrote: https://github.com/aerogear/aerogear-unifiedpush-server/blob/1.1.x-dev/pu... it's the issue Yves described, make sure you have a dev cert for your dev app (or vice versa) -M -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ twitter: http://twitter.com/mwessendorf

Is archive a release build ? If so, you need a production cert. Here is doc, how to get to the .p12 files: https://aerogear.org/docs/unifiedpush/aerogear-push-ios/guides/#app-id-ss... On Mon, Jun 13, 2016 at 8:38 AM, Raghavendra <raghavendra.dabbir(a)gmail.com&gt; wrote: -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ twitter: http://twitter.com/mwessendorf