cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michal Mocny <mmo...@chromium.org>
Subject Re: [ios] plugin os version support
Date Wed, 30 Apr 2014 23:38:03 GMT
Why do we need to do that?

If the cordova-ios template support iOS 6+, don't we only need to update
the cordova engine requirements?  If you are using an older cordova-ios
platform (that still supported iOS5), then would you be using a CLI that
understood apple-ios engine tag?

-Michal


On Wed, Apr 30, 2014 at 4:54 PM, Shazron <shazron@gmail.com> wrote:

> I agree of course, now comes the part where we add the "apple-ios" key into
> the engines tag for all plugins. We can add 6.0 for everything or actually
> test whether it actually needs 6.0 (more work, requires testing with an
> older Cordova version, and Xcode version that has the iOS 5 SDK....)
>
>
> On Wed, Apr 30, 2014 at 1:47 PM, Michal Mocny <mmocny@chromium.org> wrote:
>
> > https://developer.apple.com/support/appstore/
> >
> > iOS <6 = 2%.  That meets the criteria we've used in the past..
> >
> >
> > On Wed, Apr 30, 2014 at 4:13 PM, Shazron <shazron@gmail.com> wrote:
> >
> > > With 3.4.0, the default template only supports iOS 6.0 and up. I know
> > that
> > > plugins can specify iOS support (apple-ios key in engines tag) but we
> > > haven't done it yet. I'm not even sure if the cli plugin installer
> checks
> > > for this yet.
> > >
> > > Should we start using this in core plugins?
> > >
> > > A specific case is this PR:
> > > https://github.com/apache/cordova-plugin-camera/pull/24
> > > It is using [ALAssetsLibrary authorizationStatus] and that API only
> > occurs
> > > in iOS 6.0 and up.
> > >
> > > Wrapping this in a runtime os version check is not hard, however
> > > (IsAtLeastVersion macro).
> > >
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message