11:41 a.m.
Hello,
I'm trying to follow this tutorial:
https://github.com/lholmquist/aerogear.org/tree/AGPUSH-549/docs/guides/ae...
Because I want to do an app that is able to receive push notifications. But
I'm having problems and seems that are coming from the AeroGear.js. But I'm
not sure.
I was debugging my application and it's returning this:
Error in response to pushMessaging.getChannelId: TypeError: Object
#<Object> has no method 'UnifiedPushClient'
anyone at anytime got this error? and know how to solve it?
this error comes from the "main.js" file on line 14 ->
https://github.com/lholmquist/aerogear.org/blob/AGPUSH-549/docs/guides/ae...
Thank you :)
--
Vasco Amaral
12:08 p.m.
Hey !
Are you sure you aerogear.js is loaded ?
In the guide I see a slight difference (and error that we should fix)
between the screenshot of the app structure showing aerogear.js is in
scripts/vendor folder and the manifest.json where it's in scripts/ (one
level higher).
Seb
On Fri, Mar 14, 2014 at 5:41 PM, Vasco Amaral <vmfamaral(a)gmail.com> wrote:
Hello,
I'm trying to follow this tutorial:
https://github.com/lholmquist/aerogear.org/tree/AGPUSH-549/docs/guides/ae...
Because I want to do an app that is able to receive push notifications.
But I'm having problems and seems that are coming from the AeroGear.js. But
I'm not sure.
I was debugging my application and it's returning this:
Error in response to pushMessaging.getChannelId: TypeError: Object
#<Object> has no method 'UnifiedPushClient'
anyone at anytime got this error? and know how to solve it?
this error comes from the "main.js" file on line 14 ->
https://github.com/lholmquist/aerogear.org/blob/AGPUSH-549/docs/guides/ae...
Thank you :)
--
Vasco Amaral
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
5:06 a.m.
Hi.
yes I'm sure, I print the aerogo (object) in the console and it appears with
a few methods, but not includes the "UnifiedPushClient". I saw the source
code of aerogo.js and some of the methods exist in the code. so I think it's
loaded correctly.
I changed it in the manifest.json file to be loaded in the scripts/vendor
folder, so that is not the problem.
(sorry for my bad english.)
Thanks again,
--
View this message in context:
http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Problem-with-Push-...
Sent from the aerogear-dev mailing list archive at Nabble.com.
6:45 a.m.
Ok I did a little change. Loading the "aerogear.unifiedpush.js" file and it
recognized the "UnifiedPushClient" . But now I have another problem when I
try to execute this command:
*/curl -3 -u "{pushApplicationID}:{masterSecret}"
-v -H "Accept: application/json" -H "Content-type:
application/json"
-X POST -d '{"message": {"alert":"Push
Notification"}}'
https://SERVER:PORT/CONTEXT/rest/sender/*
with all fields full filled correctly it returns me in the response:
/* upload completely sent off: 42out of 42 bytes
< HTTP/1.1 401 Unauthorized
< Connection: keep-alive
* Authentication problem. Ignoring this.
< WWW-Authenticate: Basic realm="AeroGear UnifiedPush Server"
< X-Powered-By: Undertow 1
< Server: Wildfly 8
< Content-Type: application/json
< Content-Length: 20
< Date: Mon, 17 Mar 2014 11:28:33 GMT*
/
any idea what can be?
--
View this message in context:
http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Problem-with-Push-...
Sent from the aerogear-dev mailing list archive at Nabble.com.
6:53 a.m.
What url are you using? Did you change the "context", etc. to your own /
platform specific parameters?
Sorry for asking ;-)
Enviado do meu iPhone
No dia 17/03/2014, às 11:45, oxsav <vmfamaral(a)gmail.com> escreveu:
Ok I did a little change. Loading the
"aerogear.unifiedpush.js" file and it
recognized the "UnifiedPushClient" . But now I have another problem when I
try to execute this command:
*/curl -3 -u "{pushApplicationID}:{masterSecret}"
-v -H "Accept: application/json" -H "Content-type:
application/json"
-X POST -d '{"message": {"alert":"Push
Notification"}}'
https://SERVER:PORT/CONTEXT/rest/sender/*
with all fields full filled correctly it returns me in the response:
/* upload completely sent off: 42out of 42 bytes
< HTTP/1.1 401 Unauthorized
< Connection: keep-alive
* Authentication problem. Ignoring this.
< WWW-Authenticate: Basic realm="AeroGear UnifiedPush Server"
< X-Powered-By: Undertow 1
< Server: Wildfly 8
< Content-Type: application/json
< Content-Length: 20
< Date: Mon, 17 Mar 2014 11:28:33 GMT*
/
any idea what can be?
--
View this message in context:
http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Problem-with-Push-...
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
6:57 a.m.
Hello I'm using
http://<ip_address>:<port>/unifiedpush-server-0.10.0/rest/sender
I'm using http because if I use https returns me an error of sslv3:
*/error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number/
*
tks
--
View this message in context:
http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Problem-with-Push-...
Sent from the aerogear-dev mailing list archive at Nabble.com.
7:24 a.m.
For http (no TLS), please skip the -3 part (that is for SSLv3)
On Mon, Mar 17, 2014 at 12:57 PM, oxsav <vmfamaral(a)gmail.com> wrote:
Hello I'm using
http://<ip_address>:<port>/unifiedpush-server-0.10.0/rest/sender
I'm using http because if I use https returns me an error of sslv3:
*/error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number/
*
tks
--
View this message in context:
http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Problem-with-Push-...
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
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
7:28 a.m.
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-...
Sent from the aerogear-dev mailing list archive at Nabble.com.
7:33 a.m.
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(a)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-...
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
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
7:51 a.m.
Yep, I'm sure that I'm doing that.
Can be a problem with the h2database? because in deployments it appears as
"undeployed".
thanks,
--
View this message in context:
http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Problem-with-Push-...
Sent from the aerogear-dev mailing list archive at Nabble.com.
7:54 a.m.
hrm, weird
make sure the xml file (
https://github.com/aerogear/aerogear-unifiedpush-server/blob/0.10.x/datab...)
is deployed into $JBOSS/standalone/deployments
On Mon, Mar 17, 2014 at 1:51 PM, oxsav <vmfamaral(a)gmail.com> wrote:
Yep, I'm sure that I'm doing that.
Can be a problem with the h2database? because in deployments it appears as
"undeployed".
thanks,
--
View this message in context:
http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Problem-with-Push-...
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
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
8:19 a.m.
Hmm did it. And the problem persists.
I analysed the log from the jboss and when I try to open the URL:
http://150.140.184.246:4441/unifiedpush-server-0.10.0 , returns me the
following error:
/*5:07:49,969 ERROR [org.jboss.as.ejb3.invocation] (default task-1)
JBAS014134: EJB Invocation failed on component Ping for method public
javax.ws.rs.core.Response
org.jboss.aerogear.unifiedpush.rest.util.Ping.ping():
javax.ejb.EJBException:
org.jboss.aerogear.security.exception.AeroGearSecurityException: Not
authorized!*/
The weird thing is, I can access that well and create my application, my
variant and I already have an device registered to a variant :S ..
Any idea?
Tks,
--
View this message in context:
http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Problem-with-Push-...
Sent from the aerogear-dev mailing list archive at Nabble.com.
8:28 a.m.
On Mon, Mar 17, 2014 at 2:19 PM, oxsav <vmfamaral(a)gmail.com> wrote:
Hmm did it. And the problem persists.
I analysed the log from the jboss and when I try to open the URL:
http://150.140.184.246:4441/unifiedpush-server-0.10.0 , returns me the
I do see the admin ui - but can not login, as I don't know your admin
password
following error:
/*5:07:49,969 ERROR [org.jboss.as.ejb3.invocation] (default task-1)
JBAS014134: EJB Invocation failed on component Ping for method public
javax.ws.rs.core.Response
org.jboss.aerogear.unifiedpush.rest.util.Ping.ping():
javax.ejb.EJBException:
org.jboss.aerogear.security.exception.AeroGearSecurityException: Not
authorized!*/
The weird thing is, I can access that well and create my application, my
variant and I already have an device registered to a variant :S ..
Any idea?
Tks,
--
View this message in context:
http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Problem-with-Push-...
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
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
9:44 a.m.
On Mon, Mar 17, 2014 at 2:19 PM, oxsav <vmfamaral(a)gmail.com> wrote:
Hmm did it. And the problem persists.
I analysed the log from the jboss and when I try to open the URL:
http://150.140.184.246:4441/unifiedpush-server-0.10.0 , returns me the
following error:
/*5:07:49,969 ERROR [org.jboss.as.ejb3.invocation] (default task-1)
JBAS014134: EJB Invocation failed on component Ping for method public
javax.ws.rs.core.Response
org.jboss.aerogear.unifiedpush.rest.util.Ping.ping():
javax.ejb.EJBException:
org.jboss.aerogear.security.exception.AeroGearSecurityException: Not
authorized!*/
The first "Ping" Rest call will always return this, the admin client uses
this to check if you are connected or not. So, having this log (probably at
the beginning) make sense.
The weird thing is, I can access that well and create my application, my
variant and I already have an device registered to a variant :S ..
Any idea?
Again, sorry again for asking stupid questions but you are sure to not have
left the "{" and "}" around the PushId and the masterID, check this
valid
example : https://github.com/sebastienblanc/chuckpush/blob/master/CURL.txt
Tks,
--
View this message in context:
http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Problem-with-Push-...
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
10:19 a.m.
Is not a stupid question. Maybe I'm a stupid guy :p
Yep the problem was the {}.
Thanks for all :)
--
View this message in context:
http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Problem-with-Push-...
Sent from the aerogear-dev mailing list archive at Nabble.com.
10:30 a.m.
On Mon, Mar 17, 2014 at 4:19 PM, oxsav <vmfamaral(a)gmail.com> wrote:
Is not a stupid question. Maybe I'm a stupid guy :p
Yep the problem was the {}.
Thanks for all :)
--
View this message in context:
http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Problem-with-Push-...
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
10:31 a.m.
On Mon, Mar 17, 2014 at 4:19 PM, oxsav <vmfamaral(a)gmail.com> wrote:
Is not a stupid question. Maybe I'm a stupid guy :p
Not at all :) you are not the first one hit by this, we should change the
doc / samples to make it more obivous !
Yep the problem was the {}.
Thanks for all :)
You're welcome, thanks again for you interest in the project.
--
View this message in context:
http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Problem-with-Push-...
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
10:36 a.m.
Yep, but if I saw the curl 's "man page", maybe I could have seen this
problem earlier. Because there we can find -u, --user <user:password>.
;) tks
--
View this message in context:
http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Problem-with-Push-...
Sent from the aerogear-dev mailing list archive at Nabble.com.
4418
days inactive
4421
days old
17 comments
5 participants
participants (5)
-
Matthias Wessendorf -
Miguel Lemos -
oxsav -
Sebastien Blanc -
Vasco Amaral