I never tried / tested the Chrome bits;

However, regarding the "send" and getting a 401;

Are you sure you are using the right PushApplicationID and the master secret ?

It's NOT the credentials from your Chrome Variant - the send requires the credentials from the root Push Application (not the variant)

On Mon, Mar 17, 2014 at 1:28 PM, oxsav <vmfamaral@gmail.com> wrote:

Skipped it same thing "Unauthorized".

this only works for packaged chrome applications? or it works for unpackaged
chrome applications too?

Because w8ting about an hour for an package application being accepted, is
not good at all..

--
View this message in context: http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Problem-with-Push-notification-chrome-app-tp6817p6845.html

Sent from the aerogear-dev mailing list archive at Nabble.com.
_______________________________________________
aerogear-dev mailing list
aerogear-dev@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