RE: Jira CB-831: File transfer tests crash on Android L

2015-04-13 Thread Josh Soref
Joe wrote:
 No idea.  Andrew already upped the API level to 22, which is Android 5.1.

 In related news, It may make sense to create an issue to add support for
 multi-SIM phones, but of course nobody has one AFAIK since they only exist
 in India.

I think Firefox Flame has support for them, and outside of India.

http://www.zdnet.com/article/meet-flame-mozillas-170-firefox-os-phone-for-devs/



smime.p7s
Description: S/MIME cryptographic signature


RE: Jira CB-831: File transfer tests crash on Android L

2015-04-13 Thread tommy-carlos williams
There are lots of multi-sim phones available in AU… 

-- 
tommy-carlos williams

On 14 April 2015 at 06:59:56, Josh Soref (jso...@blackberry.com) wrote:

Joe wrote:  
 No idea. Andrew already upped the API level to 22, which is Android 5.1.  

 In related news, It may make sense to create an issue to add support for  
 multi-SIM phones, but of course nobody has one AFAIK since they only exist  
 in India.  

I think Firefox Flame has support for them, and outside of India.  

http://www.zdnet.com/article/meet-flame-mozillas-170-firefox-os-phone-for-devs/ 
 



Re: Jira CB-831: File transfer tests crash on Android L

2015-04-11 Thread julio cesar sanchez
Google added official multi sim support on the latest version, not sure how
that affects to apps. I have a motorola moto g 2014 and it's dual sim (at
least the spanish model), let me know if you need me to test anything when
I receive the 5.1 version (I'm on 5.0.2 right now)


Re: Jira CB-831: File transfer tests crash on Android L

2015-04-10 Thread Frederico Galvão
@Joe On a side-note: What do you mean by support for multi-SIM phones?
And by that I mean, what doesn't Cordova already support in these?
Also, phones with more than one SIM slots are very common here in Brazil
and even some places in Europe, so you might not have to visit India for
that ;)

2015-04-10 13:56 GMT-03:00 Carlos Santana csantan...@gmail.com:

 Thanks Joe for the explanation !

 On Fri, Apr 10, 2015 at 11:10 AM, Joe Bowser bows...@gmail.com wrote:

  On Thu, Apr 9, 2015 at 6:31 AM Carlos Santana csantan...@gmail.com
  wrote:
 
   On Tue, Apr 7, 2015 at 8:30 PM, Joe Bowser bows...@gmail.com wrote:
  
Sorry, I mis-read this e-mail.  Does this Race Condition happen on
   Lollipop
proper, or just on L.  If it's just on L, this isn't a priority
  because L
is not a release meant to go to any users, just a Developer Preview.
  
  
   Joe sorry my ignorance on Android land :-p
   But L to me is Lollipop, and the final API is 21 and is release and in
  the
   wild for users.
   http://developer.android.com/preview/index.html
  
  
  There was a Developer Preview called L that was released six months
 before
  Lollipop.  The API target was L, and this was only available on the Nexus
  devices as a dev image and not intended for end users, or even OEMs.
  Developer previews are rare in Android, and usually a release process
 goes
  something like this:
 
  - Source Code Drop in AOSP
  - API Release with Emulators
  - Roll out to Nexus Devices
 
  As far as getting to real world devices, that's all in relation to the
  speed of the OEM to get the image completed.  Each OEM needs to polish
  their version of Android so that it differentiates from the others, and
  make sure that Android actually works on their phone.
 
 
   I think API 22 is even out.
   Which is the API that is not out? Some sort of API 23 beta/preview?
  
  
  No idea.  Andrew already upped the API level to 22, which is Android 5.1.
  In related news, It may make sense to create an issue to add support for
  multi-SIM phones, but of course nobody has one AFAIK since they only
 exist
  in India.
 
 
   +1 setting cordova target to 22
  
  
   
  
   On Tue, Apr 7, 2015 at 5:27 PM Nikhil Khandelwal 
 nikhi...@microsoft.com
  
wrote:
   
 The JIRA which was marked as 'Won't fix' is currently blocking
  Android
 test runs on http://ci.cordova.io:  https://issues.apache.org/
 jira/browse/CB-8431.

 It looks like Android L's implementation of OkHttp has a race
  condition
 which hits quite consistently with our current file transfer tests.
   There
 is a comment by Andrew in the bug that points to using this plugin
 on
 Android L:
 https://github.com/MobileChromeApps/cordova-plugin-okhttp
  .

 Should this plugin be a dependency to the file transfer plugin? Or
  the
 code for it be rolled in as part of file transfer plugin itself?

 For the short term I'm leaning towards working around this issue,
 by
using
 an older AVD (instead of Android L) on our CI setup. However, there
  is
   a
 chance developers running Cordova apps on Android L will run into
  this
and
 would expect some guidance here.

 Thanks,
 Nikhil



   
  
  
  
   --
   Carlos Santana
   csantan...@gmail.com
  
 



 --
 Carlos Santana
 csantan...@gmail.com




-- 

*Frederico Galvão*

Diretor de Tecnologia

PontoGet Inovação Web


( +55(62) 8131-5720

* www.pontoget.com.br http://www.pontoget.com/


Re: Jira CB-831: File transfer tests crash on Android L

2015-04-09 Thread Carlos Santana
On Tue, Apr 7, 2015 at 8:30 PM, Joe Bowser bows...@gmail.com wrote:

 Sorry, I mis-read this e-mail.  Does this Race Condition happen on Lollipop
 proper, or just on L.  If it's just on L, this isn't a priority because L
 is not a release meant to go to any users, just a Developer Preview.


Joe sorry my ignorance on Android land :-p
But L to me is Lollipop, and the final API is 21 and is release and in the
wild for users.
http://developer.android.com/preview/index.html

I think API 22 is even out.
Which is the API that is not out? Some sort of API 23 beta/preview?

+1 setting cordova target to 22




On Tue, Apr 7, 2015 at 5:27 PM Nikhil Khandelwal nikhi...@microsoft.com
 wrote:

  The JIRA which was marked as 'Won't fix' is currently blocking Android
  test runs on http://ci.cordova.io:  https://issues.apache.org/
  jira/browse/CB-8431.
 
  It looks like Android L's implementation of OkHttp has a race condition
  which hits quite consistently with our current file transfer tests. There
  is a comment by Andrew in the bug that points to using this plugin on
  Android L: https://github.com/MobileChromeApps/cordova-plugin-okhttp.
 
  Should this plugin be a dependency to the file transfer plugin? Or the
  code for it be rolled in as part of file transfer plugin itself?
 
  For the short term I'm leaning towards working around this issue, by
 using
  an older AVD (instead of Android L) on our CI setup. However, there is a
  chance developers running Cordova apps on Android L will run into this
 and
  would expect some guidance here.
 
  Thanks,
  Nikhil
 
 
 




-- 
Carlos Santana
csantan...@gmail.com


Re: Jira CB-831: File transfer tests crash on Android L

2015-04-08 Thread Joe Bowser
I was about to say the same thing about API 22.  We should do that before
release.

On Tue, Apr 7, 2015 at 6:31 PM Andrew Grieve agri...@chromium.org wrote:

 - In 4.0.0, we remove OkHttp from our code, but Android L starts including
 it for its own network stack (crazy coincidence!)
 - We're not sure how frequent the crash happens - just that MobileSpec's
 use of FileTransfer triggers it every time
 - It is fixed by replacing the network stack with a newer version of OkHttp
 - I've published cordova-plugin-okhttp to npm, so it's installable via
 cordova-cli@master
 - Bug says it's fixed in Android 5.1.1 (API level 22). (thanks for finding
 that okio issue!)

 On a side note - should we switch our targetSdk to 22? Probably...?



 On Tue, Apr 7, 2015 at 9:14 PM, Nikhil Khandelwal nikhi...@microsoft.com
 wrote:

  Why am I seeing this crash with the latest master on the BuildBot CI?
 
  I understand that we're not bundling OkHttp, but it's being used with the
  File Transfer plugin on an emulator for Android 5.0.1 (API 21).
 
  The crash is happening with the stack at
  com.android.okio.OkBuffer.write(OkBuffer.java:574) and not
  com.squareup.okhttp which Android 3.7.1 platform used to package.
 
  Does Android ship with a version okhttp? Here's the issue description and
  a fix for it in Okio: https://github.com/square/okio/issues/79. It does
  not look like this fix is part of Android 5.0.1 - the emulator that was
  being used to run tests on our CI server.
 
  (I'm quite new to Android development - bear with me if I'm missing
  something obvious here).
 
  Thanks,
  Nikhil
 
 
  -Original Message-
  From: Joe Bowser [mailto:bows...@gmail.com]
  Sent: Tuesday, April 7, 2015 5:29 PM
  To: dev@cordova.apache.org
  Subject: Re: Jira CB-831: File transfer tests crash on Android L
 
  This is a Won't Fix because we're not bundling OkHttp anymore.  This will
  be resolved when we release Cordova-Android 4.0.0
 
  On Tue, Apr 7, 2015 at 5:27 PM Nikhil Khandelwal nikhi...@microsoft.com
 
  wrote:
 
   The JIRA which was marked as 'Won't fix' is currently blocking Android
   test runs on http://ci.cordova.io:  https://issues.apache.org/
   jira/browse/CB-8431.
  
   It looks like Android L's implementation of OkHttp has a race
   condition which hits quite consistently with our current file transfer
   tests. There is a comment by Andrew in the bug that points to using
   this plugin on Android L:
  https://github.com/MobileChromeApps/cordova-plugin-okhttp.
  
   Should this plugin be a dependency to the file transfer plugin? Or the
   code for it be rolled in as part of file transfer plugin itself?
  
   For the short term I'm leaning towards working around this issue, by
   using an older AVD (instead of Android L) on our CI setup. However,
   there is a chance developers running Cordova apps on Android L will
   run into this and would expect some guidance here.
  
   Thanks,
   Nikhil
  
  
  
 



RE: Jira CB-831: File transfer tests crash on Android L

2015-04-08 Thread Nikhil Khandelwal
Thanks for explaining the issue. For our CI, we could continue using Android 
4.4.2 for our emulator image as that's what most devs care about currently. 

I have updated the JIRA https://issues.apache.org/jira/browse/CB-8431 with more 
details and changed the title. This should serve as documentation.

The tests that triggers it almost every time, does a file transfer request for 
a non-existent URL and does an abort as well. Request and abort happen on 
different threadpool threads and they trigger a race in Android's 
implementation of OKHttp. There are two workarounds for this issue:
- Upgrade to Android 5.1.1
- Use the plugin suggested by Andrew below to move to an updated version of 
OkHttp.

Thanks,
Nikhil


-Original Message-
From: Joe Bowser [mailto:bows...@gmail.com] 
Sent: Wednesday, April 8, 2015 9:21 AM
To: dev@cordova.apache.org
Subject: Re: Jira CB-831: File transfer tests crash on Android L

I was about to say the same thing about API 22.  We should do that before 
release.

On Tue, Apr 7, 2015 at 6:31 PM Andrew Grieve agri...@chromium.org wrote:

 - In 4.0.0, we remove OkHttp from our code, but Android L starts 
 including it for its own network stack (crazy coincidence!)
 - We're not sure how frequent the crash happens - just that 
 MobileSpec's use of FileTransfer triggers it every time
 - It is fixed by replacing the network stack with a newer version of 
 OkHttp
 - I've published cordova-plugin-okhttp to npm, so it's installable via 
 cordova-cli@master
 - Bug says it's fixed in Android 5.1.1 (API level 22). (thanks for 
 finding that okio issue!)

 On a side note - should we switch our targetSdk to 22? Probably...?



 On Tue, Apr 7, 2015 at 9:14 PM, Nikhil Khandelwal 
 nikhi...@microsoft.com
 wrote:

  Why am I seeing this crash with the latest master on the BuildBot CI?
 
  I understand that we're not bundling OkHttp, but it's being used 
  with the File Transfer plugin on an emulator for Android 5.0.1 (API 21).
 
  The crash is happening with the stack at
  com.android.okio.OkBuffer.write(OkBuffer.java:574) and not 
  com.squareup.okhttp which Android 3.7.1 platform used to package.
 
  Does Android ship with a version okhttp? Here's the issue 
  description and a fix for it in Okio: 
  https://github.com/square/okio/issues/79. It does not look like this 
  fix is part of Android 5.0.1 - the emulator that was being used to run 
  tests on our CI server.
 
  (I'm quite new to Android development - bear with me if I'm missing 
  something obvious here).
 
  Thanks,
  Nikhil
 
 
  -Original Message-
  From: Joe Bowser [mailto:bows...@gmail.com]
  Sent: Tuesday, April 7, 2015 5:29 PM
  To: dev@cordova.apache.org
  Subject: Re: Jira CB-831: File transfer tests crash on Android L
 
  This is a Won't Fix because we're not bundling OkHttp anymore.  This 
  will be resolved when we release Cordova-Android 4.0.0
 
  On Tue, Apr 7, 2015 at 5:27 PM Nikhil Khandelwal 
  nikhi...@microsoft.com
 
  wrote:
 
   The JIRA which was marked as 'Won't fix' is currently blocking 
   Android test runs on http://ci.cordova.io:  
   https://issues.apache.org/ jira/browse/CB-8431.
  
   It looks like Android L's implementation of OkHttp has a race 
   condition which hits quite consistently with our current file 
   transfer tests. There is a comment by Andrew in the bug that 
   points to using this plugin on Android L:
  https://github.com/MobileChromeApps/cordova-plugin-okhttp.
  
   Should this plugin be a dependency to the file transfer plugin? Or 
   the code for it be rolled in as part of file transfer plugin itself?
  
   For the short term I'm leaning towards working around this issue, 
   by using an older AVD (instead of Android L) on our CI setup. 
   However, there is a chance developers running Cordova apps on 
   Android L will run into this and would expect some guidance here.
  
   Thanks,
   Nikhil
  
  
  
 



Re: Jira CB-831: File transfer tests crash on Android L

2015-04-07 Thread Joe Bowser
This is a Won't Fix because we're not bundling OkHttp anymore.  This will
be resolved when we release Cordova-Android 4.0.0

On Tue, Apr 7, 2015 at 5:27 PM Nikhil Khandelwal nikhi...@microsoft.com
wrote:

 The JIRA which was marked as 'Won't fix' is currently blocking Android
 test runs on http://ci.cordova.io:  https://issues.apache.org/
 jira/browse/CB-8431.

 It looks like Android L's implementation of OkHttp has a race condition
 which hits quite consistently with our current file transfer tests. There
 is a comment by Andrew in the bug that points to using this plugin on
 Android L: https://github.com/MobileChromeApps/cordova-plugin-okhttp.

 Should this plugin be a dependency to the file transfer plugin? Or the
 code for it be rolled in as part of file transfer plugin itself?

 For the short term I'm leaning towards working around this issue, by using
 an older AVD (instead of Android L) on our CI setup. However, there is a
 chance developers running Cordova apps on Android L will run into this and
 would expect some guidance here.

 Thanks,
 Nikhil





Re: Jira CB-831: File transfer tests crash on Android L

2015-04-07 Thread Joe Bowser
Sorry, I mis-read this e-mail.  Does this Race Condition happen on Lollipop
proper, or just on L.  If it's just on L, this isn't a priority because L
is not a release meant to go to any users, just a Developer Preview.

On Tue, Apr 7, 2015 at 5:27 PM Nikhil Khandelwal nikhi...@microsoft.com
wrote:

 The JIRA which was marked as 'Won't fix' is currently blocking Android
 test runs on http://ci.cordova.io:  https://issues.apache.org/
 jira/browse/CB-8431.

 It looks like Android L's implementation of OkHttp has a race condition
 which hits quite consistently with our current file transfer tests. There
 is a comment by Andrew in the bug that points to using this plugin on
 Android L: https://github.com/MobileChromeApps/cordova-plugin-okhttp.

 Should this plugin be a dependency to the file transfer plugin? Or the
 code for it be rolled in as part of file transfer plugin itself?

 For the short term I'm leaning towards working around this issue, by using
 an older AVD (instead of Android L) on our CI setup. However, there is a
 chance developers running Cordova apps on Android L will run into this and
 would expect some guidance here.

 Thanks,
 Nikhil





RE: Jira CB-831: File transfer tests crash on Android L

2015-04-07 Thread Nikhil Khandelwal
Why am I seeing this crash with the latest master on the BuildBot CI?

I understand that we're not bundling OkHttp, but it's being used with the File 
Transfer plugin on an emulator for Android 5.0.1 (API 21). 

The crash is happening with the stack at 
com.android.okio.OkBuffer.write(OkBuffer.java:574) and not com.squareup.okhttp 
which Android 3.7.1 platform used to package. 

Does Android ship with a version okhttp? Here's the issue description and a fix 
for it in Okio: https://github.com/square/okio/issues/79. It does not look like 
this fix is part of Android 5.0.1 - the emulator that was being used to run 
tests on our CI server.

(I'm quite new to Android development - bear with me if I'm missing something 
obvious here).

Thanks,
Nikhil


-Original Message-
From: Joe Bowser [mailto:bows...@gmail.com] 
Sent: Tuesday, April 7, 2015 5:29 PM
To: dev@cordova.apache.org
Subject: Re: Jira CB-831: File transfer tests crash on Android L

This is a Won't Fix because we're not bundling OkHttp anymore.  This will be 
resolved when we release Cordova-Android 4.0.0

On Tue, Apr 7, 2015 at 5:27 PM Nikhil Khandelwal nikhi...@microsoft.com
wrote:

 The JIRA which was marked as 'Won't fix' is currently blocking Android 
 test runs on http://ci.cordova.io:  https://issues.apache.org/ 
 jira/browse/CB-8431.

 It looks like Android L's implementation of OkHttp has a race 
 condition which hits quite consistently with our current file transfer 
 tests. There is a comment by Andrew in the bug that points to using 
 this plugin on Android L: 
 https://github.com/MobileChromeApps/cordova-plugin-okhttp.

 Should this plugin be a dependency to the file transfer plugin? Or the 
 code for it be rolled in as part of file transfer plugin itself?

 For the short term I'm leaning towards working around this issue, by 
 using an older AVD (instead of Android L) on our CI setup. However, 
 there is a chance developers running Cordova apps on Android L will 
 run into this and would expect some guidance here.

 Thanks,
 Nikhil





Re: Jira CB-831: File transfer tests crash on Android L

2015-04-07 Thread Andrew Grieve
- In 4.0.0, we remove OkHttp from our code, but Android L starts including
it for its own network stack (crazy coincidence!)
- We're not sure how frequent the crash happens - just that MobileSpec's
use of FileTransfer triggers it every time
- It is fixed by replacing the network stack with a newer version of OkHttp
- I've published cordova-plugin-okhttp to npm, so it's installable via
cordova-cli@master
- Bug says it's fixed in Android 5.1.1 (API level 22). (thanks for finding
that okio issue!)

On a side note - should we switch our targetSdk to 22? Probably...?



On Tue, Apr 7, 2015 at 9:14 PM, Nikhil Khandelwal nikhi...@microsoft.com
wrote:

 Why am I seeing this crash with the latest master on the BuildBot CI?

 I understand that we're not bundling OkHttp, but it's being used with the
 File Transfer plugin on an emulator for Android 5.0.1 (API 21).

 The crash is happening with the stack at
 com.android.okio.OkBuffer.write(OkBuffer.java:574) and not
 com.squareup.okhttp which Android 3.7.1 platform used to package.

 Does Android ship with a version okhttp? Here's the issue description and
 a fix for it in Okio: https://github.com/square/okio/issues/79. It does
 not look like this fix is part of Android 5.0.1 - the emulator that was
 being used to run tests on our CI server.

 (I'm quite new to Android development - bear with me if I'm missing
 something obvious here).

 Thanks,
 Nikhil


 -Original Message-
 From: Joe Bowser [mailto:bows...@gmail.com]
 Sent: Tuesday, April 7, 2015 5:29 PM
 To: dev@cordova.apache.org
 Subject: Re: Jira CB-831: File transfer tests crash on Android L

 This is a Won't Fix because we're not bundling OkHttp anymore.  This will
 be resolved when we release Cordova-Android 4.0.0

 On Tue, Apr 7, 2015 at 5:27 PM Nikhil Khandelwal nikhi...@microsoft.com
 wrote:

  The JIRA which was marked as 'Won't fix' is currently blocking Android
  test runs on http://ci.cordova.io:  https://issues.apache.org/
  jira/browse/CB-8431.
 
  It looks like Android L's implementation of OkHttp has a race
  condition which hits quite consistently with our current file transfer
  tests. There is a comment by Andrew in the bug that points to using
  this plugin on Android L:
 https://github.com/MobileChromeApps/cordova-plugin-okhttp.
 
  Should this plugin be a dependency to the file transfer plugin? Or the
  code for it be rolled in as part of file transfer plugin itself?
 
  For the short term I'm leaning towards working around this issue, by
  using an older AVD (instead of Android L) on our CI setup. However,
  there is a chance developers running Cordova apps on Android L will
  run into this and would expect some guidance here.
 
  Thanks,
  Nikhil