You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cordova.apache.org by Nikhil Khandelwal <ni...@microsoft.com> on 2015/09/30 02:08:02 UTC

cordova-plugin-whitelist ios issue

1.       cordova create test

2.       cordova platform add ios

WARNING: Applications for platform ios can not be built on this OS - win32.
Adding ios project...
iOS project created with cordova-ios@3.9.1
Discovered plugin "cordova-plugin-whitelist" in config.xml. Installing to the project
Fetching plugin "cordova-plugin-whitelist@1" via npm
Installing "cordova-plugin-whitelist" for ios
Plugin doesn't support this project's cordova-ios version. cordova-ios: 3.9.1, failed version requirement: >=4.0.0-dev
Skipping 'cordova-plugin-whitelist' for ios
Installing "cordova-plugin-whitelist" for ios
Plugin doesn't support this project's cordova-ios version. cordova-ios: 3.9.1, failed version requirement: >=4.0.0-dev
Skipping 'cordova-plugin-whitelist' for ios

Looks like we have a rogue version of cordova-plugin-whitelist published that requires iOS 4.0.0. What's the best way to fix it? Can we unpublish this whitelist plugin version from npm to fix this? Alternatively, we should release another version of the plugin that does not get this warning. It's misleading and confusing for developers to see this warning.

Thanks,
Nikhil

Re: cordova-plugin-whitelist ios issue

Posted by Shazron <sh...@gmail.com>.
If you have cordova-ios and android 3.x you do not need
cordova-plugin-whitelist *at all*. It is only for cordova-ios and
android 4.x. The 3.x series have built in whitelists.

On Tue, Sep 29, 2015 at 5:17 PM, Shazron <sh...@gmail.com> wrote:
> No its not a "rogue version". cordova-plugin-whitelist requires
> cordova-ios 4.0 and cordova-android 4.0.
> It's just a warning and is expected to work this way.
> https://github.com/apache/cordova-plugin-whitelist/blob/master/README.md
>
> On Tue, Sep 29, 2015 at 5:08 PM, Nikhil Khandelwal
> <ni...@microsoft.com> wrote:
>> 1.       cordova create test
>>
>> 2.       cordova platform add ios
>>
>> WARNING: Applications for platform ios can not be built on this OS - win32.
>> Adding ios project...
>> iOS project created with cordova-ios@3.9.1
>> Discovered plugin "cordova-plugin-whitelist" in config.xml. Installing to the project
>> Fetching plugin "cordova-plugin-whitelist@1" via npm
>> Installing "cordova-plugin-whitelist" for ios
>> Plugin doesn't support this project's cordova-ios version. cordova-ios: 3.9.1, failed version requirement: >=4.0.0-dev
>> Skipping 'cordova-plugin-whitelist' for ios
>> Installing "cordova-plugin-whitelist" for ios
>> Plugin doesn't support this project's cordova-ios version. cordova-ios: 3.9.1, failed version requirement: >=4.0.0-dev
>> Skipping 'cordova-plugin-whitelist' for ios
>>
>> Looks like we have a rogue version of cordova-plugin-whitelist published that requires iOS 4.0.0. What's the best way to fix it? Can we unpublish this whitelist plugin version from npm to fix this? Alternatively, we should release another version of the plugin that does not get this warning. It's misleading and confusing for developers to see this warning.
>>
>> Thanks,
>> Nikhil

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
For additional commands, e-mail: dev-help@cordova.apache.org

Re: cordova-plugin-whitelist ios issue

Posted by Carlos Santana <cs...@gmail.com>.
I'm available after 4PM EST today, coordinate in the #pmc or #plugins
channel?


On Wed, Sep 30, 2015 at 2:17 PM Carlos Santana <cs...@gmail.com> wrote:

> oh, having no network access by default I 100% agree, we already discuss
> this to death. Apps can be created that work offline with no network
> access, that should be the baseline, from there then people can do a
> whitelist to allow different type of access (i.e. navigation, access, etc..)
>
> On Wed, Sep 30, 2015 at 1:50 PM Nikhil Khandelwal <ni...@microsoft.com>
> wrote:
>
>> I'm up for a hangout on this subject. I do think e-mail is making it hard
>> to communicate this. I am with Carlos - we should not have warnings that
>> cannot be resolved for unreleased platform versions. This is particularly,
>> a problem for a new web developer to Cordova who does not understand the
>> history of whitelist and the user of it and is confronted with it upfront.
>> There is not the first time this feedback has been voiced. [1][2]
>>
>> Carlos does raise some other important concerns. I've heard a lot of
>> confusion from Cordova devs on whitelist changes. This is especially
>> painful for Android 4.0 which has no network access without whitelist. I
>> think we are making better defaults (of having network access)  with
>> Cordova IOS 4.0. Perhaps we should change the behavior for Android with
>> Android 5.0.
>>
>> -Nikhil
>>
>> [1]
>> https://github.com/apache/cordova-plugin-whitelist/commit/72a067c96e4e54efb8f1f152220d4a5fdf404324#commitcomment-11624636
>> [2] http://callback.markmail.org/thread/w2pjyndljbdng23f
>>
>> -----Original Message-----
>> From: Carlos Santana [mailto:csantana23@gmail.com]
>> Sent: Wednesday, September 30, 2015 9:03 AM
>> To: dev@cordova.apache.org
>> Subject: Re: cordova-plugin-whitelist ios issue
>>
>> People are already getting surprised today that their apps do not connect
>> to any network when they create an app that contains cordova-android@4.x
>> because the whitelist plugin is not included by default.
>> Why whitelist is not included by default?
>> - the don't use the cordova-cli, the use cordova-android/bin/create (shell
>> mode)
>> - because they use their own templates, for example I created an app with
>> my own template that has my config.xml that doesn't have whitelist plugin
>> because I created the template in the cordova-android@3.x time frame.
>> - people creating apps with other CLIs, for example ionic cli, whitelist
>> plugin is not one of the default plugins added with their ionic templates,
>> etc..
>>
>>
>> On Wed, Sep 30, 2015 at 11:48 AM Carlos Santana <cs...@gmail.com>
>> wrote:
>>
>> > So this mean I can add this engine tag today to the whitelist plugin
>> > with some code specific to firefoxos?
>> >  <engine name="cordova-firefoxos" version=">=4.0.0-dev" />
>> >
>> > I know cordova-firefoxos@4.0.0-dev or ordova-firefoxos@4.0.0 is not on
>> > npm but is very useful to give users the warning now.
>> > This will avoid the user from upgrading the plugin ever in the future
>> > when
>> > cordova-firefoxos@4.0.0 is published to npm, I might get c
>> > ordova-firefoxos@4.0.0 around december or longer  so I don't think it
>> > will be a problem for them to see the warning until then.
>> >
>> > If everyone is OK I will put this code today? this will avoid user
>> > from having to upgrade the plugin in the future :-p
>> >
>> > This is the point I want to make, and guess email communication is not
>> > being our friend to express my point of view.
>> > Will those interested on this topic up for a quick Hangout? Simon,
>> > Shaz, Nikhil
>> >
>> >
>> > On Wed, Sep 30, 2015 at 10:55 AM Simon MacDonald <
>> > simon.macdonald@gmail.com> wrote:
>> >
>> >> -1 to this proposal IMHO
>> >>
>> >> Warnings are useful. If someone sees this and is confused as to why
>> >> there is a new whitelist plugin then looks into it some more detail
>> >> that will be beneficial. I think the warning should be more explicit.
>> >> Put an info tag into the plugin.xml for the whitelist linking to the
>> >> docs and what the upcoming change is in cordova-ios 4.0.0. That way
>> people will be "less"
>> >> surprised that they need to install this plugin in the future.
>> >>
>> >>
>> >>
>> >> Simon Mac Donald
>> >> https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fhi.im
>> >> %2fsimonmacdonald&data=01%7c01%7cnikhilkh%40microsoft.com%7caa884ed39
>> >> 282462add6208d2c9b0f4ab%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=
>> >> NW%2bD7WmSnLFc9L9nYI6Q%2fabIiY6GjTci8x49Tsve%2biw%3d
>> >>
>> >> On Tue, Sep 29, 2015 at 11:35 PM, Tommy Williams <to...@devgeeks.org>
>> >> wrote:
>> >>
>> >> > This.
>> >> >
>> >> > +1
>> >> >
>> >> >
>> >> > On 30 September 2015 at 12:31:29, Carlos Santana
>> >> > (csantana23@gmail.com)
>> >> > wrote:
>> >> >
>> >> > In summary I proposed that we update the plugin with a version that
>> >> > only contains the android code.
>> >> > When we publish cordova-ios@4.0.0 then we publish a new version
>> >> > that contains the ios code and contains engine tag stating that it
>> >> > needs minimum
>> >> > cordova-ios@4.0.0
>> >> >
>> >> > I'm OK if you want to have two branches to make it clear to devs,
>> >> > 1.x it contains android only, branch 2.x contains both android and
>> ios.
>> >> >
>> >>
>> >
>>
>

Re: cordova-plugin-whitelist ios issue

Posted by Carlos Santana <cs...@gmail.com>.
oh, having no network access by default I 100% agree, we already discuss
this to death. Apps can be created that work offline with no network
access, that should be the baseline, from there then people can do a
whitelist to allow different type of access (i.e. navigation, access, etc..)

On Wed, Sep 30, 2015 at 1:50 PM Nikhil Khandelwal <ni...@microsoft.com>
wrote:

> I'm up for a hangout on this subject. I do think e-mail is making it hard
> to communicate this. I am with Carlos - we should not have warnings that
> cannot be resolved for unreleased platform versions. This is particularly,
> a problem for a new web developer to Cordova who does not understand the
> history of whitelist and the user of it and is confronted with it upfront.
> There is not the first time this feedback has been voiced. [1][2]
>
> Carlos does raise some other important concerns. I've heard a lot of
> confusion from Cordova devs on whitelist changes. This is especially
> painful for Android 4.0 which has no network access without whitelist. I
> think we are making better defaults (of having network access)  with
> Cordova IOS 4.0. Perhaps we should change the behavior for Android with
> Android 5.0.
>
> -Nikhil
>
> [1]
> https://github.com/apache/cordova-plugin-whitelist/commit/72a067c96e4e54efb8f1f152220d4a5fdf404324#commitcomment-11624636
> [2] http://callback.markmail.org/thread/w2pjyndljbdng23f
>
> -----Original Message-----
> From: Carlos Santana [mailto:csantana23@gmail.com]
> Sent: Wednesday, September 30, 2015 9:03 AM
> To: dev@cordova.apache.org
> Subject: Re: cordova-plugin-whitelist ios issue
>
> People are already getting surprised today that their apps do not connect
> to any network when they create an app that contains cordova-android@4.x
> because the whitelist plugin is not included by default.
> Why whitelist is not included by default?
> - the don't use the cordova-cli, the use cordova-android/bin/create (shell
> mode)
> - because they use their own templates, for example I created an app with
> my own template that has my config.xml that doesn't have whitelist plugin
> because I created the template in the cordova-android@3.x time frame.
> - people creating apps with other CLIs, for example ionic cli, whitelist
> plugin is not one of the default plugins added with their ionic templates,
> etc..
>
>
> On Wed, Sep 30, 2015 at 11:48 AM Carlos Santana <cs...@gmail.com>
> wrote:
>
> > So this mean I can add this engine tag today to the whitelist plugin
> > with some code specific to firefoxos?
> >  <engine name="cordova-firefoxos" version=">=4.0.0-dev" />
> >
> > I know cordova-firefoxos@4.0.0-dev or ordova-firefoxos@4.0.0 is not on
> > npm but is very useful to give users the warning now.
> > This will avoid the user from upgrading the plugin ever in the future
> > when
> > cordova-firefoxos@4.0.0 is published to npm, I might get c
> > ordova-firefoxos@4.0.0 around december or longer  so I don't think it
> > will be a problem for them to see the warning until then.
> >
> > If everyone is OK I will put this code today? this will avoid user
> > from having to upgrade the plugin in the future :-p
> >
> > This is the point I want to make, and guess email communication is not
> > being our friend to express my point of view.
> > Will those interested on this topic up for a quick Hangout? Simon,
> > Shaz, Nikhil
> >
> >
> > On Wed, Sep 30, 2015 at 10:55 AM Simon MacDonald <
> > simon.macdonald@gmail.com> wrote:
> >
> >> -1 to this proposal IMHO
> >>
> >> Warnings are useful. If someone sees this and is confused as to why
> >> there is a new whitelist plugin then looks into it some more detail
> >> that will be beneficial. I think the warning should be more explicit.
> >> Put an info tag into the plugin.xml for the whitelist linking to the
> >> docs and what the upcoming change is in cordova-ios 4.0.0. That way
> people will be "less"
> >> surprised that they need to install this plugin in the future.
> >>
> >>
> >>
> >> Simon Mac Donald
> >> https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fhi.im
> >> %2fsimonmacdonald&data=01%7c01%7cnikhilkh%40microsoft.com%7caa884ed39
> >> 282462add6208d2c9b0f4ab%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=
> >> NW%2bD7WmSnLFc9L9nYI6Q%2fabIiY6GjTci8x49Tsve%2biw%3d
> >>
> >> On Tue, Sep 29, 2015 at 11:35 PM, Tommy Williams <to...@devgeeks.org>
> >> wrote:
> >>
> >> > This.
> >> >
> >> > +1
> >> >
> >> >
> >> > On 30 September 2015 at 12:31:29, Carlos Santana
> >> > (csantana23@gmail.com)
> >> > wrote:
> >> >
> >> > In summary I proposed that we update the plugin with a version that
> >> > only contains the android code.
> >> > When we publish cordova-ios@4.0.0 then we publish a new version
> >> > that contains the ios code and contains engine tag stating that it
> >> > needs minimum
> >> > cordova-ios@4.0.0
> >> >
> >> > I'm OK if you want to have two branches to make it clear to devs,
> >> > 1.x it contains android only, branch 2.x contains both android and
> ios.
> >> >
> >>
> >
>

RE: cordova-plugin-whitelist ios issue

Posted by Nikhil Khandelwal <ni...@microsoft.com>.
I'm up for a hangout on this subject. I do think e-mail is making it hard to communicate this. I am with Carlos - we should not have warnings that cannot be resolved for unreleased platform versions. This is particularly, a problem for a new web developer to Cordova who does not understand the history of whitelist and the user of it and is confronted with it upfront. There is not the first time this feedback has been voiced. [1][2]

Carlos does raise some other important concerns. I've heard a lot of confusion from Cordova devs on whitelist changes. This is especially painful for Android 4.0 which has no network access without whitelist. I think we are making better defaults (of having network access)  with Cordova IOS 4.0. Perhaps we should change the behavior for Android with Android 5.0.

-Nikhil

[1] https://github.com/apache/cordova-plugin-whitelist/commit/72a067c96e4e54efb8f1f152220d4a5fdf404324#commitcomment-11624636
[2] http://callback.markmail.org/thread/w2pjyndljbdng23f

-----Original Message-----
From: Carlos Santana [mailto:csantana23@gmail.com] 
Sent: Wednesday, September 30, 2015 9:03 AM
To: dev@cordova.apache.org
Subject: Re: cordova-plugin-whitelist ios issue

People are already getting surprised today that their apps do not connect to any network when they create an app that contains cordova-android@4.x because the whitelist plugin is not included by default.
Why whitelist is not included by default?
- the don't use the cordova-cli, the use cordova-android/bin/create (shell
mode)
- because they use their own templates, for example I created an app with my own template that has my config.xml that doesn't have whitelist plugin because I created the template in the cordova-android@3.x time frame.
- people creating apps with other CLIs, for example ionic cli, whitelist plugin is not one of the default plugins added with their ionic templates, etc..


On Wed, Sep 30, 2015 at 11:48 AM Carlos Santana <cs...@gmail.com>
wrote:

> So this mean I can add this engine tag today to the whitelist plugin 
> with some code specific to firefoxos?
>  <engine name="cordova-firefoxos" version=">=4.0.0-dev" />
>
> I know cordova-firefoxos@4.0.0-dev or ordova-firefoxos@4.0.0 is not on 
> npm but is very useful to give users the warning now.
> This will avoid the user from upgrading the plugin ever in the future 
> when
> cordova-firefoxos@4.0.0 is published to npm, I might get c
> ordova-firefoxos@4.0.0 around december or longer  so I don't think it 
> will be a problem for them to see the warning until then.
>
> If everyone is OK I will put this code today? this will avoid user 
> from having to upgrade the plugin in the future :-p
>
> This is the point I want to make, and guess email communication is not 
> being our friend to express my point of view.
> Will those interested on this topic up for a quick Hangout? Simon, 
> Shaz, Nikhil
>
>
> On Wed, Sep 30, 2015 at 10:55 AM Simon MacDonald < 
> simon.macdonald@gmail.com> wrote:
>
>> -1 to this proposal IMHO
>>
>> Warnings are useful. If someone sees this and is confused as to why 
>> there is a new whitelist plugin then looks into it some more detail 
>> that will be beneficial. I think the warning should be more explicit. 
>> Put an info tag into the plugin.xml for the whitelist linking to the 
>> docs and what the upcoming change is in cordova-ios 4.0.0. That way people will be "less"
>> surprised that they need to install this plugin in the future.
>>
>>
>>
>> Simon Mac Donald
>> https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fhi.im
>> %2fsimonmacdonald&data=01%7c01%7cnikhilkh%40microsoft.com%7caa884ed39
>> 282462add6208d2c9b0f4ab%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=
>> NW%2bD7WmSnLFc9L9nYI6Q%2fabIiY6GjTci8x49Tsve%2biw%3d
>>
>> On Tue, Sep 29, 2015 at 11:35 PM, Tommy Williams <to...@devgeeks.org>
>> wrote:
>>
>> > This.
>> >
>> > +1
>> >
>> >
>> > On 30 September 2015 at 12:31:29, Carlos Santana 
>> > (csantana23@gmail.com)
>> > wrote:
>> >
>> > In summary I proposed that we update the plugin with a version that 
>> > only contains the android code.
>> > When we publish cordova-ios@4.0.0 then we publish a new version 
>> > that contains the ios code and contains engine tag stating that it 
>> > needs minimum
>> > cordova-ios@4.0.0
>> >
>> > I'm OK if you want to have two branches to make it clear to devs, 
>> > 1.x it contains android only, branch 2.x contains both android and ios.
>> >
>>
>

Re: cordova-plugin-whitelist ios issue

Posted by Carlos Santana <cs...@gmail.com>.
People are already getting surprised today that their apps do not connect
to any network when they create an app that contains cordova-android@4.x
because the whitelist plugin is not included by default.
Why whitelist is not included by default?
- the don't use the cordova-cli, the use cordova-android/bin/create (shell
mode)
- because they use their own templates, for example I created an app with
my own template that has my config.xml that doesn't have whitelist plugin
because I created the template in the cordova-android@3.x time frame.
- people creating apps with other CLIs, for example ionic cli, whitelist
plugin is not one of the default plugins added with their ionic templates,
etc..


On Wed, Sep 30, 2015 at 11:48 AM Carlos Santana <cs...@gmail.com>
wrote:

> So this mean I can add this engine tag today to the whitelist plugin with
> some code specific to firefoxos?
>  <engine name="cordova-firefoxos" version=">=4.0.0-dev" />
>
> I know cordova-firefoxos@4.0.0-dev or ordova-firefoxos@4.0.0 is not on
> npm but is very useful to give users the warning now.
> This will avoid the user from upgrading the plugin ever in the future when
> cordova-firefoxos@4.0.0 is published to npm, I might get c
> ordova-firefoxos@4.0.0 around december or longer  so I don't think it
> will be a problem for them to see the warning until then.
>
> If everyone is OK I will put this code today? this will avoid user from
> having to upgrade the plugin in the future :-p
>
> This is the point I want to make, and guess email communication is not
> being our friend to express my point of view.
> Will those interested on this topic up for a quick Hangout? Simon, Shaz,
> Nikhil
>
>
> On Wed, Sep 30, 2015 at 10:55 AM Simon MacDonald <
> simon.macdonald@gmail.com> wrote:
>
>> -1 to this proposal IMHO
>>
>> Warnings are useful. If someone sees this and is confused as to why there
>> is a new whitelist plugin then looks into it some more detail that will be
>> beneficial. I think the warning should be more explicit. Put an info tag
>> into the plugin.xml for the whitelist linking to the docs and what the
>> upcoming change is in cordova-ios 4.0.0. That way people will be "less"
>> surprised that they need to install this plugin in the future.
>>
>>
>>
>> Simon Mac Donald
>> http://hi.im/simonmacdonald
>>
>> On Tue, Sep 29, 2015 at 11:35 PM, Tommy Williams <to...@devgeeks.org>
>> wrote:
>>
>> > This.
>> >
>> > +1
>> >
>> >
>> > On 30 September 2015 at 12:31:29, Carlos Santana (csantana23@gmail.com)
>> > wrote:
>> >
>> > In summary I proposed that we update the plugin with a version that only
>> > contains the android code.
>> > When we publish cordova-ios@4.0.0 then we publish a new version that
>> > contains the ios code and contains engine tag stating that it needs
>> > minimum
>> > cordova-ios@4.0.0
>> >
>> > I'm OK if you want to have two branches to make it clear to devs, 1.x it
>> > contains android only, branch 2.x contains both android and ios.
>> >
>>
>

Re: cordova-plugin-whitelist ios issue

Posted by Shazron <sh...@gmail.com>.
That's a bad argument Carlos and you know it. No one will see the
warning unless they add the firefoxos platform, and if they added it,
it is relevant to them. This is a valid warning.

Plugins are in cross-platform territory and this will happen, let's
not skirt around it. We can hide now by "fixing the source" but that's
just avoiding it. The problem here is not the warning, but informing
the user properly. Like I said, we can add an <info> tag.


On Wed, Sep 30, 2015 at 8:48 AM, Carlos Santana <cs...@gmail.com> wrote:
> So this mean I can add this engine tag today to the whitelist plugin with
> some code specific to firefoxos?
>  <engine name="cordova-firefoxos" version=">=4.0.0-dev" />
>
> I know cordova-firefoxos@4.0.0-dev or ordova-firefoxos@4.0.0 is not on npm
> but is very useful to give users the warning now.
> This will avoid the user from upgrading the plugin ever in the future when c
> ordova-firefoxos@4.0.0 is published to npm, I might get c
> ordova-firefoxos@4.0.0 around december or longer  so I don't think it will
> be a problem for them to see the warning until then.
>
> If everyone is OK I will put this code today? this will avoid user from
> having to upgrade the plugin in the future :-p
>
> This is the point I want to make, and guess email communication is not
> being our friend to express my point of view.
> Will those interested on this topic up for a quick Hangout? Simon, Shaz,
> Nikhil
>
>
> On Wed, Sep 30, 2015 at 10:55 AM Simon MacDonald <si...@gmail.com>
> wrote:
>
>> -1 to this proposal IMHO
>>
>> Warnings are useful. If someone sees this and is confused as to why there
>> is a new whitelist plugin then looks into it some more detail that will be
>> beneficial. I think the warning should be more explicit. Put an info tag
>> into the plugin.xml for the whitelist linking to the docs and what the
>> upcoming change is in cordova-ios 4.0.0. That way people will be "less"
>> surprised that they need to install this plugin in the future.
>>
>>
>>
>> Simon Mac Donald
>> http://hi.im/simonmacdonald
>>
>> On Tue, Sep 29, 2015 at 11:35 PM, Tommy Williams <to...@devgeeks.org>
>> wrote:
>>
>> > This.
>> >
>> > +1
>> >
>> >
>> > On 30 September 2015 at 12:31:29, Carlos Santana (csantana23@gmail.com)
>> > wrote:
>> >
>> > In summary I proposed that we update the plugin with a version that only
>> > contains the android code.
>> > When we publish cordova-ios@4.0.0 then we publish a new version that
>> > contains the ios code and contains engine tag stating that it needs
>> > minimum
>> > cordova-ios@4.0.0
>> >
>> > I'm OK if you want to have two branches to make it clear to devs, 1.x it
>> > contains android only, branch 2.x contains both android and ios.
>> >
>>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
For additional commands, e-mail: dev-help@cordova.apache.org

Re: cordova-plugin-whitelist ios issue

Posted by Carlos Santana <cs...@gmail.com>.
So this mean I can add this engine tag today to the whitelist plugin with
some code specific to firefoxos?
 <engine name="cordova-firefoxos" version=">=4.0.0-dev" />

I know cordova-firefoxos@4.0.0-dev or ordova-firefoxos@4.0.0 is not on npm
but is very useful to give users the warning now.
This will avoid the user from upgrading the plugin ever in the future when c
ordova-firefoxos@4.0.0 is published to npm, I might get c
ordova-firefoxos@4.0.0 around december or longer  so I don't think it will
be a problem for them to see the warning until then.

If everyone is OK I will put this code today? this will avoid user from
having to upgrade the plugin in the future :-p

This is the point I want to make, and guess email communication is not
being our friend to express my point of view.
Will those interested on this topic up for a quick Hangout? Simon, Shaz,
Nikhil


On Wed, Sep 30, 2015 at 10:55 AM Simon MacDonald <si...@gmail.com>
wrote:

> -1 to this proposal IMHO
>
> Warnings are useful. If someone sees this and is confused as to why there
> is a new whitelist plugin then looks into it some more detail that will be
> beneficial. I think the warning should be more explicit. Put an info tag
> into the plugin.xml for the whitelist linking to the docs and what the
> upcoming change is in cordova-ios 4.0.0. That way people will be "less"
> surprised that they need to install this plugin in the future.
>
>
>
> Simon Mac Donald
> http://hi.im/simonmacdonald
>
> On Tue, Sep 29, 2015 at 11:35 PM, Tommy Williams <to...@devgeeks.org>
> wrote:
>
> > This.
> >
> > +1
> >
> >
> > On 30 September 2015 at 12:31:29, Carlos Santana (csantana23@gmail.com)
> > wrote:
> >
> > In summary I proposed that we update the plugin with a version that only
> > contains the android code.
> > When we publish cordova-ios@4.0.0 then we publish a new version that
> > contains the ios code and contains engine tag stating that it needs
> > minimum
> > cordova-ios@4.0.0
> >
> > I'm OK if you want to have two branches to make it clear to devs, 1.x it
> > contains android only, branch 2.x contains both android and ios.
> >
>

Re: cordova-plugin-whitelist ios issue

Posted by Simon MacDonald <si...@gmail.com>.
-1 to this proposal IMHO

Warnings are useful. If someone sees this and is confused as to why there
is a new whitelist plugin then looks into it some more detail that will be
beneficial. I think the warning should be more explicit. Put an info tag
into the plugin.xml for the whitelist linking to the docs and what the
upcoming change is in cordova-ios 4.0.0. That way people will be "less"
surprised that they need to install this plugin in the future.



Simon Mac Donald
http://hi.im/simonmacdonald

On Tue, Sep 29, 2015 at 11:35 PM, Tommy Williams <to...@devgeeks.org> wrote:

> This.
>
> +1
>
>
> On 30 September 2015 at 12:31:29, Carlos Santana (csantana23@gmail.com)
> wrote:
>
> In summary I proposed that we update the plugin with a version that only
> contains the android code.
> When we publish cordova-ios@4.0.0 then we publish a new version that
> contains the ios code and contains engine tag stating that it needs
> minimum
> cordova-ios@4.0.0
>
> I'm OK if you want to have two branches to make it clear to devs, 1.x it
> contains android only, branch 2.x contains both android and ios.
>

Re: cordova-plugin-whitelist ios issue

Posted by Tommy Williams <to...@devgeeks.org>.
This.

+1


On 30 September 2015 at 12:31:29, Carlos Santana (csantana23@gmail.com) wrote:

In summary I proposed that we update the plugin with a version that only 
contains the android code. 
When we publish cordova-ios@4.0.0 then we publish a new version that 
contains the ios code and contains engine tag stating that it needs minimum 
cordova-ios@4.0.0 

I'm OK if you want to have two branches to make it clear to devs, 1.x it 
contains android only, branch 2.x contains both android and ios. 

Re: cordova-plugin-whitelist ios issue

Posted by Steven Gill <st...@gmail.com>.
Made the switch. 1.0.0 is set to latest again and 1.1.0 can be switched to
latest once we release cordova-ios@4.0.0

On Wed, Sep 30, 2015 at 1:22 PM, Nikhil Khandelwal <ni...@microsoft.com>
wrote:

> +1 to changing the tag. We should not release the plugin with the engine
> tag for ios until cordova-ios 4.0 is released.
>
> -Nikhil
>
> -----Original Message-----
> From: Carlos Santana [mailto:csantana23@gmail.com]
> Sent: Wednesday, September 30, 2015 1:00 PM
> To: dev@cordova.apache.org
> Subject: Re: cordova-plugin-whitelist ios issue
>
> +1
> OK I guess I did a hoorible job doing an example :-)
>
> I compare 1.0.0 vs. 1.1.0
> And it looks like android didn't change. And the solution is that
> plugin.xml doesn't have the <platform name="ios"> and it doesn't have the
> offending <engine tag for ios>
>
> OK so still my position is that version 1.1.0 is a good version of the
> plugin. It adds ios feature and this feature required >
> cordova-ios@4.0.0-dev Just wait until cordova-ios@4.0.0 is released to
> make 1.1.0 public
>
>
> On Wed, Sep 30, 2015 at 3:27 PM Shazron <sh...@gmail.com> wrote:
>
> > +1 to the dist-tag change until we sort this out :)
> >
> > On Wed, Sep 30, 2015 at 12:25 PM, Steven Gill <st...@gmail.com>
> > wrote:
> > > I can change whitelist back to version 1 which only has the engine
> > > check for android. I can do that now if everyone is okay with it. We
> > > can change it back once cordova-ios@4 releases.
> > >
> > > On Wed, Sep 30, 2015 at 12:13 PM, Shazron <sh...@gmail.com> wrote:
> > >
> > >> -1.
> > >> We can just update the dist-tag so @latest goes to a previous version.
> > >> All released versions have been voted on, so its a matter of
> > >> dist-tag carousel.
> > >>
> > >>
> > >>
> > >> On Tue, Sep 29, 2015 at 7:31 PM, Carlos Santana
> > >> <cs...@gmail.com>
> > >> wrote:
> > >> > In summary I proposed that we update the plugin with a version
> > >> > that
> > only
> > >> > contains the android code.
> > >> > When we publish cordova-ios@4.0.0 then we publish a new version
> > >> > that contains the ios code and contains engine tag stating that
> > >> > it needs
> > >> minimum
> > >> > cordova-ios@4.0.0
> > >> >
> > >> > I'm OK if you want to have two branches to make it clear to devs,
> > >> > 1.x
> > it
> > >> > contains android only, branch 2.x contains both android and ios.
> > >> >
> > >> >
> > >> > On Tue, Sep 29, 2015 at 10:26 PM Carlos Santana
> > >> > <csantana23@gmail.com
> > >
> > >> > wrote:
> > >> >
> > >> >> Here are my two cents, and I'm aware of the situation.
> > >> >>
> > >> >> publish a new version of cordova-plugin-whitelist  that only
> > >> >> contains
> > >> the
> > >> >> android code and only supports android platform (means to remove
> > >> >> any
> > ios
> > >> >> code from the plugin)
> > >> >>
> > >> >> Currently the plugin is public and published on npm as latest,
> > >> >> and it states in the README:
> > >> >>
> > >> >>    - Android 4.0.0 or above
> > >> >>    - iOS 4.0.0 or above
> > >> >>
> > >> >> Guess what iOS 4.0.0 is it doesn't exist, it's not out, it's not
> > >> >> born
> > >> yet.
> > >> >> I guess you get the picture. The day that cordova-ios@4.0.0
> > >> >> get's published to npm is the day that it exist, then is valid
> > >> >> to published plugins that depend on that version of the platform.
> > >> >>
> > >> >> The day we published cordova-ios@4.0.0 to npm, on the same day
> > >> >> we
> > >> publish
> > >> >> cordova-plugin-whitelist that has code for ios and depends on
> > >> >> cordova-ios@4.0.0
> > >> >>
> > >> >> In general to my eyes we should NOT published plugins that
> > >> >> depends
> > (i.e.
> > >> >> engines) depend on a version of a component that it's not born yet.
> > >> >>
> > >> >>
> > >> >>
> > >> >> On Tue, Sep 29, 2015 at 8:57 PM Shazron <sh...@gmail.com> wrote:
> > >> >>
> > >> >>> This has nothing to do with cordova-ios being released. Think
> > >> >>> of it solely by the plugin's requirements: it requires
> > >> >>> cordova-android 4, and cordova-ios 4. I have cordova-android 4,
> > >> >>> so it installs. I have cordova-ios 3.9 so it doesn't, and it
> warns me.
> > >> >>>
> > >> >>> We *will* have this problem later with plugins, guaranteed, we
> > should
> > >> >>> not try to hide this problem for our own convenience.
> > >> >>>
> > >> >>> Let's say we took out this engine requirement, and they
> > >> >>> installed
> > the
> > >> >>> plugin on cordova-ios 3.9. Hey the warning goes away, great!
> > >> >>> But
> > this
> > >> >>> is a huge problem, because the code will be installed and it
> > >> >>> wasn't meant for your platform, and will probably cause bugs.
> > >> >>> It is
> > dependent
> > >> >>> of a platform version for a reason.
> > >> >>>
> > >> >>>
> > >> >>> On Tue, Sep 29, 2015 at 5:49 PM, Shazron <sh...@gmail.com>
> wrote:
> > >> >>> > I don't agree.
> > >> >>> >
> > >> >>> > I still don't think you understand the issue. I realize you
> > >> >>> > want
> > to
> > >> >>> > get "rid of the warnings" but there is really nothing to fix.
> > Nothing
> > >> >>> > at all. Users do not have to do anything, you don't have to
> > >> >>> > do anything.
> > >> >>> >
> > >> >>> > If they have cordova-ios 3.x installed - ignore this warning.
> > >> >>> > This plugin wasn't meant for your platform.
> > >> >>> >
> > >> >>> >
> > >> >>> >
> > >> >>> > On Tue, Sep 29, 2015 at 5:37 PM, Nikhil Khandelwal
> > >> >>> > <ni...@microsoft.com> wrote:
> > >> >>> >> I think the first version of the whitelist plugin was
> > >> >>> >> released
> > >> without
> > >> >>> the corodva-ios 4.0 check, so that developers do not see this
> > warning
> > >> >>> because cordova-ios 4.0 was not released. I agree with Tommy,
> > >> >>> that
> > the
> > >> >>> wording of the warning seems to suggest there is a way for me
> > >> >>> to fix
> > >> this
> > >> >>> issue:
> > >> >>> >> "Plugin doesn't support this project's cordova-ios version.
> > >> >>> cordova-ios: 3.9.1, failed version requirement: >=4.0.0-dev."
> > >> >>> >>
> > >> >>> >> However, with this plugin we do not have a way to fix it
> > >> >>> >> because
> > ios
> > >> >>> 4.0 is not released.
> > >> >>> >>
> > >> >>> >> I suggest we do the following:
> > >> >>> >> - Unpublish the version that has a dependency on ios 4.x
> > >> >>> >> - Release cordova-plugin-whitelist v2 which has an ios 4.x
> > depdency
> > >> >>> >> - In the tools release, that pins cordova-ios 4.x we should
> > >> >>> >> ship
> > a
> > >> >>> cordova-app-hello-world template that targets v2 of this plugin.
> > >> >>> >>
> > >> >>> >> Thanks,
> > >> >>> >> Nikhil
> > >> >>> >>
> > >> >>> >> -----Original Message-----
> > >> >>> >> From: Shazron [mailto:shazron@gmail.com]
> > >> >>> >> Sent: Tuesday, September 29, 2015 5:28 PM
> > >> >>> >> To: dev@cordova.apache.org
> > >> >>> >> Subject: Re: cordova-plugin-whitelist ios issue
> > >> >>> >>
> > >> >>> >> This is only happening because we have two engine
> > >> >>> >> requirements -
> > >> >>> cordova-android 4.x and cordova-ios 4.x. This is correct for
> > >> >>> cordova-plugin-whitelist.
> > >> >>> >>
> > >> >>> >> Like I mentioned before, cordova-android+ios 3.x *do not*
> > >> >>> >> require
> > >> this
> > >> >>> plugin as it is built in. Perhaps this could be communicated
> > >> >>> better,
> > >> but
> > >> >>> the warning is generic, and there's no way to communicate this
> > >> >>> in an <engine> tag.
> > >> >>> >>
> > >> >>> >> We could release core plugins that have different core
> > >> >>> >> platform
> > >> >>> version requirements as well in the future (like android 5
> > >> >>> plugin
> > >> >>> >> changes) and this will occur again.
> > >> >>> >>
> > >> >>> >>
> > >> >>> >> On Tue, Sep 29, 2015 at 5:21 PM, Shazron <sh...@gmail.com>
> > wrote:
> > >> >>> >>> "IMO we should never release a plugin which always emits a
> > warning
> > >> >>> >>> that cannot be resolved."
> > >> >>> >>>
> > >> >>> >>> There is nothing to resolve. The resolution is to ignore it.
> > It's
> > >> >>> >>> supposed to warn you, as it is working as expected.
> > >> >>> >>>
> > >> >>> >>> On Tue, Sep 29, 2015 at 5:19 PM, Nikhil Khandelwal
> > >> >>> >>> <ni...@microsoft.com> wrote:
> > >> >>> >>>> I understand the warning w.r.t. plugins and android 5.0 as
> > >> >>> >>>> we
> > will
> > >> >>> release android 5.0 along with the plugin update and there
> > >> >>> would be
> > a
> > >> path
> > >> >>> for people to resolve the warning.
> > >> >>> >>>>
> > >> >>> >>>> In this case, ios 4.0 is not even released and users have
> > >> >>> >>>> no
> > way
> > >> to
> > >> >>> work around this warning. We're getting feedback from customers
> > about
> > >> this.
> > >> >>> >>>>
> > >> >>> >>>> IMO we should never release a plugin which always emits a
> > warning
> > >> >>> that cannot be resolved.
> > >> >>> >>>>
> > >> >>> >>>> -Nikhil
> > >> >>> >>>>
> > >> >>> >>>> -----Original Message-----
> > >> >>> >>>> From: Shazron [mailto:shazron@gmail.com]
> > >> >>> >>>> Sent: Tuesday, September 29, 2015 5:17 PM
> > >> >>> >>>> To: dev@cordova.apache.org
> > >> >>> >>>> Subject: Re: cordova-plugin-whitelist ios issue
> > >> >>> >>>>
> > >> >>> >>>> No its not a "rogue version". cordova-plugin-whitelist
> > >> >>> >>>> requires
> > >> >>> cordova-ios 4.0 and cordova-android 4.0.
> > >> >>> >>>> It's just a warning and is expected to work this way.
> > >> >>> >>>>
> > >> >>>
> > https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fgith
> > >> >>> >>>> https://na01.safelinks.protection.outlook.com/?url=ub.com&
> > >> >>> >>>> data=01%7c01%7cnikhilkh%40microsoft.com%7c682981093cb14dda
> > >> >>> >>>> e5b308d2c9d1d65f%7c72f988bf86f141af91ab2d7cd011db47%7c1&sd
> > >> >>> >>>> ata=RWf5R%2bvPz8mB%2bGszBjU7hUqWAiyGallYFHElER6DxwM%3d
> > >> >>> %2fapache%2fcordova-plugin-whitelist%2fblob%2fmaster%2fREADME.m
> > >> >>> >>>> d&data=01%7c01%7cnikhilkh%40microsoft.com
> > >> >>> %7cd638675115ae4fa7be2d08d2c
> > >> >>> >>>>
> > >> 92c9d89%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=iO9NDS0BgD53OV
> > >> ED
> > >> >>> >>>> yxGv0zNW5SKXLVK0loo8ZAEmfOM%3d
> > >> >>> >>>>
> > >> >>> >>>> On Tue, Sep 29, 2015 at 5:08 PM, Nikhil Khandelwal <
> > >> >>> nikhilkh@microsoft.com> wrote:
> > >> >>> >>>>> 1.       cordova create test
> > >> >>> >>>>>
> > >> >>> >>>>> 2.       cordova platform add ios
> > >> >>> >>>>>
> > >> >>> >>>>> WARNING: Applications for platform ios can not be built
> > >> >>> >>>>> on
> > this
> > >> OS
> > >> >>> - win32.
> > >> >>> >>>>> Adding ios project...
> > >> >>> >>>>> iOS project created with cordova-ios@3.9.1 Discovered
> > >> >>> >>>>> plugin "cordova-plugin-whitelist" in config.xml.
> > >> >>> >>>>> Installing to the
> > >> project
> > >> >>> >>>>> Fetching plugin "cordova-plugin-whitelist@1" via npm
> > Installing
> > >> >>> >>>>> "cordova-plugin-whitelist" for ios Plugin doesn't support
> > >> >>> >>>>> this project's cordova-ios version. cordova-ios: 3.9.1,
> > >> >>> >>>>> failed
> > version
> > >> >>> >>>>> requirement: >=4.0.0-dev Skipping 'cordova-plugin-whitelist'
> > for
> > >> ios
> > >> >>> >>>>> Installing "cordova-plugin-whitelist" for ios Plugin
> > >> >>> >>>>> doesn't
> > >> support
> > >> >>> >>>>> this project's cordova-ios version. cordova-ios: 3.9.1,
> > >> >>> >>>>> failed version
> > >> >>> >>>>> requirement: >=4.0.0-dev Skipping 'cordova-plugin-whitelist'
> > for
> > >> ios
> > >> >>> >>>>>
> > >> >>> >>>>> Looks like we have a rogue version of
> > >> >>> >>>>> cordova-plugin-whitelist
> > >> >>> published that requires iOS 4.0.0. What's the best way to fix it?
> > Can
> > >> we
> > >> >>> unpublish this whitelist plugin version from npm to fix this?
> > >> >>> Alternatively, we should release another version of the plugin
> > >> >>> that
> > >> does
> > >> >>> not get this warning. It's misleading and confusing for
> > >> >>> developers
> > to
> > >> see
> > >> >>> this warning.
> > >> >>> >>>>>
> > >> >>> >>>>> Thanks,
> > >> >>> >>>>> Nikhil
> > >> >>> >>>>
> > >> >>> >>>>
> > >> -------------------------------------------------------------------
> > >> --
> > >> >>> >>>> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> > >> >>> >>>> For additional commands, e-mail:
> > >> >>> >>>> dev-help@cordova.apache.org
> > >> >>> >>>>
> > >> >>> >>>>
> > >> >>> >>>>
> > >> -------------------------------------------------------------------
> > >> --
> > >> >>> >>>> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> > >> >>> >>>> For additional commands, e-mail:
> > >> >>> >>>> dev-help@cordova.apache.org
> > >> >>> >>
> > >> >>> >>
> > >> -------------------------------------------------------------------
> > >> --
> > >> >>> >> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> > >> >>> >> For additional commands, e-mail: dev-help@cordova.apache.org
> > >> >>> >>
> > >> >>> >>
> > >> >>> >>
> > >> -------------------------------------------------------------------
> > >> --
> > >> >>> >> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> > >> >>> >> For additional commands, e-mail: dev-help@cordova.apache.org
> > >> >>>
> > >> >>>
> > ---------------------------------------------------------------------
> > >> >>> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> > >> >>> For additional commands, e-mail: dev-help@cordova.apache.org
> > >> >>>
> > >> >>>
> > >>
> > >> -------------------------------------------------------------------
> > >> -- To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> > >> For additional commands, e-mail: dev-help@cordova.apache.org
> > >>
> > >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> > For additional commands, e-mail: dev-help@cordova.apache.org
> >
> >
>

RE: cordova-plugin-whitelist ios issue

Posted by Nikhil Khandelwal <ni...@microsoft.com>.
+1 to changing the tag. We should not release the plugin with the engine tag for ios until cordova-ios 4.0 is released.

-Nikhil

-----Original Message-----
From: Carlos Santana [mailto:csantana23@gmail.com] 
Sent: Wednesday, September 30, 2015 1:00 PM
To: dev@cordova.apache.org
Subject: Re: cordova-plugin-whitelist ios issue

+1
OK I guess I did a hoorible job doing an example :-)

I compare 1.0.0 vs. 1.1.0
And it looks like android didn't change. And the solution is that plugin.xml doesn't have the <platform name="ios"> and it doesn't have the offending <engine tag for ios>

OK so still my position is that version 1.1.0 is a good version of the plugin. It adds ios feature and this feature required > cordova-ios@4.0.0-dev Just wait until cordova-ios@4.0.0 is released to make 1.1.0 public


On Wed, Sep 30, 2015 at 3:27 PM Shazron <sh...@gmail.com> wrote:

> +1 to the dist-tag change until we sort this out :)
>
> On Wed, Sep 30, 2015 at 12:25 PM, Steven Gill <st...@gmail.com>
> wrote:
> > I can change whitelist back to version 1 which only has the engine 
> > check for android. I can do that now if everyone is okay with it. We 
> > can change it back once cordova-ios@4 releases.
> >
> > On Wed, Sep 30, 2015 at 12:13 PM, Shazron <sh...@gmail.com> wrote:
> >
> >> -1.
> >> We can just update the dist-tag so @latest goes to a previous version.
> >> All released versions have been voted on, so its a matter of 
> >> dist-tag carousel.
> >>
> >>
> >>
> >> On Tue, Sep 29, 2015 at 7:31 PM, Carlos Santana 
> >> <cs...@gmail.com>
> >> wrote:
> >> > In summary I proposed that we update the plugin with a version 
> >> > that
> only
> >> > contains the android code.
> >> > When we publish cordova-ios@4.0.0 then we publish a new version 
> >> > that contains the ios code and contains engine tag stating that 
> >> > it needs
> >> minimum
> >> > cordova-ios@4.0.0
> >> >
> >> > I'm OK if you want to have two branches to make it clear to devs, 
> >> > 1.x
> it
> >> > contains android only, branch 2.x contains both android and ios.
> >> >
> >> >
> >> > On Tue, Sep 29, 2015 at 10:26 PM Carlos Santana 
> >> > <csantana23@gmail.com
> >
> >> > wrote:
> >> >
> >> >> Here are my two cents, and I'm aware of the situation.
> >> >>
> >> >> publish a new version of cordova-plugin-whitelist  that only 
> >> >> contains
> >> the
> >> >> android code and only supports android platform (means to remove 
> >> >> any
> ios
> >> >> code from the plugin)
> >> >>
> >> >> Currently the plugin is public and published on npm as latest, 
> >> >> and it states in the README:
> >> >>
> >> >>    - Android 4.0.0 or above
> >> >>    - iOS 4.0.0 or above
> >> >>
> >> >> Guess what iOS 4.0.0 is it doesn't exist, it's not out, it's not 
> >> >> born
> >> yet.
> >> >> I guess you get the picture. The day that cordova-ios@4.0.0 
> >> >> get's published to npm is the day that it exist, then is valid 
> >> >> to published plugins that depend on that version of the platform.
> >> >>
> >> >> The day we published cordova-ios@4.0.0 to npm, on the same day 
> >> >> we
> >> publish
> >> >> cordova-plugin-whitelist that has code for ios and depends on
> >> >> cordova-ios@4.0.0
> >> >>
> >> >> In general to my eyes we should NOT published plugins that 
> >> >> depends
> (i.e.
> >> >> engines) depend on a version of a component that it's not born yet.
> >> >>
> >> >>
> >> >>
> >> >> On Tue, Sep 29, 2015 at 8:57 PM Shazron <sh...@gmail.com> wrote:
> >> >>
> >> >>> This has nothing to do with cordova-ios being released. Think 
> >> >>> of it solely by the plugin's requirements: it requires 
> >> >>> cordova-android 4, and cordova-ios 4. I have cordova-android 4, 
> >> >>> so it installs. I have cordova-ios 3.9 so it doesn't, and it warns me.
> >> >>>
> >> >>> We *will* have this problem later with plugins, guaranteed, we
> should
> >> >>> not try to hide this problem for our own convenience.
> >> >>>
> >> >>> Let's say we took out this engine requirement, and they 
> >> >>> installed
> the
> >> >>> plugin on cordova-ios 3.9. Hey the warning goes away, great! 
> >> >>> But
> this
> >> >>> is a huge problem, because the code will be installed and it 
> >> >>> wasn't meant for your platform, and will probably cause bugs. 
> >> >>> It is
> dependent
> >> >>> of a platform version for a reason.
> >> >>>
> >> >>>
> >> >>> On Tue, Sep 29, 2015 at 5:49 PM, Shazron <sh...@gmail.com> wrote:
> >> >>> > I don't agree.
> >> >>> >
> >> >>> > I still don't think you understand the issue. I realize you 
> >> >>> > want
> to
> >> >>> > get "rid of the warnings" but there is really nothing to fix.
> Nothing
> >> >>> > at all. Users do not have to do anything, you don't have to 
> >> >>> > do anything.
> >> >>> >
> >> >>> > If they have cordova-ios 3.x installed - ignore this warning. 
> >> >>> > This plugin wasn't meant for your platform.
> >> >>> >
> >> >>> >
> >> >>> >
> >> >>> > On Tue, Sep 29, 2015 at 5:37 PM, Nikhil Khandelwal 
> >> >>> > <ni...@microsoft.com> wrote:
> >> >>> >> I think the first version of the whitelist plugin was 
> >> >>> >> released
> >> without
> >> >>> the corodva-ios 4.0 check, so that developers do not see this
> warning
> >> >>> because cordova-ios 4.0 was not released. I agree with Tommy, 
> >> >>> that
> the
> >> >>> wording of the warning seems to suggest there is a way for me 
> >> >>> to fix
> >> this
> >> >>> issue:
> >> >>> >> "Plugin doesn't support this project's cordova-ios version.
> >> >>> cordova-ios: 3.9.1, failed version requirement: >=4.0.0-dev."
> >> >>> >>
> >> >>> >> However, with this plugin we do not have a way to fix it 
> >> >>> >> because
> ios
> >> >>> 4.0 is not released.
> >> >>> >>
> >> >>> >> I suggest we do the following:
> >> >>> >> - Unpublish the version that has a dependency on ios 4.x
> >> >>> >> - Release cordova-plugin-whitelist v2 which has an ios 4.x
> depdency
> >> >>> >> - In the tools release, that pins cordova-ios 4.x we should 
> >> >>> >> ship
> a
> >> >>> cordova-app-hello-world template that targets v2 of this plugin.
> >> >>> >>
> >> >>> >> Thanks,
> >> >>> >> Nikhil
> >> >>> >>
> >> >>> >> -----Original Message-----
> >> >>> >> From: Shazron [mailto:shazron@gmail.com]
> >> >>> >> Sent: Tuesday, September 29, 2015 5:28 PM
> >> >>> >> To: dev@cordova.apache.org
> >> >>> >> Subject: Re: cordova-plugin-whitelist ios issue
> >> >>> >>
> >> >>> >> This is only happening because we have two engine 
> >> >>> >> requirements -
> >> >>> cordova-android 4.x and cordova-ios 4.x. This is correct for 
> >> >>> cordova-plugin-whitelist.
> >> >>> >>
> >> >>> >> Like I mentioned before, cordova-android+ios 3.x *do not* 
> >> >>> >> require
> >> this
> >> >>> plugin as it is built in. Perhaps this could be communicated 
> >> >>> better,
> >> but
> >> >>> the warning is generic, and there's no way to communicate this 
> >> >>> in an <engine> tag.
> >> >>> >>
> >> >>> >> We could release core plugins that have different core 
> >> >>> >> platform
> >> >>> version requirements as well in the future (like android 5 
> >> >>> plugin
> >> >>> >> changes) and this will occur again.
> >> >>> >>
> >> >>> >>
> >> >>> >> On Tue, Sep 29, 2015 at 5:21 PM, Shazron <sh...@gmail.com>
> wrote:
> >> >>> >>> "IMO we should never release a plugin which always emits a
> warning
> >> >>> >>> that cannot be resolved."
> >> >>> >>>
> >> >>> >>> There is nothing to resolve. The resolution is to ignore it.
> It's
> >> >>> >>> supposed to warn you, as it is working as expected.
> >> >>> >>>
> >> >>> >>> On Tue, Sep 29, 2015 at 5:19 PM, Nikhil Khandelwal 
> >> >>> >>> <ni...@microsoft.com> wrote:
> >> >>> >>>> I understand the warning w.r.t. plugins and android 5.0 as 
> >> >>> >>>> we
> will
> >> >>> release android 5.0 along with the plugin update and there 
> >> >>> would be
> a
> >> path
> >> >>> for people to resolve the warning.
> >> >>> >>>>
> >> >>> >>>> In this case, ios 4.0 is not even released and users have 
> >> >>> >>>> no
> way
> >> to
> >> >>> work around this warning. We're getting feedback from customers
> about
> >> this.
> >> >>> >>>>
> >> >>> >>>> IMO we should never release a plugin which always emits a
> warning
> >> >>> that cannot be resolved.
> >> >>> >>>>
> >> >>> >>>> -Nikhil
> >> >>> >>>>
> >> >>> >>>> -----Original Message-----
> >> >>> >>>> From: Shazron [mailto:shazron@gmail.com]
> >> >>> >>>> Sent: Tuesday, September 29, 2015 5:17 PM
> >> >>> >>>> To: dev@cordova.apache.org
> >> >>> >>>> Subject: Re: cordova-plugin-whitelist ios issue
> >> >>> >>>>
> >> >>> >>>> No its not a "rogue version". cordova-plugin-whitelist 
> >> >>> >>>> requires
> >> >>> cordova-ios 4.0 and cordova-android 4.0.
> >> >>> >>>> It's just a warning and is expected to work this way.
> >> >>> >>>>
> >> >>>
> https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fgith
> >> >>> >>>> https://na01.safelinks.protection.outlook.com/?url=ub.com&
> >> >>> >>>> data=01%7c01%7cnikhilkh%40microsoft.com%7c682981093cb14dda
> >> >>> >>>> e5b308d2c9d1d65f%7c72f988bf86f141af91ab2d7cd011db47%7c1&sd
> >> >>> >>>> ata=RWf5R%2bvPz8mB%2bGszBjU7hUqWAiyGallYFHElER6DxwM%3d
> >> >>> %2fapache%2fcordova-plugin-whitelist%2fblob%2fmaster%2fREADME.m
> >> >>> >>>> d&data=01%7c01%7cnikhilkh%40microsoft.com
> >> >>> %7cd638675115ae4fa7be2d08d2c
> >> >>> >>>>
> >> 92c9d89%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=iO9NDS0BgD53OV
> >> ED
> >> >>> >>>> yxGv0zNW5SKXLVK0loo8ZAEmfOM%3d
> >> >>> >>>>
> >> >>> >>>> On Tue, Sep 29, 2015 at 5:08 PM, Nikhil Khandelwal <
> >> >>> nikhilkh@microsoft.com> wrote:
> >> >>> >>>>> 1.       cordova create test
> >> >>> >>>>>
> >> >>> >>>>> 2.       cordova platform add ios
> >> >>> >>>>>
> >> >>> >>>>> WARNING: Applications for platform ios can not be built 
> >> >>> >>>>> on
> this
> >> OS
> >> >>> - win32.
> >> >>> >>>>> Adding ios project...
> >> >>> >>>>> iOS project created with cordova-ios@3.9.1 Discovered 
> >> >>> >>>>> plugin "cordova-plugin-whitelist" in config.xml. 
> >> >>> >>>>> Installing to the
> >> project
> >> >>> >>>>> Fetching plugin "cordova-plugin-whitelist@1" via npm
> Installing
> >> >>> >>>>> "cordova-plugin-whitelist" for ios Plugin doesn't support 
> >> >>> >>>>> this project's cordova-ios version. cordova-ios: 3.9.1, 
> >> >>> >>>>> failed
> version
> >> >>> >>>>> requirement: >=4.0.0-dev Skipping 'cordova-plugin-whitelist'
> for
> >> ios
> >> >>> >>>>> Installing "cordova-plugin-whitelist" for ios Plugin 
> >> >>> >>>>> doesn't
> >> support
> >> >>> >>>>> this project's cordova-ios version. cordova-ios: 3.9.1, 
> >> >>> >>>>> failed version
> >> >>> >>>>> requirement: >=4.0.0-dev Skipping 'cordova-plugin-whitelist'
> for
> >> ios
> >> >>> >>>>>
> >> >>> >>>>> Looks like we have a rogue version of 
> >> >>> >>>>> cordova-plugin-whitelist
> >> >>> published that requires iOS 4.0.0. What's the best way to fix it?
> Can
> >> we
> >> >>> unpublish this whitelist plugin version from npm to fix this?
> >> >>> Alternatively, we should release another version of the plugin 
> >> >>> that
> >> does
> >> >>> not get this warning. It's misleading and confusing for 
> >> >>> developers
> to
> >> see
> >> >>> this warning.
> >> >>> >>>>>
> >> >>> >>>>> Thanks,
> >> >>> >>>>> Nikhil
> >> >>> >>>>
> >> >>> >>>>
> >> -------------------------------------------------------------------
> >> --
> >> >>> >>>> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> >> >>> >>>> For additional commands, e-mail: 
> >> >>> >>>> dev-help@cordova.apache.org
> >> >>> >>>>
> >> >>> >>>>
> >> >>> >>>>
> >> -------------------------------------------------------------------
> >> --
> >> >>> >>>> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> >> >>> >>>> For additional commands, e-mail: 
> >> >>> >>>> dev-help@cordova.apache.org
> >> >>> >>
> >> >>> >>
> >> -------------------------------------------------------------------
> >> --
> >> >>> >> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> >> >>> >> For additional commands, e-mail: dev-help@cordova.apache.org
> >> >>> >>
> >> >>> >>
> >> >>> >>
> >> -------------------------------------------------------------------
> >> --
> >> >>> >> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> >> >>> >> For additional commands, e-mail: dev-help@cordova.apache.org
> >> >>>
> >> >>>
> ---------------------------------------------------------------------
> >> >>> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> >> >>> For additional commands, e-mail: dev-help@cordova.apache.org
> >> >>>
> >> >>>
> >>
> >> -------------------------------------------------------------------
> >> -- To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> >> For additional commands, e-mail: dev-help@cordova.apache.org
> >>
> >>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> For additional commands, e-mail: dev-help@cordova.apache.org
>
>

Re: cordova-plugin-whitelist ios issue

Posted by Carlos Santana <cs...@gmail.com>.
+1
OK I guess I did a hoorible job doing an example :-)

I compare 1.0.0 vs. 1.1.0
And it looks like android didn't change. And the solution is that
plugin.xml doesn't have the <platform name="ios"> and it doesn't have the
offending <engine tag for ios>

OK so still my position is that version 1.1.0 is a good version of the
plugin. It adds ios feature and this feature required >
cordova-ios@4.0.0-dev
Just wait until cordova-ios@4.0.0 is released to make 1.1.0 public


On Wed, Sep 30, 2015 at 3:27 PM Shazron <sh...@gmail.com> wrote:

> +1 to the dist-tag change until we sort this out :)
>
> On Wed, Sep 30, 2015 at 12:25 PM, Steven Gill <st...@gmail.com>
> wrote:
> > I can change whitelist back to version 1 which only has the engine check
> > for android. I can do that now if everyone is okay with it. We can change
> > it back once cordova-ios@4 releases.
> >
> > On Wed, Sep 30, 2015 at 12:13 PM, Shazron <sh...@gmail.com> wrote:
> >
> >> -1.
> >> We can just update the dist-tag so @latest goes to a previous version.
> >> All released versions have been voted on, so its a matter of dist-tag
> >> carousel.
> >>
> >>
> >>
> >> On Tue, Sep 29, 2015 at 7:31 PM, Carlos Santana <cs...@gmail.com>
> >> wrote:
> >> > In summary I proposed that we update the plugin with a version that
> only
> >> > contains the android code.
> >> > When we publish cordova-ios@4.0.0 then we publish a new version that
> >> > contains the ios code and contains engine tag stating that it needs
> >> minimum
> >> > cordova-ios@4.0.0
> >> >
> >> > I'm OK if you want to have two branches to make it clear to devs, 1.x
> it
> >> > contains android only, branch 2.x contains both android and ios.
> >> >
> >> >
> >> > On Tue, Sep 29, 2015 at 10:26 PM Carlos Santana <csantana23@gmail.com
> >
> >> > wrote:
> >> >
> >> >> Here are my two cents, and I'm aware of the situation.
> >> >>
> >> >> publish a new version of cordova-plugin-whitelist  that only contains
> >> the
> >> >> android code and only supports android platform (means to remove any
> ios
> >> >> code from the plugin)
> >> >>
> >> >> Currently the plugin is public and published on npm as latest, and it
> >> >> states in the README:
> >> >>
> >> >>    - Android 4.0.0 or above
> >> >>    - iOS 4.0.0 or above
> >> >>
> >> >> Guess what iOS 4.0.0 is it doesn't exist, it's not out, it's not born
> >> yet.
> >> >> I guess you get the picture. The day that cordova-ios@4.0.0 get's
> >> >> published to npm is the day that it exist, then is valid to published
> >> >> plugins that depend on that version of the platform.
> >> >>
> >> >> The day we published cordova-ios@4.0.0 to npm, on the same day we
> >> publish
> >> >> cordova-plugin-whitelist that has code for ios and depends on
> >> >> cordova-ios@4.0.0
> >> >>
> >> >> In general to my eyes we should NOT published plugins that depends
> (i.e.
> >> >> engines) depend on a version of a component that it's not born yet.
> >> >>
> >> >>
> >> >>
> >> >> On Tue, Sep 29, 2015 at 8:57 PM Shazron <sh...@gmail.com> wrote:
> >> >>
> >> >>> This has nothing to do with cordova-ios being released. Think of it
> >> >>> solely by the plugin's requirements: it requires cordova-android 4,
> >> >>> and cordova-ios 4. I have cordova-android 4, so it installs. I have
> >> >>> cordova-ios 3.9 so it doesn't, and it warns me.
> >> >>>
> >> >>> We *will* have this problem later with plugins, guaranteed, we
> should
> >> >>> not try to hide this problem for our own convenience.
> >> >>>
> >> >>> Let's say we took out this engine requirement, and they installed
> the
> >> >>> plugin on cordova-ios 3.9. Hey the warning goes away, great! But
> this
> >> >>> is a huge problem, because the code will be installed and it wasn't
> >> >>> meant for your platform, and will probably cause bugs. It is
> dependent
> >> >>> of a platform version for a reason.
> >> >>>
> >> >>>
> >> >>> On Tue, Sep 29, 2015 at 5:49 PM, Shazron <sh...@gmail.com> wrote:
> >> >>> > I don't agree.
> >> >>> >
> >> >>> > I still don't think you understand the issue. I realize you want
> to
> >> >>> > get "rid of the warnings" but there is really nothing to fix.
> Nothing
> >> >>> > at all. Users do not have to do anything, you don't have to do
> >> >>> > anything.
> >> >>> >
> >> >>> > If they have cordova-ios 3.x installed - ignore this warning. This
> >> >>> > plugin wasn't meant for your platform.
> >> >>> >
> >> >>> >
> >> >>> >
> >> >>> > On Tue, Sep 29, 2015 at 5:37 PM, Nikhil Khandelwal
> >> >>> > <ni...@microsoft.com> wrote:
> >> >>> >> I think the first version of the whitelist plugin was released
> >> without
> >> >>> the corodva-ios 4.0 check, so that developers do not see this
> warning
> >> >>> because cordova-ios 4.0 was not released. I agree with Tommy, that
> the
> >> >>> wording of the warning seems to suggest there is a way for me to fix
> >> this
> >> >>> issue:
> >> >>> >> "Plugin doesn't support this project's cordova-ios version.
> >> >>> cordova-ios: 3.9.1, failed version requirement: >=4.0.0-dev."
> >> >>> >>
> >> >>> >> However, with this plugin we do not have a way to fix it because
> ios
> >> >>> 4.0 is not released.
> >> >>> >>
> >> >>> >> I suggest we do the following:
> >> >>> >> - Unpublish the version that has a dependency on ios 4.x
> >> >>> >> - Release cordova-plugin-whitelist v2 which has an ios 4.x
> depdency
> >> >>> >> - In the tools release, that pins cordova-ios 4.x we should ship
> a
> >> >>> cordova-app-hello-world template that targets v2 of this plugin.
> >> >>> >>
> >> >>> >> Thanks,
> >> >>> >> Nikhil
> >> >>> >>
> >> >>> >> -----Original Message-----
> >> >>> >> From: Shazron [mailto:shazron@gmail.com]
> >> >>> >> Sent: Tuesday, September 29, 2015 5:28 PM
> >> >>> >> To: dev@cordova.apache.org
> >> >>> >> Subject: Re: cordova-plugin-whitelist ios issue
> >> >>> >>
> >> >>> >> This is only happening because we have two engine requirements -
> >> >>> cordova-android 4.x and cordova-ios 4.x. This is correct for
> >> >>> cordova-plugin-whitelist.
> >> >>> >>
> >> >>> >> Like I mentioned before, cordova-android+ios 3.x *do not* require
> >> this
> >> >>> plugin as it is built in. Perhaps this could be communicated better,
> >> but
> >> >>> the warning is generic, and there's no way to communicate this in an
> >> >>> <engine> tag.
> >> >>> >>
> >> >>> >> We could release core plugins that have different core platform
> >> >>> version requirements as well in the future (like android 5 plugin
> >> >>> >> changes) and this will occur again.
> >> >>> >>
> >> >>> >>
> >> >>> >> On Tue, Sep 29, 2015 at 5:21 PM, Shazron <sh...@gmail.com>
> wrote:
> >> >>> >>> "IMO we should never release a plugin which always emits a
> warning
> >> >>> >>> that cannot be resolved."
> >> >>> >>>
> >> >>> >>> There is nothing to resolve. The resolution is to ignore it.
> It's
> >> >>> >>> supposed to warn you, as it is working as expected.
> >> >>> >>>
> >> >>> >>> On Tue, Sep 29, 2015 at 5:19 PM, Nikhil Khandelwal
> >> >>> >>> <ni...@microsoft.com> wrote:
> >> >>> >>>> I understand the warning w.r.t. plugins and android 5.0 as we
> will
> >> >>> release android 5.0 along with the plugin update and there would be
> a
> >> path
> >> >>> for people to resolve the warning.
> >> >>> >>>>
> >> >>> >>>> In this case, ios 4.0 is not even released and users have no
> way
> >> to
> >> >>> work around this warning. We're getting feedback from customers
> about
> >> this.
> >> >>> >>>>
> >> >>> >>>> IMO we should never release a plugin which always emits a
> warning
> >> >>> that cannot be resolved.
> >> >>> >>>>
> >> >>> >>>> -Nikhil
> >> >>> >>>>
> >> >>> >>>> -----Original Message-----
> >> >>> >>>> From: Shazron [mailto:shazron@gmail.com]
> >> >>> >>>> Sent: Tuesday, September 29, 2015 5:17 PM
> >> >>> >>>> To: dev@cordova.apache.org
> >> >>> >>>> Subject: Re: cordova-plugin-whitelist ios issue
> >> >>> >>>>
> >> >>> >>>> No its not a "rogue version". cordova-plugin-whitelist requires
> >> >>> cordova-ios 4.0 and cordova-android 4.0.
> >> >>> >>>> It's just a warning and is expected to work this way.
> >> >>> >>>>
> >> >>>
> https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fgith
> >> >>> >>>> ub.com
> >> >>> %2fapache%2fcordova-plugin-whitelist%2fblob%2fmaster%2fREADME.m
> >> >>> >>>> d&data=01%7c01%7cnikhilkh%40microsoft.com
> >> >>> %7cd638675115ae4fa7be2d08d2c
> >> >>> >>>>
> >> 92c9d89%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=iO9NDS0BgD53OVED
> >> >>> >>>> yxGv0zNW5SKXLVK0loo8ZAEmfOM%3d
> >> >>> >>>>
> >> >>> >>>> On Tue, Sep 29, 2015 at 5:08 PM, Nikhil Khandelwal <
> >> >>> nikhilkh@microsoft.com> wrote:
> >> >>> >>>>> 1.       cordova create test
> >> >>> >>>>>
> >> >>> >>>>> 2.       cordova platform add ios
> >> >>> >>>>>
> >> >>> >>>>> WARNING: Applications for platform ios can not be built on
> this
> >> OS
> >> >>> - win32.
> >> >>> >>>>> Adding ios project...
> >> >>> >>>>> iOS project created with cordova-ios@3.9.1 Discovered plugin
> >> >>> >>>>> "cordova-plugin-whitelist" in config.xml. Installing to the
> >> project
> >> >>> >>>>> Fetching plugin "cordova-plugin-whitelist@1" via npm
> Installing
> >> >>> >>>>> "cordova-plugin-whitelist" for ios Plugin doesn't support this
> >> >>> >>>>> project's cordova-ios version. cordova-ios: 3.9.1, failed
> version
> >> >>> >>>>> requirement: >=4.0.0-dev Skipping 'cordova-plugin-whitelist'
> for
> >> ios
> >> >>> >>>>> Installing "cordova-plugin-whitelist" for ios Plugin doesn't
> >> support
> >> >>> >>>>> this project's cordova-ios version. cordova-ios: 3.9.1, failed
> >> >>> >>>>> version
> >> >>> >>>>> requirement: >=4.0.0-dev Skipping 'cordova-plugin-whitelist'
> for
> >> ios
> >> >>> >>>>>
> >> >>> >>>>> Looks like we have a rogue version of cordova-plugin-whitelist
> >> >>> published that requires iOS 4.0.0. What's the best way to fix it?
> Can
> >> we
> >> >>> unpublish this whitelist plugin version from npm to fix this?
> >> >>> Alternatively, we should release another version of the plugin that
> >> does
> >> >>> not get this warning. It's misleading and confusing for developers
> to
> >> see
> >> >>> this warning.
> >> >>> >>>>>
> >> >>> >>>>> Thanks,
> >> >>> >>>>> Nikhil
> >> >>> >>>>
> >> >>> >>>>
> >> ---------------------------------------------------------------------
> >> >>> >>>> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> >> >>> >>>> For additional commands, e-mail: dev-help@cordova.apache.org
> >> >>> >>>>
> >> >>> >>>>
> >> >>> >>>>
> >> ---------------------------------------------------------------------
> >> >>> >>>> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> >> >>> >>>> For additional commands, e-mail: dev-help@cordova.apache.org
> >> >>> >>
> >> >>> >>
> >> ---------------------------------------------------------------------
> >> >>> >> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> >> >>> >> For additional commands, e-mail: dev-help@cordova.apache.org
> >> >>> >>
> >> >>> >>
> >> >>> >>
> >> ---------------------------------------------------------------------
> >> >>> >> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> >> >>> >> For additional commands, e-mail: dev-help@cordova.apache.org
> >> >>>
> >> >>>
> ---------------------------------------------------------------------
> >> >>> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> >> >>> For additional commands, e-mail: dev-help@cordova.apache.org
> >> >>>
> >> >>>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> >> For additional commands, e-mail: dev-help@cordova.apache.org
> >>
> >>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> For additional commands, e-mail: dev-help@cordova.apache.org
>
>

Re: cordova-plugin-whitelist ios issue

Posted by Shazron <sh...@gmail.com>.
+1 to the dist-tag change until we sort this out :)

On Wed, Sep 30, 2015 at 12:25 PM, Steven Gill <st...@gmail.com> wrote:
> I can change whitelist back to version 1 which only has the engine check
> for android. I can do that now if everyone is okay with it. We can change
> it back once cordova-ios@4 releases.
>
> On Wed, Sep 30, 2015 at 12:13 PM, Shazron <sh...@gmail.com> wrote:
>
>> -1.
>> We can just update the dist-tag so @latest goes to a previous version.
>> All released versions have been voted on, so its a matter of dist-tag
>> carousel.
>>
>>
>>
>> On Tue, Sep 29, 2015 at 7:31 PM, Carlos Santana <cs...@gmail.com>
>> wrote:
>> > In summary I proposed that we update the plugin with a version that only
>> > contains the android code.
>> > When we publish cordova-ios@4.0.0 then we publish a new version that
>> > contains the ios code and contains engine tag stating that it needs
>> minimum
>> > cordova-ios@4.0.0
>> >
>> > I'm OK if you want to have two branches to make it clear to devs, 1.x it
>> > contains android only, branch 2.x contains both android and ios.
>> >
>> >
>> > On Tue, Sep 29, 2015 at 10:26 PM Carlos Santana <cs...@gmail.com>
>> > wrote:
>> >
>> >> Here are my two cents, and I'm aware of the situation.
>> >>
>> >> publish a new version of cordova-plugin-whitelist  that only contains
>> the
>> >> android code and only supports android platform (means to remove any ios
>> >> code from the plugin)
>> >>
>> >> Currently the plugin is public and published on npm as latest, and it
>> >> states in the README:
>> >>
>> >>    - Android 4.0.0 or above
>> >>    - iOS 4.0.0 or above
>> >>
>> >> Guess what iOS 4.0.0 is it doesn't exist, it's not out, it's not born
>> yet.
>> >> I guess you get the picture. The day that cordova-ios@4.0.0 get's
>> >> published to npm is the day that it exist, then is valid to published
>> >> plugins that depend on that version of the platform.
>> >>
>> >> The day we published cordova-ios@4.0.0 to npm, on the same day we
>> publish
>> >> cordova-plugin-whitelist that has code for ios and depends on
>> >> cordova-ios@4.0.0
>> >>
>> >> In general to my eyes we should NOT published plugins that depends (i.e.
>> >> engines) depend on a version of a component that it's not born yet.
>> >>
>> >>
>> >>
>> >> On Tue, Sep 29, 2015 at 8:57 PM Shazron <sh...@gmail.com> wrote:
>> >>
>> >>> This has nothing to do with cordova-ios being released. Think of it
>> >>> solely by the plugin's requirements: it requires cordova-android 4,
>> >>> and cordova-ios 4. I have cordova-android 4, so it installs. I have
>> >>> cordova-ios 3.9 so it doesn't, and it warns me.
>> >>>
>> >>> We *will* have this problem later with plugins, guaranteed, we should
>> >>> not try to hide this problem for our own convenience.
>> >>>
>> >>> Let's say we took out this engine requirement, and they installed the
>> >>> plugin on cordova-ios 3.9. Hey the warning goes away, great! But this
>> >>> is a huge problem, because the code will be installed and it wasn't
>> >>> meant for your platform, and will probably cause bugs. It is dependent
>> >>> of a platform version for a reason.
>> >>>
>> >>>
>> >>> On Tue, Sep 29, 2015 at 5:49 PM, Shazron <sh...@gmail.com> wrote:
>> >>> > I don't agree.
>> >>> >
>> >>> > I still don't think you understand the issue. I realize you want to
>> >>> > get "rid of the warnings" but there is really nothing to fix. Nothing
>> >>> > at all. Users do not have to do anything, you don't have to do
>> >>> > anything.
>> >>> >
>> >>> > If they have cordova-ios 3.x installed - ignore this warning. This
>> >>> > plugin wasn't meant for your platform.
>> >>> >
>> >>> >
>> >>> >
>> >>> > On Tue, Sep 29, 2015 at 5:37 PM, Nikhil Khandelwal
>> >>> > <ni...@microsoft.com> wrote:
>> >>> >> I think the first version of the whitelist plugin was released
>> without
>> >>> the corodva-ios 4.0 check, so that developers do not see this warning
>> >>> because cordova-ios 4.0 was not released. I agree with Tommy, that the
>> >>> wording of the warning seems to suggest there is a way for me to fix
>> this
>> >>> issue:
>> >>> >> "Plugin doesn't support this project's cordova-ios version.
>> >>> cordova-ios: 3.9.1, failed version requirement: >=4.0.0-dev."
>> >>> >>
>> >>> >> However, with this plugin we do not have a way to fix it because ios
>> >>> 4.0 is not released.
>> >>> >>
>> >>> >> I suggest we do the following:
>> >>> >> - Unpublish the version that has a dependency on ios 4.x
>> >>> >> - Release cordova-plugin-whitelist v2 which has an ios 4.x depdency
>> >>> >> - In the tools release, that pins cordova-ios 4.x we should ship a
>> >>> cordova-app-hello-world template that targets v2 of this plugin.
>> >>> >>
>> >>> >> Thanks,
>> >>> >> Nikhil
>> >>> >>
>> >>> >> -----Original Message-----
>> >>> >> From: Shazron [mailto:shazron@gmail.com]
>> >>> >> Sent: Tuesday, September 29, 2015 5:28 PM
>> >>> >> To: dev@cordova.apache.org
>> >>> >> Subject: Re: cordova-plugin-whitelist ios issue
>> >>> >>
>> >>> >> This is only happening because we have two engine requirements -
>> >>> cordova-android 4.x and cordova-ios 4.x. This is correct for
>> >>> cordova-plugin-whitelist.
>> >>> >>
>> >>> >> Like I mentioned before, cordova-android+ios 3.x *do not* require
>> this
>> >>> plugin as it is built in. Perhaps this could be communicated better,
>> but
>> >>> the warning is generic, and there's no way to communicate this in an
>> >>> <engine> tag.
>> >>> >>
>> >>> >> We could release core plugins that have different core platform
>> >>> version requirements as well in the future (like android 5 plugin
>> >>> >> changes) and this will occur again.
>> >>> >>
>> >>> >>
>> >>> >> On Tue, Sep 29, 2015 at 5:21 PM, Shazron <sh...@gmail.com> wrote:
>> >>> >>> "IMO we should never release a plugin which always emits a warning
>> >>> >>> that cannot be resolved."
>> >>> >>>
>> >>> >>> There is nothing to resolve. The resolution is to ignore it. It's
>> >>> >>> supposed to warn you, as it is working as expected.
>> >>> >>>
>> >>> >>> On Tue, Sep 29, 2015 at 5:19 PM, Nikhil Khandelwal
>> >>> >>> <ni...@microsoft.com> wrote:
>> >>> >>>> I understand the warning w.r.t. plugins and android 5.0 as we will
>> >>> release android 5.0 along with the plugin update and there would be a
>> path
>> >>> for people to resolve the warning.
>> >>> >>>>
>> >>> >>>> In this case, ios 4.0 is not even released and users have no way
>> to
>> >>> work around this warning. We're getting feedback from customers about
>> this.
>> >>> >>>>
>> >>> >>>> IMO we should never release a plugin which always emits a warning
>> >>> that cannot be resolved.
>> >>> >>>>
>> >>> >>>> -Nikhil
>> >>> >>>>
>> >>> >>>> -----Original Message-----
>> >>> >>>> From: Shazron [mailto:shazron@gmail.com]
>> >>> >>>> Sent: Tuesday, September 29, 2015 5:17 PM
>> >>> >>>> To: dev@cordova.apache.org
>> >>> >>>> Subject: Re: cordova-plugin-whitelist ios issue
>> >>> >>>>
>> >>> >>>> No its not a "rogue version". cordova-plugin-whitelist requires
>> >>> cordova-ios 4.0 and cordova-android 4.0.
>> >>> >>>> It's just a warning and is expected to work this way.
>> >>> >>>>
>> >>> https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fgith
>> >>> >>>> ub.com
>> >>> %2fapache%2fcordova-plugin-whitelist%2fblob%2fmaster%2fREADME.m
>> >>> >>>> d&data=01%7c01%7cnikhilkh%40microsoft.com
>> >>> %7cd638675115ae4fa7be2d08d2c
>> >>> >>>>
>> 92c9d89%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=iO9NDS0BgD53OVED
>> >>> >>>> yxGv0zNW5SKXLVK0loo8ZAEmfOM%3d
>> >>> >>>>
>> >>> >>>> On Tue, Sep 29, 2015 at 5:08 PM, Nikhil Khandelwal <
>> >>> nikhilkh@microsoft.com> wrote:
>> >>> >>>>> 1.       cordova create test
>> >>> >>>>>
>> >>> >>>>> 2.       cordova platform add ios
>> >>> >>>>>
>> >>> >>>>> WARNING: Applications for platform ios can not be built on this
>> OS
>> >>> - win32.
>> >>> >>>>> Adding ios project...
>> >>> >>>>> iOS project created with cordova-ios@3.9.1 Discovered plugin
>> >>> >>>>> "cordova-plugin-whitelist" in config.xml. Installing to the
>> project
>> >>> >>>>> Fetching plugin "cordova-plugin-whitelist@1" via npm Installing
>> >>> >>>>> "cordova-plugin-whitelist" for ios Plugin doesn't support this
>> >>> >>>>> project's cordova-ios version. cordova-ios: 3.9.1, failed version
>> >>> >>>>> requirement: >=4.0.0-dev Skipping 'cordova-plugin-whitelist' for
>> ios
>> >>> >>>>> Installing "cordova-plugin-whitelist" for ios Plugin doesn't
>> support
>> >>> >>>>> this project's cordova-ios version. cordova-ios: 3.9.1, failed
>> >>> >>>>> version
>> >>> >>>>> requirement: >=4.0.0-dev Skipping 'cordova-plugin-whitelist' for
>> ios
>> >>> >>>>>
>> >>> >>>>> Looks like we have a rogue version of cordova-plugin-whitelist
>> >>> published that requires iOS 4.0.0. What's the best way to fix it? Can
>> we
>> >>> unpublish this whitelist plugin version from npm to fix this?
>> >>> Alternatively, we should release another version of the plugin that
>> does
>> >>> not get this warning. It's misleading and confusing for developers to
>> see
>> >>> this warning.
>> >>> >>>>>
>> >>> >>>>> Thanks,
>> >>> >>>>> Nikhil
>> >>> >>>>
>> >>> >>>>
>> ---------------------------------------------------------------------
>> >>> >>>> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
>> >>> >>>> For additional commands, e-mail: dev-help@cordova.apache.org
>> >>> >>>>
>> >>> >>>>
>> >>> >>>>
>> ---------------------------------------------------------------------
>> >>> >>>> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
>> >>> >>>> For additional commands, e-mail: dev-help@cordova.apache.org
>> >>> >>
>> >>> >>
>> ---------------------------------------------------------------------
>> >>> >> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
>> >>> >> For additional commands, e-mail: dev-help@cordova.apache.org
>> >>> >>
>> >>> >>
>> >>> >>
>> ---------------------------------------------------------------------
>> >>> >> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
>> >>> >> For additional commands, e-mail: dev-help@cordova.apache.org
>> >>>
>> >>> ---------------------------------------------------------------------
>> >>> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
>> >>> For additional commands, e-mail: dev-help@cordova.apache.org
>> >>>
>> >>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
>> For additional commands, e-mail: dev-help@cordova.apache.org
>>
>>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
For additional commands, e-mail: dev-help@cordova.apache.org

Re: cordova-plugin-whitelist ios issue

Posted by Steven Gill <st...@gmail.com>.
I can change whitelist back to version 1 which only has the engine check
for android. I can do that now if everyone is okay with it. We can change
it back once cordova-ios@4 releases.

On Wed, Sep 30, 2015 at 12:13 PM, Shazron <sh...@gmail.com> wrote:

> -1.
> We can just update the dist-tag so @latest goes to a previous version.
> All released versions have been voted on, so its a matter of dist-tag
> carousel.
>
>
>
> On Tue, Sep 29, 2015 at 7:31 PM, Carlos Santana <cs...@gmail.com>
> wrote:
> > In summary I proposed that we update the plugin with a version that only
> > contains the android code.
> > When we publish cordova-ios@4.0.0 then we publish a new version that
> > contains the ios code and contains engine tag stating that it needs
> minimum
> > cordova-ios@4.0.0
> >
> > I'm OK if you want to have two branches to make it clear to devs, 1.x it
> > contains android only, branch 2.x contains both android and ios.
> >
> >
> > On Tue, Sep 29, 2015 at 10:26 PM Carlos Santana <cs...@gmail.com>
> > wrote:
> >
> >> Here are my two cents, and I'm aware of the situation.
> >>
> >> publish a new version of cordova-plugin-whitelist  that only contains
> the
> >> android code and only supports android platform (means to remove any ios
> >> code from the plugin)
> >>
> >> Currently the plugin is public and published on npm as latest, and it
> >> states in the README:
> >>
> >>    - Android 4.0.0 or above
> >>    - iOS 4.0.0 or above
> >>
> >> Guess what iOS 4.0.0 is it doesn't exist, it's not out, it's not born
> yet.
> >> I guess you get the picture. The day that cordova-ios@4.0.0 get's
> >> published to npm is the day that it exist, then is valid to published
> >> plugins that depend on that version of the platform.
> >>
> >> The day we published cordova-ios@4.0.0 to npm, on the same day we
> publish
> >> cordova-plugin-whitelist that has code for ios and depends on
> >> cordova-ios@4.0.0
> >>
> >> In general to my eyes we should NOT published plugins that depends (i.e.
> >> engines) depend on a version of a component that it's not born yet.
> >>
> >>
> >>
> >> On Tue, Sep 29, 2015 at 8:57 PM Shazron <sh...@gmail.com> wrote:
> >>
> >>> This has nothing to do with cordova-ios being released. Think of it
> >>> solely by the plugin's requirements: it requires cordova-android 4,
> >>> and cordova-ios 4. I have cordova-android 4, so it installs. I have
> >>> cordova-ios 3.9 so it doesn't, and it warns me.
> >>>
> >>> We *will* have this problem later with plugins, guaranteed, we should
> >>> not try to hide this problem for our own convenience.
> >>>
> >>> Let's say we took out this engine requirement, and they installed the
> >>> plugin on cordova-ios 3.9. Hey the warning goes away, great! But this
> >>> is a huge problem, because the code will be installed and it wasn't
> >>> meant for your platform, and will probably cause bugs. It is dependent
> >>> of a platform version for a reason.
> >>>
> >>>
> >>> On Tue, Sep 29, 2015 at 5:49 PM, Shazron <sh...@gmail.com> wrote:
> >>> > I don't agree.
> >>> >
> >>> > I still don't think you understand the issue. I realize you want to
> >>> > get "rid of the warnings" but there is really nothing to fix. Nothing
> >>> > at all. Users do not have to do anything, you don't have to do
> >>> > anything.
> >>> >
> >>> > If they have cordova-ios 3.x installed - ignore this warning. This
> >>> > plugin wasn't meant for your platform.
> >>> >
> >>> >
> >>> >
> >>> > On Tue, Sep 29, 2015 at 5:37 PM, Nikhil Khandelwal
> >>> > <ni...@microsoft.com> wrote:
> >>> >> I think the first version of the whitelist plugin was released
> without
> >>> the corodva-ios 4.0 check, so that developers do not see this warning
> >>> because cordova-ios 4.0 was not released. I agree with Tommy, that the
> >>> wording of the warning seems to suggest there is a way for me to fix
> this
> >>> issue:
> >>> >> "Plugin doesn't support this project's cordova-ios version.
> >>> cordova-ios: 3.9.1, failed version requirement: >=4.0.0-dev."
> >>> >>
> >>> >> However, with this plugin we do not have a way to fix it because ios
> >>> 4.0 is not released.
> >>> >>
> >>> >> I suggest we do the following:
> >>> >> - Unpublish the version that has a dependency on ios 4.x
> >>> >> - Release cordova-plugin-whitelist v2 which has an ios 4.x depdency
> >>> >> - In the tools release, that pins cordova-ios 4.x we should ship a
> >>> cordova-app-hello-world template that targets v2 of this plugin.
> >>> >>
> >>> >> Thanks,
> >>> >> Nikhil
> >>> >>
> >>> >> -----Original Message-----
> >>> >> From: Shazron [mailto:shazron@gmail.com]
> >>> >> Sent: Tuesday, September 29, 2015 5:28 PM
> >>> >> To: dev@cordova.apache.org
> >>> >> Subject: Re: cordova-plugin-whitelist ios issue
> >>> >>
> >>> >> This is only happening because we have two engine requirements -
> >>> cordova-android 4.x and cordova-ios 4.x. This is correct for
> >>> cordova-plugin-whitelist.
> >>> >>
> >>> >> Like I mentioned before, cordova-android+ios 3.x *do not* require
> this
> >>> plugin as it is built in. Perhaps this could be communicated better,
> but
> >>> the warning is generic, and there's no way to communicate this in an
> >>> <engine> tag.
> >>> >>
> >>> >> We could release core plugins that have different core platform
> >>> version requirements as well in the future (like android 5 plugin
> >>> >> changes) and this will occur again.
> >>> >>
> >>> >>
> >>> >> On Tue, Sep 29, 2015 at 5:21 PM, Shazron <sh...@gmail.com> wrote:
> >>> >>> "IMO we should never release a plugin which always emits a warning
> >>> >>> that cannot be resolved."
> >>> >>>
> >>> >>> There is nothing to resolve. The resolution is to ignore it. It's
> >>> >>> supposed to warn you, as it is working as expected.
> >>> >>>
> >>> >>> On Tue, Sep 29, 2015 at 5:19 PM, Nikhil Khandelwal
> >>> >>> <ni...@microsoft.com> wrote:
> >>> >>>> I understand the warning w.r.t. plugins and android 5.0 as we will
> >>> release android 5.0 along with the plugin update and there would be a
> path
> >>> for people to resolve the warning.
> >>> >>>>
> >>> >>>> In this case, ios 4.0 is not even released and users have no way
> to
> >>> work around this warning. We're getting feedback from customers about
> this.
> >>> >>>>
> >>> >>>> IMO we should never release a plugin which always emits a warning
> >>> that cannot be resolved.
> >>> >>>>
> >>> >>>> -Nikhil
> >>> >>>>
> >>> >>>> -----Original Message-----
> >>> >>>> From: Shazron [mailto:shazron@gmail.com]
> >>> >>>> Sent: Tuesday, September 29, 2015 5:17 PM
> >>> >>>> To: dev@cordova.apache.org
> >>> >>>> Subject: Re: cordova-plugin-whitelist ios issue
> >>> >>>>
> >>> >>>> No its not a "rogue version". cordova-plugin-whitelist requires
> >>> cordova-ios 4.0 and cordova-android 4.0.
> >>> >>>> It's just a warning and is expected to work this way.
> >>> >>>>
> >>> https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fgith
> >>> >>>> ub.com
> >>> %2fapache%2fcordova-plugin-whitelist%2fblob%2fmaster%2fREADME.m
> >>> >>>> d&data=01%7c01%7cnikhilkh%40microsoft.com
> >>> %7cd638675115ae4fa7be2d08d2c
> >>> >>>>
> 92c9d89%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=iO9NDS0BgD53OVED
> >>> >>>> yxGv0zNW5SKXLVK0loo8ZAEmfOM%3d
> >>> >>>>
> >>> >>>> On Tue, Sep 29, 2015 at 5:08 PM, Nikhil Khandelwal <
> >>> nikhilkh@microsoft.com> wrote:
> >>> >>>>> 1.       cordova create test
> >>> >>>>>
> >>> >>>>> 2.       cordova platform add ios
> >>> >>>>>
> >>> >>>>> WARNING: Applications for platform ios can not be built on this
> OS
> >>> - win32.
> >>> >>>>> Adding ios project...
> >>> >>>>> iOS project created with cordova-ios@3.9.1 Discovered plugin
> >>> >>>>> "cordova-plugin-whitelist" in config.xml. Installing to the
> project
> >>> >>>>> Fetching plugin "cordova-plugin-whitelist@1" via npm Installing
> >>> >>>>> "cordova-plugin-whitelist" for ios Plugin doesn't support this
> >>> >>>>> project's cordova-ios version. cordova-ios: 3.9.1, failed version
> >>> >>>>> requirement: >=4.0.0-dev Skipping 'cordova-plugin-whitelist' for
> ios
> >>> >>>>> Installing "cordova-plugin-whitelist" for ios Plugin doesn't
> support
> >>> >>>>> this project's cordova-ios version. cordova-ios: 3.9.1, failed
> >>> >>>>> version
> >>> >>>>> requirement: >=4.0.0-dev Skipping 'cordova-plugin-whitelist' for
> ios
> >>> >>>>>
> >>> >>>>> Looks like we have a rogue version of cordova-plugin-whitelist
> >>> published that requires iOS 4.0.0. What's the best way to fix it? Can
> we
> >>> unpublish this whitelist plugin version from npm to fix this?
> >>> Alternatively, we should release another version of the plugin that
> does
> >>> not get this warning. It's misleading and confusing for developers to
> see
> >>> this warning.
> >>> >>>>>
> >>> >>>>> Thanks,
> >>> >>>>> Nikhil
> >>> >>>>
> >>> >>>>
> ---------------------------------------------------------------------
> >>> >>>> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> >>> >>>> For additional commands, e-mail: dev-help@cordova.apache.org
> >>> >>>>
> >>> >>>>
> >>> >>>>
> ---------------------------------------------------------------------
> >>> >>>> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> >>> >>>> For additional commands, e-mail: dev-help@cordova.apache.org
> >>> >>
> >>> >>
> ---------------------------------------------------------------------
> >>> >> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> >>> >> For additional commands, e-mail: dev-help@cordova.apache.org
> >>> >>
> >>> >>
> >>> >>
> ---------------------------------------------------------------------
> >>> >> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> >>> >> For additional commands, e-mail: dev-help@cordova.apache.org
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> >>> For additional commands, e-mail: dev-help@cordova.apache.org
> >>>
> >>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> For additional commands, e-mail: dev-help@cordova.apache.org
>
>

Re: cordova-plugin-whitelist ios issue

Posted by Shazron <sh...@gmail.com>.
-1.
We can just update the dist-tag so @latest goes to a previous version.
All released versions have been voted on, so its a matter of dist-tag
carousel.



On Tue, Sep 29, 2015 at 7:31 PM, Carlos Santana <cs...@gmail.com> wrote:
> In summary I proposed that we update the plugin with a version that only
> contains the android code.
> When we publish cordova-ios@4.0.0 then we publish a new version that
> contains the ios code and contains engine tag stating that it needs minimum
> cordova-ios@4.0.0
>
> I'm OK if you want to have two branches to make it clear to devs, 1.x it
> contains android only, branch 2.x contains both android and ios.
>
>
> On Tue, Sep 29, 2015 at 10:26 PM Carlos Santana <cs...@gmail.com>
> wrote:
>
>> Here are my two cents, and I'm aware of the situation.
>>
>> publish a new version of cordova-plugin-whitelist  that only contains the
>> android code and only supports android platform (means to remove any ios
>> code from the plugin)
>>
>> Currently the plugin is public and published on npm as latest, and it
>> states in the README:
>>
>>    - Android 4.0.0 or above
>>    - iOS 4.0.0 or above
>>
>> Guess what iOS 4.0.0 is it doesn't exist, it's not out, it's not born yet.
>> I guess you get the picture. The day that cordova-ios@4.0.0 get's
>> published to npm is the day that it exist, then is valid to published
>> plugins that depend on that version of the platform.
>>
>> The day we published cordova-ios@4.0.0 to npm, on the same day we publish
>> cordova-plugin-whitelist that has code for ios and depends on
>> cordova-ios@4.0.0
>>
>> In general to my eyes we should NOT published plugins that depends (i.e.
>> engines) depend on a version of a component that it's not born yet.
>>
>>
>>
>> On Tue, Sep 29, 2015 at 8:57 PM Shazron <sh...@gmail.com> wrote:
>>
>>> This has nothing to do with cordova-ios being released. Think of it
>>> solely by the plugin's requirements: it requires cordova-android 4,
>>> and cordova-ios 4. I have cordova-android 4, so it installs. I have
>>> cordova-ios 3.9 so it doesn't, and it warns me.
>>>
>>> We *will* have this problem later with plugins, guaranteed, we should
>>> not try to hide this problem for our own convenience.
>>>
>>> Let's say we took out this engine requirement, and they installed the
>>> plugin on cordova-ios 3.9. Hey the warning goes away, great! But this
>>> is a huge problem, because the code will be installed and it wasn't
>>> meant for your platform, and will probably cause bugs. It is dependent
>>> of a platform version for a reason.
>>>
>>>
>>> On Tue, Sep 29, 2015 at 5:49 PM, Shazron <sh...@gmail.com> wrote:
>>> > I don't agree.
>>> >
>>> > I still don't think you understand the issue. I realize you want to
>>> > get "rid of the warnings" but there is really nothing to fix. Nothing
>>> > at all. Users do not have to do anything, you don't have to do
>>> > anything.
>>> >
>>> > If they have cordova-ios 3.x installed - ignore this warning. This
>>> > plugin wasn't meant for your platform.
>>> >
>>> >
>>> >
>>> > On Tue, Sep 29, 2015 at 5:37 PM, Nikhil Khandelwal
>>> > <ni...@microsoft.com> wrote:
>>> >> I think the first version of the whitelist plugin was released without
>>> the corodva-ios 4.0 check, so that developers do not see this warning
>>> because cordova-ios 4.0 was not released. I agree with Tommy, that the
>>> wording of the warning seems to suggest there is a way for me to fix this
>>> issue:
>>> >> "Plugin doesn't support this project's cordova-ios version.
>>> cordova-ios: 3.9.1, failed version requirement: >=4.0.0-dev."
>>> >>
>>> >> However, with this plugin we do not have a way to fix it because ios
>>> 4.0 is not released.
>>> >>
>>> >> I suggest we do the following:
>>> >> - Unpublish the version that has a dependency on ios 4.x
>>> >> - Release cordova-plugin-whitelist v2 which has an ios 4.x depdency
>>> >> - In the tools release, that pins cordova-ios 4.x we should ship a
>>> cordova-app-hello-world template that targets v2 of this plugin.
>>> >>
>>> >> Thanks,
>>> >> Nikhil
>>> >>
>>> >> -----Original Message-----
>>> >> From: Shazron [mailto:shazron@gmail.com]
>>> >> Sent: Tuesday, September 29, 2015 5:28 PM
>>> >> To: dev@cordova.apache.org
>>> >> Subject: Re: cordova-plugin-whitelist ios issue
>>> >>
>>> >> This is only happening because we have two engine requirements -
>>> cordova-android 4.x and cordova-ios 4.x. This is correct for
>>> cordova-plugin-whitelist.
>>> >>
>>> >> Like I mentioned before, cordova-android+ios 3.x *do not* require this
>>> plugin as it is built in. Perhaps this could be communicated better, but
>>> the warning is generic, and there's no way to communicate this in an
>>> <engine> tag.
>>> >>
>>> >> We could release core plugins that have different core platform
>>> version requirements as well in the future (like android 5 plugin
>>> >> changes) and this will occur again.
>>> >>
>>> >>
>>> >> On Tue, Sep 29, 2015 at 5:21 PM, Shazron <sh...@gmail.com> wrote:
>>> >>> "IMO we should never release a plugin which always emits a warning
>>> >>> that cannot be resolved."
>>> >>>
>>> >>> There is nothing to resolve. The resolution is to ignore it. It's
>>> >>> supposed to warn you, as it is working as expected.
>>> >>>
>>> >>> On Tue, Sep 29, 2015 at 5:19 PM, Nikhil Khandelwal
>>> >>> <ni...@microsoft.com> wrote:
>>> >>>> I understand the warning w.r.t. plugins and android 5.0 as we will
>>> release android 5.0 along with the plugin update and there would be a path
>>> for people to resolve the warning.
>>> >>>>
>>> >>>> In this case, ios 4.0 is not even released and users have no way to
>>> work around this warning. We're getting feedback from customers about this.
>>> >>>>
>>> >>>> IMO we should never release a plugin which always emits a warning
>>> that cannot be resolved.
>>> >>>>
>>> >>>> -Nikhil
>>> >>>>
>>> >>>> -----Original Message-----
>>> >>>> From: Shazron [mailto:shazron@gmail.com]
>>> >>>> Sent: Tuesday, September 29, 2015 5:17 PM
>>> >>>> To: dev@cordova.apache.org
>>> >>>> Subject: Re: cordova-plugin-whitelist ios issue
>>> >>>>
>>> >>>> No its not a "rogue version". cordova-plugin-whitelist requires
>>> cordova-ios 4.0 and cordova-android 4.0.
>>> >>>> It's just a warning and is expected to work this way.
>>> >>>>
>>> https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fgith
>>> >>>> ub.com
>>> %2fapache%2fcordova-plugin-whitelist%2fblob%2fmaster%2fREADME.m
>>> >>>> d&data=01%7c01%7cnikhilkh%40microsoft.com
>>> %7cd638675115ae4fa7be2d08d2c
>>> >>>> 92c9d89%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=iO9NDS0BgD53OVED
>>> >>>> yxGv0zNW5SKXLVK0loo8ZAEmfOM%3d
>>> >>>>
>>> >>>> On Tue, Sep 29, 2015 at 5:08 PM, Nikhil Khandelwal <
>>> nikhilkh@microsoft.com> wrote:
>>> >>>>> 1.       cordova create test
>>> >>>>>
>>> >>>>> 2.       cordova platform add ios
>>> >>>>>
>>> >>>>> WARNING: Applications for platform ios can not be built on this OS
>>> - win32.
>>> >>>>> Adding ios project...
>>> >>>>> iOS project created with cordova-ios@3.9.1 Discovered plugin
>>> >>>>> "cordova-plugin-whitelist" in config.xml. Installing to the project
>>> >>>>> Fetching plugin "cordova-plugin-whitelist@1" via npm Installing
>>> >>>>> "cordova-plugin-whitelist" for ios Plugin doesn't support this
>>> >>>>> project's cordova-ios version. cordova-ios: 3.9.1, failed version
>>> >>>>> requirement: >=4.0.0-dev Skipping 'cordova-plugin-whitelist' for ios
>>> >>>>> Installing "cordova-plugin-whitelist" for ios Plugin doesn't support
>>> >>>>> this project's cordova-ios version. cordova-ios: 3.9.1, failed
>>> >>>>> version
>>> >>>>> requirement: >=4.0.0-dev Skipping 'cordova-plugin-whitelist' for ios
>>> >>>>>
>>> >>>>> Looks like we have a rogue version of cordova-plugin-whitelist
>>> published that requires iOS 4.0.0. What's the best way to fix it? Can we
>>> unpublish this whitelist plugin version from npm to fix this?
>>> Alternatively, we should release another version of the plugin that does
>>> not get this warning. It's misleading and confusing for developers to see
>>> this warning.
>>> >>>>>
>>> >>>>> Thanks,
>>> >>>>> Nikhil
>>> >>>>
>>> >>>> ---------------------------------------------------------------------
>>> >>>> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
>>> >>>> For additional commands, e-mail: dev-help@cordova.apache.org
>>> >>>>
>>> >>>>
>>> >>>> ---------------------------------------------------------------------
>>> >>>> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
>>> >>>> For additional commands, e-mail: dev-help@cordova.apache.org
>>> >>
>>> >> ---------------------------------------------------------------------
>>> >> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
>>> >> For additional commands, e-mail: dev-help@cordova.apache.org
>>> >>
>>> >>
>>> >> ---------------------------------------------------------------------
>>> >> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
>>> >> For additional commands, e-mail: dev-help@cordova.apache.org
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
>>> For additional commands, e-mail: dev-help@cordova.apache.org
>>>
>>>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
For additional commands, e-mail: dev-help@cordova.apache.org

Re: cordova-plugin-whitelist ios issue

Posted by Carlos Santana <cs...@gmail.com>.
In summary I proposed that we update the plugin with a version that only
contains the android code.
When we publish cordova-ios@4.0.0 then we publish a new version that
contains the ios code and contains engine tag stating that it needs minimum
cordova-ios@4.0.0

I'm OK if you want to have two branches to make it clear to devs, 1.x it
contains android only, branch 2.x contains both android and ios.


On Tue, Sep 29, 2015 at 10:26 PM Carlos Santana <cs...@gmail.com>
wrote:

> Here are my two cents, and I'm aware of the situation.
>
> publish a new version of cordova-plugin-whitelist  that only contains the
> android code and only supports android platform (means to remove any ios
> code from the plugin)
>
> Currently the plugin is public and published on npm as latest, and it
> states in the README:
>
>    - Android 4.0.0 or above
>    - iOS 4.0.0 or above
>
> Guess what iOS 4.0.0 is it doesn't exist, it's not out, it's not born yet.
> I guess you get the picture. The day that cordova-ios@4.0.0 get's
> published to npm is the day that it exist, then is valid to published
> plugins that depend on that version of the platform.
>
> The day we published cordova-ios@4.0.0 to npm, on the same day we publish
> cordova-plugin-whitelist that has code for ios and depends on
> cordova-ios@4.0.0
>
> In general to my eyes we should NOT published plugins that depends (i.e.
> engines) depend on a version of a component that it's not born yet.
>
>
>
> On Tue, Sep 29, 2015 at 8:57 PM Shazron <sh...@gmail.com> wrote:
>
>> This has nothing to do with cordova-ios being released. Think of it
>> solely by the plugin's requirements: it requires cordova-android 4,
>> and cordova-ios 4. I have cordova-android 4, so it installs. I have
>> cordova-ios 3.9 so it doesn't, and it warns me.
>>
>> We *will* have this problem later with plugins, guaranteed, we should
>> not try to hide this problem for our own convenience.
>>
>> Let's say we took out this engine requirement, and they installed the
>> plugin on cordova-ios 3.9. Hey the warning goes away, great! But this
>> is a huge problem, because the code will be installed and it wasn't
>> meant for your platform, and will probably cause bugs. It is dependent
>> of a platform version for a reason.
>>
>>
>> On Tue, Sep 29, 2015 at 5:49 PM, Shazron <sh...@gmail.com> wrote:
>> > I don't agree.
>> >
>> > I still don't think you understand the issue. I realize you want to
>> > get "rid of the warnings" but there is really nothing to fix. Nothing
>> > at all. Users do not have to do anything, you don't have to do
>> > anything.
>> >
>> > If they have cordova-ios 3.x installed - ignore this warning. This
>> > plugin wasn't meant for your platform.
>> >
>> >
>> >
>> > On Tue, Sep 29, 2015 at 5:37 PM, Nikhil Khandelwal
>> > <ni...@microsoft.com> wrote:
>> >> I think the first version of the whitelist plugin was released without
>> the corodva-ios 4.0 check, so that developers do not see this warning
>> because cordova-ios 4.0 was not released. I agree with Tommy, that the
>> wording of the warning seems to suggest there is a way for me to fix this
>> issue:
>> >> "Plugin doesn't support this project's cordova-ios version.
>> cordova-ios: 3.9.1, failed version requirement: >=4.0.0-dev."
>> >>
>> >> However, with this plugin we do not have a way to fix it because ios
>> 4.0 is not released.
>> >>
>> >> I suggest we do the following:
>> >> - Unpublish the version that has a dependency on ios 4.x
>> >> - Release cordova-plugin-whitelist v2 which has an ios 4.x depdency
>> >> - In the tools release, that pins cordova-ios 4.x we should ship a
>> cordova-app-hello-world template that targets v2 of this plugin.
>> >>
>> >> Thanks,
>> >> Nikhil
>> >>
>> >> -----Original Message-----
>> >> From: Shazron [mailto:shazron@gmail.com]
>> >> Sent: Tuesday, September 29, 2015 5:28 PM
>> >> To: dev@cordova.apache.org
>> >> Subject: Re: cordova-plugin-whitelist ios issue
>> >>
>> >> This is only happening because we have two engine requirements -
>> cordova-android 4.x and cordova-ios 4.x. This is correct for
>> cordova-plugin-whitelist.
>> >>
>> >> Like I mentioned before, cordova-android+ios 3.x *do not* require this
>> plugin as it is built in. Perhaps this could be communicated better, but
>> the warning is generic, and there's no way to communicate this in an
>> <engine> tag.
>> >>
>> >> We could release core plugins that have different core platform
>> version requirements as well in the future (like android 5 plugin
>> >> changes) and this will occur again.
>> >>
>> >>
>> >> On Tue, Sep 29, 2015 at 5:21 PM, Shazron <sh...@gmail.com> wrote:
>> >>> "IMO we should never release a plugin which always emits a warning
>> >>> that cannot be resolved."
>> >>>
>> >>> There is nothing to resolve. The resolution is to ignore it. It's
>> >>> supposed to warn you, as it is working as expected.
>> >>>
>> >>> On Tue, Sep 29, 2015 at 5:19 PM, Nikhil Khandelwal
>> >>> <ni...@microsoft.com> wrote:
>> >>>> I understand the warning w.r.t. plugins and android 5.0 as we will
>> release android 5.0 along with the plugin update and there would be a path
>> for people to resolve the warning.
>> >>>>
>> >>>> In this case, ios 4.0 is not even released and users have no way to
>> work around this warning. We're getting feedback from customers about this.
>> >>>>
>> >>>> IMO we should never release a plugin which always emits a warning
>> that cannot be resolved.
>> >>>>
>> >>>> -Nikhil
>> >>>>
>> >>>> -----Original Message-----
>> >>>> From: Shazron [mailto:shazron@gmail.com]
>> >>>> Sent: Tuesday, September 29, 2015 5:17 PM
>> >>>> To: dev@cordova.apache.org
>> >>>> Subject: Re: cordova-plugin-whitelist ios issue
>> >>>>
>> >>>> No its not a "rogue version". cordova-plugin-whitelist requires
>> cordova-ios 4.0 and cordova-android 4.0.
>> >>>> It's just a warning and is expected to work this way.
>> >>>>
>> https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fgith
>> >>>> ub.com
>> %2fapache%2fcordova-plugin-whitelist%2fblob%2fmaster%2fREADME.m
>> >>>> d&data=01%7c01%7cnikhilkh%40microsoft.com
>> %7cd638675115ae4fa7be2d08d2c
>> >>>> 92c9d89%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=iO9NDS0BgD53OVED
>> >>>> yxGv0zNW5SKXLVK0loo8ZAEmfOM%3d
>> >>>>
>> >>>> On Tue, Sep 29, 2015 at 5:08 PM, Nikhil Khandelwal <
>> nikhilkh@microsoft.com> wrote:
>> >>>>> 1.       cordova create test
>> >>>>>
>> >>>>> 2.       cordova platform add ios
>> >>>>>
>> >>>>> WARNING: Applications for platform ios can not be built on this OS
>> - win32.
>> >>>>> Adding ios project...
>> >>>>> iOS project created with cordova-ios@3.9.1 Discovered plugin
>> >>>>> "cordova-plugin-whitelist" in config.xml. Installing to the project
>> >>>>> Fetching plugin "cordova-plugin-whitelist@1" via npm Installing
>> >>>>> "cordova-plugin-whitelist" for ios Plugin doesn't support this
>> >>>>> project's cordova-ios version. cordova-ios: 3.9.1, failed version
>> >>>>> requirement: >=4.0.0-dev Skipping 'cordova-plugin-whitelist' for ios
>> >>>>> Installing "cordova-plugin-whitelist" for ios Plugin doesn't support
>> >>>>> this project's cordova-ios version. cordova-ios: 3.9.1, failed
>> >>>>> version
>> >>>>> requirement: >=4.0.0-dev Skipping 'cordova-plugin-whitelist' for ios
>> >>>>>
>> >>>>> Looks like we have a rogue version of cordova-plugin-whitelist
>> published that requires iOS 4.0.0. What's the best way to fix it? Can we
>> unpublish this whitelist plugin version from npm to fix this?
>> Alternatively, we should release another version of the plugin that does
>> not get this warning. It's misleading and confusing for developers to see
>> this warning.
>> >>>>>
>> >>>>> Thanks,
>> >>>>> Nikhil
>> >>>>
>> >>>> ---------------------------------------------------------------------
>> >>>> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
>> >>>> For additional commands, e-mail: dev-help@cordova.apache.org
>> >>>>
>> >>>>
>> >>>> ---------------------------------------------------------------------
>> >>>> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
>> >>>> For additional commands, e-mail: dev-help@cordova.apache.org
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
>> >> For additional commands, e-mail: dev-help@cordova.apache.org
>> >>
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
>> >> For additional commands, e-mail: dev-help@cordova.apache.org
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
>> For additional commands, e-mail: dev-help@cordova.apache.org
>>
>>

Re: cordova-plugin-whitelist ios issue

Posted by Carlos Santana <cs...@gmail.com>.
Here are my two cents, and I'm aware of the situation.

publish a new version of cordova-plugin-whitelist  that only contains the
android code and only supports android platform (means to remove any ios
code from the plugin)

Currently the plugin is public and published on npm as latest, and it
states in the README:

   - Android 4.0.0 or above
   - iOS 4.0.0 or above

Guess what iOS 4.0.0 is it doesn't exist, it's not out, it's not born yet.
I guess you get the picture. The day that cordova-ios@4.0.0 get's published
to npm is the day that it exist, then is valid to published plugins that
depend on that version of the platform.

The day we published cordova-ios@4.0.0 to npm, on the same day we publish
cordova-plugin-whitelist that has code for ios and depends on
cordova-ios@4.0.0

In general to my eyes we should NOT published plugins that depends (i.e.
engines) depend on a version of a component that it's not born yet.



On Tue, Sep 29, 2015 at 8:57 PM Shazron <sh...@gmail.com> wrote:

> This has nothing to do with cordova-ios being released. Think of it
> solely by the plugin's requirements: it requires cordova-android 4,
> and cordova-ios 4. I have cordova-android 4, so it installs. I have
> cordova-ios 3.9 so it doesn't, and it warns me.
>
> We *will* have this problem later with plugins, guaranteed, we should
> not try to hide this problem for our own convenience.
>
> Let's say we took out this engine requirement, and they installed the
> plugin on cordova-ios 3.9. Hey the warning goes away, great! But this
> is a huge problem, because the code will be installed and it wasn't
> meant for your platform, and will probably cause bugs. It is dependent
> of a platform version for a reason.
>
>
> On Tue, Sep 29, 2015 at 5:49 PM, Shazron <sh...@gmail.com> wrote:
> > I don't agree.
> >
> > I still don't think you understand the issue. I realize you want to
> > get "rid of the warnings" but there is really nothing to fix. Nothing
> > at all. Users do not have to do anything, you don't have to do
> > anything.
> >
> > If they have cordova-ios 3.x installed - ignore this warning. This
> > plugin wasn't meant for your platform.
> >
> >
> >
> > On Tue, Sep 29, 2015 at 5:37 PM, Nikhil Khandelwal
> > <ni...@microsoft.com> wrote:
> >> I think the first version of the whitelist plugin was released without
> the corodva-ios 4.0 check, so that developers do not see this warning
> because cordova-ios 4.0 was not released. I agree with Tommy, that the
> wording of the warning seems to suggest there is a way for me to fix this
> issue:
> >> "Plugin doesn't support this project's cordova-ios version.
> cordova-ios: 3.9.1, failed version requirement: >=4.0.0-dev."
> >>
> >> However, with this plugin we do not have a way to fix it because ios
> 4.0 is not released.
> >>
> >> I suggest we do the following:
> >> - Unpublish the version that has a dependency on ios 4.x
> >> - Release cordova-plugin-whitelist v2 which has an ios 4.x depdency
> >> - In the tools release, that pins cordova-ios 4.x we should ship a
> cordova-app-hello-world template that targets v2 of this plugin.
> >>
> >> Thanks,
> >> Nikhil
> >>
> >> -----Original Message-----
> >> From: Shazron [mailto:shazron@gmail.com]
> >> Sent: Tuesday, September 29, 2015 5:28 PM
> >> To: dev@cordova.apache.org
> >> Subject: Re: cordova-plugin-whitelist ios issue
> >>
> >> This is only happening because we have two engine requirements -
> cordova-android 4.x and cordova-ios 4.x. This is correct for
> cordova-plugin-whitelist.
> >>
> >> Like I mentioned before, cordova-android+ios 3.x *do not* require this
> plugin as it is built in. Perhaps this could be communicated better, but
> the warning is generic, and there's no way to communicate this in an
> <engine> tag.
> >>
> >> We could release core plugins that have different core platform version
> requirements as well in the future (like android 5 plugin
> >> changes) and this will occur again.
> >>
> >>
> >> On Tue, Sep 29, 2015 at 5:21 PM, Shazron <sh...@gmail.com> wrote:
> >>> "IMO we should never release a plugin which always emits a warning
> >>> that cannot be resolved."
> >>>
> >>> There is nothing to resolve. The resolution is to ignore it. It's
> >>> supposed to warn you, as it is working as expected.
> >>>
> >>> On Tue, Sep 29, 2015 at 5:19 PM, Nikhil Khandelwal
> >>> <ni...@microsoft.com> wrote:
> >>>> I understand the warning w.r.t. plugins and android 5.0 as we will
> release android 5.0 along with the plugin update and there would be a path
> for people to resolve the warning.
> >>>>
> >>>> In this case, ios 4.0 is not even released and users have no way to
> work around this warning. We're getting feedback from customers about this.
> >>>>
> >>>> IMO we should never release a plugin which always emits a warning
> that cannot be resolved.
> >>>>
> >>>> -Nikhil
> >>>>
> >>>> -----Original Message-----
> >>>> From: Shazron [mailto:shazron@gmail.com]
> >>>> Sent: Tuesday, September 29, 2015 5:17 PM
> >>>> To: dev@cordova.apache.org
> >>>> Subject: Re: cordova-plugin-whitelist ios issue
> >>>>
> >>>> No its not a "rogue version". cordova-plugin-whitelist requires
> cordova-ios 4.0 and cordova-android 4.0.
> >>>> It's just a warning and is expected to work this way.
> >>>> https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fgith
> >>>> ub.com%2fapache%2fcordova-plugin-whitelist%2fblob%2fmaster%2fREADME.m
> >>>> d&data=01%7c01%7cnikhilkh%40microsoft.com%7cd638675115ae4fa7be2d08d2c
> >>>> 92c9d89%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=iO9NDS0BgD53OVED
> >>>> yxGv0zNW5SKXLVK0loo8ZAEmfOM%3d
> >>>>
> >>>> On Tue, Sep 29, 2015 at 5:08 PM, Nikhil Khandelwal <
> nikhilkh@microsoft.com> wrote:
> >>>>> 1.       cordova create test
> >>>>>
> >>>>> 2.       cordova platform add ios
> >>>>>
> >>>>> WARNING: Applications for platform ios can not be built on this OS -
> win32.
> >>>>> Adding ios project...
> >>>>> iOS project created with cordova-ios@3.9.1 Discovered plugin
> >>>>> "cordova-plugin-whitelist" in config.xml. Installing to the project
> >>>>> Fetching plugin "cordova-plugin-whitelist@1" via npm Installing
> >>>>> "cordova-plugin-whitelist" for ios Plugin doesn't support this
> >>>>> project's cordova-ios version. cordova-ios: 3.9.1, failed version
> >>>>> requirement: >=4.0.0-dev Skipping 'cordova-plugin-whitelist' for ios
> >>>>> Installing "cordova-plugin-whitelist" for ios Plugin doesn't support
> >>>>> this project's cordova-ios version. cordova-ios: 3.9.1, failed
> >>>>> version
> >>>>> requirement: >=4.0.0-dev Skipping 'cordova-plugin-whitelist' for ios
> >>>>>
> >>>>> Looks like we have a rogue version of cordova-plugin-whitelist
> published that requires iOS 4.0.0. What's the best way to fix it? Can we
> unpublish this whitelist plugin version from npm to fix this?
> Alternatively, we should release another version of the plugin that does
> not get this warning. It's misleading and confusing for developers to see
> this warning.
> >>>>>
> >>>>> Thanks,
> >>>>> Nikhil
> >>>>
> >>>> ---------------------------------------------------------------------
> >>>> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> >>>> For additional commands, e-mail: dev-help@cordova.apache.org
> >>>>
> >>>>
> >>>> ---------------------------------------------------------------------
> >>>> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> >>>> For additional commands, e-mail: dev-help@cordova.apache.org
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> >> For additional commands, e-mail: dev-help@cordova.apache.org
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> >> For additional commands, e-mail: dev-help@cordova.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> For additional commands, e-mail: dev-help@cordova.apache.org
>
>

Re: cordova-plugin-whitelist ios issue

Posted by Shazron <sh...@gmail.com>.
This has nothing to do with cordova-ios being released. Think of it
solely by the plugin's requirements: it requires cordova-android 4,
and cordova-ios 4. I have cordova-android 4, so it installs. I have
cordova-ios 3.9 so it doesn't, and it warns me.

We *will* have this problem later with plugins, guaranteed, we should
not try to hide this problem for our own convenience.

Let's say we took out this engine requirement, and they installed the
plugin on cordova-ios 3.9. Hey the warning goes away, great! But this
is a huge problem, because the code will be installed and it wasn't
meant for your platform, and will probably cause bugs. It is dependent
of a platform version for a reason.


On Tue, Sep 29, 2015 at 5:49 PM, Shazron <sh...@gmail.com> wrote:
> I don't agree.
>
> I still don't think you understand the issue. I realize you want to
> get "rid of the warnings" but there is really nothing to fix. Nothing
> at all. Users do not have to do anything, you don't have to do
> anything.
>
> If they have cordova-ios 3.x installed - ignore this warning. This
> plugin wasn't meant for your platform.
>
>
>
> On Tue, Sep 29, 2015 at 5:37 PM, Nikhil Khandelwal
> <ni...@microsoft.com> wrote:
>> I think the first version of the whitelist plugin was released without the corodva-ios 4.0 check, so that developers do not see this warning because cordova-ios 4.0 was not released. I agree with Tommy, that the wording of the warning seems to suggest there is a way for me to fix this issue:
>> "Plugin doesn't support this project's cordova-ios version. cordova-ios: 3.9.1, failed version requirement: >=4.0.0-dev."
>>
>> However, with this plugin we do not have a way to fix it because ios 4.0 is not released.
>>
>> I suggest we do the following:
>> - Unpublish the version that has a dependency on ios 4.x
>> - Release cordova-plugin-whitelist v2 which has an ios 4.x depdency
>> - In the tools release, that pins cordova-ios 4.x we should ship a cordova-app-hello-world template that targets v2 of this plugin.
>>
>> Thanks,
>> Nikhil
>>
>> -----Original Message-----
>> From: Shazron [mailto:shazron@gmail.com]
>> Sent: Tuesday, September 29, 2015 5:28 PM
>> To: dev@cordova.apache.org
>> Subject: Re: cordova-plugin-whitelist ios issue
>>
>> This is only happening because we have two engine requirements - cordova-android 4.x and cordova-ios 4.x. This is correct for cordova-plugin-whitelist.
>>
>> Like I mentioned before, cordova-android+ios 3.x *do not* require this plugin as it is built in. Perhaps this could be communicated better, but the warning is generic, and there's no way to communicate this in an <engine> tag.
>>
>> We could release core plugins that have different core platform version requirements as well in the future (like android 5 plugin
>> changes) and this will occur again.
>>
>>
>> On Tue, Sep 29, 2015 at 5:21 PM, Shazron <sh...@gmail.com> wrote:
>>> "IMO we should never release a plugin which always emits a warning
>>> that cannot be resolved."
>>>
>>> There is nothing to resolve. The resolution is to ignore it. It's
>>> supposed to warn you, as it is working as expected.
>>>
>>> On Tue, Sep 29, 2015 at 5:19 PM, Nikhil Khandelwal
>>> <ni...@microsoft.com> wrote:
>>>> I understand the warning w.r.t. plugins and android 5.0 as we will release android 5.0 along with the plugin update and there would be a path for people to resolve the warning.
>>>>
>>>> In this case, ios 4.0 is not even released and users have no way to work around this warning. We're getting feedback from customers about this.
>>>>
>>>> IMO we should never release a plugin which always emits a warning that cannot be resolved.
>>>>
>>>> -Nikhil
>>>>
>>>> -----Original Message-----
>>>> From: Shazron [mailto:shazron@gmail.com]
>>>> Sent: Tuesday, September 29, 2015 5:17 PM
>>>> To: dev@cordova.apache.org
>>>> Subject: Re: cordova-plugin-whitelist ios issue
>>>>
>>>> No its not a "rogue version". cordova-plugin-whitelist requires cordova-ios 4.0 and cordova-android 4.0.
>>>> It's just a warning and is expected to work this way.
>>>> https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fgith
>>>> ub.com%2fapache%2fcordova-plugin-whitelist%2fblob%2fmaster%2fREADME.m
>>>> d&data=01%7c01%7cnikhilkh%40microsoft.com%7cd638675115ae4fa7be2d08d2c
>>>> 92c9d89%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=iO9NDS0BgD53OVED
>>>> yxGv0zNW5SKXLVK0loo8ZAEmfOM%3d
>>>>
>>>> On Tue, Sep 29, 2015 at 5:08 PM, Nikhil Khandelwal <ni...@microsoft.com> wrote:
>>>>> 1.       cordova create test
>>>>>
>>>>> 2.       cordova platform add ios
>>>>>
>>>>> WARNING: Applications for platform ios can not be built on this OS - win32.
>>>>> Adding ios project...
>>>>> iOS project created with cordova-ios@3.9.1 Discovered plugin
>>>>> "cordova-plugin-whitelist" in config.xml. Installing to the project
>>>>> Fetching plugin "cordova-plugin-whitelist@1" via npm Installing
>>>>> "cordova-plugin-whitelist" for ios Plugin doesn't support this
>>>>> project's cordova-ios version. cordova-ios: 3.9.1, failed version
>>>>> requirement: >=4.0.0-dev Skipping 'cordova-plugin-whitelist' for ios
>>>>> Installing "cordova-plugin-whitelist" for ios Plugin doesn't support
>>>>> this project's cordova-ios version. cordova-ios: 3.9.1, failed
>>>>> version
>>>>> requirement: >=4.0.0-dev Skipping 'cordova-plugin-whitelist' for ios
>>>>>
>>>>> Looks like we have a rogue version of cordova-plugin-whitelist published that requires iOS 4.0.0. What's the best way to fix it? Can we unpublish this whitelist plugin version from npm to fix this? Alternatively, we should release another version of the plugin that does not get this warning. It's misleading and confusing for developers to see this warning.
>>>>>
>>>>> Thanks,
>>>>> Nikhil
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
>>>> For additional commands, e-mail: dev-help@cordova.apache.org
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
>>>> For additional commands, e-mail: dev-help@cordova.apache.org
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
>> For additional commands, e-mail: dev-help@cordova.apache.org
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
>> For additional commands, e-mail: dev-help@cordova.apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
For additional commands, e-mail: dev-help@cordova.apache.org

Re: cordova-plugin-whitelist ios issue

Posted by Shazron <sh...@gmail.com>.
I don't agree.

I still don't think you understand the issue. I realize you want to
get "rid of the warnings" but there is really nothing to fix. Nothing
at all. Users do not have to do anything, you don't have to do
anything.

If they have cordova-ios 3.x installed - ignore this warning. This
plugin wasn't meant for your platform.



On Tue, Sep 29, 2015 at 5:37 PM, Nikhil Khandelwal
<ni...@microsoft.com> wrote:
> I think the first version of the whitelist plugin was released without the corodva-ios 4.0 check, so that developers do not see this warning because cordova-ios 4.0 was not released. I agree with Tommy, that the wording of the warning seems to suggest there is a way for me to fix this issue:
> "Plugin doesn't support this project's cordova-ios version. cordova-ios: 3.9.1, failed version requirement: >=4.0.0-dev."
>
> However, with this plugin we do not have a way to fix it because ios 4.0 is not released.
>
> I suggest we do the following:
> - Unpublish the version that has a dependency on ios 4.x
> - Release cordova-plugin-whitelist v2 which has an ios 4.x depdency
> - In the tools release, that pins cordova-ios 4.x we should ship a cordova-app-hello-world template that targets v2 of this plugin.
>
> Thanks,
> Nikhil
>
> -----Original Message-----
> From: Shazron [mailto:shazron@gmail.com]
> Sent: Tuesday, September 29, 2015 5:28 PM
> To: dev@cordova.apache.org
> Subject: Re: cordova-plugin-whitelist ios issue
>
> This is only happening because we have two engine requirements - cordova-android 4.x and cordova-ios 4.x. This is correct for cordova-plugin-whitelist.
>
> Like I mentioned before, cordova-android+ios 3.x *do not* require this plugin as it is built in. Perhaps this could be communicated better, but the warning is generic, and there's no way to communicate this in an <engine> tag.
>
> We could release core plugins that have different core platform version requirements as well in the future (like android 5 plugin
> changes) and this will occur again.
>
>
> On Tue, Sep 29, 2015 at 5:21 PM, Shazron <sh...@gmail.com> wrote:
>> "IMO we should never release a plugin which always emits a warning
>> that cannot be resolved."
>>
>> There is nothing to resolve. The resolution is to ignore it. It's
>> supposed to warn you, as it is working as expected.
>>
>> On Tue, Sep 29, 2015 at 5:19 PM, Nikhil Khandelwal
>> <ni...@microsoft.com> wrote:
>>> I understand the warning w.r.t. plugins and android 5.0 as we will release android 5.0 along with the plugin update and there would be a path for people to resolve the warning.
>>>
>>> In this case, ios 4.0 is not even released and users have no way to work around this warning. We're getting feedback from customers about this.
>>>
>>> IMO we should never release a plugin which always emits a warning that cannot be resolved.
>>>
>>> -Nikhil
>>>
>>> -----Original Message-----
>>> From: Shazron [mailto:shazron@gmail.com]
>>> Sent: Tuesday, September 29, 2015 5:17 PM
>>> To: dev@cordova.apache.org
>>> Subject: Re: cordova-plugin-whitelist ios issue
>>>
>>> No its not a "rogue version". cordova-plugin-whitelist requires cordova-ios 4.0 and cordova-android 4.0.
>>> It's just a warning and is expected to work this way.
>>> https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fgith
>>> ub.com%2fapache%2fcordova-plugin-whitelist%2fblob%2fmaster%2fREADME.m
>>> d&data=01%7c01%7cnikhilkh%40microsoft.com%7cd638675115ae4fa7be2d08d2c
>>> 92c9d89%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=iO9NDS0BgD53OVED
>>> yxGv0zNW5SKXLVK0loo8ZAEmfOM%3d
>>>
>>> On Tue, Sep 29, 2015 at 5:08 PM, Nikhil Khandelwal <ni...@microsoft.com> wrote:
>>>> 1.       cordova create test
>>>>
>>>> 2.       cordova platform add ios
>>>>
>>>> WARNING: Applications for platform ios can not be built on this OS - win32.
>>>> Adding ios project...
>>>> iOS project created with cordova-ios@3.9.1 Discovered plugin
>>>> "cordova-plugin-whitelist" in config.xml. Installing to the project
>>>> Fetching plugin "cordova-plugin-whitelist@1" via npm Installing
>>>> "cordova-plugin-whitelist" for ios Plugin doesn't support this
>>>> project's cordova-ios version. cordova-ios: 3.9.1, failed version
>>>> requirement: >=4.0.0-dev Skipping 'cordova-plugin-whitelist' for ios
>>>> Installing "cordova-plugin-whitelist" for ios Plugin doesn't support
>>>> this project's cordova-ios version. cordova-ios: 3.9.1, failed
>>>> version
>>>> requirement: >=4.0.0-dev Skipping 'cordova-plugin-whitelist' for ios
>>>>
>>>> Looks like we have a rogue version of cordova-plugin-whitelist published that requires iOS 4.0.0. What's the best way to fix it? Can we unpublish this whitelist plugin version from npm to fix this? Alternatively, we should release another version of the plugin that does not get this warning. It's misleading and confusing for developers to see this warning.
>>>>
>>>> Thanks,
>>>> Nikhil
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
>>> For additional commands, e-mail: dev-help@cordova.apache.org
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
>>> For additional commands, e-mail: dev-help@cordova.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> For additional commands, e-mail: dev-help@cordova.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> For additional commands, e-mail: dev-help@cordova.apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
For additional commands, e-mail: dev-help@cordova.apache.org

RE: cordova-plugin-whitelist ios issue

Posted by Nikhil Khandelwal <ni...@microsoft.com>.
I think the first version of the whitelist plugin was released without the corodva-ios 4.0 check, so that developers do not see this warning because cordova-ios 4.0 was not released. I agree with Tommy, that the wording of the warning seems to suggest there is a way for me to fix this issue:
"Plugin doesn't support this project's cordova-ios version. cordova-ios: 3.9.1, failed version requirement: >=4.0.0-dev."

However, with this plugin we do not have a way to fix it because ios 4.0 is not released. 

I suggest we do the following:
- Unpublish the version that has a dependency on ios 4.x
- Release cordova-plugin-whitelist v2 which has an ios 4.x depdency
- In the tools release, that pins cordova-ios 4.x we should ship a cordova-app-hello-world template that targets v2 of this plugin.

Thanks,
Nikhil

-----Original Message-----
From: Shazron [mailto:shazron@gmail.com] 
Sent: Tuesday, September 29, 2015 5:28 PM
To: dev@cordova.apache.org
Subject: Re: cordova-plugin-whitelist ios issue

This is only happening because we have two engine requirements - cordova-android 4.x and cordova-ios 4.x. This is correct for cordova-plugin-whitelist.

Like I mentioned before, cordova-android+ios 3.x *do not* require this plugin as it is built in. Perhaps this could be communicated better, but the warning is generic, and there's no way to communicate this in an <engine> tag.

We could release core plugins that have different core platform version requirements as well in the future (like android 5 plugin
changes) and this will occur again.


On Tue, Sep 29, 2015 at 5:21 PM, Shazron <sh...@gmail.com> wrote:
> "IMO we should never release a plugin which always emits a warning 
> that cannot be resolved."
>
> There is nothing to resolve. The resolution is to ignore it. It's 
> supposed to warn you, as it is working as expected.
>
> On Tue, Sep 29, 2015 at 5:19 PM, Nikhil Khandelwal 
> <ni...@microsoft.com> wrote:
>> I understand the warning w.r.t. plugins and android 5.0 as we will release android 5.0 along with the plugin update and there would be a path for people to resolve the warning.
>>
>> In this case, ios 4.0 is not even released and users have no way to work around this warning. We're getting feedback from customers about this.
>>
>> IMO we should never release a plugin which always emits a warning that cannot be resolved.
>>
>> -Nikhil
>>
>> -----Original Message-----
>> From: Shazron [mailto:shazron@gmail.com]
>> Sent: Tuesday, September 29, 2015 5:17 PM
>> To: dev@cordova.apache.org
>> Subject: Re: cordova-plugin-whitelist ios issue
>>
>> No its not a "rogue version". cordova-plugin-whitelist requires cordova-ios 4.0 and cordova-android 4.0.
>> It's just a warning and is expected to work this way.
>> https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fgith
>> ub.com%2fapache%2fcordova-plugin-whitelist%2fblob%2fmaster%2fREADME.m
>> d&data=01%7c01%7cnikhilkh%40microsoft.com%7cd638675115ae4fa7be2d08d2c
>> 92c9d89%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=iO9NDS0BgD53OVED
>> yxGv0zNW5SKXLVK0loo8ZAEmfOM%3d
>>
>> On Tue, Sep 29, 2015 at 5:08 PM, Nikhil Khandelwal <ni...@microsoft.com> wrote:
>>> 1.       cordova create test
>>>
>>> 2.       cordova platform add ios
>>>
>>> WARNING: Applications for platform ios can not be built on this OS - win32.
>>> Adding ios project...
>>> iOS project created with cordova-ios@3.9.1 Discovered plugin 
>>> "cordova-plugin-whitelist" in config.xml. Installing to the project 
>>> Fetching plugin "cordova-plugin-whitelist@1" via npm Installing 
>>> "cordova-plugin-whitelist" for ios Plugin doesn't support this 
>>> project's cordova-ios version. cordova-ios: 3.9.1, failed version
>>> requirement: >=4.0.0-dev Skipping 'cordova-plugin-whitelist' for ios 
>>> Installing "cordova-plugin-whitelist" for ios Plugin doesn't support 
>>> this project's cordova-ios version. cordova-ios: 3.9.1, failed 
>>> version
>>> requirement: >=4.0.0-dev Skipping 'cordova-plugin-whitelist' for ios
>>>
>>> Looks like we have a rogue version of cordova-plugin-whitelist published that requires iOS 4.0.0. What's the best way to fix it? Can we unpublish this whitelist plugin version from npm to fix this? Alternatively, we should release another version of the plugin that does not get this warning. It's misleading and confusing for developers to see this warning.
>>>
>>> Thanks,
>>> Nikhil
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
>> For additional commands, e-mail: dev-help@cordova.apache.org
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
>> For additional commands, e-mail: dev-help@cordova.apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
For additional commands, e-mail: dev-help@cordova.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
For additional commands, e-mail: dev-help@cordova.apache.org

Re: cordova-plugin-whitelist ios issue

Posted by Shazron <sh...@gmail.com>.
One solution is to add an <info> tag with more information/clarification.

On Tue, Sep 29, 2015 at 5:28 PM, Shazron <sh...@gmail.com> wrote:
> This is only happening because we have two engine requirements -
> cordova-android 4.x and cordova-ios 4.x. This is correct for
> cordova-plugin-whitelist.
>
> Like I mentioned before, cordova-android+ios 3.x *do not* require this
> plugin as it is built in. Perhaps this could be communicated better,
> but the warning is generic, and there's no way to communicate this in
> an <engine> tag.
>
> We could release core plugins that have different core platform
> version requirements as well in the future (like android 5 plugin
> changes) and this will occur again.
>
>
> On Tue, Sep 29, 2015 at 5:21 PM, Shazron <sh...@gmail.com> wrote:
>> "IMO we should never release a plugin which always emits a warning
>> that cannot be resolved."
>>
>> There is nothing to resolve. The resolution is to ignore it. It's
>> supposed to warn you, as it is working as expected.
>>
>> On Tue, Sep 29, 2015 at 5:19 PM, Nikhil Khandelwal
>> <ni...@microsoft.com> wrote:
>>> I understand the warning w.r.t. plugins and android 5.0 as we will release android 5.0 along with the plugin update and there would be a path for people to resolve the warning.
>>>
>>> In this case, ios 4.0 is not even released and users have no way to work around this warning. We're getting feedback from customers about this.
>>>
>>> IMO we should never release a plugin which always emits a warning that cannot be resolved.
>>>
>>> -Nikhil
>>>
>>> -----Original Message-----
>>> From: Shazron [mailto:shazron@gmail.com]
>>> Sent: Tuesday, September 29, 2015 5:17 PM
>>> To: dev@cordova.apache.org
>>> Subject: Re: cordova-plugin-whitelist ios issue
>>>
>>> No its not a "rogue version". cordova-plugin-whitelist requires cordova-ios 4.0 and cordova-android 4.0.
>>> It's just a warning and is expected to work this way.
>>> https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fgithub.com%2fapache%2fcordova-plugin-whitelist%2fblob%2fmaster%2fREADME.md&data=01%7c01%7cnikhilkh%40microsoft.com%7cd638675115ae4fa7be2d08d2c92c9d89%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=iO9NDS0BgD53OVEDyxGv0zNW5SKXLVK0loo8ZAEmfOM%3d
>>>
>>> On Tue, Sep 29, 2015 at 5:08 PM, Nikhil Khandelwal <ni...@microsoft.com> wrote:
>>>> 1.       cordova create test
>>>>
>>>> 2.       cordova platform add ios
>>>>
>>>> WARNING: Applications for platform ios can not be built on this OS - win32.
>>>> Adding ios project...
>>>> iOS project created with cordova-ios@3.9.1 Discovered plugin
>>>> "cordova-plugin-whitelist" in config.xml. Installing to the project
>>>> Fetching plugin "cordova-plugin-whitelist@1" via npm Installing
>>>> "cordova-plugin-whitelist" for ios Plugin doesn't support this
>>>> project's cordova-ios version. cordova-ios: 3.9.1, failed version
>>>> requirement: >=4.0.0-dev Skipping 'cordova-plugin-whitelist' for ios
>>>> Installing "cordova-plugin-whitelist" for ios Plugin doesn't support
>>>> this project's cordova-ios version. cordova-ios: 3.9.1, failed version
>>>> requirement: >=4.0.0-dev Skipping 'cordova-plugin-whitelist' for ios
>>>>
>>>> Looks like we have a rogue version of cordova-plugin-whitelist published that requires iOS 4.0.0. What's the best way to fix it? Can we unpublish this whitelist plugin version from npm to fix this? Alternatively, we should release another version of the plugin that does not get this warning. It's misleading and confusing for developers to see this warning.
>>>>
>>>> Thanks,
>>>> Nikhil
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
>>> For additional commands, e-mail: dev-help@cordova.apache.org
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
>>> For additional commands, e-mail: dev-help@cordova.apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
For additional commands, e-mail: dev-help@cordova.apache.org

Re: cordova-plugin-whitelist ios issue

Posted by Shazron <sh...@gmail.com>.
This is only happening because we have two engine requirements -
cordova-android 4.x and cordova-ios 4.x. This is correct for
cordova-plugin-whitelist.

Like I mentioned before, cordova-android+ios 3.x *do not* require this
plugin as it is built in. Perhaps this could be communicated better,
but the warning is generic, and there's no way to communicate this in
an <engine> tag.

We could release core plugins that have different core platform
version requirements as well in the future (like android 5 plugin
changes) and this will occur again.


On Tue, Sep 29, 2015 at 5:21 PM, Shazron <sh...@gmail.com> wrote:
> "IMO we should never release a plugin which always emits a warning
> that cannot be resolved."
>
> There is nothing to resolve. The resolution is to ignore it. It's
> supposed to warn you, as it is working as expected.
>
> On Tue, Sep 29, 2015 at 5:19 PM, Nikhil Khandelwal
> <ni...@microsoft.com> wrote:
>> I understand the warning w.r.t. plugins and android 5.0 as we will release android 5.0 along with the plugin update and there would be a path for people to resolve the warning.
>>
>> In this case, ios 4.0 is not even released and users have no way to work around this warning. We're getting feedback from customers about this.
>>
>> IMO we should never release a plugin which always emits a warning that cannot be resolved.
>>
>> -Nikhil
>>
>> -----Original Message-----
>> From: Shazron [mailto:shazron@gmail.com]
>> Sent: Tuesday, September 29, 2015 5:17 PM
>> To: dev@cordova.apache.org
>> Subject: Re: cordova-plugin-whitelist ios issue
>>
>> No its not a "rogue version". cordova-plugin-whitelist requires cordova-ios 4.0 and cordova-android 4.0.
>> It's just a warning and is expected to work this way.
>> https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fgithub.com%2fapache%2fcordova-plugin-whitelist%2fblob%2fmaster%2fREADME.md&data=01%7c01%7cnikhilkh%40microsoft.com%7cd638675115ae4fa7be2d08d2c92c9d89%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=iO9NDS0BgD53OVEDyxGv0zNW5SKXLVK0loo8ZAEmfOM%3d
>>
>> On Tue, Sep 29, 2015 at 5:08 PM, Nikhil Khandelwal <ni...@microsoft.com> wrote:
>>> 1.       cordova create test
>>>
>>> 2.       cordova platform add ios
>>>
>>> WARNING: Applications for platform ios can not be built on this OS - win32.
>>> Adding ios project...
>>> iOS project created with cordova-ios@3.9.1 Discovered plugin
>>> "cordova-plugin-whitelist" in config.xml. Installing to the project
>>> Fetching plugin "cordova-plugin-whitelist@1" via npm Installing
>>> "cordova-plugin-whitelist" for ios Plugin doesn't support this
>>> project's cordova-ios version. cordova-ios: 3.9.1, failed version
>>> requirement: >=4.0.0-dev Skipping 'cordova-plugin-whitelist' for ios
>>> Installing "cordova-plugin-whitelist" for ios Plugin doesn't support
>>> this project's cordova-ios version. cordova-ios: 3.9.1, failed version
>>> requirement: >=4.0.0-dev Skipping 'cordova-plugin-whitelist' for ios
>>>
>>> Looks like we have a rogue version of cordova-plugin-whitelist published that requires iOS 4.0.0. What's the best way to fix it? Can we unpublish this whitelist plugin version from npm to fix this? Alternatively, we should release another version of the plugin that does not get this warning. It's misleading and confusing for developers to see this warning.
>>>
>>> Thanks,
>>> Nikhil
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
>> For additional commands, e-mail: dev-help@cordova.apache.org
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
>> For additional commands, e-mail: dev-help@cordova.apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
For additional commands, e-mail: dev-help@cordova.apache.org

Re: cordova-plugin-whitelist ios issue

Posted by Shazron <sh...@gmail.com>.
"IMO we should never release a plugin which always emits a warning
that cannot be resolved."

There is nothing to resolve. The resolution is to ignore it. It's
supposed to warn you, as it is working as expected.

On Tue, Sep 29, 2015 at 5:19 PM, Nikhil Khandelwal
<ni...@microsoft.com> wrote:
> I understand the warning w.r.t. plugins and android 5.0 as we will release android 5.0 along with the plugin update and there would be a path for people to resolve the warning.
>
> In this case, ios 4.0 is not even released and users have no way to work around this warning. We're getting feedback from customers about this.
>
> IMO we should never release a plugin which always emits a warning that cannot be resolved.
>
> -Nikhil
>
> -----Original Message-----
> From: Shazron [mailto:shazron@gmail.com]
> Sent: Tuesday, September 29, 2015 5:17 PM
> To: dev@cordova.apache.org
> Subject: Re: cordova-plugin-whitelist ios issue
>
> No its not a "rogue version". cordova-plugin-whitelist requires cordova-ios 4.0 and cordova-android 4.0.
> It's just a warning and is expected to work this way.
> https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fgithub.com%2fapache%2fcordova-plugin-whitelist%2fblob%2fmaster%2fREADME.md&data=01%7c01%7cnikhilkh%40microsoft.com%7cd638675115ae4fa7be2d08d2c92c9d89%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=iO9NDS0BgD53OVEDyxGv0zNW5SKXLVK0loo8ZAEmfOM%3d
>
> On Tue, Sep 29, 2015 at 5:08 PM, Nikhil Khandelwal <ni...@microsoft.com> wrote:
>> 1.       cordova create test
>>
>> 2.       cordova platform add ios
>>
>> WARNING: Applications for platform ios can not be built on this OS - win32.
>> Adding ios project...
>> iOS project created with cordova-ios@3.9.1 Discovered plugin
>> "cordova-plugin-whitelist" in config.xml. Installing to the project
>> Fetching plugin "cordova-plugin-whitelist@1" via npm Installing
>> "cordova-plugin-whitelist" for ios Plugin doesn't support this
>> project's cordova-ios version. cordova-ios: 3.9.1, failed version
>> requirement: >=4.0.0-dev Skipping 'cordova-plugin-whitelist' for ios
>> Installing "cordova-plugin-whitelist" for ios Plugin doesn't support
>> this project's cordova-ios version. cordova-ios: 3.9.1, failed version
>> requirement: >=4.0.0-dev Skipping 'cordova-plugin-whitelist' for ios
>>
>> Looks like we have a rogue version of cordova-plugin-whitelist published that requires iOS 4.0.0. What's the best way to fix it? Can we unpublish this whitelist plugin version from npm to fix this? Alternatively, we should release another version of the plugin that does not get this warning. It's misleading and confusing for developers to see this warning.
>>
>> Thanks,
>> Nikhil
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> For additional commands, e-mail: dev-help@cordova.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> For additional commands, e-mail: dev-help@cordova.apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
For additional commands, e-mail: dev-help@cordova.apache.org

RE: cordova-plugin-whitelist ios issue

Posted by Nikhil Khandelwal <ni...@microsoft.com>.
I understand the warning w.r.t. plugins and android 5.0 as we will release android 5.0 along with the plugin update and there would be a path for people to resolve the warning.

In this case, ios 4.0 is not even released and users have no way to work around this warning. We're getting feedback from customers about this.

IMO we should never release a plugin which always emits a warning that cannot be resolved.

-Nikhil

-----Original Message-----
From: Shazron [mailto:shazron@gmail.com] 
Sent: Tuesday, September 29, 2015 5:17 PM
To: dev@cordova.apache.org
Subject: Re: cordova-plugin-whitelist ios issue

No its not a "rogue version". cordova-plugin-whitelist requires cordova-ios 4.0 and cordova-android 4.0.
It's just a warning and is expected to work this way.
https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fgithub.com%2fapache%2fcordova-plugin-whitelist%2fblob%2fmaster%2fREADME.md&data=01%7c01%7cnikhilkh%40microsoft.com%7cd638675115ae4fa7be2d08d2c92c9d89%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=iO9NDS0BgD53OVEDyxGv0zNW5SKXLVK0loo8ZAEmfOM%3d

On Tue, Sep 29, 2015 at 5:08 PM, Nikhil Khandelwal <ni...@microsoft.com> wrote:
> 1.       cordova create test
>
> 2.       cordova platform add ios
>
> WARNING: Applications for platform ios can not be built on this OS - win32.
> Adding ios project...
> iOS project created with cordova-ios@3.9.1 Discovered plugin 
> "cordova-plugin-whitelist" in config.xml. Installing to the project 
> Fetching plugin "cordova-plugin-whitelist@1" via npm Installing 
> "cordova-plugin-whitelist" for ios Plugin doesn't support this 
> project's cordova-ios version. cordova-ios: 3.9.1, failed version 
> requirement: >=4.0.0-dev Skipping 'cordova-plugin-whitelist' for ios 
> Installing "cordova-plugin-whitelist" for ios Plugin doesn't support 
> this project's cordova-ios version. cordova-ios: 3.9.1, failed version 
> requirement: >=4.0.0-dev Skipping 'cordova-plugin-whitelist' for ios
>
> Looks like we have a rogue version of cordova-plugin-whitelist published that requires iOS 4.0.0. What's the best way to fix it? Can we unpublish this whitelist plugin version from npm to fix this? Alternatively, we should release another version of the plugin that does not get this warning. It's misleading and confusing for developers to see this warning.
>
> Thanks,
> Nikhil

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
For additional commands, e-mail: dev-help@cordova.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
For additional commands, e-mail: dev-help@cordova.apache.org

Re: cordova-plugin-whitelist ios issue

Posted by Shazron <sh...@gmail.com>.
No its not a "rogue version". cordova-plugin-whitelist requires
cordova-ios 4.0 and cordova-android 4.0.
It's just a warning and is expected to work this way.
https://github.com/apache/cordova-plugin-whitelist/blob/master/README.md

On Tue, Sep 29, 2015 at 5:08 PM, Nikhil Khandelwal
<ni...@microsoft.com> wrote:
> 1.       cordova create test
>
> 2.       cordova platform add ios
>
> WARNING: Applications for platform ios can not be built on this OS - win32.
> Adding ios project...
> iOS project created with cordova-ios@3.9.1
> Discovered plugin "cordova-plugin-whitelist" in config.xml. Installing to the project
> Fetching plugin "cordova-plugin-whitelist@1" via npm
> Installing "cordova-plugin-whitelist" for ios
> Plugin doesn't support this project's cordova-ios version. cordova-ios: 3.9.1, failed version requirement: >=4.0.0-dev
> Skipping 'cordova-plugin-whitelist' for ios
> Installing "cordova-plugin-whitelist" for ios
> Plugin doesn't support this project's cordova-ios version. cordova-ios: 3.9.1, failed version requirement: >=4.0.0-dev
> Skipping 'cordova-plugin-whitelist' for ios
>
> Looks like we have a rogue version of cordova-plugin-whitelist published that requires iOS 4.0.0. What's the best way to fix it? Can we unpublish this whitelist plugin version from npm to fix this? Alternatively, we should release another version of the plugin that does not get this warning. It's misleading and confusing for developers to see this warning.
>
> Thanks,
> Nikhil

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
For additional commands, e-mail: dev-help@cordova.apache.org

Re: cordova-plugin-whitelist ios issue

Posted by Tommy Williams <to...@devgeeks.org>.
Maybe less terse? It’s a little confronting, like you have messed something up and actually need to figure out how to update to 4.0.0-dev

:/


On 30 September 2015 at 10:14:57, Steven Gill (stevengill97@gmail.com) wrote:

It is just a warning though. Shouldn't break any builds. This will become  
more common once we release the new plugins which will require  
cordova-android 5.0+. Is the suggestion to remove the warning completely?  




On Tue, Sep 29, 2015 at 5:08 PM, Nikhil Khandelwal <ni...@microsoft.com>  
wrote:  

> 1. cordova create test  
>  
> 2. cordova platform add ios  
>  
> WARNING: Applications for platform ios can not be built on this OS - win32.  
> Adding ios project...  
> iOS project created with cordova-ios@3.9.1  
> Discovered plugin "cordova-plugin-whitelist" in config.xml. Installing to  
> the project  
> Fetching plugin "cordova-plugin-whitelist@1" via npm  
> Installing "cordova-plugin-whitelist" for ios  
> Plugin doesn't support this project's cordova-ios version. cordova-ios:  
> 3.9.1, failed version requirement: >=4.0.0-dev  
> Skipping 'cordova-plugin-whitelist' for ios  
> Installing "cordova-plugin-whitelist" for ios  
> Plugin doesn't support this project's cordova-ios version. cordova-ios:  
> 3.9.1, failed version requirement: >=4.0.0-dev  
> Skipping 'cordova-plugin-whitelist' for ios  
>  
> Looks like we have a rogue version of cordova-plugin-whitelist published  
> that requires iOS 4.0.0. What's the best way to fix it? Can we unpublish  
> this whitelist plugin version from npm to fix this? Alternatively, we  
> should release another version of the plugin that does not get this  
> warning. It's misleading and confusing for developers to see this warning.  
>  
> Thanks,  
> Nikhil  
>

Re: cordova-plugin-whitelist ios issue

Posted by Steven Gill <st...@gmail.com>.
It is just a warning though. Shouldn't break any builds. This will become
more common once we release the new plugins which will require
cordova-android 5.0+. Is the suggestion to remove the warning completely?




On Tue, Sep 29, 2015 at 5:08 PM, Nikhil Khandelwal <ni...@microsoft.com>
wrote:

> 1.       cordova create test
>
> 2.       cordova platform add ios
>
> WARNING: Applications for platform ios can not be built on this OS - win32.
> Adding ios project...
> iOS project created with cordova-ios@3.9.1
> Discovered plugin "cordova-plugin-whitelist" in config.xml. Installing to
> the project
> Fetching plugin "cordova-plugin-whitelist@1" via npm
> Installing "cordova-plugin-whitelist" for ios
> Plugin doesn't support this project's cordova-ios version. cordova-ios:
> 3.9.1, failed version requirement: >=4.0.0-dev
> Skipping 'cordova-plugin-whitelist' for ios
> Installing "cordova-plugin-whitelist" for ios
> Plugin doesn't support this project's cordova-ios version. cordova-ios:
> 3.9.1, failed version requirement: >=4.0.0-dev
> Skipping 'cordova-plugin-whitelist' for ios
>
> Looks like we have a rogue version of cordova-plugin-whitelist published
> that requires iOS 4.0.0. What's the best way to fix it? Can we unpublish
> this whitelist plugin version from npm to fix this? Alternatively, we
> should release another version of the plugin that does not get this
> warning. It's misleading and confusing for developers to see this warning.
>
> Thanks,
> Nikhil
>