Matthias,

Does the behaviour I described makes sense?

In 1.0.0, if one of the token is invalid, can it block the whole push sending to other tokens?

 

Matthias

 

De : aerogear-users-bounces@lists.jboss.org [mailto:aerogear-users-bounces@lists.jboss.org] De la part de Matthias Wessendorf
Envoyé : lundi 6 juin 2016 11:20
À : aerogear-users@lists.jboss.org
Objet : Re: [Aerogear-users] iOS Push issue when having multiple Installations

 

Hi,

 

I think you are hitting a a bug. in the 1.1.0 series we did add a catch for reported invalid tokens:

https://github.com/aerogear/aerogear-unifiedpush-server/commit/a44773a8dba1d9ce57a99de2dc11463f16e8e79f

 

-Matthias

 

On Mon, Jun 6, 2016 at 11:14 AM, Bourillon, Matthias <Matthias.Bourillon@saint-gobain.com> wrote:

Hello,

We are facing an issue while using Aerogear Push Server with an iOS variant.

Here is the scenario :

1.       We have 89 installations registered against an iOS Production Variant

2.       We send a message

3.       No one receive the message on our iOS App

4.       We disable ALL installations but 1

5.       We send a message

6.       The 1 device receives the push notification and works as expected

 

We have other iOS variants with thousands of registrations working without any problem like this.

 

Can the number of registered device impact the sending behavior? Can a wrong token or anything else block the notification sending to Apple? Logs do not seem to complain about any particular issue.

We are using Aerogear Push Server 1.0.0.

 

Thanks,

Matthias


_______________________________________________
Aerogear-users mailing list
Aerogear-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-users



 

--

Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
twitter: http://twitter.com/mwessendorf