<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Jul 22, 2016 at 11:19 AM, mischa <span dir="ltr"><<a href="mailto:mischa.neumann@init.de" target="_blank">mischa.neumann@init.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">Matthias Wessendorf wrote<br>
> On Fri, Jul 22, 2016 at 10:42 AM, mischa &lt;<br>
<br>
> mischa.neumann@<br>
<span class=""><br>
> &gt; wrote:<br>
><br>
>> Matthias Wessendorf wrote<br>
>> > Ah, I think the delegate is the issue; because it lacks the FCM topic<br>
>> code<br>
>> > from Android SDK<br>
>><br>
>> we had no problems with aerogear-unifiedpush-server-1.2.0-alpha.1<br>
>> and not when naming the variants with<br>
>><br>
><br>
> 1.1.2 and 1.2.0-alpha.1 is not containing FCM<br>
><br>
><br>
>> aerogear-unifiedpush-server-1.1.3.Final<br>
>><br>
><br>
> but FCM is included in 1.1.3 and master (1.2.0-alpha.2-SNAPSHOT)<br>
><br>
><br>
> FCM registration is done here:<br>
> <a href="https://github.com/aerogear/aerogear-android-push/blob/master/aerogear-android-push/src/main/java/org/jboss/aerogear/android/unifiedpush/fcm/AeroGearFCMPushRegistrar.java#L186-L191" rel="noreferrer" target="_blank">https://github.com/aerogear/aerogear-android-push/blob/master/aerogear-android-push/src/main/java/org/jboss/aerogear/android/unifiedpush/fcm/AeroGearFCMPushRegistrar.java#L186-L191</a><br>
><br>
> But... I wonder... if we can, or should, do something about that on the<br>
> srver side... hrm...<br>
<br>
</span>I see:<br>
... Sent push notification to GCM topic: &#x2F;topics&#x2F;PRODUCTS ...<br>
and as no client didn't register with the help of aerogear-android-push for<br>
this topic at Firebase, it wouldn't get any notifications.<br>
<br>
then the frontend message "X receivers" is misleadingly as one receiver is a<br>
FCM topic channel :-)<br></blockquote><div><br></div><div>yeah, that's something we need to fix - I am not happy w/ that too </div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">
<br>
and it's not clear, why the UPS is behaving differently when the android<br>
variant is directly targeted in the push request.<br></blockquote><div><br></div><div>because, than we don't do the topic :) we do direct device tokens:</div><div><a href="https://github.com/aerogear/aerogear-unifiedpush-server/blob/1.1.3.Final/push/sender/src/main/java/org/jboss/aerogear/unifiedpush/message/token/TokenLoader.java#L129">https://github.com/aerogear/aerogear-unifiedpush-server/blob/1.1.3.Final/push/sender/src/main/java/org/jboss/aerogear/unifiedpush/message/token/TokenLoader.java#L129</a><br></div><div><a href="https://github.com/aerogear/aerogear-unifiedpush-server/blob/1.1.3.Final/push/sender/src/main/java/org/jboss/aerogear/unifiedpush/message/token/TokenLoaderUtils.java#L82">https://github.com/aerogear/aerogear-unifiedpush-server/blob/1.1.3.Final/push/sender/src/main/java/org/jboss/aerogear/unifiedpush/message/token/TokenLoaderUtils.java#L82</a><br></div><div><br></div><div>So... we have some hooks to not go w/ FCM topics..... but I hate to introduce a flag to not use FCM topics..... </div><div>So, perhaps for you guys, just send a few request w/ variants tagged? instead of one - that would work - and will continue to work :D</div><div><br></div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">
<br>
Mischa<br>
<br>
<br>
<br>
--<br>
View this message in context: <a href="http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-broken-push-notification-in-UPS-1-1-3-Final-tp12629p12643.html" rel="noreferrer" target="_blank">http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-broken-push-notification-in-UPS-1-1-3-Final-tp12629p12643.html</a><br>
<div class=""><div class="h5">Sent from the aerogear-dev mailing list archive at Nabble.com.<br>
_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div>Matthias Wessendorf <br><br>blog: <a href="http://matthiaswessendorf.wordpress.com/" target="_blank">http://matthiaswessendorf.wordpress.com/</a><br>twitter: <a href="http://twitter.com/mwessendorf" target="_blank">http://twitter.com/mwessendorf</a></div></div></div>
</div></div>