Matthias Wessendorf wrote
> Ah, I think the delegate is the issue; because it lacks the FCM topic code
> from Android SDK

we had no problems with aerogear-unifiedpush-server-1.2.0-alpha.1
and not when naming the variants with

aerogear-unifiedpush-server-1.1.3.Final

but I would give it a try:

how would a correct json request look like?
couldn't find something matching at
https://aerogear.org/docs/specs/aerogear-unifiedpush-rest-1.0.x/registry/device/index.html

Mischa



--
View this message in context: http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-broken-push-notification-in-UPS-1-1-3-Final-tp12629p12641.html

Sent from the aerogear-dev mailing list archive at Nabble.com.
_______________________________________________
aerogear-dev mailing list
aerogear-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev