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@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:
is not accepted by the Aerogear server. The format of the
InstanceId.getToken is different.
Beginnning of gcm.register - Token :
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
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:



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