cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Carlos Santana <>
Subject Re: Marshmallow Update and Cordova-Android 5.0
Date Tue, 01 Sep 2015 13:39:41 GMT
Joe I understand the feeling. One part of me saying that we should name the
version 4.2 since there are no API changes.
But my other part says that if developer's ignore because is 4.x stuff will
break in new major release of Android M (23)

I would say that also agree that best option is to name is cordova-android@5
, then is clear to developers that they can use targetsdk=23 and also new
major versions for the affected plugins that need updates to support

But as you can see this is less important that getting the plugins to work
correctly with permissions :-)

On Tue, Sep 1, 2015 at 12:03 AM Joe Bowser <> wrote:

> BTW: I got Contacts somewhat working with Marshmellow.  It's still got the
> same crappy concurrency bugs that it always has, and I am not sure how to
> resolve those without re-writing the damn thing, but the purpose of this is
> to figure out how to get permissions to work, and I have something that
> works.
> This works with the latest smores tree of Cordova Android, and I tested it
> on Lollipop and Marshmellow.  I'm going to move on to some of the other
> plugins to get them ready for Marshmellow, but it'd be good to have people
> look these over.
> I did find a nasty security bug with this, though.  If you request one
> permission out of the permission group, you get all the permissions.  So,
> anything that can read contacts can magically write contacts even if you
> don't request that permission explicitly.  I think this is a serious bug,
> and I'm going to dig tomorrow to see if someone already reported it.
> On Mon, Aug 31, 2015 at 11:35 AM Joe Bowser <> wrote:
> > Hey
> >
> > So, I created a new topic branch of my github with the new changes as
> > suggested earlier.
> >
> >
> >
> > The thing we have to make sure works is if the user turns off the
> > permissions on Marshmellow.  Right now if the permissions are off,
> > everything crashes and dies, so we're going to issue a 5.0 because
> plugins
> > will have to have this code to work on the latest version of Android.
> It's
> > not a API change, since we're adding it, but I feel that it's important
> > enough that we should bump the major version anyway.
> >
> > Can we PLEASE not have any other features creep into 5.0?  If we need
> > additional features, we can do a 6.0.  I'm not against bumping major
> > versions as long as we get into a trend of not breaking shit like we did
> in
> > the bump from 3.7 to 4.0.
> >
> > Also, we're going to deprecate 3.7, is there any major third-party
> plugins
> > that still don't work with 4.0.x that we should be aware of?  Do we have
> > people to cover the docs on that.
> >
> > Thoughts?
> >
> > Joe
> >
> >
> >

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