Hello Matthias,

 

in regard of the upgrade, we were running the 1.0.2 and we migrate to the 1.1.1, here some problem you might want to be aware of.

 

The update was smooth from 1.0.2 to 1.0.3, but I have to add the parameter ‘transformedBitIsBoolean’ in our DB connection (standalone.xml).

<connection-url>jdbc:mysql://localhost:3306/unifiedpush?transformedBitIsBoolean=true</connection-url>

 

But it was quite hard for us to update to 1.1.0 from our 1.0.3, the problem where coming from our DB :

·         Redundancy of FK

·         Wrong data type

·         Wrong data order in the table (even if it shouldn’t matter, it does for some reasons)

·         Wrong table name

 

So basically our database was not in sync with the one the migrator tool expect, specially the part related to the table ‘variant’.

 

The way we proceed to make the migration is the following :

1.       We made some modification in our current database (creation of columns, change columns order in table)

2.       We exported the data, and reimport all of it in a fresh 1.0.3 installation

3.       We run the migrator tool to 1.1.0

4.       We add in variant.VARIANT_TYPE the type of OS (ios, android) wich was missing

 

The modifications made in the step 1 make the data import in the step 2 possible,

they come from the differences between our schema and the schema from scratch.

 

Best Regards,

Romain

 

De : Bourillon, Matthias
Envoyé : mercredi 15 juin 2016 11:45
À : Javornik, Romain
Objet : Re: [Aerogear-users] iOS Push issue when having multiple Installations

 

Fait un reply là-dessus sur la liste aerogear-users@lists.jboss.org

 

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

 



On Tuesday, 7 June 2016, Bourillon, Matthias <Matthias.Bourillon@saint-gobain.com> wrote:

Hello Matthias,

We are still in 1.0.0 as 1.1.0 migration process fails with our instance.

 

hrm, any pointers?

 

To me, invalid tokens have been added on the server due to App development process during which App with development provisioning profile have registered against the server.

yes!

Please note, dev/prod variant settings should not be mixed, for different reasons

 

 

 

If I understand correctly, in 1.1.0, if we have Dev token registered against the server they’ll be discovered invalid by Aerogear server and message sending will not be impacted. Is this right?

 

Thanks,

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 21:17
À : aerogear-users@lists.jboss.org
Objet : Re: [Aerogear-users] iOS Push issue when having multiple Installations

 

are you using the 1.1.0 ? 

 

I think it should not stop.

 

Question: how did invalid tokens end up at the server?

 

On Mon, Jun 6, 2016 at 4:56 PM, Bourillon, Matthias <Matthias.Bourillon@saint-gobain.com> wrote:

Matthias,

I wanted to validate this behavior and I just created a script, manually sending a Payload to Apple Push service, 1 by 1 to our 89 installations.
I am getting the same behavior : as soon as a payload is being sent to an invalid token, remaining payloads are not sent to devices. Is this something Apple block on their side?

 

Thanks,

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 12:40


À : aerogear-users@lists.jboss.org
Objet : Re: [Aerogear-users] iOS Push issue when having multiple Installations

 

I think yes, the problem was the a mix of tokens for different profiles (e.g. dev vs. prod)

 

-M

 

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

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:

 

-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



 

--


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



 

--


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



 

--



--
Sent from Gmail Mobile