Re: [aerogear-dev] broken push notification in UPS 1.1.3.Final
On Fri, Jul 22, 2016 at 10:42 AM, mischa <mischa.neumann(a)init.de> wrote:
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
1.1.2 and 1.2.0-alpha.1 is not containing FCM
aerogear-unifiedpush-server-1.1.3.Final
but FCM is included in 1.1.3 and master (1.2.0-alpha.2-SNAPSHOT)
FCM registration is done here:
https://github.com/aerogear/aerogear-android-push/blob/master/aerogear-an...
But... I wonder... if we can, or should, do something about that on the
srver side... hrm...
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/...
Mischa
--
View this message in context:
http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-broken-push-notifi...
Sent from the aerogear-dev mailing list archive at Nabble.com.
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
twitter: http://twitter.com/mwessendorf
Attachments:
- attachment.html (text/html — 3.3 KB)