[jira] [Commented] (CB-5999) App crashes on Nexus 5/Kitkat 4.4.2 with error Unable to lock surface

[Christiaan Rakowski (JIRA)]

[ 
https://issues.apache.org/jira/browse/CB-5999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13897646#comment-13897646
 ] 

Christiaan Rakowski commented on CB-5999:
-

While trying to make the repo sample I started by removing all HTML, javascript 
and css and found out it still crashed. This pretty much rules out any css3 
transition/transform related issues and only leaves plugins as possible 
culprits. I don't yet know which one(s), or how they cause an issue that 
otherwise seems to relate to OpenGL, but it seems to not be cordova core 
related.
Sorry for not testing this is more detail before posting it here, the signs 
just seemed too clear.

Would you like me to close the issue now, or change it to a low priority and 
document my later findings for future reference?



 App crashes on Nexus 5/Kitkat 4.4.2 with error Unable to lock surface
 ---

 Key: CB-5999
 URL: https://issues.apache.org/jira/browse/CB-5999
 Project: Apache Cordova
  Issue Type: Bug
  Components: Android
Affects Versions: 3.3.0
 Environment: Published from Windows 8.1 Professional, using ADT 
 v22.2.1-833290 and Cordova 3.3.1-0.3.0
 Published to fresh out of box (European) Nexus 5, running KitKat 4.4.2
Reporter: Christiaan Rakowski
Priority: Blocker

 We have a cordova app which was developed for iOS, and runs fine there.
 Now we are porting it over to Android and we get the following crash during 
 start up:
 {{{quote}
 02-10 13:39:11.231: E/Surface(31190): dequeueBuffer failed (Invalid argument)
 02-10 13:39:11.241: E/ViewRootImpl(31190): Could not lock surface
 02-10 13:39:11.241: E/ViewRootImpl(31190): java.lang.IllegalArgumentException
 02-10 13:39:11.241: E/ViewRootImpl(31190):at 
 android.view.Surface.nativeLockCanvas(Native Method)
 02-10 13:39:11.241: E/ViewRootImpl(31190):at 
 android.view.Surface.lockCanvas(Surface.java:243)
 02-10 13:39:11.241: E/ViewRootImpl(31190):at 
 android.view.ViewRootImpl.drawSoftware(ViewRootImpl.java:2435)
 02-10 13:39:11.241: E/ViewRootImpl(31190):at 
 android.view.ViewRootImpl.draw(ViewRootImpl.java:2409)
 02-10 13:39:11.241: E/ViewRootImpl(31190):at 
 android.view.ViewRootImpl.performDraw(ViewRootImpl.java:2253)
 02-10 13:39:11.241: E/ViewRootImpl(31190):at 
 android.view.ViewRootImpl.performTraversals(ViewRootImpl.java:1883)
 02-10 13:39:11.241: E/ViewRootImpl(31190):at 
 android.view.ViewRootImpl.doTraversal(ViewRootImpl.java:1000)
 02-10 13:39:11.241: E/ViewRootImpl(31190):at 
 android.view.ViewRootImpl$TraversalRunnable.run(ViewRootImpl.java:5670)
 02-10 13:39:11.241: E/ViewRootImpl(31190):at 
 android.view.Choreographer$CallbackRecord.run(Choreographer.java:761)
 02-10 13:39:11.241: E/ViewRootImpl(31190):at 
 android.view.Choreographer.doCallbacks(Choreographer.java:574)
 02-10 13:39:11.241: E/ViewRootImpl(31190):at 
 android.view.Choreographer.doFrame(Choreographer.java:544)
 02-10 13:39:11.241: E/ViewRootImpl(31190):at 
 android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:747)
 02-10 13:39:11.241: E/ViewRootImpl(31190):at 
 android.os.Handler.handleCallback(Handler.java:733)
 02-10 13:39:11.241: E/ViewRootImpl(31190):at 
 android.os.Handler.dispatchMessage(Handler.java:95)
 02-10 13:39:11.241: E/ViewRootImpl(31190):at 
 android.os.Looper.loop(Looper.java:136)
 02-10 13:39:11.241: E/ViewRootImpl(31190):at 
 android.app.ActivityThread.main(ActivityThread.java:5017)
 02-10 13:39:11.241: E/ViewRootImpl(31190):at 
 java.lang.reflect.Method.invokeNative(Native Method)
 02-10 13:39:11.241: E/ViewRootImpl(31190):at 
 java.lang.reflect.Method.invoke(Method.java:515)
 02-10 13:39:11.241: E/ViewRootImpl(31190):at 
 com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:779)
 02-10 13:39:11.241: E/ViewRootImpl(31190):at 
 com.android.internal.os.ZygoteInit.main(ZygoteInit.java:595)
 02-10 13:39:11.241: E/ViewRootImpl(31190):at 
 dalvik.system.NativeStart.main(Native Method)
 {quote}}}
 I have tried attaching the Chrome debug bridge, but that gave me no 
 additional information.
 I did some searching online, but in all the posts I found people using OpenGL 
 directly, but none of them had a real solution either. Most of the posts were 
 from people running on Snapdragon 800 devices though.
 I assume css3 transitions/transforms get translated to OpenGL by the 
 ChromeWebView, so I think this might be related to the SoC and how it handles 
 OpenGL. I currently don't have access to a different Android device, so I 
 can't do more testing with that.
 I have tested the Hello World application, and that did run fine on the Nexus 
 5.
 If you have any tests you would like me to run or need addition information, 
 please let me 

[jira] [Commented] (CB-1247) An option similar to webviewbounce is needed that works on Windows Phone

[Lee Crossley (JIRA)]

[ 
https://issues.apache.org/jira/browse/CB-1247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13897676#comment-13897676
 ] 

Lee Crossley commented on CB-1247:
--

Using ```-ms-touch-action: none``` on the body doesn't always solve the issue. 
If you have an element with ```overflow: scroll``` within the body, 
occasionally the body element itself can scroll beyond the bounds of the html. 
I've tried ```-ms-scroll-chaining``` etc but there doesn't seem to be a way to 
prevent this behaviour reliably and have any scrollable content.

 An option similar to webviewbounce is needed that works on Windows Phone
 --

 Key: CB-1247
 URL: https://issues.apache.org/jira/browse/CB-1247
 Project: Apache Cordova
  Issue Type: Bug
  Components: WP7, WP8
Affects Versions: 2.0.0, 2.1.0, 2.2.0, 2.3.0, 2.4.0
 Environment: Windows Phone
Reporter: Rob Van Wicklen
Assignee: Jesse MacFadyen

 A webviewbounce option can be set to fix an app's viewable area in place on 
 the iOS screen, making it so that users cannot drag it and move it off the 
 side of the screen. A similar setting is needed for Windows Phone.
 Currently, even if the viewport size is set to the device screen dimensions 
 and the scale is fixed at 1.0, Windows Phone users can still drag the app's 
 viewport which results in a bounce effect similar to what's seen on iOS when 
 the webviewbounce option isn't set to false.
 The Windows Phone WebBrowser control doesn't directly expose a property that 
 lets you eliminate the bounce, but the desired result can be acheived with a 
 small amount of wrapper code around the control. This would need to be 
 implemented within Cordova. The following article explains how to do it:
  
 http://www.scottlogic.co.uk/blog/colin/2011/11/suppressing-zoom-and-scroll-interactions-in-the-windows-phone-7-browser-control
 Justification: the ability to eliminate the bounce effect is important for 
 app developers who want to create an experience that's similar to a native 
 app. This is not currently possible on Windows Phone.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Updated] (CB-6006) ms-touch-action doesn't always solve 'overscroll'

[Lee Crossley (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-6006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lee Crossley updated CB-6006:
-

Description: 
Using:
{code}
-ms-touch-action: none
{code}
on the body doesn't always prevent overscroll.

If you have an element with:
{code}
overflow: scroll
{code}
within the body, occasionally the body element itself can scroll beyond the 
bounds of the html.

I've tried 
{code}
-ms-scroll-chaining
{code}
etc but there doesn't seem to be a way to prevent this behaviour reliably and 
have any scrollable content.

  was:
Using:
{code:css}
-ms-touch-action: none
{code}
on the body doesn't always prevent overscroll.

If you have an element with:
{code:css}
overflow: scroll
{code}
within the body, occasionally the body element itself can scroll beyond the 
bounds of the html.

I've tried 
{code:css}
-ms-scroll-chaining
{code}
etc but there doesn't seem to be a way to prevent this behaviour reliably and 
have any scrollable content.


 ms-touch-action doesn't always solve 'overscroll'
 -

 Key: CB-6006
 URL: https://issues.apache.org/jira/browse/CB-6006
 Project: Apache Cordova
  Issue Type: Bug
  Components: WP8
Affects Versions: 3.3.0
Reporter: Lee Crossley
Assignee: Jesse MacFadyen

 Using:
 {code}
 -ms-touch-action: none
 {code}
 on the body doesn't always prevent overscroll.
 If you have an element with:
 {code}
 overflow: scroll
 {code}
 within the body, occasionally the body element itself can scroll beyond the 
 bounds of the html.
 I've tried 
 {code}
 -ms-scroll-chaining
 {code}
 etc but there doesn't seem to be a way to prevent this behaviour reliably and 
 have any scrollable content.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Created] (CB-6006) ms-touch-action doesn't always solve 'overscroll'

[Lee Crossley (JIRA)]

Lee Crossley created CB-6006:


 Summary: ms-touch-action doesn't always solve 'overscroll'
 Key: CB-6006
 URL: https://issues.apache.org/jira/browse/CB-6006
 Project: Apache Cordova
  Issue Type: Bug
  Components: WP8
Affects Versions: 3.3.0
Reporter: Lee Crossley
Assignee: Jesse MacFadyen


Using:
{code:css}
-ms-touch-action: none
{code}
on the body doesn't always prevent overscroll.

If you have an element with:
{code:css}
overflow: scroll
{code}
within the body, occasionally the body element itself can scroll beyond the 
bounds of the html.

I've tried 
{code:css}
-ms-scroll-chaining
{code}
etc but there doesn't seem to be a way to prevent this behaviour reliably and 
have any scrollable content.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Commented] (CB-5438) Can't build/test cordova-js on Windows

[qi (JIRA)]

[ 
https://issues.apache.org/jira/browse/CB-5438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13897692#comment-13897692
 ] 

qi commented on CB-5438:


Hi [~BBosman] thanks, build's now properly working but test still failed. Those 
two js files are intended to test 

 Can't build/test cordova-js on Windows
 --

 Key: CB-5438
 URL: https://issues.apache.org/jira/browse/CB-5438
 Project: Apache Cordova
  Issue Type: Bug
  Components: CordovaJS
Affects Versions: Master
 Environment: Windows 8 x64
 Node v0.10.13
Reporter: qi
Priority: Critical

 Simply run 'grunt build', got,
 Running jshint:src (jshint) task
 Linting lib/test/androidexec.js ...ERROR
 [L1:C1] E030: Expected an identifier and instead saw '.'.
 ../android/exec.js
 [L1:C2] E033: Expected an operator and instead saw '.'.
 ../android/exec.js
 [L1:C3] E033: Expected an operator and instead saw '/'.
 ../android/exec.js
 [L1:C4] W033: Missing semicolon.
 ../android/exec.js
 [L1:C4] W015: Expected 'android' to have an indentation at 1 instead at 4.
 ../android/exec.js
 [L1:C19] W033: Missing semicolon.
 ../android/exec.js
 [L1:C4] W117: 'android' is not defined.
 ../android/exec.js
 [L1:C12] W117: 'exec' is not defined.
 ../android/exec.js
 Linting lib/test/iosexec.js ...ERROR
 [L1:C1] E030: Expected an identifier and instead saw '.'.
 ../ios/exec.js
 [L1:C2] E033: Expected an operator and instead saw '.'.
 ../ios/exec.js
 [L1:C3] E033: Expected an operator and instead saw '/'.
 ../ios/exec.js
 [L1:C4] W033: Missing semicolon.
 ../ios/exec.js
 [L1:C4] W015: Expected 'ios' to have an indentation at 1 instead at 4.
 ../ios/exec.js
 [L1:C15] W033: Missing semicolon.
 ../ios/exec.js
 [L1:C4] W117: 'ios' is not defined.
 ../ios/exec.js
 [L1:C8] W117: 'exec' is not defined.
 ../ios/exec.js
 Warning: Task jshint:src failed. Use --force to continue.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Comment Edited] (CB-5438) Can't build/test cordova-js on Windows

[qi (JIRA)]

[ 
https://issues.apache.org/jira/browse/CB-5438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13897692#comment-13897692
 ] 

qi edited comment on CB-5438 at 2/11/14 10:02 AM:
--

Hi [~BBosman] thanks, build's now properly working but test still failed. Those 
two js files are intended to test, we cannot simply ignore them 


was (Author: luoq):
Hi [~BBosman] thanks, build's now properly working but test still failed. Those 
two js files are intended to test 

 Can't build/test cordova-js on Windows
 --

 Key: CB-5438
 URL: https://issues.apache.org/jira/browse/CB-5438
 Project: Apache Cordova
  Issue Type: Bug
  Components: CordovaJS
Affects Versions: Master
 Environment: Windows 8 x64
 Node v0.10.13
Reporter: qi
Priority: Critical

 Simply run 'grunt build', got,
 Running jshint:src (jshint) task
 Linting lib/test/androidexec.js ...ERROR
 [L1:C1] E030: Expected an identifier and instead saw '.'.
 ../android/exec.js
 [L1:C2] E033: Expected an operator and instead saw '.'.
 ../android/exec.js
 [L1:C3] E033: Expected an operator and instead saw '/'.
 ../android/exec.js
 [L1:C4] W033: Missing semicolon.
 ../android/exec.js
 [L1:C4] W015: Expected 'android' to have an indentation at 1 instead at 4.
 ../android/exec.js
 [L1:C19] W033: Missing semicolon.
 ../android/exec.js
 [L1:C4] W117: 'android' is not defined.
 ../android/exec.js
 [L1:C12] W117: 'exec' is not defined.
 ../android/exec.js
 Linting lib/test/iosexec.js ...ERROR
 [L1:C1] E030: Expected an identifier and instead saw '.'.
 ../ios/exec.js
 [L1:C2] E033: Expected an operator and instead saw '.'.
 ../ios/exec.js
 [L1:C3] E033: Expected an operator and instead saw '/'.
 ../ios/exec.js
 [L1:C4] W033: Missing semicolon.
 ../ios/exec.js
 [L1:C4] W015: Expected 'ios' to have an indentation at 1 instead at 4.
 ../ios/exec.js
 [L1:C15] W033: Missing semicolon.
 ../ios/exec.js
 [L1:C4] W117: 'ios' is not defined.
 ../ios/exec.js
 [L1:C8] W117: 'exec' is not defined.
 ../ios/exec.js
 Warning: Task jshint:src failed. Use --force to continue.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Created] (CB-6007) If cordova.js is referenced using cache bust the plugin path is derived incorrectly.

[Rik Schennink (JIRA)]

Rik Schennink created CB-6007:
-

 Summary: If cordova.js is referenced using cache bust the plugin 
path is derived incorrectly.
 Key: CB-6007
 URL: https://issues.apache.org/jira/browse/CB-6007
 Project: Apache Cordova
  Issue Type: Bug
  Components: CordovaJS
Affects Versions: 3.3.0
Reporter: Rik Schennink


The path below functions correctly.
vendor/apache/ios/cordova.js - vendor/apache/ios

The following path returns 'null'.
vendor/apache/ios/cordova.js?bust=v1.1

Problem is located in 'findCordovaPath()' line '1369'. Adding the following 
line of js before the if statement fixes the problem for me (could probably be 
optimised).

{code}
// make sure querystring parameters are not taken into account in the comparison
src = src.indexOf('?') !== -1 ? src.split('?')[0] : src;
{code}



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Commented] (CB-5996) config.xml in platforms/firefoxos/www instead of platforms/firefoxos

[Gert-Jan Braas (JIRA)]

[ 
https://issues.apache.org/jira/browse/CB-5996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13897738#comment-13897738
 ] 

Gert-Jan Braas commented on CB-5996:


Created a one-line-patch
https://github.com/Steckelfisch/cordova-plugman/commit/b7c32d8079526cfd9021713dfb61274d707bc0dc

issued a pull-request to  apache:master 

 config.xml in platforms/firefoxos/www instead of platforms/firefoxos
 

 Key: CB-5996
 URL: https://issues.apache.org/jira/browse/CB-5996
 Project: Apache Cordova
  Issue Type: Bug
  Components: FirefoxOS, Plugman
Affects Versions: 3.3.0, 3.4.0
 Environment: Ubuntu 13.10, installed from npm repository 
 (3.3.1-0.3.1) and from git repo (3.3.0 and 3.4.0)
Reporter: Gert-Jan Braas
Priority: Blocker

 (local src from git (3.4.0-rc.1))
 braas@chickenrun:~/projects/test$ cordova create FOSTEST
 Creating a new cordova project with name HelloCordova and id 
 io.cordova.hellocordova at location /var/tmp/braas/projects/test/FOSTEST
 Downloading cordova library for www...
 Download complete
 ~/projects/test$ cd FOSTEST
 ~/projects/test$ cordova plugin add org.apache.cordova.geolocation
 Fetching plugin org.apache.cordova.geolocation via plugin registry
 ~/projects/test/FOSTEST$ cordova platform add firefoxos
 Downloading cordova library for firefoxos...
 Download complete
 Creating firefoxos project...
 Generating config.xml from defaults for platform firefoxos
 Preparing firefoxos project
 Starting installation of org.apache.cordova.geolocation for firefoxos
 Preparing firefoxos project
 Error: ENOENT, no such file or directory 
 '/home/braas/projects/test/FOSTEST/platforms/firefoxos/www/config.xml'
 at Object.fs.openSync (fs.js:427:18)
 at Object.fs.readFileSync (fs.js:284:15)
 at Object.module.exports.parseElementtreeSync 
 (/home/braas/npm/lib/node_modules/plugman/src/util/xml-helpers.js:119:27)
 at Object.module.exports.package_name 
 (/home/braas/npm/lib/node_modules/plugman/src/platforms/firefoxos.js:10:38)
 at Object.module.exports.generate_plugin_config_munge 
 (/home/braas/npm/lib/node_modules/plugman/src/util/config-changes.js:100:53)
 at Object.module.exports.add_plugin_changes 
 (/home/braas/npm/lib/node_modules/plugman/src/util/config-changes.js:300:43)
 at 
 /home/braas/npm/lib/node_modules/plugman/src/util/config-changes.js:440:28
 at Array.forEach (native)
 at Object.module.exports.process 
 (/home/braas/npm/lib/node_modules/plugman/src/util/config-changes.js:439:49)
 at Object.handlePrepare 
 (/home/braas/npm/lib/node_modules/plugman/src/prepare.js:69:20)
 ~/projects/test/FOSTEST$ 
 ~/projects/test/FOSTEST$ ls platforms/firefoxos/www
 cordova.js  cordova_plugins.js  css  img  index.html  js  manifest.webapp
 :~/projects/test/FOSTEST$ ls platforms/firefoxos
 config.xml  cordova  platform_www  www



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Created] (CB-6008) Cannot install inAppBrowser with CLI tool.

[Manos Koufakis (JIRA)]

Manos Koufakis created CB-6008:
--

 Summary: Cannot install inAppBrowser with CLI tool.
 Key: CB-6008
 URL: https://issues.apache.org/jira/browse/CB-6008
 Project: Apache Cordova
  Issue Type: Bug
  Components: Android
Affects Versions: 3.3.0
 Environment: Windows 7 / Android Platform
Reporter: Manos Koufakis


As of yesterday, everytime I use the CLI tool to add the inAppBrowser plugin, I 
get the following error:
C:\ cd findmovieapp
C:\findmovieapp cordova plugin add https://git-wip-us.apache.org/repos/asf/cord
ova-plugin-inappbrowser.git
Fetching plugin from https://git-wip-us.apache.org/repos/asf/cordova-plugin-ina
ppbrowser.git...
Starting installation of org.apache.cordova.inappbrowser for android

C:\Users\vs0513\AppData\Roaming\npm\node_modules\cordova\node_modules\q\q.js:126

throw e;
  ^
TypeError: Cannot read property 'install' of undefined
at C:\Users\vs0513\AppData\Roaming\npm\node_modules\cordova\node_modules\plu
gman\src\install.js:361:71
at Array.forEach (native)
at handleInstall (C:\Users\vs0513\AppData\Roaming\npm\node_modules\cordova\n
ode_modules\plugman\src\install.js:360:40)
at C:\Users\vs0513\AppData\Roaming\npm\node_modules\cordova\node_modules\plu
gman\src\install.js:331:20
at _fulfilled (C:\Users\vs0513\AppData\Roaming\npm\node_modules\cordova\node
_modules\q\q.js:798:54)
at self.promiseDispatch.done (C:\Users\vs0513\AppData\Roaming\npm\node_modul
es\cordova\node_modules\q\q.js:827:30)
at Promise.promise.promiseDispatch (C:\Users\vs0513\AppData\Roaming\npm\node
_modules\cordova\node_modules\q\q.js:760:13)
at C:\Users\vs0513\AppData\Roaming\npm\node_modules\cordova\node_modules\q\q
.js:574:44
at flush (C:\Users\vs0513\AppData\Roaming\npm\node_modules\cordova\node_modu
les\q\q.js:108:17)
at process._tickCallback (node.js:415:13)



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Created] (CB-6009) Android CLI support missing Windows

[Dan van Leeuwen (JIRA)]

Dan van Leeuwen created CB-6009:
---

 Summary: Android CLI support missing Windows
 Key: CB-6009
 URL: https://issues.apache.org/jira/browse/CB-6009
 Project: Apache Cordova
  Issue Type: Bug
  Components: Docs
Affects Versions: 3.3.0, 3.2.0
 Environment: Android on Windows
Reporter: Dan van Leeuwen


The following page
http://cordova.apache.org/docs/en/3.3.0/guide_cli_index.md.html

contains the text

To add support or rebuild a project for any platform, you need to run the 
command-line interface from the same machine that supports the platform's SDK. 
The CLI supports the following combinations:
•   iOS (Mac)
•   Amazon Fire OS (Mac, Linux, Windows)
•   Android (Mac, Linux)

Notice above that Windows support is missing for Android.

I believe this is a typo.  



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Commented] (CB-3562) Wrong splash screen ratio for landscape-only applications

[Emil Marashliev (JIRA)]

[ 
https://issues.apache.org/jira/browse/CB-3562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13897872#comment-13897872
 ] 

Emil Marashliev commented on CB-3562:
-

The bug is not actually fixed, it's still ugly. We need truly disable of 
autorotation. I suggest somehow to disable rotation through - 
[CDVViewController shouldAutorotate] method when the view of splash screen 
plugin is shown.


 Wrong splash screen ratio for landscape-only applications
 -

 Key: CB-3562
 URL: https://issues.apache.org/jira/browse/CB-3562
 Project: Apache Cordova
  Issue Type: Bug
  Components: iOS, Plugin SplashScreen
Affects Versions: 2.6.0, 2.7.0, 2.9.0
Reporter: Michael Hanselmann
Assignee: Shazron Abdullah
 Fix For: 3.4.0


 CDVSplashScreen.m shows the splash image with a wrong ratio for 
 landscape-only applications on iPhone/iPod touch devices. I fixed it locally 
 by applying a 90° transformation (“CGAffineTransformMakeRotation(M_PI / 2)”) 
 to the image view.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Created] (CB-6010) CDVAssetLibraryFilesystem does not have URLforFilesystemPath

[Claudius Coenen (JIRA)]

Claudius Coenen created CB-6010:
---

 Summary: CDVAssetLibraryFilesystem does not have 
URLforFilesystemPath
 Key: CB-6010
 URL: https://issues.apache.org/jira/browse/CB-6010
 Project: Apache Cordova
  Issue Type: Bug
  Components: Plugin File, Plugin File Transfer
Affects Versions: 3.3.0
 Environment: ios
Reporter: Claudius Coenen


when i try to FileTransfer.download(...) a file (code itself used to work in 
2.7) my app now crashes.

Step-Debugging revealed, that in CDVFile#fileSystemURLforLocalPath (Line 267) 
all available filesystems are tested. One of those appears to be a 
CDVAssetLibraryFilesystem - which does not implement URLforFilesystemPath

I added a dummy URLforFilesystemPath wich just returns nil. This got me around 
the crash, but now i'm stuck with a FILE_NOT_FOUND_ERR, which is probably my 
own responsibility. But the aforementioned crash took me a while to find.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Updated] (CB-6010) CDVAssetLibraryFilesystem does not have URLforFilesystemPath

[Claudius Coenen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-6010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claudius Coenen updated CB-6010:


Description: 
when i try to {{FileTransfer.download(...)}} a file (code itself used to work 
in 2.7) my app now crashes.

Step-Debugging revealed, that in {{CDVFile#fileSystemURLforLocalPath}} _(Line 
267)_ all available filesystems are tested. One of those appears to be a 
{{CDVAssetLibraryFilesystem}} - which does not implement 
{{URLforFilesystemPath}}

I added a dummy {{URLforFilesystemPath}} wich just returns {{nil}}. This got me 
around the crash, but now i'm stuck with a {{FILE_NOT_FOUND_ERR}}, which is 
probably my own responsibility. But the aforementioned crash took me a while to 
find.

  was:
when i try to FileTransfer.download(...) a file (code itself used to work in 
2.7) my app now crashes.

Step-Debugging revealed, that in CDVFile#fileSystemURLforLocalPath (Line 267) 
all available filesystems are tested. One of those appears to be a 
CDVAssetLibraryFilesystem - which does not implement URLforFilesystemPath

I added a dummy URLforFilesystemPath wich just returns nil. This got me around 
the crash, but now i'm stuck with a FILE_NOT_FOUND_ERR, which is probably my 
own responsibility. But the aforementioned crash took me a while to find.


 CDVAssetLibraryFilesystem does not have URLforFilesystemPath
 

 Key: CB-6010
 URL: https://issues.apache.org/jira/browse/CB-6010
 Project: Apache Cordova
  Issue Type: Bug
  Components: Plugin File, Plugin File Transfer
Affects Versions: 3.3.0
 Environment: ios
Reporter: Claudius Coenen

 when i try to {{FileTransfer.download(...)}} a file (code itself used to work 
 in 2.7) my app now crashes.
 Step-Debugging revealed, that in {{CDVFile#fileSystemURLforLocalPath}} _(Line 
 267)_ all available filesystems are tested. One of those appears to be a 
 {{CDVAssetLibraryFilesystem}} - which does not implement 
 {{URLforFilesystemPath}}
 I added a dummy {{URLforFilesystemPath}} wich just returns {{nil}}. This got 
 me around the crash, but now i'm stuck with a {{FILE_NOT_FOUND_ERR}}, which 
 is probably my own responsibility. But the aforementioned crash took me a 
 while to find.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Updated] (CB-6011) Cordova Media doesn't work properly on Kindle Fire (Android 2.3)

[Thibault Durand (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-6011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Thibault Durand updated CB-6011:


Description: 
Hello,

I have an issue with my Kindle Fire (Android 2.3)

First, i've managed to create a sample app to reproduce the bug: 
https://github.com/mosalingua/cordova-sampleapp-bug-media-sound-kindle

You can download the apk here : 
https://github.com/mosalingua/cordova-sampleapp-bug-media-sound-kindle/raw/master/platforms/android/bin/HelloWorld-debug.apk

This app just has a button to play a sound, and we can visualise the Media 
Callback when they are called. 

And the problem is that on the Kindle Fire (Based on Android OS 2.3.3), the 
callback mediaSuccess isn't called. 

I've tested on these devices:

 - Kindle Fire (1st GEN), Android 2.3.3 = KO
 - Nexus 7, Android 4.4 = OK
 - Samsung Galaxy S1, Android 2.3.3 = OK 
 - Samsung Galaxy S2, Android 4.0.4 = OK

As i've released my app on Amazon, i'm currently blocked on this platform to 
keep releasing update, mi last update was based on cordova 2.7, which worked 
fine on Kindle.

I've dug into the Media Plugin, and i've find out that int the AudioPlayer.java 
, the setState method is working just fine, and send this message to the 
javascript part with the correct status. ( 4 == MEDIA_STOPPED )
cordova.require('org.apache.cordova.media.Media').onStatus('c5f1ec7b-9cdf-0a49-3f62-0def8bd2d9b2',
 1, 4);

But, when i put a console.log in the Media.onStatus callback in the Media.js 
file, i don't get anything, it seems that the message isn't caught.
So my question is : Do you see how that could be possible ?

Thanks, i can give you more information if needed.

Best regards,

Thibault


  was:
Hello,

I have an issue with my Kindle Fire (Android 2.3)

First, i've managed to create a sample app to reproduce the bug: 
https://github.com/mosalingua/cordova-sampleapp-bug-media-sound-kindle

You can download the apk here : 
https://github.com/mosalingua/cordova-sampleapp-bug-media-sound-kindle/raw/master/platforms/android/bin/HelloWorld-debug.apk

This app just has a button to play a sound, and we can visualise the Media 
Callback when they are called. 

And the problem is that on the Kindle Fire (Based on Android OS 2.3.3), the 
callback mediaSuccess isn't called. 

I've tested on these devices:

 - Kindle Fire (1st GEN), Android 2.3.3 = KO
 - Nexus 7, Android 4.4 = OK
 - Samsung Galaxy S1, Android 2.3.3 = OK 
 - Samsung Galaxy S2, Android 4.0.4 = OK

As i've released my app on Amazon, i'm currently blocked on this platform to 
keep releasing update, mi last update was bases on cordova 2.7, which worked 
fine on Kindle.

I've dug into the Media Plugin, and i've find out that int the AudioPlayer.java 
, the setState method is working just fine, and send this message to the 
javascript part with the correct status. ( 4 == MEDIA_STOPPED )
cordova.require('org.apache.cordova.media.Media').onStatus('c5f1ec7b-9cdf-0a49-3f62-0def8bd2d9b2',
 1, 4);

But, when i put a console.log in the Media.onStatus callback in the Media.js 
file, i don't get anything, it seems that the message isn't caught.
So my question is : Do you see how that could be possible ?

Thanks, i can give you more information if needed.

Best regards,

Thibault



 Cordova Media doesn't work properly on Kindle Fire (Android 2.3)
 

 Key: CB-6011
 URL: https://issues.apache.org/jira/browse/CB-6011
 Project: Apache Cordova
  Issue Type: Bug
  Components: Android
Affects Versions: 3.3.0
 Environment: Kindle Fire (1st generation ), Based on Android OS 2.3.3
Reporter: Thibault Durand
Priority: Blocker

 Hello,
 I have an issue with my Kindle Fire (Android 2.3)
 First, i've managed to create a sample app to reproduce the bug: 
 https://github.com/mosalingua/cordova-sampleapp-bug-media-sound-kindle
 You can download the apk here : 
 https://github.com/mosalingua/cordova-sampleapp-bug-media-sound-kindle/raw/master/platforms/android/bin/HelloWorld-debug.apk
 This app just has a button to play a sound, and we can visualise the Media 
 Callback when they are called. 
 And the problem is that on the Kindle Fire (Based on Android OS 2.3.3), the 
 callback mediaSuccess isn't called. 
 I've tested on these devices:
  - Kindle Fire (1st GEN), Android 2.3.3 = KO
  - Nexus 7, Android 4.4 = OK
  - Samsung Galaxy S1, Android 2.3.3 = OK 
  - Samsung Galaxy S2, Android 4.0.4 = OK
 As i've released my app on Amazon, i'm currently blocked on this platform to 
 keep releasing update, mi last update was based on cordova 2.7, which worked 
 fine on Kindle.
 I've dug into the Media Plugin, and i've find out that int the 
 AudioPlayer.java , the setState method is working just fine, and send this 
 message to the javascript part with the correct status. ( 4 == MEDIA_STOPPED )

[jira] [Updated] (CB-6011) Cordova Media doesn't work properly on Kindle Fire (Android 2.3)

[Thibault Durand (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-6011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Thibault Durand updated CB-6011:


Description: 
Hello,

I have an issue with my Kindle Fire (Android 2.3)

First, i've managed to create a sample app to reproduce the bug: 
https://github.com/mosalingua/cordova-sampleapp-bug-media-sound-kindle

You can download the apk here : 
https://github.com/mosalingua/cordova-sampleapp-bug-media-sound-kindle/raw/master/platforms/android/bin/HelloWorld-debug.apk

This app just has a button to play a sound, and we can visualise the Media 
Callback when they are called. 

And the problem is that on the Kindle Fire (Based on Android OS 2.3.3), the 
callback mediaSuccess isn't called. 

I've tested on these devices:

 - Kindle Fire (1st GEN), Android 2.3.3 = KO
 - Nexus 7, Android 4.4 = OK
 - Samsung Galaxy S1, Android 2.3.3 = OK 
 - Samsung Galaxy S2, Android 4.0.4 = OK

As i've released my app on Amazon, i'm currently blocked on this platform to 
keep releasing update, my last update was based on cordova 2.7, which worked 
fine on Kindle.

I've dug into the Media Plugin, and i've find out that in the AudioPlayer.java 
, the setState method is working just fine, and send this message to the 
javascript part with the correct status ( 4 == MEDIA_STOPPED ):

cordova.require('org.apache.cordova.media.Media').onStatus('c5f1ec7b-9cdf-0a49-3f62-0def8bd2d9b2',
 1, 4);

But, when i put a console.log in the Media.onStatus callback in the Media.js 
file, i don't get anything, it seems that the message isn't caught.
So my question is : Do you see how that could be possible ?

Thanks, i can give you more information if needed.

Best regards,

Thibault


  was:
Hello,

I have an issue with my Kindle Fire (Android 2.3)

First, i've managed to create a sample app to reproduce the bug: 
https://github.com/mosalingua/cordova-sampleapp-bug-media-sound-kindle

You can download the apk here : 
https://github.com/mosalingua/cordova-sampleapp-bug-media-sound-kindle/raw/master/platforms/android/bin/HelloWorld-debug.apk

This app just has a button to play a sound, and we can visualise the Media 
Callback when they are called. 

And the problem is that on the Kindle Fire (Based on Android OS 2.3.3), the 
callback mediaSuccess isn't called. 

I've tested on these devices:

 - Kindle Fire (1st GEN), Android 2.3.3 = KO
 - Nexus 7, Android 4.4 = OK
 - Samsung Galaxy S1, Android 2.3.3 = OK 
 - Samsung Galaxy S2, Android 4.0.4 = OK

As i've released my app on Amazon, i'm currently blocked on this platform to 
keep releasing update, mi last update was based on cordova 2.7, which worked 
fine on Kindle.

I've dug into the Media Plugin, and i've find out that int the AudioPlayer.java 
, the setState method is working just fine, and send this message to the 
javascript part with the correct status. ( 4 == MEDIA_STOPPED )
cordova.require('org.apache.cordova.media.Media').onStatus('c5f1ec7b-9cdf-0a49-3f62-0def8bd2d9b2',
 1, 4);

But, when i put a console.log in the Media.onStatus callback in the Media.js 
file, i don't get anything, it seems that the message isn't caught.
So my question is : Do you see how that could be possible ?

Thanks, i can give you more information if needed.

Best regards,

Thibault



 Cordova Media doesn't work properly on Kindle Fire (Android 2.3)
 

 Key: CB-6011
 URL: https://issues.apache.org/jira/browse/CB-6011
 Project: Apache Cordova
  Issue Type: Bug
  Components: Android
Affects Versions: 3.3.0
 Environment: Kindle Fire (1st generation ), Based on Android OS 2.3.3
Reporter: Thibault Durand
Priority: Blocker

 Hello,
 I have an issue with my Kindle Fire (Android 2.3)
 First, i've managed to create a sample app to reproduce the bug: 
 https://github.com/mosalingua/cordova-sampleapp-bug-media-sound-kindle
 You can download the apk here : 
 https://github.com/mosalingua/cordova-sampleapp-bug-media-sound-kindle/raw/master/platforms/android/bin/HelloWorld-debug.apk
 This app just has a button to play a sound, and we can visualise the Media 
 Callback when they are called. 
 And the problem is that on the Kindle Fire (Based on Android OS 2.3.3), the 
 callback mediaSuccess isn't called. 
 I've tested on these devices:
  - Kindle Fire (1st GEN), Android 2.3.3 = KO
  - Nexus 7, Android 4.4 = OK
  - Samsung Galaxy S1, Android 2.3.3 = OK 
  - Samsung Galaxy S2, Android 4.0.4 = OK
 As i've released my app on Amazon, i'm currently blocked on this platform to 
 keep releasing update, my last update was based on cordova 2.7, which worked 
 fine on Kindle.
 I've dug into the Media Plugin, and i've find out that in the 
 AudioPlayer.java , the setState method is working just fine, and send this 
 message to the javascript part with the correct status ( 4 == MEDIA_STOPPED ):
 

[jira] [Updated] (CB-5999) App crashes on Nexus 5/Kitkat 4.4.2 with error Unable to lock surface

[Andrew Grieve (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-5999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Grieve updated CB-5999:
--

Priority: Minor  (was: Blocker)

 App crashes on Nexus 5/Kitkat 4.4.2 with error Unable to lock surface
 ---

 Key: CB-5999
 URL: https://issues.apache.org/jira/browse/CB-5999
 Project: Apache Cordova
  Issue Type: Bug
  Components: Android
Affects Versions: 3.3.0
 Environment: Published from Windows 8.1 Professional, using ADT 
 v22.2.1-833290 and Cordova 3.3.1-0.3.0
 Published to fresh out of box (European) Nexus 5, running KitKat 4.4.2
Reporter: Christiaan Rakowski
Priority: Minor

 We have a cordova app which was developed for iOS, and runs fine there.
 Now we are porting it over to Android and we get the following crash during 
 start up:
 {{{quote}
 02-10 13:39:11.231: E/Surface(31190): dequeueBuffer failed (Invalid argument)
 02-10 13:39:11.241: E/ViewRootImpl(31190): Could not lock surface
 02-10 13:39:11.241: E/ViewRootImpl(31190): java.lang.IllegalArgumentException
 02-10 13:39:11.241: E/ViewRootImpl(31190):at 
 android.view.Surface.nativeLockCanvas(Native Method)
 02-10 13:39:11.241: E/ViewRootImpl(31190):at 
 android.view.Surface.lockCanvas(Surface.java:243)
 02-10 13:39:11.241: E/ViewRootImpl(31190):at 
 android.view.ViewRootImpl.drawSoftware(ViewRootImpl.java:2435)
 02-10 13:39:11.241: E/ViewRootImpl(31190):at 
 android.view.ViewRootImpl.draw(ViewRootImpl.java:2409)
 02-10 13:39:11.241: E/ViewRootImpl(31190):at 
 android.view.ViewRootImpl.performDraw(ViewRootImpl.java:2253)
 02-10 13:39:11.241: E/ViewRootImpl(31190):at 
 android.view.ViewRootImpl.performTraversals(ViewRootImpl.java:1883)
 02-10 13:39:11.241: E/ViewRootImpl(31190):at 
 android.view.ViewRootImpl.doTraversal(ViewRootImpl.java:1000)
 02-10 13:39:11.241: E/ViewRootImpl(31190):at 
 android.view.ViewRootImpl$TraversalRunnable.run(ViewRootImpl.java:5670)
 02-10 13:39:11.241: E/ViewRootImpl(31190):at 
 android.view.Choreographer$CallbackRecord.run(Choreographer.java:761)
 02-10 13:39:11.241: E/ViewRootImpl(31190):at 
 android.view.Choreographer.doCallbacks(Choreographer.java:574)
 02-10 13:39:11.241: E/ViewRootImpl(31190):at 
 android.view.Choreographer.doFrame(Choreographer.java:544)
 02-10 13:39:11.241: E/ViewRootImpl(31190):at 
 android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:747)
 02-10 13:39:11.241: E/ViewRootImpl(31190):at 
 android.os.Handler.handleCallback(Handler.java:733)
 02-10 13:39:11.241: E/ViewRootImpl(31190):at 
 android.os.Handler.dispatchMessage(Handler.java:95)
 02-10 13:39:11.241: E/ViewRootImpl(31190):at 
 android.os.Looper.loop(Looper.java:136)
 02-10 13:39:11.241: E/ViewRootImpl(31190):at 
 android.app.ActivityThread.main(ActivityThread.java:5017)
 02-10 13:39:11.241: E/ViewRootImpl(31190):at 
 java.lang.reflect.Method.invokeNative(Native Method)
 02-10 13:39:11.241: E/ViewRootImpl(31190):at 
 java.lang.reflect.Method.invoke(Method.java:515)
 02-10 13:39:11.241: E/ViewRootImpl(31190):at 
 com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:779)
 02-10 13:39:11.241: E/ViewRootImpl(31190):at 
 com.android.internal.os.ZygoteInit.main(ZygoteInit.java:595)
 02-10 13:39:11.241: E/ViewRootImpl(31190):at 
 dalvik.system.NativeStart.main(Native Method)
 {quote}}}
 I have tried attaching the Chrome debug bridge, but that gave me no 
 additional information.
 I did some searching online, but in all the posts I found people using OpenGL 
 directly, but none of them had a real solution either. Most of the posts were 
 from people running on Snapdragon 800 devices though.
 I assume css3 transitions/transforms get translated to OpenGL by the 
 ChromeWebView, so I think this might be related to the SoC and how it handles 
 OpenGL. I currently don't have access to a different Android device, so I 
 can't do more testing with that.
 I have tested the Hello World application, and that did run fine on the Nexus 
 5.
 If you have any tests you would like me to run or need addition information, 
 please let me know.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Commented] (CB-5999) App crashes on Nexus 5/Kitkat 4.4.2 with error Unable to lock surface

[Andrew Grieve (JIRA)]

[ 
https://issues.apache.org/jira/browse/CB-5999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13897941#comment-13897941
 ] 

Andrew Grieve commented on CB-5999:
---

Lowered the priority.

Would certainly be interested to know the culprit if you figure it out. Thanks 
for digging.

 App crashes on Nexus 5/Kitkat 4.4.2 with error Unable to lock surface
 ---

 Key: CB-5999
 URL: https://issues.apache.org/jira/browse/CB-5999
 Project: Apache Cordova
  Issue Type: Bug
  Components: Android
Affects Versions: 3.3.0
 Environment: Published from Windows 8.1 Professional, using ADT 
 v22.2.1-833290 and Cordova 3.3.1-0.3.0
 Published to fresh out of box (European) Nexus 5, running KitKat 4.4.2
Reporter: Christiaan Rakowski
Priority: Minor

 We have a cordova app which was developed for iOS, and runs fine there.
 Now we are porting it over to Android and we get the following crash during 
 start up:
 {{{quote}
 02-10 13:39:11.231: E/Surface(31190): dequeueBuffer failed (Invalid argument)
 02-10 13:39:11.241: E/ViewRootImpl(31190): Could not lock surface
 02-10 13:39:11.241: E/ViewRootImpl(31190): java.lang.IllegalArgumentException
 02-10 13:39:11.241: E/ViewRootImpl(31190):at 
 android.view.Surface.nativeLockCanvas(Native Method)
 02-10 13:39:11.241: E/ViewRootImpl(31190):at 
 android.view.Surface.lockCanvas(Surface.java:243)
 02-10 13:39:11.241: E/ViewRootImpl(31190):at 
 android.view.ViewRootImpl.drawSoftware(ViewRootImpl.java:2435)
 02-10 13:39:11.241: E/ViewRootImpl(31190):at 
 android.view.ViewRootImpl.draw(ViewRootImpl.java:2409)
 02-10 13:39:11.241: E/ViewRootImpl(31190):at 
 android.view.ViewRootImpl.performDraw(ViewRootImpl.java:2253)
 02-10 13:39:11.241: E/ViewRootImpl(31190):at 
 android.view.ViewRootImpl.performTraversals(ViewRootImpl.java:1883)
 02-10 13:39:11.241: E/ViewRootImpl(31190):at 
 android.view.ViewRootImpl.doTraversal(ViewRootImpl.java:1000)
 02-10 13:39:11.241: E/ViewRootImpl(31190):at 
 android.view.ViewRootImpl$TraversalRunnable.run(ViewRootImpl.java:5670)
 02-10 13:39:11.241: E/ViewRootImpl(31190):at 
 android.view.Choreographer$CallbackRecord.run(Choreographer.java:761)
 02-10 13:39:11.241: E/ViewRootImpl(31190):at 
 android.view.Choreographer.doCallbacks(Choreographer.java:574)
 02-10 13:39:11.241: E/ViewRootImpl(31190):at 
 android.view.Choreographer.doFrame(Choreographer.java:544)
 02-10 13:39:11.241: E/ViewRootImpl(31190):at 
 android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:747)
 02-10 13:39:11.241: E/ViewRootImpl(31190):at 
 android.os.Handler.handleCallback(Handler.java:733)
 02-10 13:39:11.241: E/ViewRootImpl(31190):at 
 android.os.Handler.dispatchMessage(Handler.java:95)
 02-10 13:39:11.241: E/ViewRootImpl(31190):at 
 android.os.Looper.loop(Looper.java:136)
 02-10 13:39:11.241: E/ViewRootImpl(31190):at 
 android.app.ActivityThread.main(ActivityThread.java:5017)
 02-10 13:39:11.241: E/ViewRootImpl(31190):at 
 java.lang.reflect.Method.invokeNative(Native Method)
 02-10 13:39:11.241: E/ViewRootImpl(31190):at 
 java.lang.reflect.Method.invoke(Method.java:515)
 02-10 13:39:11.241: E/ViewRootImpl(31190):at 
 com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:779)
 02-10 13:39:11.241: E/ViewRootImpl(31190):at 
 com.android.internal.os.ZygoteInit.main(ZygoteInit.java:595)
 02-10 13:39:11.241: E/ViewRootImpl(31190):at 
 dalvik.system.NativeStart.main(Native Method)
 {quote}}}
 I have tried attaching the Chrome debug bridge, but that gave me no 
 additional information.
 I did some searching online, but in all the posts I found people using OpenGL 
 directly, but none of them had a real solution either. Most of the posts were 
 from people running on Snapdragon 800 devices though.
 I assume css3 transitions/transforms get translated to OpenGL by the 
 ChromeWebView, so I think this might be related to the SoC and how it handles 
 OpenGL. I currently don't have access to a different Android device, so I 
 can't do more testing with that.
 I have tested the Hello World application, and that did run fine on the Nexus 
 5.
 If you have any tests you would like me to run or need addition information, 
 please let me know.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Assigned] (CB-5233) Make resolveLocalFileSystemURL() work with asset-library:// URLs returned by the Camera API

[Ian Clelland (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-5233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ian Clelland reassigned CB-5233:


Assignee: Ian Clelland  (was: Andrew Grieve)

 Make resolveLocalFileSystemURL() work with asset-library:// URLs returned by 
 the Camera API
 ---

 Key: CB-5233
 URL: https://issues.apache.org/jira/browse/CB-5233
 Project: Apache Cordova
  Issue Type: Bug
  Components: iOS, Plugin File
Reporter: Andrew Grieve
Assignee: Ian Clelland
Priority: Minor





--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Resolved] (CB-6004) Run Benchmark-ArrayBuffer but 'Echo plugin did not respond'

[Andrew Grieve (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-6004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Grieve resolved CB-6004.
---

   Resolution: Fixed
Fix Version/s: 3.5.0
 Assignee: Andrew Grieve

 Run Benchmark-ArrayBuffer but 'Echo plugin did not respond'
 

 Key: CB-6004
 URL: https://issues.apache.org/jira/browse/CB-6004
 Project: Apache Cordova
  Issue Type: Bug
  Components: mobile-spec
Affects Versions: 3.3.0
Reporter: glmnbeyond
Assignee: Andrew Grieve
 Fix For: 3.5.0


 Can't run Benchmark-ArrayBuffer test since ‘module cordova/plugin/echo not 
 found’



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Commented] (CB-6004) Run Benchmark-ArrayBuffer but 'Echo plugin did not respond'

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/CB-6004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13897948#comment-13897948
 ] 

ASF subversion and git services commented on CB-6004:
-

Commit c6dd498dd5f5738505580d31e159f8cfdab61065 in branch refs/heads/master 
from [~glmnbeyond]
[ https://git-wip-us.apache.org/repos/asf?p=cordova-mobile-spec.git;h=c6dd498 ]

CB-6004 Fix the problem that run Benchmark-ArrayBuffer test but 'Echo plugin 
did not respond'

The safari console window outputs ‘module cordova/plugin/echo not
found’!


 Run Benchmark-ArrayBuffer but 'Echo plugin did not respond'
 

 Key: CB-6004
 URL: https://issues.apache.org/jira/browse/CB-6004
 Project: Apache Cordova
  Issue Type: Bug
  Components: mobile-spec
Affects Versions: 3.3.0
Reporter: glmnbeyond
 Fix For: 3.5.0


 Can't run Benchmark-ArrayBuffer test since ‘module cordova/plugin/echo not 
 found’



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Commented] (CB-6005) Can't go back from Benchmark test page!

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/CB-6005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13897950#comment-13897950
 ] 

ASF subversion and git services commented on CB-6005:
-

Commit 3f5528ba125d3419a042ce33f70b898f052fb605 in branch refs/heads/master 
from [~glmnbeyond]
[ https://git-wip-us.apache.org/repos/asf?p=cordova-mobile-spec.git;h=3f5528b ]

CB-6005 Add back button for Benchmark test page!


 Can't go back from Benchmark test page!
 ---

 Key: CB-6005
 URL: https://issues.apache.org/jira/browse/CB-6005
 Project: Apache Cordova
  Issue Type: Bug
  Components: mobile-spec
Affects Versions: 3.3.0
Reporter: glmnbeyond
 Fix For: 3.5.0


 1. Load mobile-spec
 2. Go to Benchmark test page
 3. There is no 'Back' button to go back!



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Assigned] (CB-6007) If cordova.js is referenced using cache bust the plugin path is derived incorrectly.

[Andrew Grieve (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-6007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Grieve reassigned CB-6007:
-

Assignee: Andrew Grieve

 If cordova.js is referenced using cache bust the plugin path is derived 
 incorrectly.
 

 Key: CB-6007
 URL: https://issues.apache.org/jira/browse/CB-6007
 Project: Apache Cordova
  Issue Type: Bug
  Components: CordovaJS
Affects Versions: 3.3.0
Reporter: Rik Schennink
Assignee: Andrew Grieve

 The path below functions correctly.
 vendor/apache/ios/cordova.js - vendor/apache/ios
 The following path returns 'null'.
 vendor/apache/ios/cordova.js?bust=v1.1
 Problem is located in 'findCordovaPath()' line '1369'. Adding the following 
 line of js before the if statement fixes the problem for me (could probably 
 be optimised).
 {code}
 // make sure querystring parameters are not taken into account in the 
 comparison
 src = src.indexOf('?') !== -1 ? src.split('?')[0] : src;
 {code}



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Commented] (CB-6007) If cordova.js is referenced using cache bust the plugin path is derived incorrectly.

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/CB-6007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13897961#comment-13897961
 ] 

ASF subversion and git services commented on CB-6007:
-

Commit e0967ed4cec10dbfdd56c3e742532ce9b7356610 in branch refs/heads/master 
from [~agrieve]
[ https://git-wip-us.apache.org/repos/asf?p=cordova-mobile-spec.git;h=e0967ed ]

CB-6007 mobile spec test for script src=cordova.js?foo


 If cordova.js is referenced using cache bust the plugin path is derived 
 incorrectly.
 

 Key: CB-6007
 URL: https://issues.apache.org/jira/browse/CB-6007
 Project: Apache Cordova
  Issue Type: Bug
  Components: CordovaJS
Affects Versions: 3.3.0
Reporter: Rik Schennink
Assignee: Andrew Grieve
 Fix For: 3.5.0


 The path below functions correctly.
 vendor/apache/ios/cordova.js - vendor/apache/ios
 The following path returns 'null'.
 vendor/apache/ios/cordova.js?bust=v1.1
 Problem is located in 'findCordovaPath()' line '1369'. Adding the following 
 line of js before the if statement fixes the problem for me (could probably 
 be optimised).
 {code}
 // make sure querystring parameters are not taken into account in the 
 comparison
 src = src.indexOf('?') !== -1 ? src.split('?')[0] : src;
 {code}



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Commented] (CB-6007) If cordova.js is referenced using cache bust the plugin path is derived incorrectly.

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/CB-6007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13897964#comment-13897964
 ] 

ASF subversion and git services commented on CB-6007:
-

Commit 799eed5f90a2e332d9f90257a7b4faf29ddcebe3 in branch refs/heads/master 
from [~agrieve]
[ https://git-wip-us.apache.org/repos/asf?p=cordova-js.git;h=799eed5 ]

CB-6007 Fix findCordovaPath() not working when path contains a query param


 If cordova.js is referenced using cache bust the plugin path is derived 
 incorrectly.
 

 Key: CB-6007
 URL: https://issues.apache.org/jira/browse/CB-6007
 Project: Apache Cordova
  Issue Type: Bug
  Components: CordovaJS
Affects Versions: 3.3.0
Reporter: Rik Schennink
Assignee: Andrew Grieve
 Fix For: 3.5.0


 The path below functions correctly.
 vendor/apache/ios/cordova.js - vendor/apache/ios
 The following path returns 'null'.
 vendor/apache/ios/cordova.js?bust=v1.1
 Problem is located in 'findCordovaPath()' line '1369'. Adding the following 
 line of js before the if statement fixes the problem for me (could probably 
 be optimised).
 {code}
 // make sure querystring parameters are not taken into account in the 
 comparison
 src = src.indexOf('?') !== -1 ? src.split('?')[0] : src;
 {code}



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Resolved] (CB-6007) If cordova.js is referenced using cache bust the plugin path is derived incorrectly.

[Andrew Grieve (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-6007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Grieve resolved CB-6007.
---

   Resolution: Fixed
Fix Version/s: 3.5.0

 If cordova.js is referenced using cache bust the plugin path is derived 
 incorrectly.
 

 Key: CB-6007
 URL: https://issues.apache.org/jira/browse/CB-6007
 Project: Apache Cordova
  Issue Type: Bug
  Components: CordovaJS
Affects Versions: 3.3.0
Reporter: Rik Schennink
Assignee: Andrew Grieve
 Fix For: 3.5.0


 The path below functions correctly.
 vendor/apache/ios/cordova.js - vendor/apache/ios
 The following path returns 'null'.
 vendor/apache/ios/cordova.js?bust=v1.1
 Problem is located in 'findCordovaPath()' line '1369'. Adding the following 
 line of js before the if statement fixes the problem for me (could probably 
 be optimised).
 {code}
 // make sure querystring parameters are not taken into account in the 
 comparison
 src = src.indexOf('?') !== -1 ? src.split('?')[0] : src;
 {code}



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Assigned] (CB-6010) CDVAssetLibraryFilesystem does not have URLforFilesystemPath

[Ian Clelland (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-6010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ian Clelland reassigned CB-6010:


Assignee: Ian Clelland

 CDVAssetLibraryFilesystem does not have URLforFilesystemPath
 

 Key: CB-6010
 URL: https://issues.apache.org/jira/browse/CB-6010
 Project: Apache Cordova
  Issue Type: Bug
  Components: Plugin File, Plugin File Transfer
Affects Versions: 3.3.0
 Environment: ios
Reporter: Claudius Coenen
Assignee: Ian Clelland

 when i try to {{FileTransfer.download(...)}} a file (code itself used to work 
 in 2.7) my app now crashes.
 Step-Debugging revealed, that in {{CDVFile#fileSystemURLforLocalPath}} _(Line 
 267)_ all available filesystems are tested. One of those appears to be a 
 {{CDVAssetLibraryFilesystem}} - which does not implement 
 {{URLforFilesystemPath}}
 I added a dummy {{URLforFilesystemPath}} wich just returns {{nil}}. This got 
 me around the crash, but now i'm stuck with a {{FILE_NOT_FOUND_ERR}}, which 
 is probably my own responsibility. But the aforementioned crash took me a 
 while to find.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Commented] (CB-6010) CDVAssetLibraryFilesystem does not have URLforFilesystemPath

[Ian Clelland (JIRA)]

[ 
https://issues.apache.org/jira/browse/CB-6010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13897967#comment-13897967
 ] 

Ian Clelland commented on CB-6010:
--

Thanks for tracking that down; I'm making some changes to 
CDVAssetLibraryFilesystem right now, and I'm definitely going to fix that.

I don't believe that the AssetLibrary assets can be simply mapped to a 
device-filesystem-path, so returning nil is probably the right thing to do.

I'll add that method to the protocol definition so that it will be very obvious 
if it isn't implemented in future filesystems as well.

 CDVAssetLibraryFilesystem does not have URLforFilesystemPath
 

 Key: CB-6010
 URL: https://issues.apache.org/jira/browse/CB-6010
 Project: Apache Cordova
  Issue Type: Bug
  Components: Plugin File, Plugin File Transfer
Affects Versions: 3.3.0
 Environment: ios
Reporter: Claudius Coenen
Assignee: Ian Clelland

 when i try to {{FileTransfer.download(...)}} a file (code itself used to work 
 in 2.7) my app now crashes.
 Step-Debugging revealed, that in {{CDVFile#fileSystemURLforLocalPath}} _(Line 
 267)_ all available filesystems are tested. One of those appears to be a 
 {{CDVAssetLibraryFilesystem}} - which does not implement 
 {{URLforFilesystemPath}}
 I added a dummy {{URLforFilesystemPath}} wich just returns {{nil}}. This got 
 me around the crash, but now i'm stuck with a {{FILE_NOT_FOUND_ERR}}, which 
 is probably my own responsibility. But the aforementioned crash took me a 
 while to find.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Commented] (CB-6010) CDVAssetLibraryFilesystem does not have URLforFilesystemPath

[Ian Clelland (JIRA)]

[ 
https://issues.apache.org/jira/browse/CB-6010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13897974#comment-13897974
 ] 

Ian Clelland commented on CB-6010:
--

Checking again; it's an optional method already; the error is in failing to 
check whether a particular filesystem object responds to it before sending it 
the message. I'll update that in CDVFile.m

 CDVAssetLibraryFilesystem does not have URLforFilesystemPath
 

 Key: CB-6010
 URL: https://issues.apache.org/jira/browse/CB-6010
 Project: Apache Cordova
  Issue Type: Bug
  Components: Plugin File, Plugin File Transfer
Affects Versions: 3.3.0
 Environment: ios
Reporter: Claudius Coenen
Assignee: Ian Clelland

 when i try to {{FileTransfer.download(...)}} a file (code itself used to work 
 in 2.7) my app now crashes.
 Step-Debugging revealed, that in {{CDVFile#fileSystemURLforLocalPath}} _(Line 
 267)_ all available filesystems are tested. One of those appears to be a 
 {{CDVAssetLibraryFilesystem}} - which does not implement 
 {{URLforFilesystemPath}}
 I added a dummy {{URLforFilesystemPath}} wich just returns {{nil}}. This got 
 me around the crash, but now i'm stuck with a {{FILE_NOT_FOUND_ERR}}, which 
 is probably my own responsibility. But the aforementioned crash took me a 
 while to find.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Assigned] (CB-4902) Broken reference to old API in FileTransfer plugin

[Ian Clelland (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-4902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ian Clelland reassigned CB-4902:


Assignee: Ian Clelland

 Broken reference to old API in FileTransfer plugin
 --

 Key: CB-4902
 URL: https://issues.apache.org/jira/browse/CB-4902
 Project: Apache Cordova
  Issue Type: Bug
  Components: Plugin File, Plugin File Transfer
Affects Versions: 3.0.0
 Environment: OS X / iOS
Reporter: Michael Gauthier
Assignee: Ian Clelland

 After installing the org.apache.cordova.file and org.apache.cordova.file 
 plugins my app fails to initialize. JavaScript stack trace when the app 
 starts up is:
 [Error] module org.apache.cordova.core.file.ProgressEvent not found
   require (cordova.js, line 56)
   localRequire (cordova.js, line 46)
   (anonymous function) (FileTransfer.js, line 25)
   build (cordova.js, line 50)
   require (cordova.js, line 65)
   localRequire (cordova.js, line 46)
   mapModules (cordova.js, line 1135)
   initialize (cordova.js, line 1197)
   (anonymous function) (cordova.js, line 1609)
   f (cordova.js, line 641)
   fire (cordova.js, line 769)
   finishPluginLoading (cordova.js, line 1295)
   onScriptLoadingComplete (cordova.js, line 1288)
   scriptLoadedCallback (cordova.js, line 1312)



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Resolved] (CB-4902) Broken reference to old API in FileTransfer plugin

[Ian Clelland (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-4902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ian Clelland resolved CB-4902.
--

   Resolution: Fixed
Fix Version/s: 3.4.0

Closing this; I was never able to reproduce the issue, and I believe that it 
should not be present in any case in the newly-released versions of File and 
File-Transfer.

If this is still occurring, please re-open.

 Broken reference to old API in FileTransfer plugin
 --

 Key: CB-4902
 URL: https://issues.apache.org/jira/browse/CB-4902
 Project: Apache Cordova
  Issue Type: Bug
  Components: Plugin File, Plugin File Transfer
Affects Versions: 3.0.0
 Environment: OS X / iOS
Reporter: Michael Gauthier
Assignee: Ian Clelland
 Fix For: 3.4.0


 After installing the org.apache.cordova.file and org.apache.cordova.file 
 plugins my app fails to initialize. JavaScript stack trace when the app 
 starts up is:
 [Error] module org.apache.cordova.core.file.ProgressEvent not found
   require (cordova.js, line 56)
   localRequire (cordova.js, line 46)
   (anonymous function) (FileTransfer.js, line 25)
   build (cordova.js, line 50)
   require (cordova.js, line 65)
   localRequire (cordova.js, line 46)
   mapModules (cordova.js, line 1135)
   initialize (cordova.js, line 1197)
   (anonymous function) (cordova.js, line 1609)
   f (cordova.js, line 641)
   fire (cordova.js, line 769)
   finishPluginLoading (cordova.js, line 1295)
   onScriptLoadingComplete (cordova.js, line 1288)
   scriptLoadedCallback (cordova.js, line 1312)



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Created] (CB-6012) Important query parameters shouldn't be dropped on cdvfile:// urls

[Ian Clelland (JIRA)]

Ian Clelland created CB-6012:


 Summary: Important query parameters shouldn't be dropped on 
cdvfile:// urls
 Key: CB-6012
 URL: https://issues.apache.org/jira/browse/CB-6012
 Project: Apache Cordova
  Issue Type: Bug
  Components: iOS, Plugin File
Affects Versions: 3.4.0
Reporter: Ian Clelland
Assignee: Ian Clelland


Mobile spec file test 10 checks that resolving a local url with query 
parameters returns a file entry object without those parameters.

On iOS, at least, those parameters may be useful for asset-library urls. They 
shouldn't be dropped automatically on cdvfile:// urls, I think. The correct 
behaviour would be to drop them on old-style file:/// urls, but not on any urls 
which are explicitly managed by the File plugin.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Commented] (CB-6012) Important query parameters shouldn't be dropped on cdvfile:// urls

[Ian Clelland (JIRA)]

[ 
https://issues.apache.org/jira/browse/CB-6012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13897995#comment-13897995
 ] 

Ian Clelland commented on CB-6012:
--

Linking to the original issue which added these tests

 Important query parameters shouldn't be dropped on cdvfile:// urls
 --

 Key: CB-6012
 URL: https://issues.apache.org/jira/browse/CB-6012
 Project: Apache Cordova
  Issue Type: Bug
  Components: iOS, Plugin File
Affects Versions: 3.4.0
Reporter: Ian Clelland
Assignee: Ian Clelland

 Mobile spec file test 10 checks that resolving a local url with query 
 parameters returns a file entry object without those parameters.
 On iOS, at least, those parameters may be useful for asset-library urls. They 
 shouldn't be dropped automatically on cdvfile:// urls, I think. The correct 
 behaviour would be to drop them on old-style file:/// urls, but not on any 
 urls which are explicitly managed by the File plugin.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Commented] (CB-6012) Important query parameters shouldn't be dropped on cdvfile:// urls

[Ian Clelland (JIRA)]

[ 
https://issues.apache.org/jira/browse/CB-6012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13898007#comment-13898007
 ] 

Ian Clelland commented on CB-6012:
--

Also, the localfilesystem file systems should strip the query parameters when 
constructing file paths, and may not preserve them when returning new URLs. 
(Especially when traversing directories to find new files, there should be no 
expectation that query parameters are preserved.)

 Important query parameters shouldn't be dropped on cdvfile:// urls
 --

 Key: CB-6012
 URL: https://issues.apache.org/jira/browse/CB-6012
 Project: Apache Cordova
  Issue Type: Bug
  Components: iOS, Plugin File
Affects Versions: 3.4.0
Reporter: Ian Clelland
Assignee: Ian Clelland

 Mobile spec file test 10 checks that resolving a local url with query 
 parameters returns a file entry object without those parameters.
 On iOS, at least, those parameters may be useful for asset-library urls. They 
 shouldn't be dropped automatically on cdvfile:// urls, I think. The correct 
 behaviour would be to drop them on old-style file:/// urls, but not on any 
 urls which are explicitly managed by the File plugin.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Commented] (CB-6012) Important query parameters shouldn't be dropped on cdvfile:// urls

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/CB-6012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13898010#comment-13898010
 ] 

ASF subversion and git services commented on CB-6012:
-

Commit 88ab61bf9f7cc6ac21a8ef8c49917cc289032d26 in branch refs/heads/master 
from [~iclelland]
[ https://git-wip-us.apache.org/repos/asf?p=cordova-mobile-spec.git;h=88ab61b ]

CB-6012: Don't necessarily drop query parameters from File plugin URLs


 Important query parameters shouldn't be dropped on cdvfile:// urls
 --

 Key: CB-6012
 URL: https://issues.apache.org/jira/browse/CB-6012
 Project: Apache Cordova
  Issue Type: Bug
  Components: iOS, Plugin File
Affects Versions: 3.4.0
Reporter: Ian Clelland
Assignee: Ian Clelland

 Mobile spec file test 10 checks that resolving a local url with query 
 parameters returns a file entry object without those parameters.
 On iOS, at least, those parameters may be useful for asset-library urls. They 
 shouldn't be dropped automatically on cdvfile:// urls, I think. The correct 
 behaviour would be to drop them on old-style file:/// urls, but not on any 
 urls which are explicitly managed by the File plugin.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Assigned] (CB-5438) Can't build/test cordova-js on Windows

[Andrew Grieve (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-5438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Grieve reassigned CB-5438:
-

Assignee: Andrew Grieve

 Can't build/test cordova-js on Windows
 --

 Key: CB-5438
 URL: https://issues.apache.org/jira/browse/CB-5438
 Project: Apache Cordova
  Issue Type: Bug
  Components: CordovaJS
Affects Versions: Master
 Environment: Windows 8 x64
 Node v0.10.13
Reporter: qi
Assignee: Andrew Grieve
Priority: Critical

 Simply run 'grunt build', got,
 Running jshint:src (jshint) task
 Linting lib/test/androidexec.js ...ERROR
 [L1:C1] E030: Expected an identifier and instead saw '.'.
 ../android/exec.js
 [L1:C2] E033: Expected an operator and instead saw '.'.
 ../android/exec.js
 [L1:C3] E033: Expected an operator and instead saw '/'.
 ../android/exec.js
 [L1:C4] W033: Missing semicolon.
 ../android/exec.js
 [L1:C4] W015: Expected 'android' to have an indentation at 1 instead at 4.
 ../android/exec.js
 [L1:C19] W033: Missing semicolon.
 ../android/exec.js
 [L1:C4] W117: 'android' is not defined.
 ../android/exec.js
 [L1:C12] W117: 'exec' is not defined.
 ../android/exec.js
 Linting lib/test/iosexec.js ...ERROR
 [L1:C1] E030: Expected an identifier and instead saw '.'.
 ../ios/exec.js
 [L1:C2] E033: Expected an operator and instead saw '.'.
 ../ios/exec.js
 [L1:C3] E033: Expected an operator and instead saw '/'.
 ../ios/exec.js
 [L1:C4] W033: Missing semicolon.
 ../ios/exec.js
 [L1:C4] W015: Expected 'ios' to have an indentation at 1 instead at 4.
 ../ios/exec.js
 [L1:C15] W033: Missing semicolon.
 ../ios/exec.js
 [L1:C4] W117: 'ios' is not defined.
 ../ios/exec.js
 [L1:C8] W117: 'exec' is not defined.
 ../ios/exec.js
 Warning: Task jshint:src failed. Use --force to continue.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Commented] (CB-5438) Can't build/test cordova-js on Windows

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/CB-5438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13898012#comment-13898012
 ] 

ASF subversion and git services commented on CB-5438:
-

Commit 19f9c02ac7d09b371b78d7ff7489f91de021a7e6 in branch refs/heads/master 
from [~agrieve]
[ https://git-wip-us.apache.org/repos/asf?p=cordova-js.git;h=19f9c02 ]

CB-5438 Remove test symlinks  fix some build errors on windows.


 Can't build/test cordova-js on Windows
 --

 Key: CB-5438
 URL: https://issues.apache.org/jira/browse/CB-5438
 Project: Apache Cordova
  Issue Type: Bug
  Components: CordovaJS
Affects Versions: Master
 Environment: Windows 8 x64
 Node v0.10.13
Reporter: qi
Assignee: Andrew Grieve
Priority: Critical

 Simply run 'grunt build', got,
 Running jshint:src (jshint) task
 Linting lib/test/androidexec.js ...ERROR
 [L1:C1] E030: Expected an identifier and instead saw '.'.
 ../android/exec.js
 [L1:C2] E033: Expected an operator and instead saw '.'.
 ../android/exec.js
 [L1:C3] E033: Expected an operator and instead saw '/'.
 ../android/exec.js
 [L1:C4] W033: Missing semicolon.
 ../android/exec.js
 [L1:C4] W015: Expected 'android' to have an indentation at 1 instead at 4.
 ../android/exec.js
 [L1:C19] W033: Missing semicolon.
 ../android/exec.js
 [L1:C4] W117: 'android' is not defined.
 ../android/exec.js
 [L1:C12] W117: 'exec' is not defined.
 ../android/exec.js
 Linting lib/test/iosexec.js ...ERROR
 [L1:C1] E030: Expected an identifier and instead saw '.'.
 ../ios/exec.js
 [L1:C2] E033: Expected an operator and instead saw '.'.
 ../ios/exec.js
 [L1:C3] E033: Expected an operator and instead saw '/'.
 ../ios/exec.js
 [L1:C4] W033: Missing semicolon.
 ../ios/exec.js
 [L1:C4] W015: Expected 'ios' to have an indentation at 1 instead at 4.
 ../ios/exec.js
 [L1:C15] W033: Missing semicolon.
 ../ios/exec.js
 [L1:C4] W117: 'ios' is not defined.
 ../ios/exec.js
 [L1:C8] W117: 'exec' is not defined.
 ../ios/exec.js
 Warning: Task jshint:src failed. Use --force to continue.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Commented] (CB-5999) App crashes on Nexus 5/Kitkat 4.4.2 with error Unable to lock surface

[Marcel Kinard (JIRA)]

[ 
https://issues.apache.org/jira/browse/CB-5999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13898006#comment-13898006
 ] 

Marcel Kinard commented on CB-5999:
---

I think lockCanvas is used to permit only a single thread to draw to a canvas. 
Cordova doesn't draw directly, it pretty much gives you an empty webview. 
Looking at the class and package names in the stack trace, I don't see any 
Cordova names. That would lead me to believe this is not Cordova related.

 App crashes on Nexus 5/Kitkat 4.4.2 with error Unable to lock surface
 ---

 Key: CB-5999
 URL: https://issues.apache.org/jira/browse/CB-5999
 Project: Apache Cordova
  Issue Type: Bug
  Components: Android
Affects Versions: 3.3.0
 Environment: Published from Windows 8.1 Professional, using ADT 
 v22.2.1-833290 and Cordova 3.3.1-0.3.0
 Published to fresh out of box (European) Nexus 5, running KitKat 4.4.2
Reporter: Christiaan Rakowski
Priority: Minor

 We have a cordova app which was developed for iOS, and runs fine there.
 Now we are porting it over to Android and we get the following crash during 
 start up:
 {{{quote}
 02-10 13:39:11.231: E/Surface(31190): dequeueBuffer failed (Invalid argument)
 02-10 13:39:11.241: E/ViewRootImpl(31190): Could not lock surface
 02-10 13:39:11.241: E/ViewRootImpl(31190): java.lang.IllegalArgumentException
 02-10 13:39:11.241: E/ViewRootImpl(31190):at 
 android.view.Surface.nativeLockCanvas(Native Method)
 02-10 13:39:11.241: E/ViewRootImpl(31190):at 
 android.view.Surface.lockCanvas(Surface.java:243)
 02-10 13:39:11.241: E/ViewRootImpl(31190):at 
 android.view.ViewRootImpl.drawSoftware(ViewRootImpl.java:2435)
 02-10 13:39:11.241: E/ViewRootImpl(31190):at 
 android.view.ViewRootImpl.draw(ViewRootImpl.java:2409)
 02-10 13:39:11.241: E/ViewRootImpl(31190):at 
 android.view.ViewRootImpl.performDraw(ViewRootImpl.java:2253)
 02-10 13:39:11.241: E/ViewRootImpl(31190):at 
 android.view.ViewRootImpl.performTraversals(ViewRootImpl.java:1883)
 02-10 13:39:11.241: E/ViewRootImpl(31190):at 
 android.view.ViewRootImpl.doTraversal(ViewRootImpl.java:1000)
 02-10 13:39:11.241: E/ViewRootImpl(31190):at 
 android.view.ViewRootImpl$TraversalRunnable.run(ViewRootImpl.java:5670)
 02-10 13:39:11.241: E/ViewRootImpl(31190):at 
 android.view.Choreographer$CallbackRecord.run(Choreographer.java:761)
 02-10 13:39:11.241: E/ViewRootImpl(31190):at 
 android.view.Choreographer.doCallbacks(Choreographer.java:574)
 02-10 13:39:11.241: E/ViewRootImpl(31190):at 
 android.view.Choreographer.doFrame(Choreographer.java:544)
 02-10 13:39:11.241: E/ViewRootImpl(31190):at 
 android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:747)
 02-10 13:39:11.241: E/ViewRootImpl(31190):at 
 android.os.Handler.handleCallback(Handler.java:733)
 02-10 13:39:11.241: E/ViewRootImpl(31190):at 
 android.os.Handler.dispatchMessage(Handler.java:95)
 02-10 13:39:11.241: E/ViewRootImpl(31190):at 
 android.os.Looper.loop(Looper.java:136)
 02-10 13:39:11.241: E/ViewRootImpl(31190):at 
 android.app.ActivityThread.main(ActivityThread.java:5017)
 02-10 13:39:11.241: E/ViewRootImpl(31190):at 
 java.lang.reflect.Method.invokeNative(Native Method)
 02-10 13:39:11.241: E/ViewRootImpl(31190):at 
 java.lang.reflect.Method.invoke(Method.java:515)
 02-10 13:39:11.241: E/ViewRootImpl(31190):at 
 com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:779)
 02-10 13:39:11.241: E/ViewRootImpl(31190):at 
 com.android.internal.os.ZygoteInit.main(ZygoteInit.java:595)
 02-10 13:39:11.241: E/ViewRootImpl(31190):at 
 dalvik.system.NativeStart.main(Native Method)
 {quote}}}
 I have tried attaching the Chrome debug bridge, but that gave me no 
 additional information.
 I did some searching online, but in all the posts I found people using OpenGL 
 directly, but none of them had a real solution either. Most of the posts were 
 from people running on Snapdragon 800 devices though.
 I assume css3 transitions/transforms get translated to OpenGL by the 
 ChromeWebView, so I think this might be related to the SoC and how it handles 
 OpenGL. I currently don't have access to a different Android device, so I 
 can't do more testing with that.
 I have tested the Hello World application, and that did run fine on the Nexus 
 5.
 If you have any tests you would like me to run or need addition information, 
 please let me know.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Resolved] (CB-5438) Can't build/test cordova-js on Windows

[Andrew Grieve (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-5438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Grieve resolved CB-5438.
---

Resolution: Fixed

Please re-open if this isn't fixed.

 Can't build/test cordova-js on Windows
 --

 Key: CB-5438
 URL: https://issues.apache.org/jira/browse/CB-5438
 Project: Apache Cordova
  Issue Type: Bug
  Components: CordovaJS
Affects Versions: Master
 Environment: Windows 8 x64
 Node v0.10.13
Reporter: qi
Assignee: Andrew Grieve
Priority: Critical

 Simply run 'grunt build', got,
 Running jshint:src (jshint) task
 Linting lib/test/androidexec.js ...ERROR
 [L1:C1] E030: Expected an identifier and instead saw '.'.
 ../android/exec.js
 [L1:C2] E033: Expected an operator and instead saw '.'.
 ../android/exec.js
 [L1:C3] E033: Expected an operator and instead saw '/'.
 ../android/exec.js
 [L1:C4] W033: Missing semicolon.
 ../android/exec.js
 [L1:C4] W015: Expected 'android' to have an indentation at 1 instead at 4.
 ../android/exec.js
 [L1:C19] W033: Missing semicolon.
 ../android/exec.js
 [L1:C4] W117: 'android' is not defined.
 ../android/exec.js
 [L1:C12] W117: 'exec' is not defined.
 ../android/exec.js
 Linting lib/test/iosexec.js ...ERROR
 [L1:C1] E030: Expected an identifier and instead saw '.'.
 ../ios/exec.js
 [L1:C2] E033: Expected an operator and instead saw '.'.
 ../ios/exec.js
 [L1:C3] E033: Expected an operator and instead saw '/'.
 ../ios/exec.js
 [L1:C4] W033: Missing semicolon.
 ../ios/exec.js
 [L1:C4] W015: Expected 'ios' to have an indentation at 1 instead at 4.
 ../ios/exec.js
 [L1:C15] W033: Missing semicolon.
 ../ios/exec.js
 [L1:C4] W117: 'ios' is not defined.
 ../ios/exec.js
 [L1:C8] W117: 'exec' is not defined.
 ../ios/exec.js
 Warning: Task jshint:src failed. Use --force to continue.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Commented] (CB-5438) Can't build/test cordova-js on Windows

[Andrew Grieve (JIRA)]

[ 
https://issues.apache.org/jira/browse/CB-5438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13898020#comment-13898020
 ] 

Andrew Grieve commented on CB-5438:
---

I took a stab at this. Never actually got to the testing phase since I don't 
want to spend the time installing visual studio at the moment (which is 
apparently needed for jsdom to work !?)

 Can't build/test cordova-js on Windows
 --

 Key: CB-5438
 URL: https://issues.apache.org/jira/browse/CB-5438
 Project: Apache Cordova
  Issue Type: Bug
  Components: CordovaJS
Affects Versions: Master
 Environment: Windows 8 x64
 Node v0.10.13
Reporter: qi
Assignee: Andrew Grieve
Priority: Critical

 Simply run 'grunt build', got,
 Running jshint:src (jshint) task
 Linting lib/test/androidexec.js ...ERROR
 [L1:C1] E030: Expected an identifier and instead saw '.'.
 ../android/exec.js
 [L1:C2] E033: Expected an operator and instead saw '.'.
 ../android/exec.js
 [L1:C3] E033: Expected an operator and instead saw '/'.
 ../android/exec.js
 [L1:C4] W033: Missing semicolon.
 ../android/exec.js
 [L1:C4] W015: Expected 'android' to have an indentation at 1 instead at 4.
 ../android/exec.js
 [L1:C19] W033: Missing semicolon.
 ../android/exec.js
 [L1:C4] W117: 'android' is not defined.
 ../android/exec.js
 [L1:C12] W117: 'exec' is not defined.
 ../android/exec.js
 Linting lib/test/iosexec.js ...ERROR
 [L1:C1] E030: Expected an identifier and instead saw '.'.
 ../ios/exec.js
 [L1:C2] E033: Expected an operator and instead saw '.'.
 ../ios/exec.js
 [L1:C3] E033: Expected an operator and instead saw '/'.
 ../ios/exec.js
 [L1:C4] W033: Missing semicolon.
 ../ios/exec.js
 [L1:C4] W015: Expected 'ios' to have an indentation at 1 instead at 4.
 ../ios/exec.js
 [L1:C15] W033: Missing semicolon.
 ../ios/exec.js
 [L1:C4] W117: 'ios' is not defined.
 ../ios/exec.js
 [L1:C8] W117: 'exec' is not defined.
 ../ios/exec.js
 Warning: Task jshint:src failed. Use --force to continue.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Commented] (CB-6012) Important query parameters shouldn't be dropped on cdvfile:// urls

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/CB-6012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13898141#comment-13898141
 ] 

ASF subversion and git services commented on CB-6012:
-

Commit 63a0b95731040e421dc1d70965a9c88cd0dc9290 in branch refs/heads/master 
from [~iclelland]
[ https://git-wip-us.apache.org/repos/asf?p=cordova-mobile-spec.git;h=63a0b95 ]

CB-6012: file.spec.10: Test fullPath rather than name for query parameter 
preservation


 Important query parameters shouldn't be dropped on cdvfile:// urls
 --

 Key: CB-6012
 URL: https://issues.apache.org/jira/browse/CB-6012
 Project: Apache Cordova
  Issue Type: Bug
  Components: iOS, Plugin File
Affects Versions: 3.4.0
Reporter: Ian Clelland
Assignee: Ian Clelland

 Mobile spec file test 10 checks that resolving a local url with query 
 parameters returns a file entry object without those parameters.
 On iOS, at least, those parameters may be useful for asset-library urls. They 
 shouldn't be dropped automatically on cdvfile:// urls, I think. The correct 
 behaviour would be to drop them on old-style file:/// urls, but not on any 
 urls which are explicitly managed by the File plugin.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Commented] (CB-4886) Support simple creation of new plugins, using an initial plugin template

[Marcel Kinard (JIRA)]

[ 
https://issues.apache.org/jira/browse/CB-4886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13898139#comment-13898139
 ] 

Marcel Kinard commented on CB-4886:
---

Nice! How about some doc in 
cordova-docs/docs/en/edge/guide/hybrid/plugins/index.md ? Or a pointer to 
cordova-plugman/README.md from there?

 Support simple creation of new plugins, using an initial plugin template
 

 Key: CB-4886
 URL: https://issues.apache.org/jira/browse/CB-4886
 Project: Apache Cordova
  Issue Type: New Feature
  Components: CLI, Plugman
Reporter: Michal Mocny
Assignee: Lucas Holmquist
Priority: Minor

 It would be great if:
   plugman create ...
   // and/or
   cordova plugin create ...
 ..would create a default plugin shell using an initial plugin template.
 In some previous mailing list discussions, we threw out the possibility of 
 shipping plugin templates with platforms, but that may not be right.
 Relevant Mailing List threads:
 - Workflow discussion, including for plugins: 
 http://callback.markmail.org/search/?q=list%3Aorg.apache.incubator.callback-dev+What%27s+your+daily+workflow+for+cordova+development%3F#query:list%3Aorg.apache.incubator.callback-dev%20What%27s%20your%20daily%20workflow%20for%20cordova%20development%3F+page:1+mid:pv3jn552gemuxdnm+state:results
 - Yeoman generator for plugins: 
 http://callback.markmail.org/search/?q=#query:%20list%3Aorg.apache.incubator.callback-dev+page:1+mid:75g57lus3maejp3p+state:results



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Created] (CB-6013) [BlackBerry10] FileReader and FileWriter not resolving File objects correctly

[Bryan Higgins (JIRA)]

Bryan Higgins created CB-6013:
-

 Summary: [BlackBerry10] FileReader and FileWriter not resolving 
File objects correctly
 Key: CB-6013
 URL: https://issues.apache.org/jira/browse/CB-6013
 Project: Apache Cordova
  Issue Type: Bug
  Components: BlackBerry, Plugin File
Reporter: Bryan Higgins
Assignee: Bryan Higgins


Reported here:

http://supportforums.blackberry.com/t5/Web-and-WebWorks-Development/Webworks-FileReader-API-differs-from-Cordova/td-p/2773057

I confirmed the observation that both FileReader and FileWriter do not work 
correctly when passed File objects.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Commented] (CB-6012) Important query parameters shouldn't be dropped on cdvfile:// urls

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/CB-6012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13898162#comment-13898162
 ] 

ASF subversion and git services commented on CB-6012:
-

Commit 5294f27a3b67224d172bf9fdbe3ac5bb3af61929 in branch refs/heads/dev from 
[~iclelland]
[ https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-file.git;h=5294f27 ]

CB-6012: Preserve query parameters in cdvfile:// urls; strip query params from 
local filesystem urls when searching for files


 Important query parameters shouldn't be dropped on cdvfile:// urls
 --

 Key: CB-6012
 URL: https://issues.apache.org/jira/browse/CB-6012
 Project: Apache Cordova
  Issue Type: Bug
  Components: iOS, Plugin File
Affects Versions: 3.4.0
Reporter: Ian Clelland
Assignee: Ian Clelland

 Mobile spec file test 10 checks that resolving a local url with query 
 parameters returns a file entry object without those parameters.
 On iOS, at least, those parameters may be useful for asset-library urls. They 
 shouldn't be dropped automatically on cdvfile:// urls, I think. The correct 
 behaviour would be to drop them on old-style file:/// urls, but not on any 
 urls which are explicitly managed by the File plugin.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Commented] (CB-5233) Make resolveLocalFileSystemURL() work with asset-library:// URLs returned by the Camera API

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/CB-5233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13898163#comment-13898163
 ] 

ASF subversion and git services commented on CB-5233:
-

Commit 1e6a5d449718acaf5f9404dc517490c76be02306 in branch refs/heads/dev from 
[~iclelland]
[ https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-file.git;h=1e6a5d4 ]

CB-5233: ios: Fixes for asset-library URLs


 Make resolveLocalFileSystemURL() work with asset-library:// URLs returned by 
 the Camera API
 ---

 Key: CB-5233
 URL: https://issues.apache.org/jira/browse/CB-5233
 Project: Apache Cordova
  Issue Type: Bug
  Components: iOS, Plugin File
Reporter: Andrew Grieve
Assignee: Ian Clelland
Priority: Minor





--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Commented] (CB-6010) CDVAssetLibraryFilesystem does not have URLforFilesystemPath

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/CB-6010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13898161#comment-13898161
 ] 

ASF subversion and git services commented on CB-6010:
-

Commit f24abdd94df624c51dfaf1a9cc73c44a8bde0eb3 in branch refs/heads/dev from 
[~iclelland]
[ https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-file.git;h=f24abdd ]

CB-6010: ios: Test filesystem plugins for presence of optional 
URLforFilesystemPath before calling


 CDVAssetLibraryFilesystem does not have URLforFilesystemPath
 

 Key: CB-6010
 URL: https://issues.apache.org/jira/browse/CB-6010
 Project: Apache Cordova
  Issue Type: Bug
  Components: Plugin File, Plugin File Transfer
Affects Versions: 3.3.0
 Environment: ios
Reporter: Claudius Coenen
Assignee: Ian Clelland

 when i try to {{FileTransfer.download(...)}} a file (code itself used to work 
 in 2.7) my app now crashes.
 Step-Debugging revealed, that in {{CDVFile#fileSystemURLforLocalPath}} _(Line 
 267)_ all available filesystems are tested. One of those appears to be a 
 {{CDVAssetLibraryFilesystem}} - which does not implement 
 {{URLforFilesystemPath}}
 I added a dummy {{URLforFilesystemPath}} wich just returns {{nil}}. This got 
 me around the crash, but now i'm stuck with a {{FILE_NOT_FOUND_ERR}}, which 
 is probably my own responsibility. But the aforementioned crash took me a 
 while to find.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Resolved] (CB-6010) CDVAssetLibraryFilesystem does not have URLforFilesystemPath

[Ian Clelland (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-6010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ian Clelland resolved CB-6010.
--

Resolution: Fixed

This is fixed on the dev branch of file; it should be released soon as v1.0.1

 CDVAssetLibraryFilesystem does not have URLforFilesystemPath
 

 Key: CB-6010
 URL: https://issues.apache.org/jira/browse/CB-6010
 Project: Apache Cordova
  Issue Type: Bug
  Components: Plugin File, Plugin File Transfer
Affects Versions: 3.3.0
 Environment: ios
Reporter: Claudius Coenen
Assignee: Ian Clelland

 when i try to {{FileTransfer.download(...)}} a file (code itself used to work 
 in 2.7) my app now crashes.
 Step-Debugging revealed, that in {{CDVFile#fileSystemURLforLocalPath}} _(Line 
 267)_ all available filesystems are tested. One of those appears to be a 
 {{CDVAssetLibraryFilesystem}} - which does not implement 
 {{URLforFilesystemPath}}
 I added a dummy {{URLforFilesystemPath}} wich just returns {{nil}}. This got 
 me around the crash, but now i'm stuck with a {{FILE_NOT_FOUND_ERR}}, which 
 is probably my own responsibility. But the aforementioned crash took me a 
 while to find.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Resolved] (CB-5233) Make resolveLocalFileSystemURL() work with asset-library:// URLs returned by the Camera API

[Ian Clelland (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-5233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ian Clelland resolved CB-5233.
--

Resolution: Fixed

Fixed on dev; several fixes made to accomodate the query parameters in 
asset-library urls.

 Make resolveLocalFileSystemURL() work with asset-library:// URLs returned by 
 the Camera API
 ---

 Key: CB-5233
 URL: https://issues.apache.org/jira/browse/CB-5233
 Project: Apache Cordova
  Issue Type: Bug
  Components: iOS, Plugin File
Reporter: Andrew Grieve
Assignee: Ian Clelland
Priority: Minor





--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Resolved] (CB-6012) Important query parameters shouldn't be dropped on cdvfile:// urls

[Ian Clelland (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-6012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ian Clelland resolved CB-6012.
--

Resolution: Fixed

Fixed on dev. The important part now is that the 'fullPath' member retains the 
query parameters, while the 'name' member can drop them. Tests have been 
updated to verify this behaviour.

 Important query parameters shouldn't be dropped on cdvfile:// urls
 --

 Key: CB-6012
 URL: https://issues.apache.org/jira/browse/CB-6012
 Project: Apache Cordova
  Issue Type: Bug
  Components: iOS, Plugin File
Affects Versions: 3.4.0
Reporter: Ian Clelland
Assignee: Ian Clelland

 Mobile spec file test 10 checks that resolving a local url with query 
 parameters returns a file entry object without those parameters.
 On iOS, at least, those parameters may be useful for asset-library urls. They 
 shouldn't be dropped automatically on cdvfile:// urls, I think. The correct 
 behaviour would be to drop them on old-style file:/// urls, but not on any 
 urls which are explicitly managed by the File plugin.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Resolved] (CB-5959) Entry.getMetadata missing size

[Ian Clelland (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-5959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ian Clelland resolved CB-5959.
--

Resolution: Fixed

This is fixed now on the dev branch; it should be released soon as v1.0.1

 Entry.getMetadata missing size
 

 Key: CB-5959
 URL: https://issues.apache.org/jira/browse/CB-5959
 Project: Apache Cordova
  Issue Type: Bug
  Components: Plugin File
Affects Versions: 3.3.0
 Environment: android all versions
Reporter: Kyle Graehl
Assignee: Ian Clelland
Priority: Trivial
  Labels: newbie
   Original Estimate: 1h
  Remaining Estimate: 1h

 According to http://www.w3.org/TR/file-system-api/#idl-def-Metadata, Metadata 
 should have a size attribute.
 When calling DirectoryEntry.getFile with the {create:true} attribute, it 
 creates a new file. When subsequently calling getMetadata on this entry, it 
 is missing the size attribute (which should be in this case, 0). The 
 lastModified is however, present.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Commented] (CB-5294) File input element not opening file picker in Android 4.4

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/CB-5294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13898207#comment-13898207
 ] 

ASF subversion and git services commented on CB-5294:
-

Commit de8a4181cdf51ab40e4bc95e1d12f567a1c14ea8 in branch refs/heads/master 
from [~mrbillau]
[ https://git-wip-us.apache.org/repos/asf?p=cordova-docs.git;h=de8a418 ]

CB-5294: Add input type=file Android quirk


 File input element not opening file picker in Android 4.4
 -

 Key: CB-5294
 URL: https://issues.apache.org/jira/browse/CB-5294
 Project: Apache Cordova
  Issue Type: Bug
  Components: Android
Affects Versions: 3.1.0
 Environment: Android 4.4 (emulator and Nexus 5)
Reporter: Paul Kane
Assignee: Joe Bowser

 The file input field doesn't respond when clicked/tapped in Android 4.4. 
 Works fine in previous Android versions. This is regardless of whether the 
 Target Level is set to 18 or 19.
 To reproduce, I created a fresh Cordova 3.1.0 project for Android. The only 
 modification I made to the default (placeholder) index.html file was adding a 
 form element with a single input type=file element inside. Clicking the 
 Choose File button does nothing. No Logcat output or errors. Normally at 
 this point a dialogue would open allowing me to select an image from the 
 gallery or take a picture, which is what happens in older Android versions.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Commented] (CB-5294) File input element not opening file picker in Android 4.4

[Mike Billau (JIRA)]

[ 
https://issues.apache.org/jira/browse/CB-5294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13898217#comment-13898217
 ] 

Mike Billau commented on CB-5294:
-

I've added a note to the Platform Upgrade Guide about this bug (it's kinda 
weird, we don't list Android platform-wide quirks anywhere so the Upgrade Guide 
seemed like a decent enough place to stick it.) 

Lets keep this ticket open so that every Android update we can check to see if 
this has been resolved, and if so, remove the quirk. 

 File input element not opening file picker in Android 4.4
 -

 Key: CB-5294
 URL: https://issues.apache.org/jira/browse/CB-5294
 Project: Apache Cordova
  Issue Type: Bug
  Components: Android
Affects Versions: 3.1.0
 Environment: Android 4.4 (emulator and Nexus 5)
Reporter: Paul Kane
Assignee: Joe Bowser

 The file input field doesn't respond when clicked/tapped in Android 4.4. 
 Works fine in previous Android versions. This is regardless of whether the 
 Target Level is set to 18 or 19.
 To reproduce, I created a fresh Cordova 3.1.0 project for Android. The only 
 modification I made to the default (placeholder) index.html file was adding a 
 form element with a single input type=file element inside. Clicking the 
 Choose File button does nothing. No Logcat output or errors. Normally at 
 this point a dialogue would open allowing me to select an image from the 
 gallery or take a picture, which is what happens in older Android versions.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Commented] (CB-5443) Handle installed 64 bit Java

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/CB-5443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13898269#comment-13898269
 ] 

ASF subversion and git services commented on CB-5443:
-

Commit c678cbdbb8bc559a72e7f90219e14b6c00e8fe45 in branch refs/heads/3.4.x from 
[~bhigg...@blackberry.com]
[ https://git-wip-us.apache.org/repos/asf?p=cordova-blackberry.git;h=c678cbd ]

CB-5660 Revert CB-5443 due to issues with parentheses in Windows PATH


 Handle installed 64 bit Java 
 -

 Key: CB-5443
 URL: https://issues.apache.org/jira/browse/CB-5443
 Project: Apache Cordova
  Issue Type: Bug
  Components: BlackBerry
Affects Versions: 3.2.0
 Environment: Java 7 x64 installed
 Java 7 x86 _not_ installed
 Node x86 installed and used to run cordova/cordova-blackberry
Reporter: Josh Soref
Assignee: Josh Soref
Priority: Minor
 Fix For: 3.3.0


 Both Java 7 x86 and Java 7 x64 install java.exe into 
 %systemroot%\system32 however, %systemroot%\system32 is magical on 
 windows.
 When Java 7 x86 installs java.exe into that directory, it's actually 
 installing into %systemroot%\syswow64 and when another 32bit application 
 (node) looks for java in its path, it sees %systemroot%\system32 which is in 
 fact %systemroot%\syswow64 and thus finds java.exe
 When Java 7 x64 installs java.exe into that directory, it's there, but when 
 a 32bit node.exe looks at %systemroot%\system32, it's actually checking 
 %systemroot%\syswow64 and won't find Java.
 This is all sorts of fun for end users It says it can't find java? java is 
 right there!.
 Since java will generally be installed in one of two well known locations 
 (under program files 32bit or program files 64bit), we can look for it there 
 (if necessary) and add that to the path.
 The limited portion of the packaging tools that we use don't care whether 
 you're using Java 7, Java 6, 32bit or 64bit... So we can just try to select a 
 Java from a well known location.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Commented] (CB-5660) [BlackBerry10] init.bat fails when parentheses exist within PATH

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/CB-5660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13898268#comment-13898268
 ] 

ASF subversion and git services commented on CB-5660:
-

Commit c678cbdbb8bc559a72e7f90219e14b6c00e8fe45 in branch refs/heads/3.4.x from 
[~bhigg...@blackberry.com]
[ https://git-wip-us.apache.org/repos/asf?p=cordova-blackberry.git;h=c678cbd ]

CB-5660 Revert CB-5443 due to issues with parentheses in Windows PATH


 [BlackBerry10] init.bat fails when parentheses exist within PATH
 

 Key: CB-5660
 URL: https://issues.apache.org/jira/browse/CB-5660
 Project: Apache Cordova
  Issue Type: Bug
  Components: BlackBerry
Affects Versions: 3.3.0
Reporter: Bryan Higgins
Assignee: Josh Soref
Priority: Blocker

 CB-5443 introduced a change to init.bat which breaks the platform for some 
 Windows users. Specifically, if they have (x86) somewhere in their path it 
 will fail to parse the file.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Commented] (CB-6000) FileTransfer content-type header not consumable for some servers

[Christoph Neumann (JIRA)]

[ 
https://issues.apache.org/jira/browse/CB-6000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13898278#comment-13898278
 ] 

Christoph Neumann commented on CB-6000:
---

I see the fix on the dev branch. It looks like it's slated for 0.4.2, is that 
right? Thanks so much for getting this in!

 FileTransfer content-type header not consumable for some servers
 

 Key: CB-6000
 URL: https://issues.apache.org/jira/browse/CB-6000
 Project: Apache Cordova
  Issue Type: Bug
  Components: Android, Plugin File Transfer, WP7, WP8
Reporter: Andrew Grieve
Assignee: Andrew Grieve
Priority: Minor

 Reported via pull request: 
 https://github.com/apache/cordova-plugin-file-transfer/pull/6
 {quote}
 I ran into this bug when testing an app on both iOS and Android and using 
 Nginx as a reverse proxy to my application server. The Content-Type produced 
 by the iOS backend is accepted just fine (with the space), but the 
 Content-Type produced by the Android backend is rejected by Nginx as being a 
 malformed HTTP request (a 400). See more discussion here:
 http://stackoverflow.com/questions/17990705/phonegap-uploading-file-to-server-using-multipart-form-data
 {quote}



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Commented] (CB-4051) Splashscreen rotation problem

[Max Stemplinger (JIRA)]

[ 
https://issues.apache.org/jira/browse/CB-4051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13898282#comment-13898282
 ] 

Max Stemplinger commented on CB-4051:
-

I think this pull request adds a new bug. I have an iPhone only app with 
orientation lock for only portrait. My launch images have all the name 
Default~iphone.png, Default-568h@2x~iphone.png, Default@2x~iphone.png as it is 
suggested by apple and the cordova doc (iPhone Apps can only be started in 
Portrait, so no need for -landscape or -portrait). When the orientation is 
locked, this pull requests adds the line
{code}
} else if (CDV_IsIPad() || isOrientationLocked) {
{code}
which then appends the filename with -Portrait in my case. Now the plugin 
can't find the image, because the names are different. The -Portrait and 
-Landscape should only be appended when the device is an iPad. So i think 
this has to be reopened, or am i doing something wrong?


 Splashscreen rotation problem
 -

 Key: CB-4051
 URL: https://issues.apache.org/jira/browse/CB-4051
 Project: Apache Cordova
  Issue Type: Bug
  Components: iOS
Affects Versions: 2.7.0
Reporter: Estelle
Assignee: Shazron Abdullah

 On Cordova 2.7
 I have made an application iPhone with Cordova, my application is only on 
 landscape mode. I have added splashscreens on the app and seen a bug.
 When I launch app, I see correctly the good splashscreen but after view 
 seconds the splashscreen rotate on 90°
 I think it's a bug because all params in XML, Xcode and plist are in 
 landscape mode.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Commented] (CB-6000) FileTransfer content-type header not consumable for some servers

[Andrew Grieve (JIRA)]

[ 
https://issues.apache.org/jira/browse/CB-6000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13898315#comment-13898315
 ] 

Andrew Grieve commented on CB-6000:
---

That's right! Probably will be released next week. Thank *you* for the fix :)

 FileTransfer content-type header not consumable for some servers
 

 Key: CB-6000
 URL: https://issues.apache.org/jira/browse/CB-6000
 Project: Apache Cordova
  Issue Type: Bug
  Components: Android, Plugin File Transfer, WP7, WP8
Reporter: Andrew Grieve
Assignee: Andrew Grieve
Priority: Minor

 Reported via pull request: 
 https://github.com/apache/cordova-plugin-file-transfer/pull/6
 {quote}
 I ran into this bug when testing an app on both iOS and Android and using 
 Nginx as a reverse proxy to my application server. The Content-Type produced 
 by the iOS backend is accepted just fine (with the space), but the 
 Content-Type produced by the Android backend is rejected by Nginx as being a 
 malformed HTTP request (a 400). See more discussion here:
 http://stackoverflow.com/questions/17990705/phonegap-uploading-file-to-server-using-multipart-form-data
 {quote}



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Resolved] (CB-5869) [Release + 3.4.0] Test Tag 3.4.0 for BlackBerry

[Bryan Higgins (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-5869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bryan Higgins resolved CB-5869.
---

Resolution: Fixed

 [Release + 3.4.0] Test  Tag 3.4.0 for BlackBerry
 -

 Key: CB-5869
 URL: https://issues.apache.org/jira/browse/CB-5869
 Project: Apache Cordova
  Issue Type: Sub-task
  Components: BlackBerry
Reporter: Steve Gill
Assignee: Bryan Higgins
 Fix For: 3.4.0


 Refer to Workflow here:
 http://wiki.apache.org/cordova/CuttingReleases



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Commented] (CB-6012) Important query parameters shouldn't be dropped on cdvfile:// urls

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/CB-6012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13898330#comment-13898330
 ] 

ASF subversion and git services commented on CB-6012:
-

Commit 71ae55766425140ac17525985bb90a5d8eb90364 in branch refs/heads/master 
from [~iclelland]
[ https://git-wip-us.apache.org/repos/asf?p=cordova-mobile-spec.git;h=71ae557 ]

CB-6012: Really fix previous^^ test


 Important query parameters shouldn't be dropped on cdvfile:// urls
 --

 Key: CB-6012
 URL: https://issues.apache.org/jira/browse/CB-6012
 Project: Apache Cordova
  Issue Type: Bug
  Components: iOS, Plugin File
Affects Versions: 3.4.0
Reporter: Ian Clelland
Assignee: Ian Clelland

 Mobile spec file test 10 checks that resolving a local url with query 
 parameters returns a file entry object without those parameters.
 On iOS, at least, those parameters may be useful for asset-library urls. They 
 shouldn't be dropped automatically on cdvfile:// urls, I think. The correct 
 behaviour would be to drop them on old-style file:/// urls, but not on any 
 urls which are explicitly managed by the File plugin.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Created] (CB-6014) [BlackBerry10] run --no-build should not generate debug token

[Bryan Higgins (JIRA)]

Bryan Higgins created CB-6014:
-

 Summary: [BlackBerry10] run --no-build should not generate debug 
token
 Key: CB-6014
 URL: https://issues.apache.org/jira/browse/CB-6014
 Project: Apache Cordova
  Issue Type: Bug
  Components: BlackBerry
Affects Versions: 3.4.0
Reporter: Bryan Higgins
Assignee: Bryan Higgins
Priority: Minor
 Fix For: 3.5.0


--no-build is generally used for deployment of release builds. It doesn't make 
sense to generate a debug token for this use case.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Commented] (CB-4662) Bad code in file autotest?

[David Kemp (JIRA)]

[ 
https://issues.apache.org/jira/browse/CB-4662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13898362#comment-13898362
 ] 

David Kemp commented on CB-4662:


This code has been fixed  d662dd36a6e6109e13e3571b5488815b7307b6cb  in the 
current release.
No effort has been made to patch previous versions.

 Bad code in file autotest?
 --

 Key: CB-4662
 URL: https://issues.apache.org/jira/browse/CB-4662
 Project: Apache Cordova
  Issue Type: Bug
  Components: mobile-spec
Affects Versions: 2.9.0
Reporter: Peter
Assignee: David Kemp
Priority: Minor

 By inspection, this code in the File autotests seems incorrect
 {code}
 function arrayBufferEqualsString(buf, str) {
 var buf = new Uint8Array(ab);
 var match = buf.length == str.length;
 for (var i = 0; match  i  buf.length; i++) {
 match = buf[i] == str.charCodeAt(i);
 }
 return match;
 }
 {code}
 Where does that _ab_ come from?
 Ref: 
 https://github.com/apache/cordova-mobile-spec/blob/master/autotest/tests/file.tests.js



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Resolved] (CB-4710) modify the repoUpdate command to clone any missing repos

[David Kemp (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-4710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

David Kemp resolved CB-4710.


Resolution: Fixed

 modify the repoUpdate command to clone any missing repos
 

 Key: CB-4710
 URL: https://issues.apache.org/jira/browse/CB-4710
 Project: Apache Cordova
  Issue Type: Bug
  Components: Coho
Affects Versions: Master
Reporter: David Kemp
Assignee: David Kemp
Priority: Minor
 Fix For: Master


 Currently if you repo-update and any of the identified repos is not present, 
 the command fails. This adds the option to have it simply clone the missing 
 repo(s).



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Commented] (CB-5739) Rewrite Win/WP8 Platform Guides

[Mike Sierra (JIRA)]

[ 
https://issues.apache.org/jira/browse/CB-5739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13898418#comment-13898418
 ] 

Mike Sierra commented on CB-5739:
-

[~purplecabbage], per my email, can you review pull req's #184  #185 asap? 
Also [~mwbrooks], can you take a look at the non-JIRA commits from #184? Hope 
to wrap up before the end of this week, Thx

 Rewrite Win/WP8 Platform Guides
 ---

 Key: CB-5739
 URL: https://issues.apache.org/jira/browse/CB-5739
 Project: Apache Cordova
  Issue Type: Task
  Components: Docs
Reporter: Mike Sierra
Assignee: Mike Sierra

 Task includes:
 - Flesh out the content, e.g., with more/better screen
 shots, especially to show device emulators. The current platform
 guide doc for iOS/Android should serve as a baseline. Fix the
 various formatting errors on these pages, align it with the
 editorial style sheet, etc.
 - Upgrade platform guide doc to present information about
 the CLI workflow along with the existing shell-tool workflow. 
 incorporate what are currently
 separate Command-line Tools pages into each platform guide
 - Look for opportunities to merge any relevant info about outdated
 wp7 platform into wp8 topic
 - Upgrade various Windows platform guides to support
 development on Mac via VMWare, Parallels, or BootCamp. 
 Leverage this content: http://bit.ly/1jqMKhz  http://bit.ly/1ktL9dS. 
 Avoid distracting readers with all available options in main platform guide.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Assigned] (CB-5878) [Release + 3.4.0] Change default docs to new version

[Steve Gill (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-5878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Steve Gill reassigned CB-5878:
--

Assignee: Steve Gill

 [Release + 3.4.0] Change default docs to new version
 

 Key: CB-5878
 URL: https://issues.apache.org/jira/browse/CB-5878
 Project: Apache Cordova
  Issue Type: Sub-task
  Components: Amazon FireOS, Android, App Hello World, BlackBerry, 
 CLI, CordovaJS, Docs, FirefoxOS, iOS, mobile-spec, Ubuntu, Windows 8, WP8
Reporter: Steve Gill
Assignee: Steve Gill
 Fix For: 3.4.0


 Refer to Workflow here:
 http://wiki.apache.org/cordova/CuttingReleases



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Assigned] (CB-5877) [Release + 3.4.0] Upload signed release .zip to Apache Dist

[Steve Gill (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-5877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Steve Gill reassigned CB-5877:
--

Assignee: Steve Gill

 [Release + 3.4.0] Upload signed release .zip to Apache Dist
 ---

 Key: CB-5877
 URL: https://issues.apache.org/jira/browse/CB-5877
 Project: Apache Cordova
  Issue Type: Sub-task
  Components: Amazon FireOS, Android, App Hello World, BlackBerry, 
 CLI, CordovaJS, Docs, FirefoxOS, iOS, mobile-spec, Ubuntu, Windows 8, WP8
Reporter: Steve Gill
Assignee: Steve Gill
 Fix For: 3.4.0


 Refer to Workflow here:
 http://wiki.apache.org/cordova/CuttingReleases



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Assigned] (CB-5868) [Release + 3.4.0] Test Tag 3.4.0 for iOS

[Steve Gill (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-5868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Steve Gill reassigned CB-5868:
--

Assignee: Shazron Abdullah

 [Release + 3.4.0] Test  Tag 3.4.0 for iOS
 --

 Key: CB-5868
 URL: https://issues.apache.org/jira/browse/CB-5868
 Project: Apache Cordova
  Issue Type: Sub-task
  Components: iOS
Reporter: Steve Gill
Assignee: Shazron Abdullah
 Fix For: 3.4.0


 Refer to Workflow here:
 http://wiki.apache.org/cordova/CuttingReleases



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Assigned] (CB-5874) [Release + 3.4.0] Test Tag 3.4.0 for Amazon Fire OS

[Steve Gill (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-5874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Steve Gill reassigned CB-5874:
--

Assignee: Steve Gill

 [Release + 3.4.0] Test  Tag 3.4.0 for Amazon Fire OS
 -

 Key: CB-5874
 URL: https://issues.apache.org/jira/browse/CB-5874
 Project: Apache Cordova
  Issue Type: Sub-task
  Components: Amazon FireOS
Reporter: Steve Gill
Assignee: Steve Gill
 Fix For: 3.4.0


 Refer to Workflow here:
 http://wiki.apache.org/cordova/CuttingReleases



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Assigned] (CB-5867) [Release + 3.4.0] Test Tag 3.4.0 for Android

[Steve Gill (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-5867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Steve Gill reassigned CB-5867:
--

Assignee: Joe Bowser

 [Release + 3.4.0] Test  Tag 3.4.0 for Android
 --

 Key: CB-5867
 URL: https://issues.apache.org/jira/browse/CB-5867
 Project: Apache Cordova
  Issue Type: Sub-task
  Components: Android
Reporter: Steve Gill
Assignee: Joe Bowser
 Fix For: 3.4.0


 Refer to Workflow here:
 http://wiki.apache.org/cordova/CuttingReleases



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Assigned] (CB-5876) [Release + 3.4.0] Create blog post for final release get reviewed

[Steve Gill (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-5876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Steve Gill reassigned CB-5876:
--

Assignee: Steve Gill

 [Release + 3.4.0] Create blog post for final release  get reviewed
 ---

 Key: CB-5876
 URL: https://issues.apache.org/jira/browse/CB-5876
 Project: Apache Cordova
  Issue Type: Sub-task
  Components: Amazon FireOS, Android, App Hello World, BlackBerry, 
 CLI, CordovaJS, Docs, FirefoxOS, iOS, mobile-spec, Ubuntu, Windows 8, WP8
Reporter: Steve Gill
Assignee: Steve Gill
 Fix For: 3.4.0


 Refer to Workflow here:
 http://wiki.apache.org/cordova/CuttingReleases



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Assigned] (CB-5864) [Release + 3.4.0] Branch Tag RC1 of cordova-cli

[Steve Gill (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-5864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Steve Gill reassigned CB-5864:
--

Assignee: Steve Gill

 [Release + 3.4.0] Branch  Tag RC1 of cordova-cli
 -

 Key: CB-5864
 URL: https://issues.apache.org/jira/browse/CB-5864
 Project: Apache Cordova
  Issue Type: Sub-task
  Components: CLI
Reporter: Steve Gill
Assignee: Steve Gill
 Fix For: 3.4.0


 Refer to Workflow here:
 http://wiki.apache.org/cordova/CuttingReleases



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Deleted] (CB-5866) [Release + 3.4.0] Create blog post for RC1 Announce

[Steve Gill (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-5866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Steve Gill deleted CB-5866:
---


 [Release + 3.4.0] Create blog post for RC1  Announce
 -

 Key: CB-5866
 URL: https://issues.apache.org/jira/browse/CB-5866
 Project: Apache Cordova
  Issue Type: Sub-task
Reporter: Steve Gill

 Refer to Workflow here:
 http://wiki.apache.org/cordova/CuttingReleases



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Assigned] (CB-5873) [Release + 3.4.0] Test Tag 3.4.0 for Ubuntu

[Steve Gill (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-5873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Steve Gill reassigned CB-5873:
--

Assignee: Steve Gill

 [Release + 3.4.0] Test  Tag 3.4.0 for Ubuntu
 -

 Key: CB-5873
 URL: https://issues.apache.org/jira/browse/CB-5873
 Project: Apache Cordova
  Issue Type: Sub-task
  Components: Ubuntu
Reporter: Steve Gill
Assignee: Steve Gill
 Fix For: 3.4.0


 Refer to Workflow here:
 http://wiki.apache.org/cordova/CuttingReleases



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Assigned] (CB-3209) geolocation

[Steve Gill (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-3209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Steve Gill reassigned CB-3209:
--

Assignee: Steve Gill  (was: Herm Wong)

 geolocation
 ---

 Key: CB-3209
 URL: https://issues.apache.org/jira/browse/CB-3209
 Project: Apache Cordova
  Issue Type: Sub-task
  Components: FirefoxOS
Affects Versions: 2.6.0
Reporter: Herm Wong
Assignee: Steve Gill
 Fix For: 3.2.0


 geolocation spec: http://www.w3.org/TR/geolocation-API/



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Assigned] (CB-3204) initial implementation of cordova apis

[Steve Gill (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-3204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Steve Gill reassigned CB-3204:
--

Assignee: James Long  (was: Herm Wong)

 initial implementation of cordova apis
 --

 Key: CB-3204
 URL: https://issues.apache.org/jira/browse/CB-3204
 Project: Apache Cordova
  Issue Type: Bug
  Components: FirefoxOS
Reporter: Herm Wong
Assignee: James Long





--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Commented] (CB-4051) Splashscreen rotation problem

[Shazron Abdullah (JIRA)]

[ 
https://issues.apache.org/jira/browse/CB-4051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13898591#comment-13898591
 ] 

Shazron Abdullah commented on CB-4051:
--

You're right - the logical operator there should be an  not ||
This code probably needs to be re-factored to be unit-testable to handle all 
cases.

 Splashscreen rotation problem
 -

 Key: CB-4051
 URL: https://issues.apache.org/jira/browse/CB-4051
 Project: Apache Cordova
  Issue Type: Bug
  Components: iOS
Affects Versions: 2.7.0
Reporter: Estelle
Assignee: Shazron Abdullah

 On Cordova 2.7
 I have made an application iPhone with Cordova, my application is only on 
 landscape mode. I have added splashscreens on the app and seen a bug.
 When I launch app, I see correctly the good splashscreen but after view 
 seconds the splashscreen rotate on 90°
 I think it's a bug because all params in XML, Xcode and plist are in 
 landscape mode.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Reopened] (CB-4051) Splashscreen rotation problem

[Shazron Abdullah (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-4051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Shazron Abdullah reopened CB-4051:
--


 Splashscreen rotation problem
 -

 Key: CB-4051
 URL: https://issues.apache.org/jira/browse/CB-4051
 Project: Apache Cordova
  Issue Type: Bug
  Components: iOS
Affects Versions: 2.7.0
Reporter: Estelle
Assignee: Shazron Abdullah

 On Cordova 2.7
 I have made an application iPhone with Cordova, my application is only on 
 landscape mode. I have added splashscreens on the app and seen a bug.
 When I launch app, I see correctly the good splashscreen but after view 
 seconds the splashscreen rotate on 90°
 I think it's a bug because all params in XML, Xcode and plist are in 
 landscape mode.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Commented] (CB-5438) Can't build/test cordova-js on Windows

[qi (JIRA)]

[ 
https://issues.apache.org/jira/browse/CB-5438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13898614#comment-13898614
 ] 

qi commented on CB-5438:


[~agrieve], I replaced jsdom to jsdom-nogyp in my fork, you could try it and no 
VS required

 Can't build/test cordova-js on Windows
 --

 Key: CB-5438
 URL: https://issues.apache.org/jira/browse/CB-5438
 Project: Apache Cordova
  Issue Type: Bug
  Components: CordovaJS
Affects Versions: Master
 Environment: Windows 8 x64
 Node v0.10.13
Reporter: qi
Assignee: Andrew Grieve
Priority: Critical

 Simply run 'grunt build', got,
 Running jshint:src (jshint) task
 Linting lib/test/androidexec.js ...ERROR
 [L1:C1] E030: Expected an identifier and instead saw '.'.
 ../android/exec.js
 [L1:C2] E033: Expected an operator and instead saw '.'.
 ../android/exec.js
 [L1:C3] E033: Expected an operator and instead saw '/'.
 ../android/exec.js
 [L1:C4] W033: Missing semicolon.
 ../android/exec.js
 [L1:C4] W015: Expected 'android' to have an indentation at 1 instead at 4.
 ../android/exec.js
 [L1:C19] W033: Missing semicolon.
 ../android/exec.js
 [L1:C4] W117: 'android' is not defined.
 ../android/exec.js
 [L1:C12] W117: 'exec' is not defined.
 ../android/exec.js
 Linting lib/test/iosexec.js ...ERROR
 [L1:C1] E030: Expected an identifier and instead saw '.'.
 ../ios/exec.js
 [L1:C2] E033: Expected an operator and instead saw '.'.
 ../ios/exec.js
 [L1:C3] E033: Expected an operator and instead saw '/'.
 ../ios/exec.js
 [L1:C4] W033: Missing semicolon.
 ../ios/exec.js
 [L1:C4] W015: Expected 'ios' to have an indentation at 1 instead at 4.
 ../ios/exec.js
 [L1:C15] W033: Missing semicolon.
 ../ios/exec.js
 [L1:C4] W117: 'ios' is not defined.
 ../ios/exec.js
 [L1:C8] W117: 'exec' is not defined.
 ../ios/exec.js
 Warning: Task jshint:src failed. Use --force to continue.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Reopened] (CB-5438) Can't build/test cordova-js on Windows

[qi (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-5438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

qi reopened CB-5438:



The last commit only fixed build, but not testing.

 Can't build/test cordova-js on Windows
 --

 Key: CB-5438
 URL: https://issues.apache.org/jira/browse/CB-5438
 Project: Apache Cordova
  Issue Type: Bug
  Components: CordovaJS
Affects Versions: Master
 Environment: Windows 8 x64
 Node v0.10.13
Reporter: qi
Assignee: Andrew Grieve
Priority: Critical

 Simply run 'grunt build', got,
 Running jshint:src (jshint) task
 Linting lib/test/androidexec.js ...ERROR
 [L1:C1] E030: Expected an identifier and instead saw '.'.
 ../android/exec.js
 [L1:C2] E033: Expected an operator and instead saw '.'.
 ../android/exec.js
 [L1:C3] E033: Expected an operator and instead saw '/'.
 ../android/exec.js
 [L1:C4] W033: Missing semicolon.
 ../android/exec.js
 [L1:C4] W015: Expected 'android' to have an indentation at 1 instead at 4.
 ../android/exec.js
 [L1:C19] W033: Missing semicolon.
 ../android/exec.js
 [L1:C4] W117: 'android' is not defined.
 ../android/exec.js
 [L1:C12] W117: 'exec' is not defined.
 ../android/exec.js
 Linting lib/test/iosexec.js ...ERROR
 [L1:C1] E030: Expected an identifier and instead saw '.'.
 ../ios/exec.js
 [L1:C2] E033: Expected an operator and instead saw '.'.
 ../ios/exec.js
 [L1:C3] E033: Expected an operator and instead saw '/'.
 ../ios/exec.js
 [L1:C4] W033: Missing semicolon.
 ../ios/exec.js
 [L1:C4] W015: Expected 'ios' to have an indentation at 1 instead at 4.
 ../ios/exec.js
 [L1:C15] W033: Missing semicolon.
 ../ios/exec.js
 [L1:C4] W117: 'ios' is not defined.
 ../ios/exec.js
 [L1:C8] W117: 'exec' is not defined.
 ../ios/exec.js
 Warning: Task jshint:src failed. Use --force to continue.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Resolved] (CB-5438) Can't build/test cordova-js on Windows

[Andrew Grieve (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-5438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Grieve resolved CB-5438.
---

   Resolution: Fixed
Fix Version/s: 3.5.0

Awesome, switched it to jsdom-nogyp and all tests passed on my win7 VM :)

 Can't build/test cordova-js on Windows
 --

 Key: CB-5438
 URL: https://issues.apache.org/jira/browse/CB-5438
 Project: Apache Cordova
  Issue Type: Bug
  Components: CordovaJS
Affects Versions: Master
 Environment: Windows 8 x64
 Node v0.10.13
Reporter: qi
Assignee: Andrew Grieve
Priority: Critical
 Fix For: 3.5.0


 Simply run 'grunt build', got,
 Running jshint:src (jshint) task
 Linting lib/test/androidexec.js ...ERROR
 [L1:C1] E030: Expected an identifier and instead saw '.'.
 ../android/exec.js
 [L1:C2] E033: Expected an operator and instead saw '.'.
 ../android/exec.js
 [L1:C3] E033: Expected an operator and instead saw '/'.
 ../android/exec.js
 [L1:C4] W033: Missing semicolon.
 ../android/exec.js
 [L1:C4] W015: Expected 'android' to have an indentation at 1 instead at 4.
 ../android/exec.js
 [L1:C19] W033: Missing semicolon.
 ../android/exec.js
 [L1:C4] W117: 'android' is not defined.
 ../android/exec.js
 [L1:C12] W117: 'exec' is not defined.
 ../android/exec.js
 Linting lib/test/iosexec.js ...ERROR
 [L1:C1] E030: Expected an identifier and instead saw '.'.
 ../ios/exec.js
 [L1:C2] E033: Expected an operator and instead saw '.'.
 ../ios/exec.js
 [L1:C3] E033: Expected an operator and instead saw '/'.
 ../ios/exec.js
 [L1:C4] W033: Missing semicolon.
 ../ios/exec.js
 [L1:C4] W015: Expected 'ios' to have an indentation at 1 instead at 4.
 ../ios/exec.js
 [L1:C15] W033: Missing semicolon.
 ../ios/exec.js
 [L1:C4] W117: 'ios' is not defined.
 ../ios/exec.js
 [L1:C8] W117: 'exec' is not defined.
 ../ios/exec.js
 Warning: Task jshint:src failed. Use --force to continue.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Commented] (CB-5438) Can't build/test cordova-js on Windows

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/CB-5438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13898691#comment-13898691
 ] 

ASF subversion and git services commented on CB-5438:
-

Commit ddf13aa89aee6ab96e11736417b9a7b53a2c02be in branch refs/heads/master 
from [~agrieve]
[ https://git-wip-us.apache.org/repos/asf?p=cordova-js.git;h=ddf13aa ]

CB-5438 Use jsdom-nogyp to avoid dependency on python  visual studio


 Can't build/test cordova-js on Windows
 --

 Key: CB-5438
 URL: https://issues.apache.org/jira/browse/CB-5438
 Project: Apache Cordova
  Issue Type: Bug
  Components: CordovaJS
Affects Versions: Master
 Environment: Windows 8 x64
 Node v0.10.13
Reporter: qi
Assignee: Andrew Grieve
Priority: Critical
 Fix For: 3.5.0


 Simply run 'grunt build', got,
 Running jshint:src (jshint) task
 Linting lib/test/androidexec.js ...ERROR
 [L1:C1] E030: Expected an identifier and instead saw '.'.
 ../android/exec.js
 [L1:C2] E033: Expected an operator and instead saw '.'.
 ../android/exec.js
 [L1:C3] E033: Expected an operator and instead saw '/'.
 ../android/exec.js
 [L1:C4] W033: Missing semicolon.
 ../android/exec.js
 [L1:C4] W015: Expected 'android' to have an indentation at 1 instead at 4.
 ../android/exec.js
 [L1:C19] W033: Missing semicolon.
 ../android/exec.js
 [L1:C4] W117: 'android' is not defined.
 ../android/exec.js
 [L1:C12] W117: 'exec' is not defined.
 ../android/exec.js
 Linting lib/test/iosexec.js ...ERROR
 [L1:C1] E030: Expected an identifier and instead saw '.'.
 ../ios/exec.js
 [L1:C2] E033: Expected an operator and instead saw '.'.
 ../ios/exec.js
 [L1:C3] E033: Expected an operator and instead saw '/'.
 ../ios/exec.js
 [L1:C4] W033: Missing semicolon.
 ../ios/exec.js
 [L1:C4] W015: Expected 'ios' to have an indentation at 1 instead at 4.
 ../ios/exec.js
 [L1:C15] W033: Missing semicolon.
 ../ios/exec.js
 [L1:C4] W117: 'ios' is not defined.
 ../ios/exec.js
 [L1:C8] W117: 'exec' is not defined.
 ../ios/exec.js
 Warning: Task jshint:src failed. Use --force to continue.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Issue Comment Deleted] (CB-5438) Can't build/test cordova-js on Windows

[qi (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-5438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

qi updated CB-5438:
---

Comment: was deleted

(was: The last commit only fixed build, but not testing.)

 Can't build/test cordova-js on Windows
 --

 Key: CB-5438
 URL: https://issues.apache.org/jira/browse/CB-5438
 Project: Apache Cordova
  Issue Type: Bug
  Components: CordovaJS
Affects Versions: Master
 Environment: Windows 8 x64
 Node v0.10.13
Reporter: qi
Assignee: Andrew Grieve
Priority: Critical
 Fix For: 3.5.0


 Simply run 'grunt build', got,
 Running jshint:src (jshint) task
 Linting lib/test/androidexec.js ...ERROR
 [L1:C1] E030: Expected an identifier and instead saw '.'.
 ../android/exec.js
 [L1:C2] E033: Expected an operator and instead saw '.'.
 ../android/exec.js
 [L1:C3] E033: Expected an operator and instead saw '/'.
 ../android/exec.js
 [L1:C4] W033: Missing semicolon.
 ../android/exec.js
 [L1:C4] W015: Expected 'android' to have an indentation at 1 instead at 4.
 ../android/exec.js
 [L1:C19] W033: Missing semicolon.
 ../android/exec.js
 [L1:C4] W117: 'android' is not defined.
 ../android/exec.js
 [L1:C12] W117: 'exec' is not defined.
 ../android/exec.js
 Linting lib/test/iosexec.js ...ERROR
 [L1:C1] E030: Expected an identifier and instead saw '.'.
 ../ios/exec.js
 [L1:C2] E033: Expected an operator and instead saw '.'.
 ../ios/exec.js
 [L1:C3] E033: Expected an operator and instead saw '/'.
 ../ios/exec.js
 [L1:C4] W033: Missing semicolon.
 ../ios/exec.js
 [L1:C4] W015: Expected 'ios' to have an indentation at 1 instead at 4.
 ../ios/exec.js
 [L1:C15] W033: Missing semicolon.
 ../ios/exec.js
 [L1:C4] W117: 'ios' is not defined.
 ../ios/exec.js
 [L1:C8] W117: 'exec' is not defined.
 ../ios/exec.js
 Warning: Task jshint:src failed. Use --force to continue.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Commented] (CB-5438) Can't build/test cordova-js on Windows

[qi (JIRA)]

[ 
https://issues.apache.org/jira/browse/CB-5438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13898718#comment-13898718
 ] 

qi commented on CB-5438:


Now everything works, wow!

 Can't build/test cordova-js on Windows
 --

 Key: CB-5438
 URL: https://issues.apache.org/jira/browse/CB-5438
 Project: Apache Cordova
  Issue Type: Bug
  Components: CordovaJS
Affects Versions: Master
 Environment: Windows 8 x64
 Node v0.10.13
Reporter: qi
Assignee: Andrew Grieve
Priority: Critical
 Fix For: 3.5.0


 Simply run 'grunt build', got,
 Running jshint:src (jshint) task
 Linting lib/test/androidexec.js ...ERROR
 [L1:C1] E030: Expected an identifier and instead saw '.'.
 ../android/exec.js
 [L1:C2] E033: Expected an operator and instead saw '.'.
 ../android/exec.js
 [L1:C3] E033: Expected an operator and instead saw '/'.
 ../android/exec.js
 [L1:C4] W033: Missing semicolon.
 ../android/exec.js
 [L1:C4] W015: Expected 'android' to have an indentation at 1 instead at 4.
 ../android/exec.js
 [L1:C19] W033: Missing semicolon.
 ../android/exec.js
 [L1:C4] W117: 'android' is not defined.
 ../android/exec.js
 [L1:C12] W117: 'exec' is not defined.
 ../android/exec.js
 Linting lib/test/iosexec.js ...ERROR
 [L1:C1] E030: Expected an identifier and instead saw '.'.
 ../ios/exec.js
 [L1:C2] E033: Expected an operator and instead saw '.'.
 ../ios/exec.js
 [L1:C3] E033: Expected an operator and instead saw '/'.
 ../ios/exec.js
 [L1:C4] W033: Missing semicolon.
 ../ios/exec.js
 [L1:C4] W015: Expected 'ios' to have an indentation at 1 instead at 4.
 ../ios/exec.js
 [L1:C15] W033: Missing semicolon.
 ../ios/exec.js
 [L1:C4] W117: 'ios' is not defined.
 ../ios/exec.js
 [L1:C8] W117: 'exec' is not defined.
 ../ios/exec.js
 Warning: Task jshint:src failed. Use --force to continue.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Assigned] (CB-6015) FileTransfer error: Read-Only filesystem

[Ian Clelland (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-6015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ian Clelland reassigned CB-6015:


Assignee: Ian Clelland

 FileTransfer error: Read-Only filesystem
 

 Key: CB-6015
 URL: https://issues.apache.org/jira/browse/CB-6015
 Project: Apache Cordova
  Issue Type: Bug
  Components: Android, Plugin File, Plugin File Transfer
Affects Versions: 3.3.0
Reporter: Darryl Pogue
Assignee: Ian Clelland

 Using the FileTransfer plugin to write to a FileEntry returned from the File 
 plugin results in an error.
 {code}
 D/FileTransfer(12423): download http://example.com/image.jpeg to //avatar.jpeg
 E/FileTransfer(12423): 
 {target:\/\/avatar.jpeg,source:http:\/\/example.com\/image.jpeg,http_status:0,code:1}
 E/FileTransfer(12423): java.io.FileNotFoundException: /avatar.jpeg: open 
 failed: EROFS (Read-only file system)
 E/FileTransfer(12423):at libcore.io.IoBridge.open(IoBridge.java:409)
 E/FileTransfer(12423):at 
 java.io.FileOutputStream.init(FileOutputStream.java:88)
 E/FileTransfer(12423):at 
 org.apache.cordova.CordovaResourceApi.openOutputStream(CordovaResourceApi.java:293)
 E/FileTransfer(12423):at 
 org.apache.cordova.CordovaResourceApi.openOutputStream(CordovaResourceApi.java:274)
 E/FileTransfer(12423):at 
 org.apache.cordova.filetransfer.FileTransfer$4.run(FileTransfer.java:708)
 E/FileTransfer(12423):at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1080)
 E/FileTransfer(12423):at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:573)
 E/FileTransfer(12423):at java.lang.Thread.run(Thread.java:841)
 E/FileTransfer(12423): Caused by: libcore.io.ErrnoException: open failed: 
 EROFS (Read-only file system)
 E/FileTransfer(12423):at libcore.io.Posix.open(Native Method)
 E/FileTransfer(12423):at 
 libcore.io.BlockGuardOs.open(BlockGuardOs.java:110)
 E/FileTransfer(12423):at libcore.io.IoBridge.open(IoBridge.java:393)
 E/FileTransfer(12423):... 7 more
 {code}
 This worked correctly before upgrading the file plugin.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Created] (CB-6016) capture.captureAudio is not supported on BlackBerry10

[Doug Moscrop (JIRA)]

Doug Moscrop created CB-6016:


 Summary: capture.captureAudio is not supported on BlackBerry10
 Key: CB-6016
 URL: https://issues.apache.org/jira/browse/CB-6016
 Project: Apache Cordova
  Issue Type: Bug
  Components: BlackBerry
Affects Versions: 3.3.0
Reporter: Doug Moscrop


In a similar fashion to CB-117, captureAudio is stubbed on in the media-capture 
plugin:

captureAudio: function (win, fail, args, env) {
var result = new PluginResult(args, env);
result.error({code: NOT_SUPPORTED_ERROR_CODE});
}

I suspect this may be due to the API offerings from BlackBerry - however, 
captureAudio is plainly listed as being supported on BlackBerry 10 in all 
documentation and even goes as far as to claim it will attempt to launch the 
voice note app and return the above error status if it is not installed. 
Recording works if I repackage my Android APK (built via Cordova) to a BAR and 
run it via the Android runtime on BB.

Sincere apologies if I've missed something.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Updated] (CB-6016) capture.captureAudio is not supported on BlackBerry10

[Doug Moscrop (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-6016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Doug Moscrop updated CB-6016:
-

Description: 
In a similar fashion to CB-117, captureAudio is stubbed out in the 
media-capture plugin and simply always calls error with 
NOT_SUPPORTED_ERROR_CODE.

I suspect this may be due to the API offerings from BlackBerry - however, 
captureAudio is plainly listed as being supported on BlackBerry 10 in all 
documentation and even goes as far as to claim it will attempt to launch the 
voice note app and return the above error status if it is not installed. 
Recording works if I repackage my Android APK (built via Cordova) to a BAR and 
run it via the Android runtime on BB.

Sincere apologies if I've missed something.

  was:
In a similar fashion to CB-117, captureAudio is stubbed on in the media-capture 
plugin:

captureAudio: function (win, fail, args, env) {
var result = new PluginResult(args, env);
result.error({code: NOT_SUPPORTED_ERROR_CODE});
}

I suspect this may be due to the API offerings from BlackBerry - however, 
captureAudio is plainly listed as being supported on BlackBerry 10 in all 
documentation and even goes as far as to claim it will attempt to launch the 
voice note app and return the above error status if it is not installed. 
Recording works if I repackage my Android APK (built via Cordova) to a BAR and 
run it via the Android runtime on BB.

Sincere apologies if I've missed something.


 capture.captureAudio is not supported on BlackBerry10
 -

 Key: CB-6016
 URL: https://issues.apache.org/jira/browse/CB-6016
 Project: Apache Cordova
  Issue Type: Bug
  Components: BlackBerry
Affects Versions: 3.3.0
Reporter: Doug Moscrop

 In a similar fashion to CB-117, captureAudio is stubbed out in the 
 media-capture plugin and simply always calls error with 
 NOT_SUPPORTED_ERROR_CODE.
 I suspect this may be due to the API offerings from BlackBerry - however, 
 captureAudio is plainly listed as being supported on BlackBerry 10 in all 
 documentation and even goes as far as to claim it will attempt to launch the 
 voice note app and return the above error status if it is not installed. 
 Recording works if I repackage my Android APK (built via Cordova) to a BAR 
 and run it via the Android runtime on BB.
 Sincere apologies if I've missed something.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)