Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cordova.apache.org
MIME-Version: 1.0
From: Joe Bowser <bowserj@gmail.com>
Date: Tue, 14 Jul 2015 22:07:50 +0000
Message-ID: 
 <CAOBL_k6oJup5k8NmpvniRi1=rzqXAgVOig3dFewjs8s8WGm4QQ@mail.gmail.com>
Subject: [Android] Working with M - An update
To: dev <dev@cordova.apache.org>
Content-Type: multipart/alternative; boundary=001a11c30bf04af25b051add1240

--001a11c30bf04af25b051add1240
Content-Type: text/plain; charset=UTF-8

So, since Cordova-Android wasn't completely killed off by Google at the
last Google IO like I thought it would be, we're going to have to make sure
it's compatible with Android M (Marshmellow? Marzipan?).  The good news is
that this only affects the following plugins:

MediaRecorder
Contacts
File
FileTransfer
Geolocation

Now, for the really bad news.  We might have to write a Geolocation plugin
for Android again, because Google's Android WebView doesn't play nice with
Android's new permission system, and even when you do grant the application
containing the process permission to use geolocation, you still get a
location error.  I still have to test this further, but it also may be
possible that file URIs no longer have the ability to get the geolocation
either, which would be weird, since this would be a Chrome thing and not an
Android thing.

Given our poor track record of maintaining plugins in general, and the
weird errors with Geolocation, I'm not really wanting to bring back the
code, so I'm hoping that this gets resolved in M3 with the next dev version
of M.

But so far, I have the changes that I made to Cordova on a private branch
on Github that people can see here:

https://github.com/infil00p/cordova-android/tree/m-compat

Let me know if you have any questions.  I'm not sure whether this makes
perfect sense yet, but I think these API changes indicate that we should
probably bump the version to 5.0 once M comes out.

Thoughts? Questions?

--001a11c30bf04af25b051add1240--