Re: [aerogear-dev] AeroGear Android Push 2.2.0

this pom.xml, on the 2.2.0 tag has incorrect version nr: https://github.com/aerogear/aerogear-android-push/blob/2.2.0/aerogear-and... On Fri, Jun 19, 2015 at 12:53 AM, Daniel Passos <dpassos(a)redhat.com&gt; wrote: > Hi, > > I've staged[1] the Push library 2.2.0 again and send a PR for UnifiedPush > helloworld[2] using it. > > We’re planning to release it next Wednesday > > Fell free to test it and let us know if you find any issues. > [1] > https://repository.jboss.org/nexus/content/repositories/jboss_releases_st... > [2] https://github.com/jboss-mobile/unified-push-helloworld/pull/15 > > > On Wed, Jun 17, 2015 at 10:36 PM, Daniel Passos <dpassos(a)redhat.com&gt; > wrote: > >> Hey Guys, >> >> We are postpone it to fix the bug Matthias found. I just send a PR[1] to >> fix it. >> >> [1] https://github.com/aerogear/aerogear-android-push/pull/38 >> >> On Wed, Jun 17, 2015 at 11:32 AM, Summers Pittman <supittma(a)redhat.com&gt; >> wrote: >> >>> >>> >>> >>> On Wed, Jun 17, 2015 at 3:17 AM, Sebastien Blanc <scm.blanc(a)gmail.com&gt; >>> wrote: >>> >>>> This fix is more a workaround since it was not needed with the >>>> previous versions. so we need to be sure to check if : >>>> >>> No. The hello world app is broken. >>> >>>> >>>> - This fix was needed because of other commits on the helloworld >>>> >>> - This fix was needed because of the new version of the library >>>> - This fix was needed because of a change from GCM server >>>> - This fix was needed because of a mix/combination of all the previous >>>> potential causes >>>> >>> >>> TL;DR: We never needed information from the PushRegistrar to handle >>> messages until metrics were added. Now we do. However, if the app is >>> garbage collected then the registration information is cleared from memory >>> (it is persisted on the device of course). Because the notification >>> handler is invoked by android it bypasses the RegisterActivity. When we >>> try to fetch the registration information to send the metric message it >>> isn't loaded and the NPE is thrown. Previously had enabled the ability to >>> unregister the client from the message list screen we would have seen >>> similar results. >>> >>> The application work by happy coincidence. It wasn't until matz tested >>> on a hellishly obsolete device that the issue appeared. ;) >>> >>> >>> >>>> Passos have you been able to test the lib with Aerodoc ? >>>> >>>> Sebi >>>> >>>> >>>> >>>> >>>> On Tue, Jun 16, 2015 at 4:50 PM, Daniel Passos <dpassos(a)redhat.com&gt; >>>> wrote: >>>> >>>>> Seems the problem was in the app not in the library. For more details >>>>> please see my comment[1] in Jira and the fix in this PR[2] >>>>> >>>>> [1] >>>>> https://issues.jboss.org/browse/AGDROID-425?focusedCommentId=13079805&... >>>>> [2] https://github.com/jboss-mobile/unified-push-helloworld/pull/14 >>>>> >>>>> On Mon, Jun 15, 2015 at 9:42 AM, Matthias Wessendorf < >>>>> matzew(a)apache.org&gt; wrote: >>>>> >>>>>> I noticed a little bug w/ the current libray >>>>>> >>>>>> https://issues.jboss.org/browse/AGDROID-425 >>>>>> >>>>>> >>>>>> >>>>>> On Mon, Jun 15, 2015 at 2:42 AM, Daniel Passos <dpassos(a)redhat.com&gt; >>>>>> wrote: >>>>>> >>>>>>> Hey Everyone, >>>>>>> >>>>>>> We are ready to release AeroGear Android Push 2.2.0, we staged[1] >>>>>>> it on Nexus. >>>>>>> >>>>>>> What is new in this version? >>>>>>> >>>>>>> - AGDROID-422 <https://issues.jboss.org/browse/AGDROID-422> - >>>>>>> Add support for push-config.json for Android Push SDK >>>>>>> - AGDROID-423 <https://issues.jboss.org/browse/AGDROID-423> - >>>>>>> Android SDK hook for notifying the server if app has been opened due to a >>>>>>> push >>>>>>> >>>>>>> >>>>>>> >>>>>>> We’re planning to release it next Thursday. >>>>>>> >>>>>>> Fell free to test it and let us know if you find any issues. >>>>>>> >>>>>>> [1] >>>>>>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_st... >>>>>>> ​ >>>>>>> -- >>>>>>> -- Passos >>>>>>> >>>>>>> _______________________________________________ >>>>>>> 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 >>>>>> >>>>>> _______________________________________________ >>>>>> aerogear-dev mailing list >>>>>> aerogear-dev(a)lists.jboss.org >>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> -- Passos >>>>> >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev(a)lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>> >>>> >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev(a)lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> >> >> -- >> -- Passos >> > > > > -- > -- Passos > > _______________________________________________ > 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 _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev