From matzew at apache.org Tue Sep 5 05:55:56 2017 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 5 Sep 2017 11:55:56 +0200 Subject: [Aerogear-users] OpenShift Online2 sunset In-Reply-To: <07a845d89ee84866b450e94ab4b309e4@ZXSWEXCHMXPR04.bhs.org> References: <07a845d89ee84866b450e94ab4b309e4@ZXSWEXCHMXPR04.bhs.org> Message-ID: Hello David, thanks for reaching out on this. For Openshift 3 the AeroGear community did develop a template for running UPS: https://github.com/aerogear/aerogear-unifiedpush-server/ tree/master/openshift The UPS does have an export feature, so you could export your devices from your Openshift2 instance, and use the import feature to re-import them into your new Openshift 3 instance! If you have more questions, or encounter problems, let us know! Greetings, Matthias On Tue, Aug 29, 2017 at 10:58 PM, Walto, David < David.Walto at baystatehealth.org> wrote: > Is the AeroGear Unified Push Server 1.1.3.final part of the OpenShift > Online 2 that is being sunset at the end of sept? > > > > I can?t find any upgrade information about AeroGear on the Migrate to > OpenShift Online 3 page. > > > > Thanks in advance for you answer. > > > > *David Walto* > > *Senior Application Engineer | EMR Engineering and Integration* > > *Baystate Health | Informatics & Technology* > > 1550 Main Street, Springfield, MA 01199 | p: 413-794-0627 | f: > 413-794-5570 > > > ------------------------------ > Please view our annual report at http://www.bhannualreport.org > > > CONFIDENTIALITY NOTICE: This e-mail communication and any attachments may > contain confidential and privileged information for the use of the > designated recipients named above. If you are not the intended recipient, > you are hereby notified that you have received this communication in error > and that any review, disclosure, dissemination, distribution or copying of > it or its contents is prohibited. If you have received this communication > in error, please reply to the sender immediately or by telephone at > 413-794-0000 and destroy all copies of this communication and any > attachments. For further information regarding Baystate Health's privacy > policy, please visit our Internet site at https://www.baystatehealth.org. > > _______________________________________________ > Aerogear-users mailing list > Aerogear-users at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-users > > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20170905/2f0b5da9/attachment.html From xfdeng at hotmail.com Tue Sep 5 22:46:05 2017 From: xfdeng at hotmail.com (jeff01) Date: Tue, 5 Sep 2017 19:46:05 -0700 (MST) Subject: [Aerogear-users] What does it mean when Aerogear UPS automatically unregister a device? Message-ID: <1504665965342-0.post@n5.nabble.com> What does it mean when Aerogear UPS automatically unregister a device? I recently noticed that Aerogear UPS (Version 1.1.0.Fonal) automatically unregister an ios device. When I open the app, it automatically register the device, but when I close the app, for s short while, through Aerogear admin console/applicaions/variants. I see the number of installations for an ios variant changed from 1 to 0? What does this mean? The .p12 certificate has issues? I am pretty sure it did not expire as I just requested it. Any thoughts? -- Sent from: http://aerogear-users.1116366.n5.nabble.com/ From matzew at apache.org Wed Sep 6 01:00:05 2017 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 6 Sep 2017 07:00:05 +0200 Subject: [Aerogear-users] What does it mean when Aerogear UPS automatically unregister a device? In-Reply-To: <1504665965342-0.post@n5.nabble.com> References: <1504665965342-0.post@n5.nabble.com> Message-ID: the server is deleting invalid or inactive tokens _after_ a push notification has been sent, here for iOS: https://github.com/aerogear/aerogear-unifiedpush-server/blob/1.1.0.Final/push/sender/src/main/java/org/jboss/aerogear/unifiedpush/message/sender/APNsPushNotificationSender.java#L234 means: if the (old) FeedBack service from apple tells the server token is not OK, server removes it On Wed, Sep 6, 2017 at 4:46 AM, jeff01 wrote: > What does it mean when Aerogear UPS automatically unregister a device? > > I recently noticed that Aerogear UPS (Version 1.1.0.Fonal) automatically > unregister an ios device. When I open the app, it automatically register > the > device, but when I close the app, for s short while, through Aerogear admin > console/applicaions/variants. I see the number of installations for an ios > variant changed from 1 to 0? > > What does this mean? The .p12 certificate has issues? I am pretty sure it > did not expire as I just requested it. > > Any thoughts? > > > > -- > Sent from: http://aerogear-users.1116366.n5.nabble.com/ > _______________________________________________ > Aerogear-users mailing list > Aerogear-users at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-users > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20170906/5997e4aa/attachment.html From vfbsilva at gmail.com Wed Sep 13 12:04:07 2017 From: vfbsilva at gmail.com (vfbsilva) Date: Wed, 13 Sep 2017 09:04:07 -0700 (MST) Subject: [Aerogear-users] Error getting a request from inside Kubernetes Message-ID: <1505318647083-0.post@n5.nabble.com> Guys I'm having a SSL issue when trying to connect aerogear from a machine inside of Kubernetes. If I send the same command from another machine or using curl it does work. Might be related to some problems I had with ingress. Anyone has some ideas? 2017-09-13 12:50:12,923 ERROR [org.keycloak.adapters.AdapterDeploymentContext] (default task-1) request scheme: http ssl required 2017-09-13 12:50:12,923 ERROR [io.undertow.request] (default task-1) UT005023: Exception handling request to /ag-push/rest/sender/: java.lang.RuntimeException: Can't resolve relative url from adapter config. at org.keycloak.adapters.AdapterDeploymentContext.getBaseBuilder(AdapterDeploymentContext.java:446) at org.keycloak.adapters.AdapterDeploymentContext.resolveUrls(AdapterDeploymentContext.java:96) at org.keycloak.adapters.AdapterDeploymentContext.resolveDeployment(AdapterDeploymentContext.java:83) at org.keycloak.adapters.PreAuthActionsHandler.preflightCors(PreAuthActionsHandler.java:74) at org.keycloak.adapters.PreAuthActionsHandler.handleRequest(PreAuthActionsHandler.java:50) at org.keycloak.adapters.undertow.ServletPreAuthActionsHandler.handleRequest(ServletPreAuthActionsHandler.java:68) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:292) at io.undertow.servlet.handlers.ServletInitialHandler.access$100(ServletInitialHandler.java:81) at io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:138) at io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:135) at io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:48) at io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43) at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44) at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44) at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44) at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44) at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44) at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44) at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:272) at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:81) at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:104) at io.undertow.server.Connectors.executeRootHandler(Connectors.java:202) at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:805) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) -- Sent from: http://aerogear-users.1116366.n5.nabble.com/ From xfdeng at hotmail.com Wed Sep 20 08:42:17 2017 From: xfdeng at hotmail.com (jeff01) Date: Wed, 20 Sep 2017 05:42:17 -0700 (MST) Subject: [Aerogear-users] What does it mean when Aerogear UPS automatically unregister a device? In-Reply-To: References: <1504665965342-0.post@n5.nabble.com> Message-ID: <1505911337575-0.post@n5.nabble.com> Just an update. In my case, the root cause of my issue is that the p12 file is not in a correct format. -- Sent from: http://aerogear-users.1116366.n5.nabble.com/ From xfdeng at hotmail.com Wed Sep 20 08:45:42 2017 From: xfdeng at hotmail.com (jeff01) Date: Wed, 20 Sep 2017 05:45:42 -0700 (MST) Subject: [Aerogear-users] Migration guide from 1.1.0-Final to 1.2.0.Final Message-ID: <1505911542335-0.post@n5.nabble.com> Hi, Any Aerogear UPS migration guide from 1.1.0-Final to 1.2.0.Final? The only relevant info I can see is here: https://github.com/aerogear/aerogear-unifiedpush-server/tree/1.2.0.Final/migrator But it looks outdated. Where can I find more instructions? I may be able to help updating the document but I need someone familiar with the process to provide more details on the migration path from from 1.1.0-Final to 1.2.0.Final. Thank you. -- Sent from: http://aerogear-users.1116366.n5.nabble.com/ From matzew at apache.org Wed Sep 20 11:07:26 2017 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 20 Sep 2017 15:07:26 +0000 Subject: [Aerogear-users] Migration guide from 1.1.0-Final to 1.2.0.Final In-Reply-To: <1505911542335-0.post@n5.nabble.com> References: <1505911542335-0.post@n5.nabble.com> Message-ID: I think it's worth to try, but make DB backup. I tested a bit (e.g 1.1.4-SNAPHOT to 1.2.0) against an existing DB .. was ok. No guarantees ;-) another thing is: export your installations from old (re)create push-app/variants and import devices On Wed, 20 Sep 2017 at 15:23, jeff01 wrote: > Hi, > > Any Aerogear UPS migration guide from 1.1.0-Final to 1.2.0.Final? The only > relevant info I can see is here: > > > https://github.com/aerogear/aerogear-unifiedpush-server/tree/1.2.0.Final/migrator > > But it looks outdated. Where can I find more instructions? I may be able to > help updating the document but I need someone familiar with the process to > provide more details on the migration path from from 1.1.0-Final to > 1.2.0.Final. > > Thank you. > > > > -- > Sent from: http://aerogear-users.1116366.n5.nabble.com/ > _______________________________________________ > Aerogear-users mailing list > Aerogear-users at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-users > -- Sent from Gmail Mobile -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20170920/71369817/attachment.html From jusanche at redhat.com Wed Sep 20 12:11:52 2017 From: jusanche at redhat.com (Julio Cesar Sanchez Hernandez) Date: Wed, 20 Sep 2017 18:11:52 +0200 Subject: [Aerogear-users] aerogear-ios-http 2.0.0 for Swift4 released Message-ID: Hi, We have updated aerogear-ios-http to Swift 4 and it has been released in CocoaPods as 2.0.0. It also drops support for iOS 8. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20170920/7bef5088/attachment.html From xfdeng at hotmail.com Wed Sep 20 15:02:23 2017 From: xfdeng at hotmail.com (jeff01) Date: Wed, 20 Sep 2017 12:02:23 -0700 (MST) Subject: [Aerogear-users] Migration guide from 1.1.0-Final to 1.2.0.Final In-Reply-To: References: <1505911542335-0.post@n5.nabble.com> Message-ID: <1505934143579-0.post@n5.nabble.com> Thanks for the reply. Can you confirm that there are no DB schema changes from V 1.1.0.Final to V 1.2.0.Final - so we can use the same schema or DB structure from V 1.1.0.Final when upgrading to V 1.2.0.Final? -- Sent from: http://aerogear-users.1116366.n5.nabble.com/ From xfdeng at hotmail.com Wed Sep 20 15:11:29 2017 From: xfdeng at hotmail.com (jeff01) Date: Wed, 20 Sep 2017 12:11:29 -0700 (MST) Subject: [Aerogear-users] [newbie] choosing the right version In-Reply-To: References: <1504149733387-0.post@n5.nabble.com> Message-ID: <1505934689226-0.post@n5.nabble.com> Since V 1.2.0.Final is out, it's no brainer now that we will use V 1.2.0.Final for PRO upgrade. -- Sent from: http://aerogear-users.1116366.n5.nabble.com/ From xfdeng at hotmail.com Wed Sep 20 15:54:43 2017 From: xfdeng at hotmail.com (jeff01) Date: Wed, 20 Sep 2017 12:54:43 -0700 (MST) Subject: [Aerogear-users] SSL handshake failed, cipher suite in SSL Session is SSL_NULL_WITH_NULL_NULL Message-ID: <1505937283908-0.post@n5.nabble.com> Hi, Does anyone know what does this error mean? Aerogaer UPS: 1.1.3.Final, Jboss AS 6.4. 2017-09-20 18:49:07,767 DEBUG [org.apache.tomcat.util] (http-SOME_HOST/SOMEIP:8443-2) JBWEB003006: Handshake failed: java.io.IOException: JBWEB002042: SSL handshake failed, cipher suite in SSL Session is SSL_NULL_WITH_NULL_NULL at org.apache.tomcat.util.net.jsse.JSSESocketFactory.handshake(JSSESocketFactory.java:203) [jbossweb-7.5.7.Final-redhat-1.jar:7.5.7.Final-redhat-1] at org.apache.tomcat.util.net.JIoEndpoint.setSocketOptions(JIoEndpoint.java:1114) [jbossweb-7.5.7.Final-redhat-1.jar:7.5.7.Final-redhat-1] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:926) [jbossweb-7.5.7.Final-redhat-1.jar:7.5.7.Final-redhat-1] at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_131] -- Sent from: http://aerogear-users.1116366.n5.nabble.com/ From matzew at apache.org Wed Sep 20 18:31:34 2017 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 21 Sep 2017 00:31:34 +0200 Subject: [Aerogear-users] Migration guide from 1.1.0-Final to 1.2.0.Final In-Reply-To: <1505934143579-0.post@n5.nabble.com> References: <1505911542335-0.post@n5.nabble.com> <1505934143579-0.post@n5.nabble.com> Message-ID: no, there were new tables, like: https://github.com/aerogear/aerogear-unifiedpush-server/commit/944d6c6f6ea6b22a0859fe527e8a23d09b556204 On Wed, Sep 20, 2017 at 9:02 PM, jeff01 wrote: > Thanks for the reply. Can you confirm that there are no DB schema changes > from V 1.1.0.Final to V 1.2.0.Final - so we can use the same schema or DB > structure from V 1.1.0.Final when upgrading to V 1.2.0.Final? > > > > > > -- > Sent from: http://aerogear-users.1116366.n5.nabble.com/ > _______________________________________________ > Aerogear-users mailing list > Aerogear-users at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-users > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20170921/53299ea7/attachment.html From xfdeng at hotmail.com Thu Sep 21 10:30:04 2017 From: xfdeng at hotmail.com (jeff01) Date: Thu, 21 Sep 2017 07:30:04 -0700 (MST) Subject: [Aerogear-users] Migration guide from 1.1.0-Final to 1.2.0.Final In-Reply-To: References: <1505911542335-0.post@n5.nabble.com> <1505934143579-0.post@n5.nabble.com> Message-ID: <1506004204733-0.post@n5.nabble.com> Thanks again for the reply. Can you provide a list of DB changes required for upgrade from V 1.1.0.Final to V 1.2.0.Final ? Or provide as many as you can if there are too many DB changes :-) -- Sent from: http://aerogear-users.1116366.n5.nabble.com/ From xfdeng at hotmail.com Thu Sep 21 10:33:27 2017 From: xfdeng at hotmail.com (jeff01) Date: Thu, 21 Sep 2017 07:33:27 -0700 (MST) Subject: [Aerogear-users] Error sending payload to APNs server: javax.net.ssl.SSLException: Received fatal alert: internal_error In-Reply-To: <1504216553664-0.post@n5.nabble.com> References: <1502897166941-1148.post@n5.nabble.com> <1502920655042-1151.post@n5.nabble.com> <1503540353006-1188.post@n5.nabble.com> <1503973178525-1189.post@n5.nabble.com> <1504149405256-0.post@n5.nabble.com> <1504216553664-0.post@n5.nabble.com> Message-ID: <1506004407549-0.post@n5.nabble.com> Just wanted to provide an update: The root cause in our case is that the p12 is incorrect, which included a personal cert in it. After it was recreated without personal cert, all is fine now. -- Sent from: http://aerogear-users.1116366.n5.nabble.com/ From dpassos at redhat.com Thu Sep 21 15:52:51 2017 From: dpassos at redhat.com (Daniel Passos) Date: Thu, 21 Sep 2017 16:52:51 -0300 Subject: [Aerogear-users] Organizing AeroGear iOS Pods Message-ID: Hi! Julio and I are preparing new releases for all our iOS libraries and we realized the Pods name are a mess Some projects are using Repo name: aerogear-ios-[feature] Project: aerogear-[feature] Pod: aerogear-[feature] We wanna move all our libraries to the same page renaming all to the following pattern: Repo name: aerogear-ios-[feature] Project: AeroGear[Feature] Pod: AeroGear[Feature] Changing the library name in CocoaPods is not a cool thing to do, but since the next release will be a major I do not see a problem. Wdyt? -- -- Passos -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20170921/0b1e2ffb/attachment-0001.html From matzew at apache.org Thu Sep 21 19:10:08 2017 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 21 Sep 2017 23:10:08 +0000 Subject: [Aerogear-users] [aerogear-dev] Organizing AeroGear iOS Pods In-Reply-To: References: Message-ID: On Thu, 21 Sep 2017 at 23:13, Daniel Passos wrote: > Hi! > > Julio and I are preparing new releases for all our iOS libraries and we > realized the Pods name are a mess > > Some projects are using > > Repo name: aerogear-ios-[feature] > Project: aerogear-[feature] > Pod: aerogear-[feature] > > We wanna move all our libraries to the same page renaming all to the > following pattern: > > Repo name: aerogear-ios-[feature] > Project: AeroGear[Feature] > Pod: AeroGear[Feature] > > Changing the library name in CocoaPods is not a cool thing to do, but > since the next release will be a major I do not see a problem. > > Wdyt? > > +1 > -- > -- Passos > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -- Sent from Gmail Mobile -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20170921/e3c79e43/attachment.html From fedecentrico at gmail.com Fri Sep 22 13:03:23 2017 From: fedecentrico at gmail.com (Federico Cerminara) Date: Fri, 22 Sep 2017 19:03:23 +0200 Subject: [Aerogear-users] Anyone could help me for notification handling on iOS devices? Message-ID: Hi, my name is Federico, I wrote some time ago for a crash scenario and tyou were very helpful. Hope I?ll be so lucky again. I?m still a beginner in cross platform app development and I am using aerogear cordova push plugin (together with Ionic 1 and Angular 1) to enable reception of push notification. Here follows my little trouble. My customer asked me to modify, if possible, app behavior in push notification handling, especially on iOS devices. He?s explaining me he finds too many push notifications after a long period of inactivity (notification are sent by a backend job each hour) and that he would like the app to handle only the last one. I don?t know if it?s possible, working on client code, to ask my app to avoid to show a push if some others have already come without being effectively handled (if you think it?s possible and you could suggest me a way, I would appreciate it very much). The best solution I am able to image is to use the onNotification() function in my angular code to make another server call, just to tell the exact time oh push notification handling. It will be after a backend trouble to decide, known which users have received a push and when eventually the same users have handled it, if it will send them another notification. Hope I have been clear describing my solution (and maybe it was not so important) but the main point is: can you tell me if there?s some useful approach (maybe using some configuration of server AAerogear) to avoid sending many push to the same user/client if he has not handled them? Or even, can you tell me if the user can handle one push for all, on a iOS device? (On Android devices I would have tried to manipulate java classes for PushHandlerActivity and NotificationMeassgeHandler). This could be very helpful for me. I have you will have a nice weekend. Federico -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20170922/f08cfb9e/attachment.html From xfdeng at hotmail.com Wed Sep 27 11:34:19 2017 From: xfdeng at hotmail.com (jeff01) Date: Wed, 27 Sep 2017 08:34:19 -0700 (MST) Subject: [Aerogear-users] Anyone could help me for notification handling on iOS devices? In-Reply-To: References: Message-ID: <1506526459217-0.post@n5.nabble.com> I think you may try to look for eventID - if you make it a constant, the ios client should only receive the latest push message. -- Sent from: http://aerogear-users.1116366.n5.nabble.com/ From xfdeng at hotmail.com Wed Sep 27 11:38:05 2017 From: xfdeng at hotmail.com (jeff01) Date: Wed, 27 Sep 2017 08:38:05 -0700 (MST) Subject: [Aerogear-users] Is Jboss AS 6.4.0 GA still supported by Aerogear UPS? In-Reply-To: <1478797794575-948.post@n5.nabble.com> References: <1478797794575-948.post@n5.nabble.com> Message-ID: <1506526685453-0.post@n5.nabble.com> I am revamping up this thread as I still did not see Jboss was supported in the latest 1.2.0-Final release. In the dist packake, I only see unifiedpush-server-wildfly.war provided. Can any one confirm if JBoss is still supported and where can we find the .way release for 1.2.0-Final for JBOss AS? Thank you. -- Sent from: http://aerogear-users.1116366.n5.nabble.com/ From matzew at apache.org Wed Sep 27 11:55:59 2017 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 27 Sep 2017 17:55:59 +0200 Subject: [Aerogear-users] Is Jboss AS 6.4.0 GA still supported by Aerogear UPS? In-Reply-To: <1506526685453-0.post@n5.nabble.com> References: <1478797794575-948.post@n5.nabble.com> <1506526685453-0.post@n5.nabble.com> Message-ID: 1.2.0 UPS is WF 10 or later On Wed, Sep 27, 2017 at 5:38 PM, jeff01 wrote: > I am revamping up this thread as I still did not see Jboss was supported in > the latest 1.2.0-Final release. In the dist packake, I only see > unifiedpush-server-wildfly.war provided. > > Can any one confirm if JBoss is still supported and where can we find the > .way release for 1.2.0-Final for JBOss AS? Thank you. > > > > -- > Sent from: http://aerogear-users.1116366.n5.nabble.com/ > _______________________________________________ > Aerogear-users mailing list > Aerogear-users at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-users > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20170927/999a50c6/attachment.html From fedecentrico at gmail.com Wed Sep 27 12:31:58 2017 From: fedecentrico at gmail.com (Federico Cerminara) Date: Wed, 27 Sep 2017 18:31:58 +0200 Subject: [Aerogear-users] Anyone could help me for notification handling on iOS devices? In-Reply-To: <1506526459217-0.post@n5.nabble.com> References: <1506526459217-0.post@n5.nabble.com> Message-ID: Where could I find it? In my Java code for sending push notification or in aerogear configuration tool? Another way I was thinking about was to use the message content to send client a complex set of metadata, containing not only the message text, but eventually an id for the sent notification or even something else... 2017-09-27 17:34 GMT+02:00 jeff01 : > I think you may try to look for eventID - if you make it a constant, the > ios > client should only receive the latest push message. > > > > -- > Sent from: http://aerogear-users.1116366.n5.nabble.com/ > _______________________________________________ > Aerogear-users mailing list > Aerogear-users at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-users > -- Puoi trovarmi qui, se vuoi: facebook , flickr , linkedin , twitter , anobii Link consigliati: Piccoli Maestri , Il clima di Cipro -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20170927/988a8344/attachment.html From fedecentrico at gmail.com Wed Sep 27 12:32:15 2017 From: fedecentrico at gmail.com (Federico Cerminara) Date: Wed, 27 Sep 2017 18:32:15 +0200 Subject: [Aerogear-users] Anyone could help me for notification handling on iOS devices? In-Reply-To: References: <1506526459217-0.post@n5.nabble.com> Message-ID: Anyway, thanks for the reply :-) 2017-09-27 18:31 GMT+02:00 Federico Cerminara : > Where could I find it? In my Java code for sending push notification or in > aerogear configuration tool? > Another way I was thinking about was to use the message content to send > client a complex set of metadata, containing not only the message text, but > eventually an id for the sent notification or even something else... > > 2017-09-27 17:34 GMT+02:00 jeff01 : > >> I think you may try to look for eventID - if you make it a constant, the >> ios >> client should only receive the latest push message. >> >> >> >> -- >> Sent from: http://aerogear-users.1116366.n5.nabble.com/ >> _______________________________________________ >> Aerogear-users mailing list >> Aerogear-users at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-users >> > > > > -- > Puoi trovarmi qui, se vuoi: > facebook , flickr > , linkedin > , twitter > , anobii > > Link consigliati: Piccoli Maestri , Il > clima di Cipro > -- Puoi trovarmi qui, se vuoi: facebook , flickr , linkedin , twitter , anobii Link consigliati: Piccoli Maestri , Il clima di Cipro -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20170927/451b687e/attachment-0001.html From xfdeng at hotmail.com Wed Sep 27 13:16:34 2017 From: xfdeng at hotmail.com (jeff01) Date: Wed, 27 Sep 2017 10:16:34 -0700 (MST) Subject: [Aerogear-users] Is Jboss AS 6.4.0 GA still supported by Aerogear UPS? In-Reply-To: <1506526685453-0.post@n5.nabble.com> References: <1478797794575-948.post@n5.nabble.com> <1506526685453-0.post@n5.nabble.com> Message-ID: <1506532594532-0.post@n5.nabble.com> I looked into the history. The AS7 build was removed since 03/18/2017 since 1.2.0 development. Any reason why and how to add them back? If someone can give directions, I can add it back. https://github.com/aerogear/aerogear-unifiedpush-server/commits/master/servers/pom.xml Commits on Mar 18, 2016 at matzew@lfrycRemove AS7 WAR and referencesmatzew committed with lfryc on Mar 18, 2016 https://github.com/aerogear/aerogear-unifiedpush-server/commit/14dae3fed27656ca65d44dc50806a62bdb03430b#diff-81882a40fd327815a95c9af82ee9f0d7 - auth-server - ups-as7 --- >> This was taken out after march 2016. - ups-wildfly - -- Sent from: http://aerogear-users.1116366.n5.nabble.com/ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20170927/c8b4ea80/attachment.html From matzew at apache.org Wed Sep 27 14:07:16 2017 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 27 Sep 2017 20:07:16 +0200 Subject: [Aerogear-users] Is Jboss AS 6.4.0 GA still supported by Aerogear UPS? In-Reply-To: <1506532594532-0.post@n5.nabble.com> References: <1478797794575-948.post@n5.nabble.com> <1506526685453-0.post@n5.nabble.com> <1506532594532-0.post@n5.nabble.com> Message-ID: WF 10+ does use a different JMS broker. Artemis - while before HornetQ was used. The 1.1.x line works on EAP 6.4. Master targets latest. WF10 now - once WF11 is out, that will be the default for moving the community forward On Wed, Sep 27, 2017 at 7:16 PM, jeff01 wrote: > I looked into the history. The AS7 build was removed since 03/18/2017 > since 1.2.0 development. Any reason why and how to add them back? If > someone can give directions, I can add it back. > https://github.com/aerogear/aerogear-unifiedpush-server/commits/master/servers/pom.xml > Commits on Mar 18, 2016 @matzew at lfryc Remove AS7 WAR and references > matzew committed with lfryc on Mar 18, 2016 https://github.com/aerogear/ > aerogear-unifiedpush-server/commit/14dae3fed27656ca65d44dc50806a6 > 2bdb03430b#diff-81882a40fd327815a95c9af82ee9f0d7 - auth-server - ups-as7 > --- >> This was taken out after march 2016. - ups-wildfly - > ------------------------------ > Sent from the aerogear-users mailing list archive > at Nabble.com. > > _______________________________________________ > Aerogear-users mailing list > Aerogear-users at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-users > > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20170927/7dc47629/attachment.html From xfdeng at hotmail.com Wed Sep 27 17:14:05 2017 From: xfdeng at hotmail.com (jeff01) Date: Wed, 27 Sep 2017 14:14:05 -0700 (MST) Subject: [Aerogear-users] Is Jboss EAP 6.4.0 GA still supported by Aerogear UPS? In-Reply-To: <1478797794575-948.post@n5.nabble.com> References: <1478797794575-948.post@n5.nabble.com> Message-ID: <1506546845223-0.post@n5.nabble.com> I filed a related Jira request here: https://issues.jboss.org/browse/AEROGEAR-1759 -- Sent from: http://aerogear-users.1116366.n5.nabble.com/ From matzew at apache.org Wed Sep 27 21:26:07 2017 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 28 Sep 2017 03:26:07 +0200 Subject: [Aerogear-users] Is Jboss EAP 6.4.0 GA still supported by Aerogear UPS? In-Reply-To: <1506546845223-0.post@n5.nabble.com> References: <1478797794575-948.post@n5.nabble.com> <1506546845223-0.post@n5.nabble.com> Message-ID: I *think* that EAP7, would work On Wed, Sep 27, 2017 at 11:14 PM, jeff01 wrote: > I filed a related Jira request here: > > https://issues.jboss.org/browse/AEROGEAR-1759 > > > > > > -- > Sent from: http://aerogear-users.1116366.n5.nabble.com/ > _______________________________________________ > Aerogear-users mailing list > Aerogear-users at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-users > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20170928/0ef814cd/attachment.html From Philipp.Koetz at mvise.de Thu Sep 28 08:50:58 2017 From: Philipp.Koetz at mvise.de (Philipp Koetz, mVISE AG) Date: Thu, 28 Sep 2017 12:50:58 +0000 Subject: [Aerogear-users] iOS 11 Support Message-ID: Dear Aerogear Team, does the 1.2 release works fine for iOS 11? We have right now the problem that messages will be rejected if there is an alert, badge or sound key in the message. In the current version of Aerogear push server we are using (1.1.3) is the alert key everytime attached to the messages json. Regards, Philipp Koetz -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20170928/bd617807/attachment.html From xfdeng at hotmail.com Thu Sep 28 12:44:59 2017 From: xfdeng at hotmail.com (jeff01) Date: Thu, 28 Sep 2017 09:44:59 -0700 (MST) Subject: [Aerogear-users] Anyone could help me for notification handling on iOS devices? In-Reply-To: References: <1506526459217-0.post@n5.nabble.com> Message-ID: <1506617099453-0.post@n5.nabble.com> You are welcome. Sorry I cannot remember it on top of my head now. You may start from the native library code to support the push plugin used in your app. -- Sent from: http://aerogear-users.1116366.n5.nabble.com/ From fedecentrico at gmail.com Thu Sep 28 17:52:48 2017 From: fedecentrico at gmail.com (Federico Cerminara) Date: Thu, 28 Sep 2017 23:52:48 +0200 Subject: [Aerogear-users] Anyone could help me for notification handling on iOS devices? In-Reply-To: <1506617099453-0.post@n5.nabble.com> References: <1506526459217-0.post@n5.nabble.com> <1506617099453-0.post@n5.nabble.com> Message-ID: Do not worry. I'll find it sooner or later :) Il 28 Set 2017 19:00, "jeff01" ha scritto: > You are welcome. > > Sorry I cannot remember it on top of my head now. You may start from the > native library code to support the push plugin used in your app. > > > > -- > Sent from: http://aerogear-users.1116366.n5.nabble.com/ > _______________________________________________ > Aerogear-users mailing list > Aerogear-users at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-users > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20170928/2527b9f3/attachment-0001.html From Philipp.Koetz at mvise.de Fri Sep 29 04:57:30 2017 From: Philipp.Koetz at mvise.de (Philipp Koetz, mVISE AG) Date: Fri, 29 Sep 2017 08:57:30 +0000 Subject: [Aerogear-users] iOS 11 Support In-Reply-To: References: Message-ID: Forgot to mention that it is about silent notifications (https://developer.apple.com/library/content/documentation/NetworkingInternet/Conceptual/RemoteNotificationsPG/CreatingtheNotificationPayload.html) Von: aerogear-users-bounces at lists.jboss.org [mailto:aerogear-users-bounces at lists.jboss.org] Im Auftrag von Philipp Koetz, mVISE AG Gesendet: Donnerstag, 28. September 2017 14:51 An: aerogear-users at lists.jboss.org Betreff: [Aerogear-users] iOS 11 Support Dear Aerogear Team, does the 1.2 release works fine for iOS 11? We have right now the problem that messages will be rejected if there is an alert, badge or sound key in the message. In the current version of Aerogear push server we are using (1.1.3) is the alert key everytime attached to the messages json. Regards, Philipp Koetz -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20170929/38673ed5/attachment.html From jusanche at redhat.com Fri Sep 29 11:58:48 2017 From: jusanche at redhat.com (Julio Cesar Sanchez Hernandez) Date: Fri, 29 Sep 2017 17:58:48 +0200 Subject: [Aerogear-users] iOS 11 Support In-Reply-To: References: Message-ID: How are you sending the push notifications? Can you provide a code sample of how do you build silent push payload? On Fri, Sep 29, 2017 at 10:57 AM, Philipp Koetz, mVISE AG < Philipp.Koetz at mvise.de> wrote: > Forgot to mention that it is about silent notifications ( > https://developer.apple.com/library/content/documentation/ > NetworkingInternet/Conceptual/RemoteNotificationsPG/ > CreatingtheNotificationPayload.html) > > > > *Von:* aerogear-users-bounces at lists.jboss.org [mailto:aerogear-users- > bounces at lists.jboss.org] *Im Auftrag von *Philipp Koetz, mVISE AG > *Gesendet:* Donnerstag, 28. September 2017 14:51 > *An:* aerogear-users at lists.jboss.org > *Betreff:* [Aerogear-users] iOS 11 Support > > > > Dear Aerogear Team, > > > > does the 1.2 release works fine for iOS 11? We have right now the problem > that messages will be rejected if there is an alert, badge or sound key in > the message. In the current version of Aerogear push server we are using > (1.1.3) is the alert key everytime attached to the messages json. > > > > Regards, > > Philipp Koetz > > _______________________________________________ > Aerogear-users mailing list > Aerogear-users at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-users > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20170929/d0147694/attachment.html From jgallaso at redhat.com Fri Sep 22 02:32:06 2017 From: jgallaso at redhat.com (Jose Miguel Gallas Olmedo) Date: Fri, 22 Sep 2017 06:32:06 -0000 Subject: [Aerogear-users] [aerogear-dev] Organizing AeroGear iOS Pods In-Reply-To: References: Message-ID: +1, consistent naming is a must JOSE MIGUEL GALLAS OLMEDO ASSOCIATE QE, mobile Red Hat M: +34618488633 On 22 September 2017 at 01:10, Matthias Wessendorf wrote: > > On Thu, 21 Sep 2017 at 23:13, Daniel Passos wrote: > >> Hi! >> >> Julio and I are preparing new releases for all our iOS libraries and we >> realized the Pods name are a mess >> >> Some projects are using >> >> Repo name: aerogear-ios-[feature] >> Project: aerogear-[feature] >> Pod: aerogear-[feature] >> >> We wanna move all our libraries to the same page renaming all to the >> following pattern: >> >> Repo name: aerogear-ios-[feature] >> Project: AeroGear[Feature] >> Pod: AeroGear[Feature] >> >> Changing the library name in CocoaPods is not a cool thing to do, but >> since the next release will be a major I do not see a problem. >> >> Wdyt? >> >> > +1 > > > > >> -- >> -- Passos >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > -- > Sent from Gmail Mobile > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20170922/32f779cf/attachment-0001.html