Sent you the test app off-list.

On Wed, Jul 15, 2015 at 11:12 AM Andrew Grieve <agri...@chromium.org> wrote:

> Thanks for looking into this Joe! The runtime permissions is quite a big
> change!
>
> M is still in preview, so if you find any webview bugs, please feel free to
> send me a repro app and I'll do my best to get it fixed.
>
> In terms of Cordova API changes, here's some thoughts on your branch:
> - Plugins may want to request different perms at different times, so I'd
> remove new functions from CordovaPlugin except onRequestPermissionResult
> - Might be better to copy how CordovaInterfaceImpl does
> startActivityForResult/onActivityResponse rather than have PluginManager do
> it.
>
>
> On Tue, Jul 14, 2015 at 6:07 PM, Joe Bowser <bows...@gmail.com> wrote:
>
> > 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?
> >
>

Reply via email to