[aerogear-dev] GCM Device Token not accepted

[Matthias Wessendorf]

Hi,

did you managed to get it working? I am wondering if it was a temporary
issue for you - looks like for Summers it worked

On Wed, Mar 30, 2016 at 5:14 PM, Summers Pittman <supittma at redhat.com>
wrote:

> I know "Works on my machine" is a bad response, but well, works on my
> machine*
>
> The caveats are I am using UPS 1.1.2 and AGDroid-push 3.0.0-SNAPSHOT.  As
> far as I know AGDroid 2.2.2 does not use Instance ID.
>
> I've uploaded some screen shots here : http://imgur.com/a/eKF4F
>
> Can you provide some more details?  What versions of things are you
> using?  Can you gist your source code, etc.
>
>
>
> On Wed, Mar 23, 2016 at 8:34 PM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>>
>>
>> On Thu, Mar 24, 2016 at 1:00 AM, Matthias Wessendorf <matzew at apache.org>
>> wrote:
>>
>>> Hello,
>>>
>>> sorry for the late reply, but the mail got stuck in my moderation queue
>>> :-(
>>>
>>>
>>> On Thu, Mar 17, 2016 at 2:44 PM, cel <heldner at glue.ch> wrote:
>>>
>>>> The new device Token returned by the new GCM - API for Android (using
>>>> InstanceId.getToken  instead of gcm.register(context), which is
>>>> deprecated)
>>>>
>>>
>>> For that we have a ticket, but weren't able to get to it:
>>> https://issues.jboss.org/browse/AGDROID-427
>>>
>>>
>>>> is not accepted by the Aerogear server. The format of the
>>>> InstanceId.getToken is different.
>>>> Example:
>>>> Beginnning of gcm.register - Token :
>>>> APA91bGdSq3-OKaDV_pyvunTZpnD_LKb6OrxIk7...
>>>> Beginning of InstanceId.getToken :
>>>> eArreQ7017w:APA91bFe5lTYzEoNSivfPYaID...
>>>>  So if I try to register with the InstanceId.getToken using the Restful
>>>> interface "/registry/device" the Http response of the aerogear server
>>>> is:
>>>> "200 OK", but I still cannot find it in the installations. Consequently
>>>> no
>>>>
>>>
>> I think the weird part is, that it's returning 200 to the Android device,
>> which means it was accepted,
>> but something else went wrong, while sending.
>>
>> Any more logs? Or can you increase logging on the UPS?
>> https://aerogear.org/docs/unifiedpush/ups_userguide/index/#debugging
>>
>>
>>
>>> push notifications from aerogear can be sent to that device. Is this a
>>>> Bug?
>>>> Has this been fixed in newer versions?
>>>>
>>>
>>> yes, that's a bug - looks like the token format changed w/ InstanceId,
>>> and our 'validator' needs to be updated.
>>>
>>> Thanks for reporting, I have filed a JIRA and we will be looking at it:
>>> https://jira.jboss.org/browse/AGPUSH-1600
>>>
>>> -Matthias
>>>
>>>
>>>
>>>
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> View this message in context:
>>>> http://aerogear-dev.1069024.n5.nabble.com/GCM-Device-Token-not-accepted-tp12403.html
>>>> Sent from the aerogear-dev mailing list archive at Nabble.com.
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>
>>>
>>>
>>>
>>> --
>>> 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 at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
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/20160408/4b0adfa7/attachment-0001.html