+1 to Joe, this update is 4.1.0 (major version bump) because the support
for API Level 10 was removed
BTW, Carlos, I've seen that you changed the issue priority from Minor to
Critical, I set it to Minor because there is an easy workaround, just tell
the user to add the android-minSdkVersion prefer
Enhance update script and notify user. We do not support API Level 10.
On Thu, Jul 30, 2015, 8:49 PM Carlos Santana wrote:
> Is still not clear to me what's the proper fix, to revert back both minsdk
> to level 10, or enhance update script to check if app minsdk have lower
> level than 14 makin
Is still not clear to me what's the proper fix, to revert back both minsdk
to level 10, or enhance update script to check if app minsdk have lower
level than 14 making incompatible with new cordovalib and update it to 14
for the user?
On Thu, Jul 30, 2015 at 9:57 PM Murat Sutunc wrote:
> Good ca
Good catch! +1 on 4.1.1
> On Jul 30, 2015, at 6:41 PM, Steven Gill wrote:
>
> +1. I can get a vote out for it tomorrow
>> On Jul 30, 2015 6:20 PM, "Carlos Santana" wrote:
>>
>> I think we need to fix and release a 4.1.1 this CB-9428 fixed before new
>> cordova-cli get's released.
>>
>> the up
+1. I can get a vote out for it tomorrow
On Jul 30, 2015 6:20 PM, "Carlos Santana" wrote:
> I think we need to fix and release a 4.1.1 this CB-9428 fixed before new
> cordova-cli get's released.
>
> the update logic lives in the platform update script, not the cordova cli
>
> https://issues.apach
I think we need to fix and release a 4.1.1 this CB-9428 fixed before new
cordova-cli get's released.
the update logic lives in the platform update script, not the cordova cli
https://issues.apache.org/jira/browse/CB-9428
basically doing an upgrade today like "cordova platform update android@4.1.
