Hello iOS Friends, AeroGear iOS 1.5 is on his way. We plan (if no objections raised) to release it end of this week. Main focus of 1.5 is to upgrade to iOS7 and AFNetworking 2.x (latest 2.2.1). To test it, open Podfile and point to the latest git branch pod 'AeroGear', :git => 'https://github.com/aerogear/aerogear-ios.git' Help us make this release a success, give it a trial, and let us know how it goes for your project. ++ Corinne _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev

Hello Sebi Actually PR are on their ways (as we test it) to set proper version, what you need here https://github.com/aerogear/aerogear-push-ios-registration/blob/master/Po... is to upgrade to: platform :ios, '7.0' pod 'AFNetworking', '2.2.1' Note that we'll support from ios 7.0 Feel free to send the PR with Podfile update if the testing works for you. ++ Thanks for the feedback, Corinne On 18 Mar 2014, at 09:44, Sebastien Blanc <scm.blanc(a)gmail.com&gt; wrote: > FNetworking (= 2.2.1)` required by `AeroGear (1.5.0)`- `AFNetworking/Serialization` required by `AFNetworking (2.2.1)`- `AFNetworking/Security` required by `AFNetworking (2.2.1)`- `AFNetworking/Reachability` required by `AFNetworking (2.2.1)`- `AFNetworking/NSURLConnection` required by `AFNetworking (2.2.1)`- `AFNetworking/NSURLSession` required by `AFNetworking (2.2.1)`- `AFNetworking/UIKit` required by `AFNetworking (2.2.1)`- `AFNetworking/Serialization` required by `AFNetworking/NSURLConnection (2.2.1)`- `AFNetworking/Reachability` required by `AFNetworking/NSURLConnection (2.2.1)`- `AFNetworking/Security` required by `AFNetworking/NSURLConnection (2.2.1)`- `AFNetworking/NSURLConnection` required by `AFNetworking/NSURLSession (2.2.1)`- `AFNetworking/NSURLConnection` required by `AFNetworking/UIKit (2.2.1) _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev

True, eventually we will remove that dependency. What about getting 1.5 out of the way and then release AG Push registration 0.9.0 without AFNetworkin dependency?

++ Corinne On 18 Mar 2014, at 09:53, Matthias Wessendorf <matzew(a)apache.org&gt; wrote: > Corinne, > > no AFN on that project, in the future: > https://issues.jboss.org/browse/AGPUSH-558 > > > > > On Tue, Mar 18, 2014 at 9:51 AM, Corinne Krych <corinnekrych(a)gmail.com&gt; wrote: > Hello Sebi > > Actually PR are on their ways (as we test it) to set proper version, what you need here > https://github.com/aerogear/aerogear-push-ios-registration/blob/master/Po... > is to upgrade to: > platform :ios, '7.0' > pod 'AFNetworking', '2.2.1' > > Note that we'll support from ios 7.0 > Feel free to send the PR with Podfile update if the testing works for you. > > ++ > Thanks for the feedback, > Corinne > > On 18 Mar 2014, at 09:44, Sebastien Blanc <scm.blanc(a)gmail.com&gt; wrote: > > > FNetworking (= 2.2.1)` required by `AeroGear (1.5.0)`- `AFNetworking/Serialization` required by `AFNetworking (2.2.1)`- `AFNetworking/Security` required by `AFNetworking (2.2.1)`- `AFNetworking/Reachability` required by `AFNetworking (2.2.1)`- `AFNetworking/NSURLConnection` required by `AFNetworking (2.2.1)`- `AFNetworking/NSURLSession` required by `AFNetworking (2.2.1)`- `AFNetworking/UIKit` required by `AFNetworking (2.2.1)`- `AFNetworking/Serialization` required by `AFNetworking/NSURLConnection (2.2.1)`- `AFNetworking/Reachability` required by `AFNetworking/NSURLConnection (2.2.1)`- `AFNetworking/Security` required by `AFNetworking/NSURLConnection (2.2.1)`- `AFNetworking/NSURLConnection` required by `AFNetworking/NSURLSession (2.2.1)`- `AFNetworking/NSURLConnection` required by `AFNetworking/UIKit (2.2.1) > > > _______________________________________________ > 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 _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev

But until AG Push registration 0.9 is released , 0.8.1 do not work with AG iOS 1.5 , right ? (Sorry if I'm totally wrong :) ) Shouldn't it make sense to make a 0.8.2 release with an updated pod (what Corinne mentionned in the second message) to "fill the gap" until 0.9 is released ? On Tue, Mar 18, 2014 at 10:06 AM, Matthias Wessendorf <matzew(a)apache.org&gt; wrote: On Tue, Mar 18, 2014 at 10:05 AM, Corinne Krych <corinnekrych(a)gmail.com&gt; wrote: True, eventually we will remove that dependency. What about getting 1.5 out of the way and then release AG Push registration 0.9.0 without AFNetworkin dependency? sounds good to me! ++ Corinne On 18 Mar 2014, at 09:53, Matthias Wessendorf <matzew(a)apache.org&gt; wrote: > Corinne, > > no AFN on that project, in the future: > https://issues.jboss.org/browse/AGPUSH-558 > > > > > On Tue, Mar 18, 2014 at 9:51 AM, Corinne Krych <corinnekrych(a)gmail.com&gt; wrote: > Hello Sebi > > Actually PR are on their ways (as we test it) to set proper version, what you need here > https://github.com/aerogear/aerogear-push-ios-registration/blob/master/Po... > is to upgrade to: > platform :ios, ‘7.0' > pod 'AFNetworking', ‘2.2.1' > > Note that we’ll support from ios 7.0 > Feel free to send the PR with Podfile update if the testing works for you. > > ++ > Thanks for the feedback, > Corinne > > On 18 Mar 2014, at 09:44, Sebastien Blanc <scm.blanc(a)gmail.com&gt; wrote: > > > FNetworking (= 2.2.1)` required by `AeroGear (1.5.0)`- `AFNetworking/Serialization` required by `AFNetworking (2.2.1)`- `AFNetworking/Security` required by `AFNetworking (2.2.1)`- `AFNetworking/Reachability` required by `AFNetworking (2.2.1)`- `AFNetworking/NSURLConnection` required by `AFNetworking (2.2.1)`- `AFNetworking/NSURLSession` required by `AFNetworking (2.2.1)`- `AFNetworking/UIKit` required by `AFNetworking (2.2.1)`- `AFNetworking/Serialization` required by `AFNetworking/NSURLConnection (2.2.1)`- `AFNetworking/Reachability` required by `AFNetworking/NSURLConnection (2.2.1)`- `AFNetworking/Security` required by `AFNetworking/NSURLConnection (2.2.1)`- `AFNetworking/NSURLConnection` required by `AFNetworking/NSURLSession (2.2.1)`- `AFNetworking/NSURLConnection` required by `AFNetworking/UIKit (2.2.1) > > > _______________________________________________ > 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 _______________________________________________ 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 _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev

On Tue, Mar 18, 2014 at 10:56 AM, Corinne Krych <corinnekrych(a)gmail.com&gt; wrote: Yep indeed coordination is needed, let’s see how we progress on removing AFNetworking dep. When releasing 1.5 we’ll go either: 0.8.2 => with AFNetworking 2.2.1 sounds like an odd thing, due to item below or 0.9.0 => without AFNetworking dep +1 Keep you posted (very soon) on that. ++ Corinne On 18 Mar 2014, at 10:47, Sebastien Blanc <scm.blanc(a)gmail.com&gt; wrote: > But until AG Push registration 0.9 is released , 0.8.1 do not work with AG iOS 1.5 , right ? (Sorry if I'm totally wrong :) ) > Shouldn't it make sense to make a 0.8.2 release with an updated pod (what Corinne mentionned in the second message) to "fill the gap" until 0.9 is released ? > > > > On Tue, Mar 18, 2014 at 10:06 AM, Matthias Wessendorf <matzew(a)apache.org&gt; wrote: > > > > On Tue, Mar 18, 2014 at 10:05 AM, Corinne Krych <corinnekrych(a)gmail.com&gt; wrote: > True, eventually we will remove that dependency. > What about getting 1.5 out of the way and then release AG Push registration 0.9.0 without AFNetworkin dependency? > > > sounds good to me! > > > ++ > Corinne > On 18 Mar 2014, at 09:53, Matthias Wessendorf <matzew(a)apache.org&gt; wrote: > > > Corinne, > > > > no AFN on that project, in the future: > > https://issues.jboss.org/browse/AGPUSH-558 > > > > > > > > > > On Tue, Mar 18, 2014 at 9:51 AM, Corinne Krych <corinnekrych(a)gmail.com&gt; wrote: > > Hello Sebi > > > > Actually PR are on their ways (as we test it) to set proper version, what you need here > > https://github.com/aerogear/aerogear-push-ios-registration/blob/master/Po... > > is to upgrade to: > > platform :ios, ‘7.0' > > pod 'AFNetworking', ‘2.2.1' > > > > Note that we’ll support from ios 7.0 > > Feel free to send the PR with Podfile update if the testing works for you. > > > > ++ > > Thanks for the feedback, > > Corinne > > > > On 18 Mar 2014, at 09:44, Sebastien Blanc <scm.blanc(a)gmail.com&gt; wrote: > > > > > FNetworking (= 2.2.1)` required by `AeroGear (1.5.0)`- `AFNetworking/Serialization` required by `AFNetworking (2.2.1)`- `AFNetworking/Security` required by `AFNetworking (2.2.1)`- `AFNetworking/Reachability` required by `AFNetworking (2.2.1)`- `AFNetworking/NSURLConnection` required by `AFNetworking (2.2.1)`- `AFNetworking/NSURLSession` required by `AFNetworking (2.2.1)`- `AFNetworking/UIKit` required by `AFNetworking (2.2.1)`- `AFNetworking/Serialization` required by `AFNetworking/NSURLConnection (2.2.1)`- `AFNetworking/Reachability` required by `AFNetworking/NSURLConnection (2.2.1)`- `AFNetworking/Security` required by `AFNetworking/NSURLConnection (2.2.1)`- `AFNetworking/NSURLConnection` required by `AFNetworking/NSURLSession (2.2.1)`- `AFNetworking/NSURLConnection` required by `AFNetworking/UIKit (2.2.1) > > > > > > _______________________________________________ > > 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 > > > _______________________________________________ > 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 > > _______________________________________________ > 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 -- 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

So, how long will there be AG iOS 1.5 without any available support for AG Push Registration?

It would make sense to me to stage&test 1.5 now and then wait for AG Push Registration 0.9.0 to happen, stage&test. Then push both into the wild simultaneously. Karel On Tue, 18 Mar 2014 11:09:34 +0100 Corinne Krych <corinnekrych(a)gmail.com&gt; wrote: > +1 > Here's the plan. > Back to testing. > ++ > Corinne > On 18 Mar 2014, at 11:07, Matthias Wessendorf <matzew(a)apache.org&gt; wrote: > > > > > > > > > On Tue, Mar 18, 2014 at 10:56 AM, Corinne Krych < corinnekrych(a)gmail.com&gt; > > wrote: Yep indeed coordination is needed, let's see how we progress on > > removing AFNetworking dep. When releasing 1.5 we'll go either: > > 0.8.2 => with AFNetworking 2.2.1 > > > > sounds like an odd thing, due to item below > > > > > > or 0.9.0 => without AFNetworking dep > > > > +1 > > > > > > Keep you posted (very soon) on that. > > > > ++ > > Corinne > > On 18 Mar 2014, at 10:47, Sebastien Blanc <scm.blanc(a)gmail.com&gt; wrote: > > > > > But until AG Push registration 0.9 is released , 0.8.1 do not work with > > > AG iOS 1.5 , right ? (Sorry if I'm totally wrong :) ) Shouldn't it make > > > sense to make a 0.8.2 release with an updated pod (what Corinne > > > mentionned in the second message) to "fill the gap" until 0.9 is > > > released ? > > > > > > > > > > > > On Tue, Mar 18, 2014 at 10:06 AM, Matthias Wessendorf < matzew(a)apache.org&gt; > > > wrote: > > > > > > > > > > > > On Tue, Mar 18, 2014 at 10:05 AM, Corinne Krych < corinnekrych(a)gmail.com&gt; > > > wrote: True, eventually we will remove that dependency. > > > What about getting 1.5 out of the way and then release AG Push > > > registration 0.9.0 without AFNetworkin dependency? > > > > > > > > > sounds good to me! > > > > > > > > > ++ > > > Corinne > > > On 18 Mar 2014, at 09:53, Matthias Wessendorf <matzew(a)apache.org&gt; wrote: > > > > > > > Corinne, > > > > > > > > no AFN on that project, in the future: > > > > https://issues.jboss.org/browse/AGPUSH-558 > > > > > > > > > > > > > > > > > > > > On Tue, Mar 18, 2014 at 9:51 AM, Corinne Krych < corinnekrych(a)gmail.com&gt; > > > > wrote: Hello Sebi > > > > > > > > Actually PR are on their ways (as we test it) to set proper version, > > > > what you need here > > > > https://github.com/aerogear/aerogear-push-ios-registration/blob/master/Po... > > > > is to upgrade to: platform :ios, '7.0' > > > > pod 'AFNetworking', '2.2.1' > > > > > > > > Note that we'll support from ios 7.0 > > > > Feel free to send the PR with Podfile update if the testing works for > > > > you. > > > > > > > > ++ > > > > Thanks for the feedback, > > > > Corinne > > > > > > > > On 18 Mar 2014, at 09:44, Sebastien Blanc <scm.blanc(a)gmail.com&gt; wrote: > > > > > > > > > FNetworking (= 2.2.1)` required by `AeroGear (1.5.0)`- > > > > > `AFNetworking/Serialization` required by `AFNetworking (2.2.1)`- > > > > > `AFNetworking/Security` required by `AFNetworking (2.2.1)`- > > > > > `AFNetworking/Reachability` required by `AFNetworking (2.2.1)`- > > > > > `AFNetworking/NSURLConnection` required by `AFNetworking (2.2.1)`- > > > > > `AFNetworking/NSURLSession` required by `AFNetworking (2.2.1)`- > > > > > `AFNetworking/UIKit` required by `AFNetworking (2.2.1)`- > > > > > `AFNetworking/Serialization` required by > > > > > `AFNetworking/NSURLConnection (2.2.1)`- `AFNetworking/Reachability` > > > > > required by `AFNetworking/NSURLConnection (2.2.1)`- > > > > > `AFNetworking/Security` required by `AFNetworking/NSURLConnection > > > > > (2.2.1)`- `AFNetworking/NSURLConnection` required by > > > > > `AFNetworking/NSURLSession (2.2.1)`- `AFNetworking/NSURLConnection` > > > > > required by `AFNetworking/UIKit (2.2.1) > > > > > > > > > > > > _______________________________________________ > > > > 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 > > > > > > > > > _______________________________________________ > > > 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 > > > > > > _______________________________________________ > > > 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 > > > > > > > > -- > > 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 > > > _______________________________________________ > 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

On Thu, 20 Mar 2014 16:59:42 +0100 Matthias Wessendorf <matzew(a)apache.org&gt; wrote: > On Thu, Mar 20, 2014 at 4:55 PM, Karel Piwko <kpiwko(a)redhat.com&gt; wrote: > > > So, how long will there be AG iOS 1.5 without any available support for AG > > Push > > Registration? > > > > zero days > > http://cocoapods.org/?q=AeroGear > > 0.9.0 is already 'out' Sweet! I haven't expected that at all give the discussion above ;-)

> > > > > > It would make sense to me to stage&test 1.5 now and then wait for AG Push > > Registration 0.9.0 to happen, stage&test. Then push both into the wild > > simultaneously. > > > > Karel > > > > On Tue, 18 Mar 2014 11:09:34 +0100 > > Corinne Krych <corinnekrych(a)gmail.com&gt; wrote: > > > > > +1 > > > Here's the plan. > > > Back to testing. > > > ++ > > > Corinne > > > On 18 Mar 2014, at 11:07, Matthias Wessendorf <matzew(a)apache.org&gt; wrote: > > > > > > > > > > > > > > > > > > > On Tue, Mar 18, 2014 at 10:56 AM, Corinne Krych < > > corinnekrych(a)gmail.com&gt; > > > > wrote: Yep indeed coordination is needed, let's see how we progress on > > > > removing AFNetworking dep. When releasing 1.5 we'll go either: > > > > 0.8.2 => with AFNetworking 2.2.1 > > > > > > > > sounds like an odd thing, due to item below > > > > > > > > > > > > or 0.9.0 => without AFNetworking dep > > > > > > > > +1 > > > > > > > > > > > > Keep you posted (very soon) on that. > > > > > > > > ++ > > > > Corinne > > > > On 18 Mar 2014, at 10:47, Sebastien Blanc <scm.blanc(a)gmail.com&gt; wrote: > > > > > > > > > But until AG Push registration 0.9 is released , 0.8.1 do not work > > with > > > > > AG iOS 1.5 , right ? (Sorry if I'm totally wrong :) ) Shouldn't it > > make > > > > > sense to make a 0.8.2 release with an updated pod (what Corinne > > > > > mentionned in the second message) to "fill the gap" until 0.9 is > > > > > released ? > > > > > > > > > > > > > > > > > > > > On Tue, Mar 18, 2014 at 10:06 AM, Matthias Wessendorf < > > matzew(a)apache.org&gt; > > > > > wrote: > > > > > > > > > > > > > > > > > > > > On Tue, Mar 18, 2014 at 10:05 AM, Corinne Krych < > > corinnekrych(a)gmail.com&gt; > > > > > wrote: True, eventually we will remove that dependency. > > > > > What about getting 1.5 out of the way and then release AG Push > > > > > registration 0.9.0 without AFNetworkin dependency? > > > > > > > > > > > > > > > sounds good to me! > > > > > > > > > > > > > > > ++ > > > > > Corinne > > > > > On 18 Mar 2014, at 09:53, Matthias Wessendorf <matzew(a)apache.org > > > wrote: > > > > > > > > > > > Corinne, > > > > > > > > > > > > no AFN on that project, in the future: > > > > > > https://issues.jboss.org/browse/AGPUSH-558 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Tue, Mar 18, 2014 at 9:51 AM, Corinne Krych < > > corinnekrych(a)gmail.com&gt; > > > > > > wrote: Hello Sebi > > > > > > > > > > > > Actually PR are on their ways (as we test it) to set proper > > version, > > > > > > what you need here > > > > > > > > https://github.com/aerogear/aerogear-push-ios-registration/blob/master/Po... > > > > > > is to upgrade to: platform :ios, '7.0' > > > > > > pod 'AFNetworking', '2.2.1' > > > > > > > > > > > > Note that we'll support from ios 7.0 > > > > > > Feel free to send the PR with Podfile update if the testing works > > for > > > > > > you. > > > > > > > > > > > > ++ > > > > > > Thanks for the feedback, > > > > > > Corinne > > > > > > > > > > > > On 18 Mar 2014, at 09:44, Sebastien Blanc <scm.blanc(a)gmail.com > > > wrote: > > > > > > > > > > > > > FNetworking (= 2.2.1)` required by `AeroGear (1.5.0)`- > > > > > > > `AFNetworking/Serialization` required by `AFNetworking (2.2.1)`- > > > > > > > `AFNetworking/Security` required by `AFNetworking (2.2.1)`- > > > > > > > `AFNetworking/Reachability` required by `AFNetworking (2.2.1)`- > > > > > > > `AFNetworking/NSURLConnection` required by `AFNetworking > > (2.2.1)`- > > > > > > > `AFNetworking/NSURLSession` required by `AFNetworking (2.2.1)`- > > > > > > > `AFNetworking/UIKit` required by `AFNetworking (2.2.1)`- > > > > > > > `AFNetworking/Serialization` required by > > > > > > > `AFNetworking/NSURLConnection (2.2.1)`- > > `AFNetworking/Reachability` > > > > > > > required by `AFNetworking/NSURLConnection (2.2.1)`- > > > > > > > `AFNetworking/Security` required by `AFNetworking/NSURLConnection > > > > > > > (2.2.1)`- `AFNetworking/NSURLConnection` required by > > > > > > > `AFNetworking/NSURLSession (2.2.1)`- > > `AFNetworking/NSURLConnection` > > > > > > > required by `AFNetworking/UIKit (2.2.1) > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > 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 > > > > > > > > > > > > > > > _______________________________________________ > > > > > 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 > > > > > > > > > > _______________________________________________ > > > > > 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 > > > > > > > > > > > > > > > > -- > > > > 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 > > > > > > > > > _______________________________________________ > > > 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

Hi, I tried to upgrade my local aerodoc-ios with the new pod : First thing I noticed was that I had to upgrade my cocoapods to 0.29 then my updated pod file : xcodeproj 'AeroDoc.xcodeproj' platform :ios, '7.1' pod 'AeroGear', :git => 'https://github.com/aerogear/aerogear-ios.git' pod 'AeroGear-Push', '0.8.0' And then after typing "pod install" I'm getting : [!] Unable to satisfy the following requirements: - `AFNetworking (= 2.2.1)` required by `AeroGear (1.5.0)`- `AFNetworking/Serialization` required by `AFNetworking (2.2.1)`- `AFNetworking/Security` required by `AFNetworking (2.2.1)`- `AFNetworking/Reachability` required by `AFNetworking (2.2.1)`- `AFNetworking/NSURLConnection` required by `AFNetworking (2.2.1)`- `AFNetworking/NSURLSession` required by `AFNetworking (2.2.1)`- `AFNetworking/UIKit` required by `AFNetworking (2.2.1)`- `AFNetworking/Serialization` required by `AFNetworking/NSURLConnection (2.2.1)`- `AFNetworking/Reachability` required by `AFNetworking/NSURLConnection (2.2.1)`- `AFNetworking/Security` required by `AFNetworking/NSURLConnection (2.2.1)`- `AFNetworking/NSURLConnection` required by `AFNetworking/NSURLSession (2.2.1)`- `AFNetworking/NSURLConnection` required by `AFNetworking/UIKit (2.2.1)`- `AFNetworking/NSURLSession` required by `AFNetworking/UIKit (2.2.1)`- `AFNetworking (= 1.3.1)` required by `AeroGear-Push (0.8.0)` I'm probably missing sometinh obvious :) , any ideas ? Do I need to explicitly add AFNetworking in my pod ?

Seb On Tue, Mar 18, 2014 at 8:37 AM, Corinne Krych <corinnekrych(a)gmail.com&gt;wrote: > Hello iOS Friends, > > AeroGear iOS 1.5 is on his way. We plan (if no objections raised) to > release it end of this week. Main focus of 1.5 is to upgrade to iOS7 and > AFNetworking 2.x (latest 2.2.1). > > To test it, open Podfile and point to the latest git branch > pod 'AeroGear', :git => 'https://github.com/aerogear/aerogear-ios.git' > > Help us make this release a success, give it a trial, and let us know how > it goes for your project. > > ++ > Corinne > _______________________________________________ > 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

Hi everyone, after discussion with Corinne, we have decided to pause the release of aerogear-ios this week, and release early next. The reason is that we would like the upcoming release to include dependency of the new aerogear-crypto changes that were incorporated this week[1], mainly the update of the symmetric encryption to use NaCI. We feel, that it makes sense to release both at the same time. For aerogear-ios, a minor 'private' API change is needed, but would like a bit of time for testing. Let us know your thoughts/concerns. Regards Christos [1] https://github.com/aerogear/aerogear-crypto-ios/pull/18 On Mar 18, 2014, at 9:37 AM, Corinne Krych <corinnekrych(a)gmail.com&gt; wrote: > Hello iOS Friends, > > AeroGear iOS 1.5 is on his way. We plan (if no objections raised) to release it end of this week. Main focus of 1.5 is to upgrade to iOS7 and AFNetworking 2.x (latest 2.2.1). > > To test it, open Podfile and point to the latest git branch > pod 'AeroGear', :git => 'https://github.com/aerogear/aerogear-ios.git' > > Help us make this release a success, give it a trial, and let us know how it goes for your project. > > ++ > Corinne > _______________________________________________ > 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

Hi everyone, after discussion with Corinne, we have decided to pause the release of aerogear-ios this week, and release early next. The reason is that we would like the upcoming release to include dependency of the new aerogear-crypto changes that were incorporated this week[1], mainly the update of the symmetric encryption to use NaCI. We feel, that it makes sense to release both at the same time. For aerogear-ios, a minor 'private' API change is needed, but would like a bit of time for testing. Let us know your thoughts/concerns. Regards Christos [1] https://github.com/aerogear/aerogear-crypto-ios/pull/18 On Mar 18, 2014, at 9:37 AM, Corinne Krych <corinnekrych(a)gmail.com&gt; wrote: > Hello iOS Friends, > > AeroGear iOS 1.5 is on his way. We plan (if no objections raised) to release it end of this week. Main focus of 1.5 is to upgrade to iOS7 and AFNetworking 2.x (latest 2.2.1). > > To test it, open Podfile and point to the latest git branch > pod 'AeroGear', :git => 'https://github.com/aerogear/aerogear-ios.git' > > Help us make this release a success, give it a trial, and let us know how it goes for your project. > > ++ > Corinne > _______________________________________________ > 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

Hey, I’m done with testing the new crypto. The only thing that I’ve already discussed with cvasilak is that if anyone updates to the new crypto and already had some data stored with the old one, it will crash when trying to read them. Other than that everything works.

— Tadeas Kriz On 21 Mar 2014, at 12:43, Christos Vasilakis <cvasilak(a)gmail.com&gt; wrote: > Hi everyone, > > after discussion with Corinne, we have decided to pause the release of aerogear-ios this week, and release early next. The reason is that we would like the upcoming release to include dependency of the new aerogear-crypto changes that were incorporated this week[1], mainly the update of the symmetric encryption to use NaCI. We feel, that it makes sense to release both at the same time. > > For aerogear-ios, a minor ‘private' API change is needed, but would like a bit of time for testing. > > Let us know your thoughts/concerns. > > Regards > Christos > > [1] https://github.com/aerogear/aerogear-crypto-ios/pull/18 > > > On Mar 18, 2014, at 9:37 AM, Corinne Krych <corinnekrych(a)gmail.com&gt; wrote: > >> Hello iOS Friends, >> >> AeroGear iOS 1.5 is on his way. We plan (if no objections raised) to release it end of this week. Main focus of 1.5 is to upgrade to iOS7 and AFNetworking 2.x (latest 2.2.1). >> >> To test it, open Podfile and point to the latest git branch >> pod 'AeroGear', :git => 'https://github.com/aerogear/aerogear-ios.git' >> >> Help us make this release a success, give it a trial, and let us know how it goes for your project. >> >> ++ >> Corinne >> _______________________________________________ >> 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

On Mon, Mar 24, 2014 at 6:47 PM, Christos Vasilakis <cvasilak(a)gmail.com&gt; wrote: On Mar 24, 2014, at 6:24 PM, Tadeas Kriz <tkriz(a)redhat.com&gt; wrote: > Hey, > > I’m done with testing the new crypto. The only thing that I’ve already discussed with cvasilak is that if anyone updates to the new crypto and already had some data stored with the old one, it will crash when trying to read them. Other than that everything works. For the record, unfortunately due to change of symmetic crypto to use NaCl and moving away from common crypto, old encrypted data will fail to be read with the new version. But we believe relying on NaCI for both symm/asymm encryption is the way to move forward and the main motivation for pausing this release of agios to incorporate latest crypto. As sooner we switch, the better. +9001 :-) For any user that will be affected by this, a possible dump of the old data using ‘read:all’, and reload on the new version can be an option. This downside will be documented on our release notes. yeah - I do not think it's a serious problem. This library is pretty young, and under active development. +1 on documentation/release notes for the issue. And yeah, as you said: better sooner than later to switch :-) Great job and thanks for the update! -Matthias Regards, Christos > > — > Tadeas Kriz > > On 21 Mar 2014, at 12:43, Christos Vasilakis <cvasilak(a)gmail.com&gt; wrote: > >> Hi everyone, >> >> after discussion with Corinne, we have decided to pause the release of aerogear-ios this week, and release early next. The reason is that we would like the upcoming release to include dependency of the new aerogear-crypto changes that were incorporated this week[1], mainly the update of the symmetric encryption to use NaCI. We feel, that it makes sense to release both at the same time. >> >> For aerogear-ios, a minor ‘private' API change is needed, but would like a bit of time for testing. >> >> Let us know your thoughts/concerns. >> >> Regards >> Christos >> >> [1] https://github.com/aerogear/aerogear-crypto-ios/pull/18 >> >> >> On Mar 18, 2014, at 9:37 AM, Corinne Krych <corinnekrych(a)gmail.com&gt; wrote: >> >>> Hello iOS Friends, >>> >>> AeroGear iOS 1.5 is on his way. We plan (if no objections raised) to release it end of this week. Main focus of 1.5 is to upgrade to iOS7 and AFNetworking 2.x (latest 2.2.1). >>> >>> To test it, open Podfile and point to the latest git branch >>> pod 'AeroGear', :git => 'https://github.com/aerogear/aerogear-ios.git' >>> >>> Help us make this release a success, give it a trial, and let us know how it goes for your project. >>> >>> ++ >>> Corinne >>> _______________________________________________ >>> 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 _______________________________________________ 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

Hi everyone, fyi, as of yesterday update[1], agios lib now uses latest crypto and you can give it a spin, try with our with crypto-ios-demo[2] or our cookbook examples[3] (the cookbook exercises both the afnet upgrade of the library and latest crypto). If there are no issues found, plan is to merge and release new aerogear-ios v1.5 early next week that will incorporate these changes. Thanks, Christos [1] https://github.com/aerogear/aerogear-ios/pull/123 [2] https://github.com/cvasilak/aerogear-crypto-ios-demo/tree/AGIOS-181 [3] https://github.com/cvasilak/aerogear-ios-cookbook/tree/AGIOS-181 _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev