Let me guess: you reuse a DB from the 1.1.x testing, but run with master ? I see undertow, which is WildFly, and only supported on master

the DB schema for 1.1.x branch (the one we test w/ EAP) is different than the one in master (the one we test w/ WildFly)

NOTE: the master code does NOT yet contain the APNs/HTTP2 fixes. I had no time to port that forward 

On Tue, May 9, 2017 at 4:58 PM, Jose Miguel Gallas Olmedo <jgallaso@redhat.com> wrote:
Hi all,

I am playing a bit with the admin-ui and added some fake variant. When trying to send a notification, a 500 Error popup showed up and the terminal spat out a couple of ugly Exceptions -> https://gist.github.com/josemigallas/614a7ffe01e213b25470bfa11925a365

What I did is create a new Android variant with some madeup senderId and serverKey and then add some fake tokens with the mock-data-loader.

I don't really know if this is some kind of error but I wouldn't expect so many Exceptions. It should simply check the response from FCM, not throwing exceptions here and there. Maybe it has nothing to do with it and I am just doing something else wrong.

WDYT?

Cheers,

--

JOSE MIGUEL GALLAS OLMEDO

ASSOCIATE QE, mobile

Red Hat 

M: +34618488633    


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



--
Matthias Wessendorf

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