7:25 a.m.
Hello,
we have encountered a problem while registering Android devices against the unified push
server. Apple devices are not affected and can register successfull.
We are using org.jboss.aerogear:aerogear-android-push:2.2.1 as client lib.
Could you also provide a Deeplink which we can manually test the device registration?
2016-05-25 13:20:15,193 WARN [org.jboss.resteasy.core.ExceptionHandler] (default task-29)
failed to execute: javax.ws.rs.NotAllowedException: No resource method found for GET,
return 405 with Allow header
at org.jboss.resteasy.core.registry.SegmentNode.match(SegmentNode.java:375)
[resteasy-jaxrs-3.0.10.Final.jar:]
at org.jboss.resteasy.core.registry.SegmentNode.match(SegmentNode.java:114)
[resteasy-jaxrs-3.0.10.Final.jar:]
at org.jboss.resteasy.core.registry.RootNode.match(RootNode.java:43)
[resteasy-jaxrs-3.0.10.Final.jar:]
at org.jboss.resteasy.core.registry.RootClassNode.match(RootClassNode.java:48)
[resteasy-jaxrs-3.0.10.Final.jar:]
at
org.jboss.resteasy.core.ResourceMethodRegistry.getResourceInvoker(ResourceMethodRegistry.java:444)
[resteasy-jaxrs-3.0.10.Final.jar:]
at
org.jboss.resteasy.core.SynchronousDispatcher.getInvoker(SynchronousDispatcher.java:234)
[resteasy-jaxrs-3.0.10.Final.jar:]
at
org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:171)
[resteasy-jaxrs-3.0.10.Final.jar:]
at
org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:220)
[resteasy-jaxrs-3.0.10.Final.jar:]
at
org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:56)
[resteasy-jaxrs-3.0.10.Final.jar:]
at
org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:51)
[resteasy-jaxrs-3.0.10.Final.jar:]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
[jboss-servlet-api_3.1_spec-1.0.0.Final.jar:1.0.0.Final]
at
io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:86)
[undertow-servlet-1.1.8.Final.jar:1.1.8.Final]
at
io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:130)
[undertow-servlet-1.1.8.Final.jar:1.1.8.Final]
at
org.jboss.aerogear.unifiedpush.rest.util.VersionFilter.doFilter(VersionFilter.java:65)
[unifiedpush-jaxrs-1.1.3.Final.jar:1.1.3.Final]
at io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:60)
[undertow-servlet-1.1.8.Final.jar:1.1.8.Final]
at
io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:132)
[undertow-servlet-1.1.8.Final.jar:1.1.8.Final]
at
org.jboss.aerogear.unifiedpush.service.filter.HttpContextFilter.doFilter(HttpContextFilter.java:55)
[unifiedpush-service-1.1.3.Final.jar:1.1.3.Final]
at io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:60)
[undertow-servlet-1.1.8.Final.jar:1.1.8.Final]
at
io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:132)
[undertow-servlet-1.1.8.Final.jar:1.1.8.Final]
at io.undertow.servlet.handlers.FilterHandler.handleRequest(FilterHandler.java:85)
[undertow-servlet-1.1.8.Final.jar:1.1.8.Final]
at
io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:62)
[undertow-servlet-1.1.8.Final.jar:1.1.8.Final]
at
io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36)
[undertow-servlet-1.1.8.Final.jar:1.1.8.Final]
at
org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78)
at
io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
[undertow-core-1.1.8.Final.jar:1.1.8.Final]
at
org.keycloak.adapters.undertow.UndertowAuthenticatedActionsHandler.handleRequest(UndertowAuthenticatedActionsHandler.java:66)
[keycloak-undertow-adapter-1.3.1.Final.jar:1.3.1.Final]
at
org.keycloak.adapters.undertow.UndertowAuthenticatedActionsHandler.handleRequest(UndertowAuthenticatedActionsHandler.java:66)
[keycloak-undertow-adapter-1.3.1.Final.jar:1.3.1.Final]
at
io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:131)
[undertow-servlet-1.1.8.Final.jar:1.1.8.Final]
at
io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:57)
[undertow-servlet-1.1.8.Final.jar:1.1.8.Final]
at
io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
[undertow-core-1.1.8.Final.jar:1.1.8.Final]
at
io.undertow.security.handlers.AuthenticationConstraintHandler.handleRequest(AuthenticationConstraintHandler.java:51)
[undertow-core-1.1.8.Final.jar:1.1.8.Final]
at
io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46)
[undertow-core-1.1.8.Final.jar:1.1.8.Final]
at
io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64)
[undertow-servlet-1.1.8.Final.jar:1.1.8.Final]
at
io.undertow.servlet.handlers.security.ServletSecurityConstraintHandler.handleRequest(ServletSecurityConstraintHandler.java:56)
[undertow-servlet-1.1.8.Final.jar:1.1.8.Final]
at
io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:58)
[undertow-core-1.1.8.Final.jar:1.1.8.Final]
at
io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:70)
[undertow-servlet-1.1.8.Final.jar:1.1.8.Final]
at
io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:76)
[undertow-core-1.1.8.Final.jar:1.1.8.Final]
at
io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
[undertow-core-1.1.8.Final.jar:1.1.8.Final]
at
org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61)
at
io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
[undertow-core-1.1.8.Final.jar:1.1.8.Final]
at
org.keycloak.adapters.undertow.ServletPreAuthActionsHandler.handleRequest(ServletPreAuthActionsHandler.java:69)
[keycloak-undertow-adapter-1.3.1.Final.jar:1.3.1.Final]
at
org.keycloak.adapters.undertow.ServletPreAuthActionsHandler.handleRequest(ServletPreAuthActionsHandler.java:69)
[keycloak-undertow-adapter-1.3.1.Final.jar:1.3.1.Final]
at
io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
[undertow-core-1.1.8.Final.jar:1.1.8.Final]
at
io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:261)
[undertow-servlet-1.1.8.Final.jar:1.1.8.Final]
at
io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:248)
[undertow-servlet-1.1.8.Final.jar:1.1.8.Final]
at
io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:77)
[undertow-servlet-1.1.8.Final.jar:1.1.8.Final]
at
io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:167)
[undertow-servlet-1.1.8.Final.jar:1.1.8.Final]
at io.undertow.server.Connectors.executeRootHandler(Connectors.java:199)
[undertow-core-1.1.8.Final.jar:1.1.8.Final]
at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:761)
[undertow-core-1.1.8.Final.jar:1.1.8.Final]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
[rt.jar:1.8.0_72-internal]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
[rt.jar:1.8.0_72-internal]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_72-internal]
8:08 a.m.
Have you registered an Android variant? This stack trace implies that you
are trying to hit the android registration endpoint but you don't have the
right credentials (which would be the variant ID and secret)
On Fri, May 27, 2016 at 7:25 AM, Philipp Koetz, mVISE AG <
Philipp.Koetz(a)mvise.de> wrote:
Hello,
we have encountered a problem while registering Android devices against
the unified push server. Apple devices are not affected and can register
successfull.
We are using org.jboss.aerogear:aerogear-android-push:2.2.1 as client lib.
Could you also provide a Deeplink which we can manually test the device
registration?
2016-05-25 13:20:15,193 WARN [org.jboss.resteasy.core.ExceptionHandler]
(default task-29) failed to execute: javax.ws.rs.NotAllowedException: No
resource method found for GET, return 405 with Allow header
at
org.jboss.resteasy.core.registry.SegmentNode.match(SegmentNode.java:375)
[resteasy-jaxrs-3.0.10.Final.jar:]
at
org.jboss.resteasy.core.registry.SegmentNode.match(SegmentNode.java:114)
[resteasy-jaxrs-3.0.10.Final.jar:]
at
org.jboss.resteasy.core.registry.RootNode.match(RootNode.java:43)
[resteasy-jaxrs-3.0.10.Final.jar:]
at
org.jboss.resteasy.core.registry.RootClassNode.match(RootClassNode.java:48)
[resteasy-jaxrs-3.0.10.Final.jar:]
at
org.jboss.resteasy.core.ResourceMethodRegistry.getResourceInvoker(ResourceMethodRegistry.java:444)
[resteasy-jaxrs-3.0.10.Final.jar:]
at
org.jboss.resteasy.core.SynchronousDispatcher.getInvoker(SynchronousDispatcher.java:234)
[resteasy-jaxrs-3.0.10.Final.jar:]
at
org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:171)
[resteasy-jaxrs-3.0.10.Final.jar:]
at
org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:220)
[resteasy-jaxrs-3.0.10.Final.jar:]
at
org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:56)
[resteasy-jaxrs-3.0.10.Final.jar:]
at
org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:51)
[resteasy-jaxrs-3.0.10.Final.jar:]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
[jboss-servlet-api_3.1_spec-1.0.0.Final.jar:1.0.0.Final]
at
io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:86)
[undertow-servlet-1.1.8.Final.jar:1.1.8.Final]
at
io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:130)
[undertow-servlet-1.1.8.Final.jar:1.1.8.Final]
at
org.jboss.aerogear.unifiedpush.rest.util.VersionFilter.doFilter(VersionFilter.java:65)
[unifiedpush-jaxrs-1.1.3.Final.jar:1.1.3.Final]
at
io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:60)
[undertow-servlet-1.1.8.Final.jar:1.1.8.Final]
at
io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:132)
[undertow-servlet-1.1.8.Final.jar:1.1.8.Final]
at
org.jboss.aerogear.unifiedpush.service.filter.HttpContextFilter.doFilter(HttpContextFilter.java:55)
[unifiedpush-service-1.1.3.Final.jar:1.1.3.Final]
at
io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:60)
[undertow-servlet-1.1.8.Final.jar:1.1.8.Final]
at
io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:132)
[undertow-servlet-1.1.8.Final.jar:1.1.8.Final]
at
io.undertow.servlet.handlers.FilterHandler.handleRequest(FilterHandler.java:85)
[undertow-servlet-1.1.8.Final.jar:1.1.8.Final]
at
io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:62)
[undertow-servlet-1.1.8.Final.jar:1.1.8.Final]
at
io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36)
[undertow-servlet-1.1.8.Final.jar:1.1.8.Final]
at
org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78)
at
io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
[undertow-core-1.1.8.Final.jar:1.1.8.Final]
at
org.keycloak.adapters.undertow.UndertowAuthenticatedActionsHandler.handleRequest(UndertowAuthenticatedActionsHandler.java:66)
[keycloak-undertow-adapter-1.3.1.Final.jar:1.3.1.Final]
at
org.keycloak.adapters.undertow.UndertowAuthenticatedActionsHandler.handleRequest(UndertowAuthenticatedActionsHandler.java:66)
[keycloak-undertow-adapter-1.3.1.Final.jar:1.3.1.Final]
at
io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:131)
[undertow-servlet-1.1.8.Final.jar:1.1.8.Final]
at
io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:57)
[undertow-servlet-1.1.8.Final.jar:1.1.8.Final]
at
io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
[undertow-core-1.1.8.Final.jar:1.1.8.Final]
at
io.undertow.security.handlers.AuthenticationConstraintHandler.handleRequest(AuthenticationConstraintHandler.java:51)
[undertow-core-1.1.8.Final.jar:1.1.8.Final]
at
io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46)
[undertow-core-1.1.8.Final.jar:1.1.8.Final]
at
io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64)
[undertow-servlet-1.1.8.Final.jar:1.1.8.Final]
at
io.undertow.servlet.handlers.security.ServletSecurityConstraintHandler.handleRequest(ServletSecurityConstraintHandler.java:56)
[undertow-servlet-1.1.8.Final.jar:1.1.8.Final]
at
io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:58)
[undertow-core-1.1.8.Final.jar:1.1.8.Final]
at
io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:70)
[undertow-servlet-1.1.8.Final.jar:1.1.8.Final]
at
io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:76)
[undertow-core-1.1.8.Final.jar:1.1.8.Final]
at
io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
[undertow-core-1.1.8.Final.jar:1.1.8.Final]
at
org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61)
at
io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
[undertow-core-1.1.8.Final.jar:1.1.8.Final]
at
org.keycloak.adapters.undertow.ServletPreAuthActionsHandler.handleRequest(ServletPreAuthActionsHandler.java:69)
[keycloak-undertow-adapter-1.3.1.Final.jar:1.3.1.Final]
at
org.keycloak.adapters.undertow.ServletPreAuthActionsHandler.handleRequest(ServletPreAuthActionsHandler.java:69)
[keycloak-undertow-adapter-1.3.1.Final.jar:1.3.1.Final]
at
io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
[undertow-core-1.1.8.Final.jar:1.1.8.Final]
at
io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:261)
[undertow-servlet-1.1.8.Final.jar:1.1.8.Final]
at
io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:248)
[undertow-servlet-1.1.8.Final.jar:1.1.8.Final]
at
io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:77)
[undertow-servlet-1.1.8.Final.jar:1.1.8.Final]
at
io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:167)
[undertow-servlet-1.1.8.Final.jar:1.1.8.Final]
at
io.undertow.server.Connectors.executeRootHandler(Connectors.java:199)
[undertow-core-1.1.8.Final.jar:1.1.8.Final]
at
io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:761)
[undertow-core-1.1.8.Final.jar:1.1.8.Final]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
[rt.jar:1.8.0_72-internal]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
[rt.jar:1.8.0_72-internal]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_72-internal]
_______________________________________________
Aerogear-users mailing list
Aerogear-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-users
6:43 a.m.
Hello,
I'm a colleague of Philipp, only that I'm working on integrating the android
part.
We generated again variantID and variantSecret and we send them correctly.
Also we tested the request using Advance REST client chrome extension and
there the connection succeeds with 200 status code and a json response. But
inside the app we still receive error 405 Method not allowed.
Exception received: org.jboss.aerogear.android.pipe.http.HttpException: The
server returned the error code 405.
Stacktrace:
"org.jboss.aerogear.android.pipe.http.HttpRestProvider.getHeaderAndBody(HttpRestProvider.java:287)"
"org.jboss.aerogear.android.pipe.http.HttpRestProvider.post(HttpRestProvider.java:148)"
"org.jboss.aerogear.android.pipe.http.HttpRestProvider.post(HttpRestProvider.java:134)"
"org.jboss.aerogear.android.unifiedpush.gcm.AeroGearGCMPushRegistrar$4.doInBackground(AeroGearGCMPushRegistrar.java:170)"
"org.jboss.aerogear.android.unifiedpush.gcm.AeroGearGCMPushRegistrar$4.doInBackground(AeroGearGCMPushRegistrar.java:135)"
"android.os.AsyncTask$2.call(AsyncTask.java:292)"
"java.util.concurrent.FutureTask.run(FutureTask.java:237)"
"android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:231)"
"java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)"
"java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)"
"java.lang.Thread.run(Thread.java:818)"
After some more digging we suspect that this is the issue we are
experiencing https://issues.jboss.org/browse/AGDROID-270 , only that we
don't receive inside the app an exception similar to that described in the
jira ticket. According to the steps described there, it seems that aero gear
library fails to establish a connection to a unified Push Server using
HTTPS, which is exactly what we are trying to do. We can provide the sample
app with our server configuration set up if needed.
--
View this message in context:
http://aerogear-users.1116366.n5.nabble.com/Aerogear-users-Device-registr...
Sent from the aerogear-users mailing list archive at Nabble.com.
8:20 a.m.
On Wed, Jun 1, 2016 at 6:43 AM, Ramona.Cristea <Ramona.Cristea(a)mvise.de>
wrote:
Hello,
I'm a colleague of Philipp, only that I'm working on integrating the
android
part.
We generated again variantID and variantSecret and we send them correctly.
Also we tested the request using Advance REST client chrome extension and
there the connection succeeds with 200 status code and a json response. But
inside the app we still receive error 405 Method not allowed.
Exception received: org.jboss.aerogear.android.pipe.http.HttpException: The
server returned the error code 405.
Stacktrace:
"org.jboss.aerogear.android.pipe.http.HttpRestProvider.getHeaderAndBody(HttpRestProvider.java:287)"
"org.jboss.aerogear.android.pipe.http.HttpRestProvider.post(HttpRestProvider.java:148)"
"org.jboss.aerogear.android.pipe.http.HttpRestProvider.post(HttpRestProvider.java:134)"
"org.jboss.aerogear.android.unifiedpush.gcm.AeroGearGCMPushRegistrar$4.doInBackground(AeroGearGCMPushRegistrar.java:170)"
"org.jboss.aerogear.android.unifiedpush.gcm.AeroGearGCMPushRegistrar$4.doInBackground(AeroGearGCMPushRegistrar.java:135)"
"android.os.AsyncTask$2.call(AsyncTask.java:292)"
"java.util.concurrent.FutureTask.run(FutureTask.java:237)"
"android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:231)"
"java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)"
"java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)"
"java.lang.Thread.run(Thread.java:818)"
After some more digging we suspect that this is the issue we are
experiencing https://issues.jboss.org/browse/AGDROID-270 , only that we
don't receive inside the app an exception similar to that described in the
jira ticket. According to the steps described there, it seems that aero
gear
library fails to establish a connection to a unified Push Server using
HTTPS, which is exactly what we are trying to do. We can provide the sample
app with our server configuration set up if needed.
The sample app would be great. Just link us a github (or any other public
repo)
and we can take a look.
--
View this message in context:
http://aerogear-users.1116366.n5.nabble.com/Aerogear-users-Device-registr...
Sent from the aerogear-users mailing list archive at Nabble.com.
_______________________________________________
Aerogear-users mailing list
Aerogear-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-users
8:35 a.m.
In Android N I have documented a workaround for this particular issue :
https://blog.sagaoftherealms.net/?p=578
On Wed, Jun 1, 2016 at 8:20 AM, Summers Pittman <supittma(a)redhat.com> wrote:
On Wed, Jun 1, 2016 at 6:43 AM, Ramona.Cristea <Ramona.Cristea(a)mvise.de>
wrote:
> Hello,
>
> I'm a colleague of Philipp, only that I'm working on integrating the
> android
> part.
>
> We generated again variantID and variantSecret and we send them correctly.
> Also we tested the request using Advance REST client chrome extension and
> there the connection succeeds with 200 status code and a json response.
> But
> inside the app we still receive error 405 Method not allowed.
>
> Exception received: org.jboss.aerogear.android.pipe.http.HttpException:
> The
> server returned the error code 405.
> Stacktrace:
>
>
"org.jboss.aerogear.android.pipe.http.HttpRestProvider.getHeaderAndBody(HttpRestProvider.java:287)"
>
>
"org.jboss.aerogear.android.pipe.http.HttpRestProvider.post(HttpRestProvider.java:148)"
>
>
"org.jboss.aerogear.android.pipe.http.HttpRestProvider.post(HttpRestProvider.java:134)"
>
>
"org.jboss.aerogear.android.unifiedpush.gcm.AeroGearGCMPushRegistrar$4.doInBackground(AeroGearGCMPushRegistrar.java:170)"
>
>
"org.jboss.aerogear.android.unifiedpush.gcm.AeroGearGCMPushRegistrar$4.doInBackground(AeroGearGCMPushRegistrar.java:135)"
> "android.os.AsyncTask$2.call(AsyncTask.java:292)"
> "java.util.concurrent.FutureTask.run(FutureTask.java:237)"
> "android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:231)"
>
>
"java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)"
>
>
"java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)"
> "java.lang.Thread.run(Thread.java:818)"
>
> After some more digging we suspect that this is the issue we are
> experiencing https://issues.jboss.org/browse/AGDROID-270 , only that we
> don't receive inside the app an exception similar to that described in the
> jira ticket. According to the steps described there, it seems that aero
> gear
> library fails to establish a connection to a unified Push Server using
> HTTPS, which is exactly what we are trying to do. We can provide the
> sample
> app with our server configuration set up if needed.
>
> The sample app would be great. Just link us a github (or any other
public repo) and we can take a look.
>
>
> --
> View this message in context:
>
http://aerogear-users.1116366.n5.nabble.com/Aerogear-users-Device-registr...
> Sent from the aerogear-users mailing list archive at Nabble.com.
> _______________________________________________
> Aerogear-users mailing list
> Aerogear-users(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-users
>
1:53 a.m.
Unfortunately the client wants to support API 16 and up, so we have to find a
solution also for the older android versions. I sent you yesterday evening
the sample app through email, hope you received it.
--
View this message in context:
http://aerogear-users.1116366.n5.nabble.com/Aerogear-users-Device-registr...
Sent from the aerogear-users mailing list archive at Nabble.com.
7:13 a.m.
On Thu, Jun 2, 2016 at 1:53 AM, Ramona.Cristea <Ramona.Cristea(a)mvise.de>
wrote:
Unfortunately the client wants to support API 16 and up, so we have
to
find a
solution also for the older android versions. I sent you yesterday evening
the sample app through email, hope you received it.
Could you test the workaround in an Android N emulator? If the app works
in that
situation we know you are facing
https://issues.jboss.org/browse/AGDROID-270 and we can work out a better
work around which works for Android 16 (and fixes this for everyone else).
I'm taking a look at the sample today.
--
View this message in context:
http://aerogear-users.1116366.n5.nabble.com/Aerogear-users-Device-registr...
Sent from the aerogear-users mailing list archive at Nabble.com.
_______________________________________________
Aerogear-users mailing list
Aerogear-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-users
7:58 a.m.
So I don't think you are experiencing AGDROID-270.
I've used the Android N network security tooling and still get the same
error. Additionally I have successfully registered with a different
instance of UPS using the sample code.
Which version of the UPS server are you running?
On Thu, Jun 2, 2016 at 7:13 AM, Summers Pittman <supittma(a)redhat.com> wrote:
On Thu, Jun 2, 2016 at 1:53 AM, Ramona.Cristea <Ramona.Cristea(a)mvise.de>
wrote:
> Unfortunately the client wants to support API 16 and up, so we have to
> find a
> solution also for the older android versions. I sent you yesterday evening
> the sample app through email, hope you received it.
>
> Could you test the workaround in an Android N emulator? If the app works
in that situation we know you are facing
https://issues.jboss.org/browse/AGDROID-270 and we can work out a better
work around which works for Android 16 (and fixes this for everyone else).
I'm taking a look at the sample today.
>
> --
> View this message in context:
>
http://aerogear-users.1116366.n5.nabble.com/Aerogear-users-Device-registr...
> Sent from the aerogear-users mailing list archive at Nabble.com.
> _______________________________________________
> Aerogear-users mailing list
> Aerogear-users(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-users
>
8:53 a.m.
We've deployed UPS 1.1.3.
--
View this message in context:
http://aerogear-users.1116366.n5.nabble.com/Aerogear-users-Device-registr...
Sent from the aerogear-users mailing list archive at Nabble.com.
9:08 a.m.
Ok I did some digging and discovered a confound which might be the issue.
When I make a request to your UPS instance using curl I get a redirect. It
is possible that the agdroid push library does not handle this redirect
elegantly.
The redirect is from "$YOUR_URL/ag-push/rest/registry/device" to
"$YOUR_URL/ag-push/rest/registry/device/". Notice how a "/" is added
onto
the end.
I'm not convinced this is the issue, but it does seem like something to
investigate.
On Thu, Jun 2, 2016 at 7:58 AM, Summers Pittman <supittma(a)redhat.com> wrote:
So I don't think you are experiencing AGDROID-270.
I've used the Android N network security tooling and still get the same
error. Additionally I have successfully registered with a different
instance of UPS using the sample code.
Which version of the UPS server are you running?
On Thu, Jun 2, 2016 at 7:13 AM, Summers Pittman <supittma(a)redhat.com>
wrote:
>
>
> On Thu, Jun 2, 2016 at 1:53 AM, Ramona.Cristea <Ramona.Cristea(a)mvise.de>
> wrote:
>
>> Unfortunately the client wants to support API 16 and up, so we have to
>> find a
>> solution also for the older android versions. I sent you yesterday
>> evening
>> the sample app through email, hope you received it.
>>
>> Could you test the workaround in an Android N emulator? If the app
> works in that situation we know you are facing
> https://issues.jboss.org/browse/AGDROID-270 and we can work out a better
> work around which works for Android 16 (and fixes this for everyone else).
>
> I'm taking a look at the sample today.
>
>
>>
>> --
>> View this message in context:
>>
http://aerogear-users.1116366.n5.nabble.com/Aerogear-users-Device-registr...
>> Sent from the aerogear-users mailing list archive at Nabble.com.
>> _______________________________________________
>> Aerogear-users mailing list
>> Aerogear-users(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-users
>>
>
>
9:31 a.m.
On Thu, Jun 2, 2016 at 9:08 AM, Summers Pittman <supittma(a)redhat.com> wrote:
Ok I did some digging and discovered a confound which might be the
issue.
When I make a request to your UPS instance using curl I get a redirect.
It is possible that the agdroid push library does not handle this redirect
elegantly.
The redirect is from "$YOUR_URL/ag-push/rest/registry/device" to
"$YOUR_URL/ag-push/rest/registry/device/". Notice how a "/" is added
onto
the end.
I'm not convinced this is the issue, but it does seem like something to
investigate.
The redirect is causing the issue/exposing the bug.
You may follow the progress on this JIRA :
https://issues.jboss.org/browse/AGDROID-549
On Thu, Jun 2, 2016 at 7:58 AM, Summers Pittman <supittma(a)redhat.com>
wrote:
> So I don't think you are experiencing AGDROID-270.
>
> I've used the Android N network security tooling and still get the same
> error. Additionally I have successfully registered with a different
> instance of UPS using the sample code.
>
> Which version of the UPS server are you running?
>
> On Thu, Jun 2, 2016 at 7:13 AM, Summers Pittman <supittma(a)redhat.com>
> wrote:
>
>>
>>
>> On Thu, Jun 2, 2016 at 1:53 AM, Ramona.Cristea <Ramona.Cristea(a)mvise.de>
>> wrote:
>>
>>> Unfortunately the client wants to support API 16 and up, so we have to
>>> find a
>>> solution also for the older android versions. I sent you yesterday
>>> evening
>>> the sample app through email, hope you received it.
>>>
>>> Could you test the workaround in an Android N emulator? If the app
>> works in that situation we know you are facing
>> https://issues.jboss.org/browse/AGDROID-270 and we can work out a
>> better work around which works for Android 16 (and fixes this for everyone
>> else).
>>
>> I'm taking a look at the sample today.
>>
>>
>>>
>>> --
>>> View this message in context:
>>>
http://aerogear-users.1116366.n5.nabble.com/Aerogear-users-Device-registr...
>>> Sent from the aerogear-users mailing list archive at Nabble.com.
>>> _______________________________________________
>>> Aerogear-users mailing list
>>> Aerogear-users(a)lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-users
>>>
>>
>>
>
3:49 a.m.
Hello
Thank you for your investigation. I forwarded everything to my colleague in
charge of the server. Also he discovered some issues on the server side. It
seems that some rules were applied to the server's firewall which caused
some connections to be refused.
--
View this message in context:
http://aerogear-users.1116366.n5.nabble.com/Aerogear-users-Device-registr...
Sent from the aerogear-users mailing list archive at Nabble.com.
2882
days inactive
2889
days old
aerogear-users@lists.jboss.org
11 comments
3 participants
participants (3)
-
Philipp Koetz, mVISE AG -
Ramona.Cristea -
Summers Pittman