On Wed, Apr 20, 2016 at 12:19 PM, Matthias Wessendorf <matzew(a)apache.org&gt; wrote: > Hi, > > the format for tokens received from InstanceID API have a slightly > different format: > > https://github.com/aerogear/aerogear-unifiedpush-server/commit/fa74eea6a1... > > It's basically (prefix_string : RegistrationID). > > Now, in order to be able to subscribe on a topic is it _really_ required > to have a 'new' InstanceID token ? I could not find a _clear_ statement > looks like InstanceID tokens are required: https://developers.google.com/android/reference/com/google/android/gms/gc... But, on the other hand it does not mention that GCM.register() tokens are not allowed :-) > > I am asking because I'm working on the server hook to send topic request. > > If the answer yes, only InstanceID tokens can subscribe, we need a little > switch on the server (not a show stopper): > 1) send /topics/{something} (should not affect 'old' tokens_ > 2) fallback: find tokens w/o the ':', so we can fallback to pure > registration Id for "non-Instance ID " tokens > > > Thanks, > Matthias > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf

One of the things to consider is that applications re-register each time they load.

So an app can move from being registered with a GCM.register token to being registered with a InstanceID token.

I think that instanceID tokens have ":"'s and GCM.register tokens do not.

We should probably make a contrived scenario where an app registered and then changes to InstanceID to see what happens.

It SHOULDN'T get double messages because the app update relaunch step should break the old gcm token. But we need to test it.

On Wed, Apr 20, 2016 at 7:33 AM, Matthias Wessendorf <matzew(a)apache.org&gt; wrote: > Even if they were allowed... Apps, with older AGDroid SDKs aren't able to > subscribe. That means if the UPS server updates, they all would receive no > message :-) > > Therefore that look up for 'old' tokens is generally needed > > On Wed, Apr 20, 2016 at 1:23 PM, Matthias Wessendorf <matzew(a)apache.org&gt; > wrote: > >> >> >> On Wed, Apr 20, 2016 at 12:19 PM, Matthias Wessendorf <matzew(a)apache.org >> > wrote: >> >>> Hi, >>> >>> the format for tokens received from InstanceID API have a slightly >>> different format: >>> >>> https://github.com/aerogear/aerogear-unifiedpush-server/commit/fa74eea6a1... >>> >>> It's basically (prefix_string : RegistrationID). >>> >>> Now, in order to be able to subscribe on a topic is it _really_ >>> required to have a 'new' InstanceID token ? I could not find a _clear_ >>> statement >>> >> >> looks like InstanceID tokens are required: >> >> https://developers.google.com/android/reference/com/google/android/gms/gc... >> >> But, on the other hand it does not mention that GCM.register() tokens >> are not allowed :-) >> >> >>> >>> I am asking because I'm working on the server hook to send topic >>> request. >>> >>> If the answer yes, only InstanceID tokens can subscribe, we need a >>> little switch on the server (not a show stopper): >>> 1) send /topics/{something} (should not affect 'old' tokens_ >>> 2) fallback: find tokens w/o the ':', so we can fallback to pure >>> registration Id for "non-Instance ID " tokens >>> >>> >>> Thanks, >>> Matthias >>> >>> -- >>> Matthias Wessendorf >>> >>> blog: http://matthiaswessendorf.wordpress.com/ >>> sessions: http://www.slideshare.net/mwessendorf >>> twitter: http://twitter.com/mwessendorf >>> >> >> >> >> -- >> Matthias Wessendorf >> >> blog: http://matthiaswessendorf.wordpress.com/ >> sessions: http://www.slideshare.net/mwessendorf >> twitter: http://twitter.com/mwessendorf >> > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev