Re: [aerogear-dev] GCM Device Token not accepted

The new device Token returned by the new GCM - API for Android (using InstanceId.getToken instead of gcm.register(context), which is deprecated)

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 push notifications from aerogear can be sent to that device. Is this a Bug? Has this been fixed in newer versions?

-- View this message in context: http://aerogear-dev.1069024.n5.nabble.com/GCM-Device-Token-not-accepted-t... Sent from the aerogear-dev mailing list archive at Nabble.com. _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev