[aerogear-dev] GCM3: InstanceID tokens versus 'old' tokens

[Matthias Wessendorf]

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 at apache.org>
wrote:

>
>
> On Wed, Apr 20, 2016 at 12:19 PM, Matthias Wessendorf <matzew at 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/fa74eea6a183d852fb26773bb1b62cf9016c9157
>>
>> 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/gcm/GcmPubSub#public-methods
>
> 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20160420/3de5c187/attachment.html