We keep seeing this failed Media test on Android 4.4:
https://github.com/apache/cordova-plugin-media/pull/166
I'm not sure of the state of our Android support, especially 4.4. Does
anyone have any pointers? Thanks
Speaking as a Cordova user, Android 4.4 still accounts for an
agonizing 10.3% of devices (as of May 2018)[1] and our company's apps
are still required to support it.
I can't speak to the media plugin, since I've never used it, but I can
confirm that the latest cordova-android still supports 4.4 al
Yeah, we official dropped support of SDK < 19 on cordova-android 7.x.x, so
we still support Android 4.4.
I think we can merge that and create a new issue for Android 4.4 tests,
media tests has been broken for a long time, so hard to tell if that
failure is related to the changes or not, but at lea
I have investigated the test failure for Android 4.4. For
cordova-plugin-media, the cause of the failure may be the SSL handshake.
The MediaPlayer in Android 4.4 can not connect to a modern SSL server.
For example:
https://cordova.apache.org/downloads/BlueZedEx.mp3
https://cordova-develop.g
Thanks Ken!
I think we should go for the simpler option, and log this as a new issue
that is known and out of our control. Android 4.4 (even though 10% of the
market) should not be a priority for us.
On Tue, Jun 19, 2018 at 12:30 PM Ken Naito wrote:
>
> I have investigated the test failure for A
Hi Shazron,
Thanks for the advice!
I sent a new commit of PR, which removes some tests for Android 4.4.
Ken Naito.
On 2018/06/19 13:35, Shazron wrote:
Thanks Ken!
I think we should go for the simpler option, and log this as a new
issue that is known and out of our control. Android 4.4 (even t
Why don't we just use http instead of https? shouldn't that fix the
problems too? or https is required in other platforms?
2018-06-19 11:32 GMT+02:00 Ken Naito :
> Hi Shazron,
>
> Thanks for the advice!
> I sent a new commit of PR, which removes some tests for Android 4.4.
>
> Ken Naito.
>
> On 2
Using http might fix the test, for sure - but I think we should move on to
testing https only, as the new normal.
Although this is through one major browser vendor (which dwarfs all others
at 60% market share) -- the coming https-pocalypse later this year (see
https://techcrunch.com/2018/02/08/chr
"We should consider KitKat 'abandoned'" w.r.t. the media plugin, not
Cordova...
On Tue, Jun 19, 2018 at 11:47 PM Shazron wrote:
> Using http might fix the test, for sure - but I think we should move on to
> testing https only, as the new normal.
>
> Although this is through one major browser ven
as security updates for KitKat, there are none. The last release of
KitKat was 5 years and 2 months ago.
I think it is safe to say that deprecating Android 4.4 support is a good
move.
Lastly, IF the votes are more in favor of dropping, the next question would
be what version should be supported at
for Android 4.4
is only at 2.6%*.
Additionally, there is a report of *128 vulnerabilities in Android 4.4.4*.
As far as security updates for KitKat, there are none. The last release of
KitKat was 5 years and 2 months ago.
I think it is safe to say that deprecating Android 4.4 support is a good
move.
Las
that the *market share for Android
> 4.4
> > is only at 2.6%*.
> >
> > Additionally, there is a report of *128 vulnerabilities in Android
> 4.4.4*.
> > As far as security updates for KitKat, there are none. The last release
> of
> > KitKat was 5 years and 2 m
eport of *128 vulnerabilities in Android
4.4.4*.
As far as security updates for KitKat, there are none. The last release
of
KitKat was 5 years and 2 months ago.
I think it is safe to say that deprecating Android 4.4 support is a good
move.
Lastly, IF the votes are more in favor of dropping, the next questi
+1 to drop Android 4.4 support
> Do we have a reason for 5.1 instead of 5.0 other than the low usage?
>
> Originally, I was thinking 5.0+, but after seeing low usage, I leaned
> over to 5.1. So low usage was my primary reasoning for my +1.
+1 to drop 5.0 and +1 on the reasoning h
+1 to drop everything before 5.1
> On Jan 28, 2020, at 7:53 AM, Chris Brody wrote:
>
> +1 to drop Android 4.4 support
>
>> Do we have a reason for 5.1 instead of 5.0 other than the low usage?
>>
>> Originally, I was thinking 5.0+, but after seeing low usage, I
ody wrote:
> +1 to drop Android 4.4 support
>
> > Do we have a reason for 5.1 instead of 5.0 other than the low usage?
> >
> > Originally, I was thinking 5.0+, but after seeing low usage, I leaned
> > over to 5.1. So low usage was my primary reasoning for my +1.
&g
rk on Android 4.4. These are changes that would possibly come.
> We just have to think about the "updatable webview" when that time comes.
>
>
> On Wed, Jan 29, 2020 at 12:53 AM Chris Brody
> wrote:
>
> > +1 to drop Android 4.4 support
> >
> > > Do we
; Lastly, if we started to convert the browser code to ES6, for example, it
> > will not work on Android 4.4. These are changes that would possibly come.
> > We just have to think about the "updatable webview" when that time comes.
> >
> >
> > On Wed, Jan 29, 202
or example, it
will not work on Android 4.4. These are changes that would possibly come.
We just have to think about the "updatable webview" when that time comes.
On Wed, Jan 29, 2020 at 12:53 AM Chris Brody
wrote:
+1 to drop Android 4.4 support
Do we have a reason for 5.1 instead
wn risk. This value could be set in config.xml.
> >>
> >> What we would say could be along the lines of, it might work with 5.0 but
> >> we officially support is 5.1.
> >>
> >> Lastly, if we started to convert the browser code to ES6, for example, it
>
20 matches
Mail list logo
