[jira] [Created] (CB-5945) Navigator.notification.confirm crashes app
Ismael Olusola Jimoh created CB-5945: Summary: Navigator.notification.confirm crashes app Key: CB-5945 URL: https://issues.apache.org/jira/browse/CB-5945 Project: Apache Cordova Issue Type: Bug Components: Windows 8 Affects Versions: 3.3.0 Reporter: Ismael Olusola Jimoh Assignee: Jesse MacFadyen Good Day All, I recently tested a code whereby I called navigator.notification.confirm on 2 pages. On the first page, I create an instance that triggers a navigator.notification.confirm query, accepting should launch the next page which also has a navigator.notification.confirm triggered from onDeviceReady. Once the second instance is triggered, app crashes and returns no error(or at least visible one). I am testing this on Windows 8 pro, PhoneGap 3.3 and I have all plugins needed installed. When I test this and have a button launch the same function on the second page, error doesn't occur. Find below sample code for said issue: Page 1: !DOCTYPE html html head titleNotification Example/title script type=text/javascript charset=utf-8 src=cordova.js/script script type=text/javascript charset=utf-8 // Wait for device API libraries to load // document.addEventListener(deviceready, onDeviceReady, false); // device APIs are available // function onDeviceReady() { // Empty } // process the confirmation dialog result function onConfirm(buttonIndex) { //alert('You selected button ' + buttonIndex); if(buttonIndex === 1){ window.open(page2.html,_self); } } // Show a custom confirmation dialog // function showConfirm() { navigator.notification.confirm( 'You are the winner!', // message onConfirm,// callback to invoke with index of button pressed 'Game Over', // title ['Restart','Exit'] // buttonLabels ); } /script /head body pa href=# onclick=showConfirm(); return false;Show Confirm/a/p /body /html Page 2: !DOCTYPE html html head titleNotification Example/title !--script type=text/javascript charset=utf-8 src=cordova.js/script-- script type=text/javascript charset=utf-8 // Wait for device API libraries to load // document.addEventListener(deviceready, onDeviceReady, false); // device APIs are available // function onDeviceReady() { // Empty showConfirm(); } // process the confirmation dialog result function onConfirm(buttonIndex) { //alert('You selected button ' + buttonIndex); if(buttonIndex === 1){ window.open(page2.html,_self); } } // Show a custom confirmation dialog // function showConfirm() { navigator.notification.confirm( 'You are the winner!', // message onConfirm,// callback to invoke with index of button pressed 'Game Over', // title ['Restart','Exit'] // buttonLabels ); } /script /head body pa href=# onclick=showConfirm(); return false;Show Confirm/a/p /body /html Thanks. Ismael -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (CB-5946) Automatic mime type
Joachim Piketz created CB-5946: -- Summary: Automatic mime type Key: CB-5946 URL: https://issues.apache.org/jira/browse/CB-5946 Project: Apache Cordova Issue Type: Improvement Components: Android, Plugin File Transfer Affects Versions: 3.3.0 Reporter: Joachim Piketz Feature request: automatically detect mime type. The following works for me in Android: {code} String mime = application/octet-stream; try { mime = cordova.getActivity().getContentResolver().getType(sourceUri); } catch (Exception e) { Log.e(LOG_TAG, e.getMessage(), e); } final String mimeType = mime; Log.d(LOG_TAG, mimeType: + mimeType); {code} -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CB-5946) Automatic mime type in Filetransfer plugin
[ https://issues.apache.org/jira/browse/CB-5946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joachim Piketz updated CB-5946: --- Summary: Automatic mime type in Filetransfer plugin (was: Automatic mime type) Automatic mime type in Filetransfer plugin -- Key: CB-5946 URL: https://issues.apache.org/jira/browse/CB-5946 Project: Apache Cordova Issue Type: Improvement Components: Android, Plugin File Transfer Affects Versions: 3.3.0 Reporter: Joachim Piketz Feature request: automatically detect mime type in filetransfer plugin. The following works for me in Android: {code} String mime = application/octet-stream; try { mime = cordova.getActivity().getContentResolver().getType(sourceUri); } catch (Exception e) { Log.e(LOG_TAG, e.getMessage(), e); } final String mimeType = mime; Log.d(LOG_TAG, mimeType: + mimeType); {code} -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CB-5946) Automatic mime type
[ https://issues.apache.org/jira/browse/CB-5946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joachim Piketz updated CB-5946: --- Description: Feature request: automatically detect mime type in filetransfer plugin. The following works for me in Android: {code} String mime = application/octet-stream; try { mime = cordova.getActivity().getContentResolver().getType(sourceUri); } catch (Exception e) { Log.e(LOG_TAG, e.getMessage(), e); } final String mimeType = mime; Log.d(LOG_TAG, mimeType: + mimeType); {code} was: Feature request: automatically detect mime type. The following works for me in Android: {code} String mime = application/octet-stream; try { mime = cordova.getActivity().getContentResolver().getType(sourceUri); } catch (Exception e) { Log.e(LOG_TAG, e.getMessage(), e); } final String mimeType = mime; Log.d(LOG_TAG, mimeType: + mimeType); {code} Automatic mime type --- Key: CB-5946 URL: https://issues.apache.org/jira/browse/CB-5946 Project: Apache Cordova Issue Type: Improvement Components: Android, Plugin File Transfer Affects Versions: 3.3.0 Reporter: Joachim Piketz Feature request: automatically detect mime type in filetransfer plugin. The following works for me in Android: {code} String mime = application/octet-stream; try { mime = cordova.getActivity().getContentResolver().getType(sourceUri); } catch (Exception e) { Log.e(LOG_TAG, e.getMessage(), e); } final String mimeType = mime; Log.d(LOG_TAG, mimeType: + mimeType); {code} -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CB-5946) Automatic mime type in Filetransfer plugin
[ https://issues.apache.org/jira/browse/CB-5946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joachim Piketz updated CB-5946: --- Description: Feature request: automatically detect mime type in filetransfer plugin. The following works for me in Android: {code} String mime = null; try { mime = this.cordova.getActivity().getContentResolver().getType(sourceUri); if (mime == null) { MimeTypeMap mimemap = MimeTypeMap.getSingleton(); String uri = sourceUri.toString(); int index = uri.lastIndexOf('.'); if (index != -1) mime = mimemap.getMimeTypeFromExtension(uri.substring(index+1).toLowerCase()); } } catch (Exception e) { Log.e(LOG_TAG, e.getMessage(), e); } if (mime == null) mime = application/octet-stream; final String mimeType = mime; Log.d(LOG_TAG, mimeType: + mimeType); {code} was: Feature request: automatically detect mime type in filetransfer plugin. The following works for me in Android: {code} String mime = application/octet-stream; try { mime = cordova.getActivity().getContentResolver().getType(sourceUri); } catch (Exception e) { Log.e(LOG_TAG, e.getMessage(), e); } final String mimeType = mime; Log.d(LOG_TAG, mimeType: + mimeType); {code} Automatic mime type in Filetransfer plugin -- Key: CB-5946 URL: https://issues.apache.org/jira/browse/CB-5946 Project: Apache Cordova Issue Type: Improvement Components: Android, Plugin File Transfer Affects Versions: 3.3.0 Reporter: Joachim Piketz Feature request: automatically detect mime type in filetransfer plugin. The following works for me in Android: {code} String mime = null; try { mime = this.cordova.getActivity().getContentResolver().getType(sourceUri); if (mime == null) { MimeTypeMap mimemap = MimeTypeMap.getSingleton(); String uri = sourceUri.toString(); int index = uri.lastIndexOf('.'); if (index != -1) mime = mimemap.getMimeTypeFromExtension(uri.substring(index+1).toLowerCase()); } } catch (Exception e) { Log.e(LOG_TAG, e.getMessage(), e); } if (mime == null) mime = application/octet-stream; final String mimeType = mime; Log.d(LOG_TAG, mimeType: + mimeType); {code} -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Assigned] (CB-5721) App crashed if invoke root.getFile() and use ../resolve.file.uri as fileNames!
[ https://issues.apache.org/jira/browse/CB-5721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ian Clelland reassigned CB-5721: Assignee: Ian Clelland App crashed if invoke root.getFile() and use ../resolve.file.uri as fileNames! Key: CB-5721 URL: https://issues.apache.org/jira/browse/CB-5721 Project: Apache Cordova Issue Type: Bug Components: iOS, mobile-spec, Plugin File Affects Versions: 3.2.0 Environment: cordova version: 3.3.1-0.1.2 Reporter: glmnbeyond Assignee: Ian Clelland Here are the steps to reproduce it: $ cordova create testFile $ cd testFile $ cordova platform add ios $ cordova platform plugin add 'cordova-plugin-file dev branch code' 1. Copy cordova-mobile-spec tests to testFile/platforms/ios/www/ 2. Modify file.tests.js file.spec.9, change fileName from resolve.file.uri to ../resolve.file.uri {color:red} var fileName = resolve.file.uri = var fileName = ../resolve.file.uri {color} 3. Run this test and app crashed! The outputs were shown as follows: Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: setObjectForKey: object cannot be nil (key: fullPath)' -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Assigned] (CB-5009) Update File API docs re: PERSISTENT TEMPORARY
[ https://issues.apache.org/jira/browse/CB-5009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ian Clelland reassigned CB-5009: Assignee: Ian Clelland Update File API docs re: PERSISTENT TEMPORARY --- Key: CB-5009 URL: https://issues.apache.org/jira/browse/CB-5009 Project: Apache Cordova Issue Type: Sub-task Components: Plugin File Affects Versions: 3.1.0 Reporter: Ian Clelland Assignee: Ian Clelland Fix For: 3.4.0 Docs need updating; {{PERSISTENT}} and {{TEMPORARY}} are still documented as existing as properties on a {{LocalFileSystem}} object. (For that matter, {{LocalFileSytem}} is still documented as being an object, when it really shouldn't exist at all) -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (CB-5947) cordova create fails when link/source arg = $CWD
Ian Clelland created CB-5947: Summary: cordova create fails when link/source arg = $CWD Key: CB-5947 URL: https://issues.apache.org/jira/browse/CB-5947 Project: Apache Cordova Issue Type: Bug Components: CLI Affects Versions: 3.3.0, 3.4.0 Reporter: Ian Clelland Assignee: Mark Koudritsky If {{cordova create}} is passed a {{--src}} or {{--link}} option whose argument is the current directory (or any parent of it, I suspect), then it will try to copy or link the current directory to {{newapp/www}} In the link case, this just creates a symlink cycle; in the copy case, it actually tries to recursively copy the directory inside itself. On OSX it eventually terminates with ENAMETOOLONG. In both cases, the project is broken and could never be used to build anything. We should detect this case and abort with an error condition. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (CB-5910) implement search
[ https://issues.apache.org/jira/browse/CB-5910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13886611#comment-13886611 ] Preston McCauley commented on CB-5910: -- I noticed that the http://plugins.cordova.io/ - search doesn't actually work. No matter what you type in it always returns no results. The same is true for tags. So as of right the site really can't be used for anything except to see a massive unorganized list of plugins. Love to help make this better! implement search Key: CB-5910 URL: https://issues.apache.org/jira/browse/CB-5910 Project: Apache Cordova Issue Type: Sub-task Components: Registry Web Reporter: Steve Gill Assignee: Josh Bavari -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (CB-1375) Sample app incorrectly positioned on BB OS 5
[ https://issues.apache.org/jira/browse/CB-1375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13886640#comment-13886640 ] Bas Bosman commented on CB-1375: Is this issue still relevant? BB OS 5-7 were last officially supported by the 2.8.0 release, which is by now more than a couple of versions ago.. As there's been no activity on this issue in the past 1.5 years I'd suggest closing it as Won't Fix. Sample app incorrectly positioned on BB OS 5 Key: CB-1375 URL: https://issues.apache.org/jira/browse/CB-1375 Project: Apache Cordova Issue Type: Bug Components: App Hello World Affects Versions: 2.1.0 Reporter: Drew Walters Assignee: Michael Brooks Fix For: Master Launching the hello world app on BlackBerry OS 5 simulator (9550 running 5.0.0.713) results in only a part of the page being visible. The entire page is shifted up with only a part of the Cordova robot being visible. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CB-1602) Android birthday field not working
[ https://issues.apache.org/jira/browse/CB-1602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bas Bosman updated CB-1602: --- Component/s: Plugin Contacts Android birthday field not working -- Key: CB-1602 URL: https://issues.apache.org/jira/browse/CB-1602 Project: Apache Cordova Issue Type: Bug Components: Android, Plugin Contacts Affects Versions: 2.1.0 Environment: Baseband : IG9100GXXKL4 (Galaxy S2) Kernel : 2.6.35.7 Android: 2.3.6 Reporter: Olivier Louvignes Assignee: Braden Shepherdson Priority: Minor Labels: contacts I'm trying to save/update a birthday field on my android device. It does work with a timestamp (int) on iOS. However on android, I'll always get the current (today) date to be saved on my device. I tried : - int timestamp - javascript Date - string -MM-DD (what is returned on read().) -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CB-151) More information about location services
[ https://issues.apache.org/jira/browse/CB-151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bas Bosman updated CB-151: -- Component/s: Plugin Geolocation More information about location services Key: CB-151 URL: https://issues.apache.org/jira/browse/CB-151 Project: Apache Cordova Issue Type: New Feature Components: iOS, Plugin Geolocation Environment: IOS Reporter: Emile khattar Priority: Minor Can we know the following? * if the location services are disabled on the phone. * if the location services are disabled for my phonegap application and how can i distinguish between these two cases and how can i open these settings via a url in IOS 4 and 5. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CB-57) Feature request: update media to support streaming
[ https://issues.apache.org/jira/browse/CB-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bas Bosman updated CB-57: - Component/s: Plugin Media Feature request: update media to support streaming -- Key: CB-57 URL: https://issues.apache.org/jira/browse/CB-57 Project: Apache Cordova Issue Type: New Feature Components: iOS, Plugin Media Reporter: Shazron Abdullah Priority: Minor reported at: https://github.com/phonegap/phonegap-iphone/issues/55 by: https://github.com/hardeep The AVAudioPlayer used to implement iOS media does not support streaming audio. In order to do that we need to use the Audio Toolbox. Example and more info here: http://cocoawithlove.com/2009/06/revisiting-old-post-streaming-and.html [Original LightHouse ticket](http://phonegap.lighthouseapp.com/projects/20116/tickets/105) This ticket has 0 attachment(s). -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CB-1033) Update Documentation Theme to Match Homepage
[ https://issues.apache.org/jira/browse/CB-1033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bas Bosman updated CB-1033: --- Issue Type: Improvement (was: Bug) Update Documentation Theme to Match Homepage Key: CB-1033 URL: https://issues.apache.org/jira/browse/CB-1033 Project: Apache Cordova Issue Type: Improvement Components: Docs Affects Versions: Master Reporter: Michael Brooks Assignee: Michael Brooks Fix For: Master Update the theme to match [cordova.io|http://cordova.io] -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (CB-635) Access application version information from JS.
[ https://issues.apache.org/jira/browse/CB-635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13886651#comment-13886651 ] Bas Bosman commented on CB-635: --- There is a plugin which already supports this for iOS and Android: https://github.com/whiteoctober/cordova-plugin-app-version Access application version information from JS. --- Key: CB-635 URL: https://issues.apache.org/jira/browse/CB-635 Project: Apache Cordova Issue Type: New Feature Components: CordovaJS Affects Versions: 1.7.0 Environment: Notably iOS/Android. Reporter: Ladar Levison Assignee: Braden Shepherdson Labels: api-change, javascript, platform Original Estimate: 4h Remaining Estimate: 4h It seems that every platform offers the ability to define an application version. iOS and Android offer string and numeric fields. They are versionName and versionCode on Android. My request is to add the ability to access this app version info using Javascript. Perhaps adding an app namespace with app.versionName, app.versionCode and app.name... It would be an easy enough plugin to write, but figured it should eventually become part of the core. https://developer.android.com/guide/publishing/versioning.html -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CB-2387) navigator.camera.getPicture targetWidth/targetHeight loses aspect ratio in WP8
[ https://issues.apache.org/jira/browse/CB-2387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bas Bosman updated CB-2387: --- Component/s: Plugin Camera navigator.camera.getPicture targetWidth/targetHeight loses aspect ratio in WP8 -- Key: CB-2387 URL: https://issues.apache.org/jira/browse/CB-2387 Project: Apache Cordova Issue Type: Bug Components: Plugin Camera, WP8 Affects Versions: 2.3.0 Environment: Tested on Visual Studio Emulator and Nokia Lumia 920 Reporter: Ole Martin Bakke Assignee: Jesse MacFadyen Priority: Minor It seesms like navigator.camera.getPicture with the targetWidth and targetHeight loses aspect ratio on WP8. navigator.camera.getPicture(onPhotoDataSuccess, onFail, { quality: 80, destinationType: destinationType.DATA_URL, sourceType: source, targetHeight: 640, targetWidth: 640 }); Returns a image which is 640px*640px although the cameras aspect ratio is 1,5:1 The same app built for Android is OK. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CB-2425) FileUploadOptions options structure not very clean, means you can't have a form field called 'header'
[ https://issues.apache.org/jira/browse/CB-2425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bas Bosman updated CB-2425: --- Component/s: (was: CordovaJS) (was: Android) (was: iOS) Plugin File FileUploadOptions options structure not very clean, means you can't have a form field called 'header' - Key: CB-2425 URL: https://issues.apache.org/jira/browse/CB-2425 Project: Apache Cordova Issue Type: Improvement Components: Plugin File Affects Versions: 2.4.0 Environment: Using FileUpload to post a multi-part form to the server. Reporter: Thomas O'Dell Assignee: Joe Bowser Priority: Minor Labels: features Original Estimate: 48h Remaining Estimate: 48h The current design of FileUploadOptions is that the options is an object, whose fields represent the form fields. A special option 'headers' represents the headers to be uploaded. The format of the form fields is not compatible with JQuery and thus has to be massaged. As well, the design makes it impossible to have a form field called headers. I propose the following format for the Options object (25 = 2.5.0, i.e. first release to support api change): { 'apache-cordova-25-form-fields': [ {name: name, value: value}, ... ], // i.e. format returned by JQuery's serializeArray(formObject) 'apache-cordova-25-header-fields': [ {name: name, value: value}, ... ], 'apache-cordova-25-upload-options': [ {name: name, value: value}, // e.g. force chunked mode, set throttle speed ... ], old-style options and headers } -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (CB-5899) FileError code 5 returned with dirEntry.readEntries()
[ https://issues.apache.org/jira/browse/CB-5899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13886655#comment-13886655 ] Boston Dell-Vandenberg commented on CB-5899: Unfortunately, the new commits are crashing the app on load. I'm running Android 4.4, there's an error and a warning showing in logcat: {code} 01-30 10:16:47.838: E/FileUtils(14632): File plugin configuration error: Please set AndroidPersistentFileLocation in config.xml to one of internal (for new applications) or compatibility (for compatibility with previous versions) 01-30 10:16:47.938: W/System.err(14632): java.lang.IndexOutOfBoundsException: Invalid index 1, size is 0 01-30 10:16:47.938: W/System.err(14632):at java.util.ArrayList.throwIndexOutOfBoundsException(ArrayList.java:255) 01-30 10:16:47.938: W/System.err(14632):at java.util.ArrayList.get(ArrayList.java:308) 01-30 10:16:47.938: W/System.err(14632):at org.apache.cordova.file.FileUtils.requestFileSystem(FileUtils.java:740) 01-30 10:16:47.938: W/System.err(14632):at org.apache.cordova.file.FileUtils.access$100(FileUtils.java:50) 01-30 10:16:47.948: W/System.err(14632):at org.apache.cordova.file.FileUtils$11.run(FileUtils.java:290) 01-30 10:16:47.948: W/System.err(14632):at org.apache.cordova.file.FileUtils$24.run(FileUtils.java:461) 01-30 10:16:47.948: W/System.err(14632):at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112) 01-30 10:16:47.948: W/System.err(14632):at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587) 01-30 10:16:47.948: W/System.err(14632):at java.lang.Thread.run(Thread.java:841) {code} Does not crash with the official release of the plugin. FileError code 5 returned with dirEntry.readEntries() - Key: CB-5899 URL: https://issues.apache.org/jira/browse/CB-5899 Project: Apache Cordova Issue Type: Bug Components: Android, Plugin File Affects Versions: 3.3.0 Environment: Android 4.1, Android 4.4 Reporter: Boston Dell-Vandenberg Assignee: Ian Clelland When attempting to read entries of a DirectoryEntry from the local file system the plugin returns an FileError code 5. I am able to successfully read the root directory of the local file system using window.requestFileSystem() but creating a directoryReader and calling readEntries() of any sub directories of the root file system results in the error. I am using Cordova 3.3 and have tried both 0.2.5 of the file plugin as well as the current Dev branch. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CB-2424) FileTransfer returns misleading File Not Found when no body in HTML return
[ https://issues.apache.org/jira/browse/CB-2424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bas Bosman updated CB-2424: --- Component/s: Plugin File Transfer FileTransfer returns misleading File Not Found when no body in HTML return Key: CB-2424 URL: https://issues.apache.org/jira/browse/CB-2424 Project: Apache Cordova Issue Type: Bug Components: Android, Plugin File Transfer Affects Versions: 2.4.0 Environment: Android client trying to upload files to Amazon S3. Reporter: Thomas O'Dell Assignee: Andrew Grieve Priority: Minor Labels: features Original Estimate: 48h Remaining Estimate: 48h FileTransfer will return File Not Found error if the remote server returns only an HTML Response Code. This is very misleading, as it leads the user to believe the file is missing on the local file system. The problem is FileTransfer attempts to open the server connection for read, which raises the exception. FileTransfer should recognise that it is possible and legitimate for the remote open to fail, and simply pass the HTML response code back to the user as the error. Note: this has not been tested on other OS's. Try sending unauthorised files to Amazon S3 and you'll get the situation. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Resolved] (CB-5466) FileTransfer plugin uses full filesystem paths, rather than URLs
[ https://issues.apache.org/jira/browse/CB-5466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ian Clelland resolved CB-5466. -- Resolution: Fixed Fixed in dev branch of file plugin. FileTransfer plugin uses full filesystem paths, rather than URLs Key: CB-5466 URL: https://issues.apache.org/jira/browse/CB-5466 Project: Apache Cordova Issue Type: Bug Components: Plugin File, Plugin File Transfer Reporter: Ian Clelland Assignee: Ian Clelland The file transfer plugin currently uses full device filesystem paths, but is also expected to interact with the File API. Since CB-5403, the File API will no longer be returning full device filesystem paths, and so the FileTransfer API needs to work when presented with filesystem:// URLs as well. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Resolved] (CB-5403) Overhaul File API implementation
[ https://issues.apache.org/jira/browse/CB-5403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ian Clelland resolved CB-5403. -- Resolution: Fixed Fixed in dev branch of file plugin Overhaul File API implementation Key: CB-5403 URL: https://issues.apache.org/jira/browse/CB-5403 Project: Apache Cordova Issue Type: Bug Components: Plugin File Reporter: Ian Clelland Assignee: Ian Clelland This is the meta-issue for all of the File API-related changes. File is getting overhauled, to provide the following features: 1. Entry.toURL() should return a filesystem:// URL on platforms which support it. Platforms which cannot support custom URL protocols are free to return URLs which *can* be used to access the local file system. 2. These URLs will look like: filesystem://localhost/persistent/path/to/file.ext filesystem://localhost/temporary/path/to/file.ext Additional roots are possible for new file systems (assets, media, documents, etc) (The specific format used does not need to conform to any existing or proposed standard, since these URLs should not be assumed valid across machines) 3. Entry.fullPath will be relative to the HTML file system root, and not a path from the root of the actual device file system. 4. Only URLs will be passed over the exec bridge; we won't be passing raw file system paths into and out of JS anymore. (This generally means filesystem:// URLs in the iOS/Android case, but platforms are free to support other URLs as needed) 5. Tests need to be updated so that they still pass when these changes are made. 6. File plugin should be modular, so that additional filesystem types can be easily supported. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Resolved] (CB-5406) [ios] Switch native code to use filesystem://localhost/* URLs internally, and change the FileSystem JS object to use those URLs for the bridge.
[ https://issues.apache.org/jira/browse/CB-5406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ian Clelland resolved CB-5406. -- Resolution: Fixed Fixed in dev branch of file plugin [ios] Switch native code to use filesystem://localhost/* URLs internally, and change the FileSystem JS object to use those URLs for the bridge. --- Key: CB-5406 URL: https://issues.apache.org/jira/browse/CB-5406 Project: Apache Cordova Issue Type: Sub-task Components: iOS, Plugin File Reporter: Ian Clelland Assignee: Ian Clelland -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Resolved] (CB-5408) [ios] Add URL handlers for filesystem:// URLs in native code
[ https://issues.apache.org/jira/browse/CB-5408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ian Clelland resolved CB-5408. -- Resolution: Fixed Fixed in dev branch of file plugin [ios] Add URL handlers for filesystem:// URLs in native code Key: CB-5408 URL: https://issues.apache.org/jira/browse/CB-5408 Project: Apache Cordova Issue Type: Sub-task Components: iOS, Plugin File Reporter: Ian Clelland Assignee: Ian Clelland -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Resolved] (CB-5404) Update File API tests
[ https://issues.apache.org/jira/browse/CB-5404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ian Clelland resolved CB-5404. -- Resolution: Fixed Fixed in dev branch of file plugin Update File API tests - Key: CB-5404 URL: https://issues.apache.org/jira/browse/CB-5404 Project: Apache Cordova Issue Type: Sub-task Components: Plugin File Reporter: Ian Clelland Assignee: Ian Clelland Fix For: 3.4.0 Many of the tests in the test suite are fragile, and depend on implementation-dependent things like whether root directory paths end with a / or not, or whether a particular URL scheme is valid. I'm first going to fix those tests which don't pass under both the old and new systems. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Comment Edited] (CB-5404) Update File API tests
[ https://issues.apache.org/jira/browse/CB-5404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=1388#comment-1388 ] Ian Clelland edited comment on CB-5404 at 1/30/14 3:30 PM: --- Fixed in master branch of mobilespec; tests pass on both master and dev branches of file plugin. was (Author: iclelland): Fixed in dev branch of file plugin Update File API tests - Key: CB-5404 URL: https://issues.apache.org/jira/browse/CB-5404 Project: Apache Cordova Issue Type: Sub-task Components: Plugin File Reporter: Ian Clelland Assignee: Ian Clelland Fix For: 3.4.0 Many of the tests in the test suite are fragile, and depend on implementation-dependent things like whether root directory paths end with a / or not, or whether a particular URL scheme is valid. I'm first going to fix those tests which don't pass under both the old and new systems. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Resolved] (CB-5409) [android] Add URL handlers for filesystem:// URLs in native code
[ https://issues.apache.org/jira/browse/CB-5409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ian Clelland resolved CB-5409. -- Resolution: Fixed Fixed in dev branch of file plugin. URLs are not filesystem:// urls, but rather cdvfile:// URLs, to work around the new Chrome-based webview in Android 4.4. URLs are of the form {{cdvfile://localhost/filesystemname/path}} [android] Add URL handlers for filesystem:// URLs in native code Key: CB-5409 URL: https://issues.apache.org/jira/browse/CB-5409 Project: Apache Cordova Issue Type: Sub-task Components: Plugin File Reporter: Ian Clelland Assignee: Ian Clelland -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Resolved] (CB-5008) resolveLocalFileSystemURL incorrectly named
[ https://issues.apache.org/jira/browse/CB-5008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ian Clelland resolved CB-5008. -- Resolution: Fixed Not running that test just yet; I've added the resolveLocalFileSystemURL symbol as a sibling to resolveLocalFileSystemURI, and added a deprecation log message to resolveLocalFileSystemURI. resolveLocalFileSystemURL incorrectly named --- Key: CB-5008 URL: https://issues.apache.org/jira/browse/CB-5008 Project: Apache Cordova Issue Type: Bug Components: Plugin File Affects Versions: 3.1.0 Reporter: Ian Clelland Assignee: Ian Clelland Fix For: 3.4.0 In the File plugin, window.resolveLocalFileSystemURL is incorrectly named resolveLocalFileSystemURI. Reference: [HTML5 FileSystem API|http://www.w3.org/TR/file-system-api/#widl-LocalFileSystem-resolveLocalFileSystemURL-void-DOMString-url-EntryCallback-successCallback-ErrorCallback-errorCallback] -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Resolved] (CB-5007) FileEntry.toURL returns a URL that cannot be used when hosted at a non-file domain
[ https://issues.apache.org/jira/browse/CB-5007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ian Clelland resolved CB-5007. -- Resolution: Fixed Fixed with the latest dev version of the File plugin. FileEntry.toURL returns a URL that cannot be used when hosted at a non-file domain -- Key: CB-5007 URL: https://issues.apache.org/jira/browse/CB-5007 Project: Apache Cordova Issue Type: Bug Components: Plugin File Affects Versions: 3.1.0 Reporter: Ian Clelland Assignee: Ian Clelland Fix For: 3.4.0 FileEntry.toURL should return a url which can be accessed by the application. It currently just prepends {{file:///}} to the pathname. THe resulting path cannot be read by the application (say, in a script or img tag) if the application is hosted at a custom scheme. Mobile Chrome Apps, hosted at {{chrome-extension://app-id/}}, can't use files they have cached on the local filesystem because of this. I'd like to change toURL to return something that can be read by any application. http://www.w3.org/TR/file-system-api/#widl-Entry-toURL-DOMString suggests using {{filesystem:///identifier}}, which is consistent with Chrome's behaviour. For older versions of Android, we may have to use content:// urls instead, but I'll investigate that first, to see if it can be consistent. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CB-2661) InAppBrowser creates channels per-instance, and Channels are assumed to be unique-per-name
[ https://issues.apache.org/jira/browse/CB-2661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bas Bosman updated CB-2661: --- Component/s: Plugin InAppBrowser InAppBrowser creates channels per-instance, and Channels are assumed to be unique-per-name -- Key: CB-2661 URL: https://issues.apache.org/jira/browse/CB-2661 Project: Apache Cordova Issue Type: Bug Components: CordovaJS, Plugin InAppBrowser Reporter: Andrew Grieve Assignee: Andrew Grieve Priority: Minor The problem with this is that the channel module maintains a reference to each channel in create(): channel[name] = channel; We should just remove this behaviour from channel.js and figure out if anyone was depending on it. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (CB-5403) Overhaul File API implementation
[ https://issues.apache.org/jira/browse/CB-5403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13886670#comment-13886670 ] Ian Clelland commented on CB-5403: -- In the end, the URLs used are of the form {code} cdvfile://localhost/filesystemname/pathtoresource {code} This change was due to the {{filesystem}} scheme being handled specially by the Chrome-based webview in Android 4.4; it is not possible to intercept requests for arbitrary {{filesystem://}} URLs. iOS was changed to match for project-level consistency, although there is no technical requirement for URLs to be consistent across platforms (or even across devices). Overhaul File API implementation Key: CB-5403 URL: https://issues.apache.org/jira/browse/CB-5403 Project: Apache Cordova Issue Type: Bug Components: Plugin File Reporter: Ian Clelland Assignee: Ian Clelland This is the meta-issue for all of the File API-related changes. File is getting overhauled, to provide the following features: 1. Entry.toURL() should return a filesystem:// URL on platforms which support it. Platforms which cannot support custom URL protocols are free to return URLs which *can* be used to access the local file system. 2. These URLs will look like: filesystem://localhost/persistent/path/to/file.ext filesystem://localhost/temporary/path/to/file.ext Additional roots are possible for new file systems (assets, media, documents, etc) (The specific format used does not need to conform to any existing or proposed standard, since these URLs should not be assumed valid across machines) 3. Entry.fullPath will be relative to the HTML file system root, and not a path from the root of the actual device file system. 4. Only URLs will be passed over the exec bridge; we won't be passing raw file system paths into and out of JS anymore. (This generally means filesystem:// URLs in the iOS/Android case, but platforms are free to support other URLs as needed) 5. Tests need to be updated so that they still pass when these changes are made. 6. File plugin should be modular, so that additional filesystem types can be easily supported. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CB-3056) Camera.getPicture() should do IO on a background thread. (android)
[ https://issues.apache.org/jira/browse/CB-3056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bas Bosman updated CB-3056: --- Component/s: Plugin Camera Camera.getPicture() should do IO on a background thread. (android) -- Key: CB-3056 URL: https://issues.apache.org/jira/browse/CB-3056 Project: Apache Cordova Issue Type: Bug Components: Android, Plugin Camera Reporter: Andrew Grieve Assignee: Andrew Grieve Priority: Minor -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CB-2655) Add InAppBrowser.executeScript() / InAppBrowser.insertCSS API (Blackberry)
[ https://issues.apache.org/jira/browse/CB-2655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bas Bosman updated CB-2655: --- Component/s: Plugin InAppBrowser Add InAppBrowser.executeScript() / InAppBrowser.insertCSS API (Blackberry) -- Key: CB-2655 URL: https://issues.apache.org/jira/browse/CB-2655 Project: Apache Cordova Issue Type: Sub-task Components: BlackBerry, Plugin InAppBrowser Reporter: Andrew Grieve Assignee: Lorin Beer Fix For: 3.4.0 -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CB-2305) Add InAppBrowser.executeScript() / InAppBrowser.insertCSS API
[ https://issues.apache.org/jira/browse/CB-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bas Bosman updated CB-2305: --- Component/s: (was: CordovaJS) Plugin InAppBrowser Add InAppBrowser.executeScript() / InAppBrowser.insertCSS API - Key: CB-2305 URL: https://issues.apache.org/jira/browse/CB-2305 Project: Apache Cordova Issue Type: Bug Components: Plugin InAppBrowser Reporter: Andrew Grieve Assignee: Lorin Beer Priority: Minor Maybe base it off of: http://developer.chrome.com/extensions/tabs.html#method-executeScript http://developer.chrome.com/extensions/tabs.html#method-insertCSS (we can probably implement insertCSS all in JS by using executeScript) var wnd = window.open('local.html', '_blank', 'location=yes'); wnd.executeScript({runAt:'document_start', file:'extra.js'}, function(result) { alert(result); // result = (result of last statement). }); -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Resolved] (CB-5407) [android] Switch native code to use filesystem://localhost/* URLs internally, and change the FileSystem JS object to use those URLs for the bridge.
[ https://issues.apache.org/jira/browse/CB-5407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ian Clelland resolved CB-5407. -- Resolution: Fixed Fixed in dev branch of file plugin [android] Switch native code to use filesystem://localhost/* URLs internally, and change the FileSystem JS object to use those URLs for the bridge. --- Key: CB-5407 URL: https://issues.apache.org/jira/browse/CB-5407 Project: Apache Cordova Issue Type: Sub-task Components: Android, Plugin File Reporter: Ian Clelland Assignee: Ian Clelland -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CB-1455) 'authorization: ...' instead of 'Authorization: ...' set in FileTransfer
[ https://issues.apache.org/jira/browse/CB-1455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bas Bosman updated CB-1455: --- Component/s: Plugin File Transfer 'authorization: ...' instead of 'Authorization: ...' set in FileTransfer Key: CB-1455 URL: https://issues.apache.org/jira/browse/CB-1455 Project: Apache Cordova Issue Type: Bug Components: Android, Plugin File Transfer Affects Versions: 2.0.0 Environment: Android Reporter: Natalia Bartol Assignee: Ian Clelland Priority: Trivial Setting params.headers = {'Authorization' : make_base_auth()}; for FileTransfer results in the request header: authorization: Basic bmssOmZvbw== According to http://tools.ietf.org/html/rfc1945#section-10.2 it should be written with capital letter: Authorization: Basic bmssOmZvbw== I bumped into this issue when trying to handle request generated by FileTransfer with ZendFramework2. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CB-2637) Speed up contacts find by ignoring entries with specified null fields
[ https://issues.apache.org/jira/browse/CB-2637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bas Bosman updated CB-2637: --- Component/s: Plugin Contacts Speed up contacts find by ignoring entries with specified null fields - Key: CB-2637 URL: https://issues.apache.org/jira/browse/CB-2637 Project: Apache Cordova Issue Type: Improvement Components: Android, Plugin Contacts Reporter: Nestor Soign Labels: contacts Finding contacts is very slow: roughly 1 second per 100 contacts on recent hardware. According to https://issues.apache.org/jira/browse/CB-1250 the current major speed limitation is the number of contacts returned by find. I have noticed that a large percentage of contacts appear to be either incomplete or lack email addresses or phone numbers, since Google combines phone and email contacts into a single list. Many applications may be interested only in contacts which have phone numbers or which have email, or which have either. By allowing specification of fields which are required to be non-null, contacts.find calls could be sped up significantly for those cases. For example, I have a contacts list with 2641 contacts in it. Of those, 614 have telephone numbers but no emails. 1134 have emails but no telephone numbers. 203 have both emails and telephone numbers, and the remainder appear to be malformed and useless. A contacts.find call on my phone (HTC EVO 4G LTE running Android 4.1.1) takes about 13 seconds to complete, but if it could be limited to only contacts with telephone numbers, it would probably take about 3-4 seconds. Even if it were limited to contacts with either a telephone number or an email, it would probably take about 9-10 seconds, still a substantial improvement. If this is easy to implement it would be very helpful in many applications. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CB-248) captureVideo() on iOS doesnt seem to save to the device's photoalbum like captureImage() does
[ https://issues.apache.org/jira/browse/CB-248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bas Bosman updated CB-248: -- Component/s: Plugin Media Capture captureVideo() on iOS doesnt seem to save to the device's photoalbum like captureImage() does - Key: CB-248 URL: https://issues.apache.org/jira/browse/CB-248 Project: Apache Cordova Issue Type: New Feature Components: iOS, Plugin Media Capture Affects Versions: 1.4.0 Environment: tested on iOS only Reporter: Filipe Cruz Priority: Minor Labels: capture, documentation, video calling navigator.device.capture.captureImage() the local path to a temporary location is retrieved and the image is saved to the device's photoalbum. calling navigator.device.capture.captureVideo() only the local path to a temporary location is retrieved, the video is not saved to the device's photoalbum. I also tested camera.getPicture() but the capturing functionality of that funciton only works for images. So there is no working solution to capture video to device photoalbum using callback-phonegap. Also, documentation of http://docs.phonegap.com/en/1.4.1/phonegap_camera_camera.md.html#cameraOptions_options is wrong. 'MediaType' should be 'mediaType' Test case below {code} !DOCTYPE html html head titleCapture Video/title script type=text/javascript charset=utf-8 src=phonegap.js/script script type=text/javascript charset=utf-8 function captureVideoSuccess(mediaFiles) { document.getElementById('videocontent').innerHTML = mediaFiles[0].fullPath; document.getElementById('videocontent2').innerHTML = 'video controls=truesource src='+mediaFiles[0].fullPath+'/video'; } function captureImageSuccess(mediaFiles) { document.getElementById('imagecontent').innerHTML = mediaFiles[0].fullPath; document.getElementById('imagecontent2').innerHTML = 'img src='+mediaFiles[0].fullPath+''; } function captureError(error) { var msg = 'An error occurred during capture: ' + error.code; navigator.notification.alert(msg, null, 'Uh oh!'); } function captureVideo() { navigator.device.capture.captureVideo(captureVideoSuccess, captureError); } function captureImage() { navigator.device.capture.captureImage(captureImageSuccess, captureError); } /script /head body button onclick=captureVideo();Capture Video/button brbr button onclick=captureImage();Capture Image/button brbr div id=videocontentvoid/div div id=videocontent2void/div div id=imagecontentvoid/div div id=imagecontent2void/div /body /html {code} -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CB-3283) FileTransfer.download should follow redirects on iOS
[ https://issues.apache.org/jira/browse/CB-3283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bas Bosman updated CB-3283: --- Component/s: Plugin File Transfer FileTransfer.download should follow redirects on iOS Key: CB-3283 URL: https://issues.apache.org/jira/browse/CB-3283 Project: Apache Cordova Issue Type: Bug Components: iOS, Plugin File Transfer Reporter: Andrew Grieve Assignee: Andrew Grieve Priority: Minor It's not currently following them. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CB-2167) Support File.slice for retrieving parts of files using FileReader
[ https://issues.apache.org/jira/browse/CB-2167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bas Bosman updated CB-2167: --- Component/s: Plugin File Support File.slice for retrieving parts of files using FileReader - Key: CB-2167 URL: https://issues.apache.org/jira/browse/CB-2167 Project: Apache Cordova Issue Type: New Feature Components: CordovaJS, Plugin File Reporter: Braden Shepherdson Assignee: Braden Shepherdson Priority: Minor Labels: android, ios These changes are nearly complete, I'm creating this bug for three reasons: To point to the commits across the various repos, to capture the one outstanding bug on iOS (see sub-bug) and to track adding this feature to more platforms (more sub-bugs). -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (CB-3020) HideKeyboardFormAccessoryBar and KeyboardShrinksView show white bar instead of removing it
[ https://issues.apache.org/jira/browse/CB-3020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13886686#comment-13886686 ] Sanjiv commented on CB-3020: Thanks Chris Emerson. This quick fix/hack worked for us. Wanted to share our scenario. -- We are on 'Sencha Touch 2.0.2 + PhoneGap 2.2'. I upgraded to PhoneGap 2.9. Upgrade was easy and nothing broke luckily. Just followed PhoneGap Platform Guide. Then applied this fix from Gist - https://gist.github.com/cemerson/6642026 I edited Config.xml for another IOS 7 related issue (Status Bar overlapping). Otherwise you can leave it as it is. Tested successfully on IPAD/IPhone 4S (iOS 5) / IPAD (iOS 7). Replied on Sencha Forum - http://www.sencha.com/forum/showthread.php?272088-Software-keyboard-pushes-tabbar-up But definitely will be upgrading to Sencha 2.3/PhoneGap (Latest) in coming months to avoid more iOS 7 UI issues. -- HideKeyboardFormAccessoryBar and KeyboardShrinksView show white bar instead of removing it -- Key: CB-3020 URL: https://issues.apache.org/jira/browse/CB-3020 Project: Apache Cordova Issue Type: Bug Components: iOS, Plugins Affects Versions: 2.6.0, 3.0.0 Environment: ios 6.1.3 Reporter: Horst Perfect Assignee: Shazron Abdullah Priority: Minor Labels: keyboard-plugin Fix For: 3.1.0 Attachments: Classes.zip, iOS Simulator Screen shot 2013-10-05 2.27.26 PM.png, iOS Simulator Screen shot 2013-10-05 2.27.36 PM.png, ios.zip I use phonegap 2.6 with the two new preferences HideKeyboardFormAccessoryBar KeyboardShrinksView set to true. Instead of the AccessoryBar a white bar appears ([screenshot|http://i.stack.imgur.com/3fgV8.png]). This is just happening when i set *both* of the preferences to true. When i just set the AccessoryBar preference to true the bar disappears as planned. Horst -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CB-402) Improve Contacts search taking a long time by using (NSArray*)filteredArrayUsingPredicate:(NSPredicate*)predicate
[ https://issues.apache.org/jira/browse/CB-402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bas Bosman updated CB-402: -- Component/s: Plugin Contacts Improve Contacts search taking a long time by using (NSArray*)filteredArrayUsingPredicate:(NSPredicate*)predicate - Key: CB-402 URL: https://issues.apache.org/jira/browse/CB-402 Project: Apache Cordova Issue Type: Improvement Components: iOS, Plugin Contacts Reporter: Shazron Abdullah Priority: Minor Labels: benchmark, unit-test We have to analyze this first to see if it is a big problem, with a huge N. I believe it is. Right now our search method is O( n ), while using Apple's search method it is possibly O( log n ) - but that's just a guess if I assume internally they use a binary search. Steps: 1. Grab all the contacts in a NSArray through ABAddressBookCopyArrayOfAllPeople 2. Construct a NSPredicate for the filter, and call filteredArrayUsingPredicate on the NSArray returned in step 1. 3. Convert the NSArray returned in step 2. to our CDVContact objects -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (CB-2167) Support File.slice for retrieving parts of files using FileReader
[ https://issues.apache.org/jira/browse/CB-2167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13886688#comment-13886688 ] Bas Bosman commented on CB-2167: Can this be marked as resolved? All Sub-Tasks have been completed. Support File.slice for retrieving parts of files using FileReader - Key: CB-2167 URL: https://issues.apache.org/jira/browse/CB-2167 Project: Apache Cordova Issue Type: New Feature Components: CordovaJS, Plugin File Reporter: Braden Shepherdson Assignee: Braden Shepherdson Priority: Minor Labels: android, ios These changes are nearly complete, I'm creating this bug for three reasons: To point to the commits across the various repos, to capture the one outstanding bug on iOS (see sub-bug) and to track adding this feature to more platforms (more sub-bugs). -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CB-2306) FileTransfer.download does not support file:/// URLs on Android
[ https://issues.apache.org/jira/browse/CB-2306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bas Bosman updated CB-2306: --- Component/s: Plugin File Transfer FileTransfer.download does not support file:/// URLs on Android --- Key: CB-2306 URL: https://issues.apache.org/jira/browse/CB-2306 Project: Apache Cordova Issue Type: Bug Components: Android, Plugin File Transfer Reporter: Andrew Grieve Assignee: Ian Clelland Priority: Minor This was recently fixed for iOS. Likely what users want here is to use the Entry.copyTo API instead, but some have tried this, so it's worth reporting. I started on a fix for this by mapping it to copyTo on the JS side: argscheck.checkArgs('ssFF*', 'FileTransfer.download', arguments); // Convert transfers from file:/// into File.copyTo calls. if ('' + (/^.*?:/.exec(source)) == 'file:') { var parts = /(.*)\/(.*?)$/.exec(target); exec(successCallback, errorCallback, File, copyTo, [source.slice(7), parts[1], parts[2]]); return; } This still failed the mobile spec test though due to /android_asset/ paths not being resolved on the native side. We may want to add /android_asset/ resolution into resolveLocalFileSystemURI as well... -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Comment Edited] (CB-3020) HideKeyboardFormAccessoryBar and KeyboardShrinksView show white bar instead of removing it
[ https://issues.apache.org/jira/browse/CB-3020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13886686#comment-13886686 ] Sanjiv edited comment on CB-3020 at 1/30/14 3:52 PM: - Thanks Chris Emerson. This quick fix/hack worked for us. Wanted to share our scenario. -- We are on 'Sencha Touch 2.0.2 + PhoneGap 2.2'. I upgraded to PhoneGap 2.9. Upgrade was easy and nothing broke luckily. Just followed PhoneGap Platform Guide. Then applied this fix from Gist - https://gist.github.com/cemerson/6642026 I edited Config.xml for another IOS 7 related issue (Status Bar overlapping). Otherwise you can leave it as it is. For reference preference name=AllowInlineMediaPlayback value=false / preference name=AutoHideSplashScreen value=true / preference name=BackupWebStorage value=cloud / preference name=DisallowOverscroll value=false / preference name=EnableLocation value=false /!-- DEPRECATED -- preference name=EnableViewportScale value=false / preference name=FadeSplashScreen value=true / preference name=FadeSplashScreenDuration value=.25 / preference name=HideKeyboardFormAccessoryBar value=false / preference name=KeyboardDisplayRequiresUserAction value=true / preference name=KeyboardShrinksView value=false / preference name=MediaPlaybackRequiresUserAction value=false / preference name=ShowSplashScreenSpinner value=true / preference name=SuppressesIncrementalRendering value=false / preference name=TopActivityIndicator value=gray / Tested successfully on IPAD/IPhone 4S (iOS 5) / IPAD (iOS 7). Replied on Sencha Forum - http://www.sencha.com/forum/showthread.php?272088-Software-keyboard-pushes-tabbar-up But definitely will be upgrading to Sencha 2.3/PhoneGap (Latest) in coming months to avoid more iOS 7 UI issues. -- was (Author: apachebite): Thanks Chris Emerson. This quick fix/hack worked for us. Wanted to share our scenario. -- We are on 'Sencha Touch 2.0.2 + PhoneGap 2.2'. I upgraded to PhoneGap 2.9. Upgrade was easy and nothing broke luckily. Just followed PhoneGap Platform Guide. Then applied this fix from Gist - https://gist.github.com/cemerson/6642026 I edited Config.xml for another IOS 7 related issue (Status Bar overlapping). Otherwise you can leave it as it is. Tested successfully on IPAD/IPhone 4S (iOS 5) / IPAD (iOS 7). Replied on Sencha Forum - http://www.sencha.com/forum/showthread.php?272088-Software-keyboard-pushes-tabbar-up But definitely will be upgrading to Sencha 2.3/PhoneGap (Latest) in coming months to avoid more iOS 7 UI issues. -- HideKeyboardFormAccessoryBar and KeyboardShrinksView show white bar instead of removing it -- Key: CB-3020 URL: https://issues.apache.org/jira/browse/CB-3020 Project: Apache Cordova Issue Type: Bug Components: iOS, Plugins Affects Versions: 2.6.0, 3.0.0 Environment: ios 6.1.3 Reporter: Horst Perfect Assignee: Shazron Abdullah Priority: Minor Labels: keyboard-plugin Fix For: 3.1.0 Attachments: Classes.zip, iOS Simulator Screen shot 2013-10-05 2.27.26 PM.png, iOS Simulator Screen shot 2013-10-05 2.27.36 PM.png, ios.zip I use phonegap 2.6 with the two new preferences HideKeyboardFormAccessoryBar KeyboardShrinksView set to true. Instead of the AccessoryBar a white bar appears ([screenshot|http://i.stack.imgur.com/3fgV8.png]). This is just happening when i set *both* of the preferences to true. When i just set the AccessoryBar preference to true the bar disappears as planned. Horst -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Resolved] (CB-2167) Support File.slice for retrieving parts of files using FileReader
[ https://issues.apache.org/jira/browse/CB-2167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Grieve resolved CB-2167. --- Resolution: Fixed Woohoo! Support File.slice for retrieving parts of files using FileReader - Key: CB-2167 URL: https://issues.apache.org/jira/browse/CB-2167 Project: Apache Cordova Issue Type: New Feature Components: CordovaJS, Plugin File Reporter: Braden Shepherdson Assignee: Braden Shepherdson Priority: Minor Labels: android, ios These changes are nearly complete, I'm creating this bug for three reasons: To point to the commits across the various repos, to capture the one outstanding bug on iOS (see sub-bug) and to track adding this feature to more platforms (more sub-bugs). -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CB-3045) Set delay to stop audio in Media API
[ https://issues.apache.org/jira/browse/CB-3045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bas Bosman updated CB-3045: --- Component/s: Plugin Media Set delay to stop audio in Media API Key: CB-3045 URL: https://issues.apache.org/jira/browse/CB-3045 Project: Apache Cordova Issue Type: Wish Components: iOS, Plugin Media Affects Versions: 2.5.0 Environment: n/a Reporter: Adam Ware Priority: Minor Labels: audio, ios, media Would like to see ability to set time delay (in seconds) to stop audio play when using the Media API (for audio) - similar to number of loops currently used with IOS. This would be handy when app uses audio in the background. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (CB-5949) framework customer=true doesn't always work
Kelvin Dart created CB-5949: --- Summary: framework customer=true doesn't always work Key: CB-5949 URL: https://issues.apache.org/jira/browse/CB-5949 Project: Apache Cordova Issue Type: Bug Components: CLI, iOS Affects Versions: 3.3.0 Environment: Mac OS X Mavericks 10.9.1; Xcode 5; Cordova 3.3.1-0.1.2. Reporter: Kelvin Dart Priority: Critical I have a plugin I have developed which has a custom framework (the plugin works fine, etc. and if I run it outside of the CLI, no problems). I have created plugin.xml to reflect all custom attributes which I need, and one of those tags in plugin.xml is: framework src=src/ios/myframework.framework customer=true And this works fine when adding it etc. I cannot be sure of the steps to replicate exactly. But somewhere along the line, the directory become corrupted (as far as I am aware, through no fault of my own) and as a result, Cordova is not building correctly unless I manually add in the framework into Xcode (which is not ideal) - so that my source file can compile. I can provide you with my project - however my code is confidential so I would need to liaise with a Cordova contributor directly. If not, I can follow some debugging instructions to ascertain, but I have not figured out which script handles the plugin.xml parsing. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (CB-5948) Env name getter
Вячеслав Шабельник created CB-5948: -- Summary: Env name getter Key: CB-5948 URL: https://issues.apache.org/jira/browse/CB-5948 Project: Apache Cordova Issue Type: New Feature Reporter: Вячеслав Шабельник It'll be really cool and useful have some getter or property inside of app that can indicate in what type of build we work (dev/prod). For example dev when we build debug build and prod when release build. It can be extremely helpful when developers build serious commercial products. In this case switching of some methods and requests in app can be automatized. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CB-5949) framework custom=true doesn't always pick up my custom framework
[ https://issues.apache.org/jira/browse/CB-5949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelvin Dart updated CB-5949: Summary: framework custom=true doesn't always pick up my custom framework (was: framework customer=true doesn't always work) framework custom=true doesn't always pick up my custom framework -- Key: CB-5949 URL: https://issues.apache.org/jira/browse/CB-5949 Project: Apache Cordova Issue Type: Bug Components: CLI, iOS Affects Versions: 3.3.0 Environment: Mac OS X Mavericks 10.9.1; Xcode 5; Cordova 3.3.1-0.1.2. Reporter: Kelvin Dart Priority: Critical Labels: CLI, custom, framework, ios, plugin I have a plugin I have developed which has a custom framework (the plugin works fine, etc. and if I run it outside of the CLI, no problems). I have created plugin.xml to reflect all custom attributes which I need, and one of those tags in plugin.xml is: framework src=src/ios/myframework.framework customer=true And this works fine when adding it etc. I cannot be sure of the steps to replicate exactly. But somewhere along the line, the directory become corrupted (as far as I am aware, through no fault of my own) and as a result, Cordova is not building correctly unless I manually add in the framework into Xcode (which is not ideal) - so that my source file can compile. I can provide you with my project - however my code is confidential so I would need to liaise with a Cordova contributor directly. If not, I can follow some debugging instructions to ascertain, but I have not figured out which script handles the plugin.xml parsing. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CB-3610) JS, spec, docs - all platforms
[ https://issues.apache.org/jira/browse/CB-3610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bas Bosman updated CB-3610: --- Component/s: Plugin InAppBrowser JS, spec, docs - all platforms -- Key: CB-3610 URL: https://issues.apache.org/jira/browse/CB-3610 Project: Apache Cordova Issue Type: Sub-task Components: CordovaJS, mobile-spec, Plugin InAppBrowser Reporter: David Kemp Assignee: David Kemp -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CB-5949) framework custom=true doesn't always pick up my custom framework
[ https://issues.apache.org/jira/browse/CB-5949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelvin Dart updated CB-5949: Priority: Major (was: Critical) framework custom=true doesn't always pick up my custom framework -- Key: CB-5949 URL: https://issues.apache.org/jira/browse/CB-5949 Project: Apache Cordova Issue Type: Bug Components: CLI, iOS Affects Versions: 3.3.0 Environment: Mac OS X Mavericks 10.9.1; Xcode 5; Cordova 3.3.1-0.1.2. Reporter: Kelvin Dart Labels: CLI, custom, framework, ios, plugin I have a plugin I have developed which has a custom framework (the plugin works fine, etc. and if I run it outside of the CLI, no problems). I have created plugin.xml to reflect all custom attributes which I need, and one of those tags in plugin.xml is: framework src=src/ios/myframework.framework customer=true And this works fine when adding it etc. I cannot be sure of the steps to replicate exactly. But somewhere along the line, the directory become corrupted (as far as I am aware, through no fault of my own) and as a result, Cordova is not building correctly unless I manually add in the framework into Xcode (which is not ideal) - so that my source file can compile. I can provide you with my project - however my code is confidential so I would need to liaise with a Cordova contributor directly. If not, I can follow some debugging instructions to ascertain, but I have not figured out which script handles the plugin.xml parsing. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (CB-5950) Android build on Windows fails with spaces in \Program Files
Jon Watte created CB-5950: - Summary: Android build on Windows fails with spaces in \Program Files Key: CB-5950 URL: https://issues.apache.org/jira/browse/CB-5950 Project: Apache Cordova Issue Type: Bug Components: Android Affects Versions: 3.3.0 Environment: Windows 8.1 Reporter: Jon Watte I downloaded and installed the latest nodejs for Windows (0.10.25,) latest JDK (1.7.0_51), latest Android SDK (19), and latest apache-ant (1.9.3) and created a new project as per the quickstart instructions. Creating the project and adding the android platform works fine. However, cordova build fails with an error: Generating config.xml from defaults for platform android Preparing android project Compiling app on platform android via command cmd /c C:\IMVU\example\example\platforms\android\cordova\build C:\Users\jwatte\AppData\Roaming\npm\node_modules\cordova\node_modules\q\q.js:126 throw e; ^ Error: An error occurred while building the android project.Error executing ant debug -f C:\IMVU\example\example\platforms\android\build.xml: BUILD FAILED C:\code\android-sdks\tools\ant\build.xml:892: The following error occurred while executing this line: C:\code\android-sdks\tools\ant\build.xml:894: The following error occurred while executing this line: C:\code\android-sdks\tools\ant\build.xml:906: The following error occurred while executing this line: C:\code\android-sdks\tools\ant\build.xml:284: null returned: 1 Total time: 3 seconds at ChildProcess.anonymous (C:\Users\jwatte\AppData\Roaming\npm\node_modules\cordova\src\compile.js:65:22) at ChildProcess.EventEmitter.emit (events.js:98:17) at maybeClose (child_process.js:743:16) at Socket.anonymous (child_process.js:956:11) at Socket.EventEmitter.emit (events.js:95:17) at Pipe.close (net.js:466:12) C:\IMVU\example\example Running the build file manually prints some more information; the error happens when trying to run dx and it claims C:\Program is not an internal or external command. There are many previous bugs about doesn't work with spaces in paths, so this seems like a regression. Spaces in paths are a fact of live on Windows, as is to dorky quoting rules for COMMAND.COM, so it would seem that a basic acceptance test that tests everything with the latest of all the dependencies on an otherwise fresh system should catch these things. If Windows is an important host for cordova developers, perhaps that would be a worthwhile investment? -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CB-3804) Not consistently setting PluginResult message for JSON_EXCEPTION Status
[ https://issues.apache.org/jira/browse/CB-3804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bas Bosman updated CB-3804: --- Component/s: Plugin InAppBrowser Not consistently setting PluginResult message for JSON_EXCEPTION Status --- Key: CB-3804 URL: https://issues.apache.org/jira/browse/CB-3804 Project: Apache Cordova Issue Type: Improvement Components: Android, Plugin InAppBrowser Affects Versions: 2.7.0 Reporter: Peter Assignee: Joe Bowser Priority: Minor The PluginResult appears to be inconsistently created for Status.JSON_EXCEPTION. exception message is passed * InAppBrowser.java: scriptResult = new PluginResult(PluginResult.Status.JSON_EXCEPTION, e.getMessage()); exception message is NOT passed * InAppBrower.java: this.callbackContext.sendPluginResult(new PluginResult(PluginResult.Status.JSON_EXCEPTION)); * Globalization.java: callbackContext.sendPluginResult(new PluginResult(PluginResult.Status.JSON_EXCEPTION)); * FileTransfer.java: result = new PluginResult(PluginResult.Status.JSON_EXCEPTION); * FileTransfer.java: context.sendPluginResult(new PluginResult(PluginResult.Status.JSON_EXCEPTION)); * App.java: callbackContext.sendPluginResult(new PluginResult(PluginResult.Status.JSON_EXCEPTION)); * PluginManager.java: PluginResult cr = new PluginResult(PluginResult.Status.JSON_EXCEPTION); Shouldn't these all be constructed the same? -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CB-1544) Support custom label on contact phone number
[ https://issues.apache.org/jira/browse/CB-1544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bas Bosman updated CB-1544: --- Component/s: Plugin Contacts Support custom label on contact phone number Key: CB-1544 URL: https://issues.apache.org/jira/browse/CB-1544 Project: Apache Cordova Issue Type: Improvement Components: iOS, Plugin Contacts Reporter: Stefan Janson Priority: Minor If I try to save a custom label with PhoneGap, it is saved as other. Would be nice if the entered value actually was saved. Have checked iOS API and apps using this and it should be doable, or is the problem in phonegap-code? I have not coded anything in COcoa but found this link that should be related I guess. http://stackoverflow.com/questions/2675783/how-to-add-a-custom-label-to-iphone-addressbook-programmaticly Last time I requested this, my issue was closed since it could not be done but no reason was given, think it got confues with Android. This improvement request is for iOS. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CB-3400) Groups settings of contacts of an Android device.
[ https://issues.apache.org/jira/browse/CB-3400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bas Bosman updated CB-3400: --- Component/s: Plugin Contacts Groups settings of contacts of an Android device. --- Key: CB-3400 URL: https://issues.apache.org/jira/browse/CB-3400 Project: Apache Cordova Issue Type: New Feature Components: Android, Plugin Contacts Affects Versions: Master, 2.9.0, 3.0.0 Environment: Android 4.0 and above Reporter: El Khal Assignee: Joe Bowser Priority: Minor Currently categories field of Contact object returns nothing. I wish it would return so called Groups settings of contacts of an Android device. Currently this field is not accessible. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CB-2332) Document new body property on FileTransferError
[ https://issues.apache.org/jira/browse/CB-2332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bas Bosman updated CB-2332: --- Component/s: Plugin File Transfer Document new body property on FileTransferError - Key: CB-2332 URL: https://issues.apache.org/jira/browse/CB-2332 Project: Apache Cordova Issue Type: Sub-task Components: Docs, Plugin File Transfer Affects Versions: 2.3.0, 2.4.0, 2.5.0, 2.6.0 Reporter: Filip Maj Assignee: Michael Brooks -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (CB-4914) Cordova CLI cannot build Android project when the path contains spaces
[ https://issues.apache.org/jira/browse/CB-4914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13886816#comment-13886816 ] Jon Watte commented on CB-4914: --- Seems like this, or something much like it, is back with cordova 3.3 and Android SDK 19. Cordova CLI cannot build Android project when the path contains spaces -- Key: CB-4914 URL: https://issues.apache.org/jira/browse/CB-4914 Project: Apache Cordova Issue Type: Bug Components: Android, CLI Affects Versions: 3.0.0 Environment: Platform: Windows 7 Cordova CLI Version: 3.0.9 Reporter: Simon Fisher Assignee: Lorin Beer Fix For: 3.2.0 When attempting to use the CLI to compile/build an android project, if the path contains spaces then the command fails. Example: C:\my pathcordova create HelloWorld com.test.helloworld HelloWorld (success) C:\my path cd helloworld C:\my path\helloworldcordova platform add android (success) C:\my path\helloworldcordova prepare android (success) C:\my path\helloworldcordova compile android [Error: An error occurred while building the android project. 'C:\my' is not recognized as an internal or external command, operable program or batch file. ] The same error occurs if I manually run platforms/android/cordova/build.bat However if I manually run platforms/android/ant debug then the build appears to succeed (at least, it gives no errors and generates an .APK file) -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (CB-5950) Android build on Windows fails with spaces in \Program Files
[ https://issues.apache.org/jira/browse/CB-5950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13886818#comment-13886818 ] Jon Watte commented on CB-5950: --- I tracked this down, and the problem is actually in the latest Android SDK. The fix is in the Android SDK: At the bottom of platform-tools\18.0.1\dx.bat, change: call %java_exe% %javaOpts% -Djava.ext.dirs=%frameworkdir% -jar %jarpath% %params% to call %java_exe% %javaOpts% -Djava.ext.dirs=%frameworkdir% -jar %jarpath% %params% Android build on Windows fails with spaces in \Program Files -- Key: CB-5950 URL: https://issues.apache.org/jira/browse/CB-5950 Project: Apache Cordova Issue Type: Bug Components: Android Affects Versions: 3.3.0 Environment: Windows 8.1 Reporter: Jon Watte I downloaded and installed the latest nodejs for Windows (0.10.25,) latest JDK (1.7.0_51), latest Android SDK (19), and latest apache-ant (1.9.3) and created a new project as per the quickstart instructions. Creating the project and adding the android platform works fine. However, cordova build fails with an error: Generating config.xml from defaults for platform android Preparing android project Compiling app on platform android via command cmd /c C:\IMVU\example\example\platforms\android\cordova\build C:\Users\jwatte\AppData\Roaming\npm\node_modules\cordova\node_modules\q\q.js:126 throw e; ^ Error: An error occurred while building the android project.Error executing ant debug -f C:\IMVU\example\example\platforms\android\build.xml: BUILD FAILED C:\code\android-sdks\tools\ant\build.xml:892: The following error occurred while executing this line: C:\code\android-sdks\tools\ant\build.xml:894: The following error occurred while executing this line: C:\code\android-sdks\tools\ant\build.xml:906: The following error occurred while executing this line: C:\code\android-sdks\tools\ant\build.xml:284: null returned: 1 Total time: 3 seconds at ChildProcess.anonymous (C:\Users\jwatte\AppData\Roaming\npm\node_modules\cordova\src\compile.js:65:22) at ChildProcess.EventEmitter.emit (events.js:98:17) at maybeClose (child_process.js:743:16) at Socket.anonymous (child_process.js:956:11) at Socket.EventEmitter.emit (events.js:95:17) at Pipe.close (net.js:466:12) C:\IMVU\example\example Running the build file manually prints some more information; the error happens when trying to run dx and it claims C:\Program is not an internal or external command. There are many previous bugs about doesn't work with spaces in paths, so this seems like a regression. Spaces in paths are a fact of live on Windows, as is to dorky quoting rules for COMMAND.COM, so it would seem that a basic acceptance test that tests everything with the latest of all the dependencies on an otherwise fresh system should catch these things. If Windows is an important host for cordova developers, perhaps that would be a worthwhile investment? -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (CB-2332) Document new body property on FileTransferError
[ https://issues.apache.org/jira/browse/CB-2332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13886820#comment-13886820 ] Bas Bosman commented on CB-2332: Is this issue still relevant? The current [documentation|https://github.com/apache/cordova-plugin-file-transfer/blob/master/docs/filetransfererror/filetransfererror.md] no longer mentions the body property or Andrew's note. Document new body property on FileTransferError - Key: CB-2332 URL: https://issues.apache.org/jira/browse/CB-2332 Project: Apache Cordova Issue Type: Sub-task Components: Docs, Plugin File Transfer Affects Versions: 2.3.0, 2.4.0, 2.5.0, 2.6.0 Reporter: Filip Maj Assignee: Michael Brooks -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CB-1401) Add reset() (and other APIs) to Windows Phone Plugin documentation
[ https://issues.apache.org/jira/browse/CB-1401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bas Bosman updated CB-1401: --- Component/s: WP8 Add reset() (and other APIs) to Windows Phone Plugin documentation --- Key: CB-1401 URL: https://issues.apache.org/jira/browse/CB-1401 Project: Apache Cordova Issue Type: Sub-task Components: Docs, WP8 Reporter: Filip Maj Assignee: Jesse MacFadyen Make sure to update the documentation related to Plugin development to mention the {{reset}} API. Also, once-over the {{Command}} class and make sure we document other API methods available. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CB-5935) Deviceready Event Does Not Fire with PhoneGap/Cordova 3.3.0, iOS 7 Simulator
[ https://issues.apache.org/jira/browse/CB-5935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shazron Abdullah updated CB-5935: - Labels: core (was: ) Deviceready Event Does Not Fire with PhoneGap/Cordova 3.3.0, iOS 7 Simulator Key: CB-5935 URL: https://issues.apache.org/jira/browse/CB-5935 Project: Apache Cordova Issue Type: Bug Components: iOS Affects Versions: 3.3.0 Reporter: Ernst de Haan Labels: core Attachments: Screenshot 2014-01-29 14.33.11.png, Screenshot 2014-01-29 14.36.13.png Prerequisites: # Use Mac with OS X 10.9.1 # Use Xcode 5.0.2 Steps to reproduce: # {{sudo npm install -g phonegap}} (installs Phonegap) # {{sudo npm install -g cordova@3.3.0-0.1.1}} (picked same version as PhoneGap uses) # {{phonegap create foodscan nl.seriousrooster.foodscan FoodScan}} # {{cordova platform add ios}} # Open the _FoodScan_ Xcode project in Xcode. # Hit the triangular run button to start the simulator Expected results: # Build succeeds. # Simulator starts. # PhoneGap start page shows. # Device ready message is displayed very quickly. Actual results: # (/) Build succeeds. # (/) Simulator starts. # (/) PhoneGap start page shows. # (x) Message “Connecting to device” keeps flashing. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (CB-5721) App crashed if invoke root.getFile() and use ../resolve.file.uri as fileNames!
[ https://issues.apache.org/jira/browse/CB-5721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13886830#comment-13886830 ] Ian Clelland commented on CB-5721: -- I don't see the crashing bug right now, on the most recent version of file. The behaviour I do see definitely isn't correct, and I'm going to add tests to verify and fix that issue, but I don't get the {{NSInvalidArgumentException}}. Does this still happen for you on the latest dev branch code? (I'm on commit aa23cf4) App crashed if invoke root.getFile() and use ../resolve.file.uri as fileNames! Key: CB-5721 URL: https://issues.apache.org/jira/browse/CB-5721 Project: Apache Cordova Issue Type: Bug Components: iOS, mobile-spec, Plugin File Affects Versions: 3.2.0 Environment: cordova version: 3.3.1-0.1.2 Reporter: glmnbeyond Assignee: Ian Clelland Here are the steps to reproduce it: $ cordova create testFile $ cd testFile $ cordova platform add ios $ cordova platform plugin add 'cordova-plugin-file dev branch code' 1. Copy cordova-mobile-spec tests to testFile/platforms/ios/www/ 2. Modify file.tests.js file.spec.9, change fileName from resolve.file.uri to ../resolve.file.uri {color:red} var fileName = resolve.file.uri = var fileName = ../resolve.file.uri {color} 3. Run this test and app crashed! The outputs were shown as follows: Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: setObjectForKey: object cannot be nil (key: fullPath)' -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CB-5945) Navigator.notification.confirm crashes app
[ https://issues.apache.org/jira/browse/CB-5945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shazron Abdullah updated CB-5945: - Component/s: Plugin Dialogs Navigator.notification.confirm crashes app -- Key: CB-5945 URL: https://issues.apache.org/jira/browse/CB-5945 Project: Apache Cordova Issue Type: Bug Components: Plugin Dialogs, Windows 8 Affects Versions: 3.3.0 Reporter: Ismael Olusola Jimoh Assignee: Jesse MacFadyen Good Day All, I recently tested a code whereby I called navigator.notification.confirm on 2 pages. On the first page, I create an instance that triggers a navigator.notification.confirm query, accepting should launch the next page which also has a navigator.notification.confirm triggered from onDeviceReady. Once the second instance is triggered, app crashes and returns no error(or at least visible one). I am testing this on Windows 8 pro, PhoneGap 3.3 and I have all plugins needed installed. When I test this and have a button launch the same function on the second page, error doesn't occur. Find below sample code for said issue: Page 1: !DOCTYPE html html head titleNotification Example/title script type=text/javascript charset=utf-8 src=cordova.js/script script type=text/javascript charset=utf-8 // Wait for device API libraries to load // document.addEventListener(deviceready, onDeviceReady, false); // device APIs are available // function onDeviceReady() { // Empty } // process the confirmation dialog result function onConfirm(buttonIndex) { //alert('You selected button ' + buttonIndex); if(buttonIndex === 1){ window.open(page2.html,_self); } } // Show a custom confirmation dialog // function showConfirm() { navigator.notification.confirm( 'You are the winner!', // message onConfirm,// callback to invoke with index of button pressed 'Game Over', // title ['Restart','Exit'] // buttonLabels ); } /script /head body pa href=# onclick=showConfirm(); return false;Show Confirm/a/p /body /html Page 2: !DOCTYPE html html head titleNotification Example/title !--script type=text/javascript charset=utf-8 src=cordova.js/script-- script type=text/javascript charset=utf-8 // Wait for device API libraries to load // document.addEventListener(deviceready, onDeviceReady, false); // device APIs are available // function onDeviceReady() { // Empty showConfirm(); } // process the confirmation dialog result function onConfirm(buttonIndex) { //alert('You selected button ' + buttonIndex); if(buttonIndex === 1){ window.open(page2.html,_self); } } // Show a custom confirmation dialog // function showConfirm() { navigator.notification.confirm( 'You are the winner!', // message onConfirm,// callback to invoke with index of button pressed 'Game Over', // title ['Restart','Exit'] // buttonLabels ); } /script /head body pa href=# onclick=showConfirm(); return false;Show Confirm/a/p /body /html Thanks. Ismael -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (CB-2332) Document new body property on FileTransferError
[ https://issues.apache.org/jira/browse/CB-2332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13886848#comment-13886848 ] Shazron Abdullah commented on CB-2332: -- The body property was still there in the 2.8.0 docs. It was removed in 2.9.0 - not sure why. Document new body property on FileTransferError - Key: CB-2332 URL: https://issues.apache.org/jira/browse/CB-2332 Project: Apache Cordova Issue Type: Sub-task Components: Docs, Plugin File Transfer Affects Versions: 2.3.0, 2.4.0, 2.5.0, 2.6.0 Reporter: Filip Maj Assignee: Michael Brooks -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CB-2425) FileUploadOptions options structure not very clean, means you can't have a form field called 'header'
[ https://issues.apache.org/jira/browse/CB-2425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shazron Abdullah updated CB-2425: - Component/s: (was: Plugin File) Plugin File Transfer FileUploadOptions options structure not very clean, means you can't have a form field called 'header' - Key: CB-2425 URL: https://issues.apache.org/jira/browse/CB-2425 Project: Apache Cordova Issue Type: Improvement Components: Plugin File Transfer Affects Versions: 2.4.0 Environment: Using FileUpload to post a multi-part form to the server. Reporter: Thomas O'Dell Assignee: Joe Bowser Priority: Minor Labels: features Original Estimate: 48h Remaining Estimate: 48h The current design of FileUploadOptions is that the options is an object, whose fields represent the form fields. A special option 'headers' represents the headers to be uploaded. The format of the form fields is not compatible with JQuery and thus has to be massaged. As well, the design makes it impossible to have a form field called headers. I propose the following format for the Options object (25 = 2.5.0, i.e. first release to support api change): { 'apache-cordova-25-form-fields': [ {name: name, value: value}, ... ], // i.e. format returned by JQuery's serializeArray(formObject) 'apache-cordova-25-header-fields': [ {name: name, value: value}, ... ], 'apache-cordova-25-upload-options': [ {name: name, value: value}, // e.g. force chunked mode, set throttle speed ... ], old-style options and headers } -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Resolved] (CB-2903) Image in iOS Getting Started guide references incubator
[ https://issues.apache.org/jira/browse/CB-2903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bas Bosman resolved CB-2903. Resolution: Fixed Fix Version/s: 3.0.0 Image is no longer in use from the 3.0.0 release on. Image in iOS Getting Started guide references incubator - Key: CB-2903 URL: https://issues.apache.org/jira/browse/CB-2903 Project: Apache Cordova Issue Type: Bug Components: Docs Affects Versions: 2.5.0 Reporter: Tommy-Carlos Williams Assignee: Michael Brooks Fix For: 3.0.0 http://docs.phonegap.com/en/2.5.0/img/guide/getting-started/ios/bin_dir_listing.png -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (CB-2332) Document new body property on FileTransferError
[ https://issues.apache.org/jira/browse/CB-2332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13886868#comment-13886868 ] Shazron Abdullah commented on CB-2332: -- It exists: https://github.com/apache/cordova-docs/commit/29585ce7f395bf0e0f8f9ebd6a4aa7e87ba678a8 Something went wrong with a merge: 1. https://github.com/apache/cordova-docs/commits/2.8.0/docs/en/edge/cordova/file/filetransfererror 2. https://github.com/apache/cordova-docs/commits/2.9.0/docs/en/edge/cordova/file/filetransfererror In the 2.8.0 branch, the May 19th commit is there, but in 2.9.0 it is missing. We should re-add this. Document new body property on FileTransferError - Key: CB-2332 URL: https://issues.apache.org/jira/browse/CB-2332 Project: Apache Cordova Issue Type: Sub-task Components: Docs, Plugin File Transfer Affects Versions: 2.3.0, 2.4.0, 2.5.0, 2.6.0 Reporter: Filip Maj Assignee: Michael Brooks -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CB-1400) Add reset() (and other APIs) to BlackBerry Plugin documentation
[ https://issues.apache.org/jira/browse/CB-1400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bas Bosman updated CB-1400: --- Component/s: BlackBerry Add reset() (and other APIs) to BlackBerry Plugin documentation Key: CB-1400 URL: https://issues.apache.org/jira/browse/CB-1400 Project: Apache Cordova Issue Type: Sub-task Components: BlackBerry, Docs Reporter: Filip Maj Assignee: Lorin Beer Make sure to update the documentation related to Plugin development to mention the {{reset}} API. Also, once over the {{Plugin}} class and make sure we document other API methods available in there ({{isSynch}}, {{onPause}}, {{onResume}}). -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Resolved] (CB-2105) Mis-linked getting started guide for BlackBerry
[ https://issues.apache.org/jira/browse/CB-2105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bas Bosman resolved CB-2105. Resolution: Fixed This has since been fixed. The parent issue that contains this issue has also already been marked as Resolved. Mis-linked getting started guide for BlackBerry --- Key: CB-2105 URL: https://issues.apache.org/jira/browse/CB-2105 Project: Apache Cordova Issue Type: Bug Components: Docs Affects Versions: 2.3.0 Reporter: Tim Kim Assignee: Michael Brooks Priority: Trivial -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CB-1024) Capture API cancellation undefined
[ https://issues.apache.org/jira/browse/CB-1024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bas Bosman updated CB-1024: --- Component/s: Plugin Media Capture Capture API cancellation undefined -- Key: CB-1024 URL: https://issues.apache.org/jira/browse/CB-1024 Project: Apache Cordova Issue Type: Bug Components: Docs, Plugin Media Capture Affects Versions: 1.9.0, 2.0.0, 2.1.0, 2.2.0, 2.3.0, 2.4.0 Reporter: Jesse MacFadyen Assignee: Michael Brooks The documentation does not state what the result of a user-cancelled capture operation is. Therefore, implementations may vary ... When the user cancels the capture operation : - does the success callback get called? without MediaFiles? - does the error callback get called? with what error code? -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CB-2495) File API master heading gets confused with File API's File Ojbect
[ https://issues.apache.org/jira/browse/CB-2495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bas Bosman updated CB-2495: --- Component/s: Plugin File File API master heading gets confused with File API's File Ojbect - Key: CB-2495 URL: https://issues.apache.org/jira/browse/CB-2495 Project: Apache Cordova Issue Type: Bug Components: Docs, Plugin File Affects Versions: 2.4.0 Reporter: Filip Maj Assignee: Michael Brooks There is a File object that is part of the File API. The generated documentation's hyperlinks, however, always point to the top-level API, not this API's File object. Confused yet? Repro steps: 1. click here http://docs.phonegap.com/en/2.4.0/cordova_file_file.md.html 2. In the Objects list at the top, click the third item (File). Expected result: page jumps to the first sub-section that describes the File object Actual result: page stays at the top of the File API index page -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CB-3286) FileReader docs incorrect (for failure callbacks)
[ https://issues.apache.org/jira/browse/CB-3286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bas Bosman updated CB-3286: --- Component/s: Plugin File FileReader docs incorrect (for failure callbacks) - Key: CB-3286 URL: https://issues.apache.org/jira/browse/CB-3286 Project: Apache Cordova Issue Type: Bug Components: Docs, Plugin File Reporter: Shazron Abdullah Assignee: Michael Brooks See: http://docs.cordova.io/en/2.6.0/cordova_file_file.md.html#FileReader Notice there are two Quick Examples with this code, which will throw an exception: {code} var fail = function(evt) { console.log(error.code); }; {code} *Expected:* {code} var fail = function(evt) { console.log(evt.target); // evt.target is the FileReader object }; {code} *Actual:* {code} var fail = function(evt) { console.log(error.code); }; {code} -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Resolved] (CB-5782) Catch exceptions and print nice error when cordova-cli run from a non cordova project.
[ https://issues.apache.org/jira/browse/CB-5782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Koudritsky resolved CB-5782. - Resolution: Fixed Catch exceptions and print nice error when cordova-cli run from a non cordova project. -- Key: CB-5782 URL: https://issues.apache.org/jira/browse/CB-5782 Project: Apache Cordova Issue Type: Bug Components: CLI Reporter: Michal Mocny Assignee: Mark Koudritsky Priority: Minor cordova prepare prints scary stack trace when run from the wrong directory. This is likely a common error and we should make it clear what is happening. Seems we are already catching the case, just failing to report it gracefully: throw new Error('Current working directory is not a Cordova-based -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Resolved] (CB-5006) Allow installing plugins by ID to resolve to local plugin directories
[ https://issues.apache.org/jira/browse/CB-5006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Koudritsky resolved CB-5006. - Resolution: Fixed Allow installing plugins by ID to resolve to local plugin directories - Key: CB-5006 URL: https://issues.apache.org/jira/browse/CB-5006 Project: Apache Cordova Issue Type: Bug Components: Plugman Reporter: Andrew Grieve Assignee: Mark Koudritsky Priority: Minor ML: http://markmail.org/thread/3w77elhdnidcdyxq Instead of always hitting the registry when installing a plugin by ID, first see if it exists within the plugin search path. The plugin search path should be specified in the same way as other plugman registry settings: https://git-wip-us.apache.org/repos/asf?p=cordova-plugman.git;a=blob;f=src/registry/registry.js;h=ccdd45ab672abe99a731b9fe0aed8837db40d6f0;hb=f240acc532f93bdf16761836d9b7418373afebec#l239 The search path should point to directories that contain directories that contain plugin.xml files. E.g., on start-up, plugman will need to scan on level deep in all search paths for plugin.xml files and parse out their IDs. We should be sure to have a console message upon installation that says where plugins are being installed from. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (CB-5202) Android Video Capture crashes app on 4.3
[ https://issues.apache.org/jira/browse/CB-5202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13886908#comment-13886908 ] Mike Billau commented on CB-5202: - I implemented a stripped down version of the pull request and it works great to fix the issue with 4.3. https://github.com/mbillau/cordova-plugin-media-capture/commit/8edfa3aea2906cd904ebc881cc822c14b8186411 Should I make a PR? If the original fix is from lubogospod do we first have to make sure he or she has signed the CLA? Android Video Capture crashes app on 4.3 Key: CB-5202 URL: https://issues.apache.org/jira/browse/CB-5202 Project: Apache Cordova Issue Type: Bug Components: Android, Plugin Media Capture Affects Versions: 3.0.0 Environment: Android 4.3 Reporter: Tom Saunders Assignee: Andrew Grieve Using the cordova video capture plugin crashes the application when returning from the capture video intent. No data is returned. This is a known issue with Android 4.3, the workaround is to explicitly specify a location for saving the video Relevant stackoverflows: http://stackoverflow.com/questions/18472953/video-capture-in-android-4-3-using-camera-app-intent http://stackoverflow.com/questions/18120775/android-android-provider-mediastore-action-video-capture-return-null-onactivityr -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Resolved] (CB-3412) Android CordovaWebView references deprecated XMLs
[ https://issues.apache.org/jira/browse/CB-3412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bas Bosman resolved CB-3412. Resolution: Fixed Fix Version/s: 3.0.0 This is no longer present in the 3.x.x documentation. Fixed by CB-3824. Android CordovaWebView references deprecated XMLs - Key: CB-3412 URL: https://issues.apache.org/jira/browse/CB-3412 Project: Apache Cordova Issue Type: Bug Components: Docs Affects Versions: 2.0.0, 2.1.0, 2.2.0, 2.3.0, 2.4.0, 2.5.0, 2.6.0, 2.7.0, 2.8.0 Reporter: Kuan Yi Ming Assignee: Michael Brooks Fix For: 3.0.0 Taken from guide/cordova-webview/android.md 7. Copy `cordova.xml` and `plugins.xml` from `/framework/res/xml` to the `/res/xml` folder in your project Both cordova.xml and plugins.xml have been deprecated and replaced by config.xml as of 2.0.0. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Resolved] (CB-3847) Weird text characters on Blackberry 10 documentation page
[ https://issues.apache.org/jira/browse/CB-3847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bas Bosman resolved CB-3847. Resolution: Fixed Fix Version/s: 2.9.0 Looks to be fixed in the 2.9.0 docs Weird text characters on Blackberry 10 documentation page - Key: CB-3847 URL: https://issues.apache.org/jira/browse/CB-3847 Project: Apache Cordova Issue Type: Bug Components: Docs Affects Versions: 2.8.0 Environment: Tested in the latest firefox and chrome on mac os x Reporter: jon campbell Assignee: Michael Brooks Priority: Trivial Fix For: 2.9.0 http://docs.phonegap.com/en/2.8.0/guide_getting-started_blackberry10_index.md.html#Getting%20Started%20with%20BlackBerry%2010 -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CB-4089) Undocumented API rule? Passing invalid option values uses default value instead.
[ https://issues.apache.org/jira/browse/CB-4089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bas Bosman updated CB-4089: --- Component/s: Plugin Globalization Undocumented API rule? Passing invalid option values uses default value instead. Key: CB-4089 URL: https://issues.apache.org/jira/browse/CB-4089 Project: Apache Cordova Issue Type: Improvement Components: Docs, Plugin Globalization Affects Versions: 2.7.0 Reporter: Peter Assignee: Michael Brooks Priority: Minor It looks like there is some undocumented rule such that if an _invalid_ option value is passed via a Cordova API then the _default_ value will be used instead. For example, the following calls are all equaivalent: {code} navigator.globalization.dateToString(new Date(), win, fail, {selector: 'banana'}) navigator.globalization.dateToString(new Date(), win, fail, {selector: 'date and time'}) navigator.globalization.dateToString(new Date(), win, fail, {}) {code} I had (wrongly) expected 'banana' would result in some kind of API error since it is not a supported value for the selector. This undocumented API rule should be documented. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CB-1371) Allow video file to be saved to iPhone Camera Roll after recording
[ https://issues.apache.org/jira/browse/CB-1371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bas Bosman updated CB-1371: --- Component/s: (was: CordovaJS) Plugin Media Capture Allow video file to be saved to iPhone Camera Roll after recording -- Key: CB-1371 URL: https://issues.apache.org/jira/browse/CB-1371 Project: Apache Cordova Issue Type: Wish Components: iOS, Plugin Media Capture Reporter: Nick Gottlieb Assignee: Filip Maj Priority: Minor Labels: audit It would be nice if we could take the video file after recording and upload to our server as well as save it to the device (so that if the upload is interrupted we can retain the video file). -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CB-3777) Implement FileWriter.write(Blob|ArrayBuffer) on Windows Phone
[ https://issues.apache.org/jira/browse/CB-3777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bas Bosman updated CB-3777: --- Component/s: Plugin File Implement FileWriter.write(Blob|ArrayBuffer) on Windows Phone - Key: CB-3777 URL: https://issues.apache.org/jira/browse/CB-3777 Project: Apache Cordova Issue Type: Sub-task Components: Plugin File, Windows 8, WP7, WP8 Reporter: Ian Clelland -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CB-4263) The FileReader readyState is not working as expected (value in onload for readAsText)
[ https://issues.apache.org/jira/browse/CB-4263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bas Bosman updated CB-4263: --- Component/s: Plugin File The FileReader readyState is not working as expected (value in onload for readAsText) - Key: CB-4263 URL: https://issues.apache.org/jira/browse/CB-4263 Project: Apache Cordova Issue Type: Bug Components: CordovaJS, Plugin File Affects Versions: 2.9.0 Environment: Gingerbread emulator Reporter: Peter Assignee: Filip Maj Priority: Minor _onload_ is called when readAsText was successful, so the readyState should be FileReader.DONE. See http://www.w3.org/TR/FileAPI/#blobreader-state But it is still set as FileReader.LOADING. Looking at the v2.9.0 cordova.js code you can see that the setting of the readyState for _readAsText_ is inconsistent with all the other read methods. i.e. {code} // If onload callback if (typeof me.onload === function) { me.onload(new ProgressEvent(load, {target:me})); } // DONE state me._readyState = FileReader.DONE; {code} It looks like that DONE state should be set *before* the onload invocation. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CB-4278) FileReader result unexpected initial value
[ https://issues.apache.org/jira/browse/CB-4278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bas Bosman updated CB-4278: --- Component/s: Plugin File FileReader result unexpected initial value -- Key: CB-4278 URL: https://issues.apache.org/jira/browse/CB-4278 Project: Apache Cordova Issue Type: Bug Components: CordovaJS, Plugin File Affects Versions: 2.9.0 Environment: Gingerbread emulator Reporter: Peter Assignee: Filip Maj Priority: Minor Expected the intitial value of FileReader result should be null as per the description in the standard http://www.w3.org/TR/FileAPI/#dfn-result which says: On getting, if the readyState is EMPTY (no read method has been called) then the result attribute must return null. My following Jasmine test fragment fails: {code} it(fr.result initial value, function() { var theReader = new FileReader(); expect(theReader.result).toBe(null); }); {code} -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CB-4266) Qt is not Quick Time
[ https://issues.apache.org/jira/browse/CB-4266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bas Bosman updated CB-4266: --- Priority: Minor (was: Major) Qt is not Quick Time Key: CB-4266 URL: https://issues.apache.org/jira/browse/CB-4266 Project: Apache Cordova Issue Type: Improvement Components: Docs, Qt, Website Affects Versions: 2.9.0 Reporter: Illya Kovalevskyy Assignee: Michael Brooks Priority: Minor Attachments: website-qt.jpg Original Estimate: 0.25h Remaining Estimate: 0.25h Come, on! Qt is not Quick Time (QT), that's why you can't use QT abbr. for it - use Qt instead. Just Qt. Not QT. Thank you -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Resolved] (CB-4386) iOS Platform Guide CLI example uses 'android'
[ https://issues.apache.org/jira/browse/CB-4386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bas Bosman resolved CB-4386. Resolution: Fixed iOS Platform Guide CLI example uses 'android' - Key: CB-4386 URL: https://issues.apache.org/jira/browse/CB-4386 Project: Apache Cordova Issue Type: Bug Components: Docs Affects Versions: 3.0.0 Reporter: Bruce Lefebvre Assignee: Lisa Seacat DeLuca Priority: Trivial At [0], (Open a Project in the SDK section): $ cordova platform add android Should be: $ cordova platform add ios [0] http://docs.phonegap.com/en/3.0.0/guide_platforms_ios_index.md.html#iOS%20Platform%20Guide_open_a_project_in_the_sdk -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Resolved] (CB-4384) API Docs all describe use of plugin element
[ https://issues.apache.org/jira/browse/CB-4384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bas Bosman resolved CB-4384. Resolution: Fixed API Docs all describe use of plugin element -- Key: CB-4384 URL: https://issues.apache.org/jira/browse/CB-4384 Project: Apache Cordova Issue Type: Bug Components: Docs Affects Versions: 3.0.0 Reporter: Lorin Beer Assignee: Michael Brooks The API documentation describes use of the deprecated plugin element in config.xml. This has been deprecated since 2.5.0 Documentation should be updated to describe the feature element. Affected api docs: Accelerometer Camera Capture Compass Connection Contacts Device Events File Geolocation Globalization InAppBrowser Media Notification Splashscreen Storage --crossoff completed items-- -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Resolved] (CB-4522) accept Https hosts
[ https://issues.apache.org/jira/browse/CB-4522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bas Bosman resolved CB-4522. Resolution: Not A Problem This is more of a support question than a Cordova issue. This issue tracker is meant to be used for bugs and feature requests for the Cordova projects. Support questions should be directed elsewhere. accept Https hosts --- Key: CB-4522 URL: https://issues.apache.org/jira/browse/CB-4522 Project: Apache Cordova Issue Type: Task Components: WP7, WP8 Affects Versions: 3.0.0 Reporter: El farouk mokrani Assignee: Jesse MacFadyen Labels: ajax, https, wp7, wp8 Hi i'm used allowsAnyHTTPSCertificateForHost in ios to accept Https hosts how to accept Https in WP ? thanks -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Resolved] (CB-5950) Android build on Windows fails with spaces in \Program Files
[ https://issues.apache.org/jira/browse/CB-5950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bas Bosman resolved CB-5950. Resolution: Not A Problem Try upgrading your Platform Tools. I'm running a similar setup as you, without any problems, using Platform Tools version 19.0.1. (That versions dx.bat contains your fix.) Closing as Not a Problem, as it isn't a Cordova specific issue. Android build on Windows fails with spaces in \Program Files -- Key: CB-5950 URL: https://issues.apache.org/jira/browse/CB-5950 Project: Apache Cordova Issue Type: Bug Components: Android Affects Versions: 3.3.0 Environment: Windows 8.1 Reporter: Jon Watte I downloaded and installed the latest nodejs for Windows (0.10.25,) latest JDK (1.7.0_51), latest Android SDK (19), and latest apache-ant (1.9.3) and created a new project as per the quickstart instructions. Creating the project and adding the android platform works fine. However, cordova build fails with an error: Generating config.xml from defaults for platform android Preparing android project Compiling app on platform android via command cmd /c C:\IMVU\example\example\platforms\android\cordova\build C:\Users\jwatte\AppData\Roaming\npm\node_modules\cordova\node_modules\q\q.js:126 throw e; ^ Error: An error occurred while building the android project.Error executing ant debug -f C:\IMVU\example\example\platforms\android\build.xml: BUILD FAILED C:\code\android-sdks\tools\ant\build.xml:892: The following error occurred while executing this line: C:\code\android-sdks\tools\ant\build.xml:894: The following error occurred while executing this line: C:\code\android-sdks\tools\ant\build.xml:906: The following error occurred while executing this line: C:\code\android-sdks\tools\ant\build.xml:284: null returned: 1 Total time: 3 seconds at ChildProcess.anonymous (C:\Users\jwatte\AppData\Roaming\npm\node_modules\cordova\src\compile.js:65:22) at ChildProcess.EventEmitter.emit (events.js:98:17) at maybeClose (child_process.js:743:16) at Socket.anonymous (child_process.js:956:11) at Socket.EventEmitter.emit (events.js:95:17) at Pipe.close (net.js:466:12) C:\IMVU\example\example Running the build file manually prints some more information; the error happens when trying to run dx and it claims C:\Program is not an internal or external command. There are many previous bugs about doesn't work with spaces in paths, so this seems like a regression. Spaces in paths are a fact of live on Windows, as is to dorky quoting rules for COMMAND.COM, so it would seem that a basic acceptance test that tests everything with the latest of all the dependencies on an otherwise fresh system should catch these things. If Windows is an important host for cordova developers, perhaps that would be a worthwhile investment? -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CB-4541) MediaFile.getFormatData throws a MediaPlayer IOException but returns callback success for a video
[ https://issues.apache.org/jira/browse/CB-4541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bas Bosman updated CB-4541: --- Component/s: Plugin Media Capture MediaFile.getFormatData throws a MediaPlayer IOException but returns callback success for a video - Key: CB-4541 URL: https://issues.apache.org/jira/browse/CB-4541 Project: Apache Cordova Issue Type: Bug Components: Android, Plugin Media Capture Affects Versions: 2.9.0 Environment: Galaxy GT-I9000 Gingerbread 2.3.6 Reporter: Angela Fowler Assignee: Joe Bowser Priority: Minor Here is the initial MediaFile success callback S01 Capture1970865120 [{lastModifiedDate:1375937605000,fullPath:file:\/\/\/mnt\/sdcard\/DCIM\/Camera\/video-2013-08-08-14-53-17.mp4,type:video\/mp4,size:1824506,name:video-2013-08-08-14-53-17.mp4}] Then try to get the format information about the media file using mediaFile.getFormatData(getFormatDataWin, getFormatDataError); In Capture.java getAudioVideoData an exception is thrown by mediaplayer.prepare() java.io.IOException: Prepare failed.: status=0xFFFC The error is logged but ignored. Error: loading video file The Capture.java execute method calls success on the callback context. Here is the getFormatData success callback message S01 Capture1970865121 {codecs:,bitrate:0,duration:0,height:0,width:0} Error callback is never returned for action getFormatData. Also what happens if another exception which is not caught is thrown? e.g. IllegalStateException It appears that no callback would be made in this case. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CB-4569) Upgrading Guides link broken on Cordova 3 release page.
[ https://issues.apache.org/jira/browse/CB-4569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bas Bosman updated CB-4569: --- Component/s: (was: Docs) Website Upgrading Guides link broken on Cordova 3 release page. --- Key: CB-4569 URL: https://issues.apache.org/jira/browse/CB-4569 Project: Apache Cordova Issue Type: Bug Components: Website Environment: Google Chrome, Mozilla FireFox Reporter: Venkata Kiran Assignee: Michael Brooks Priority: Trivial In the below page, the link to upgrading guides in 'Upgrading' section is broken. http://cordova.apache.org/blog/releases/2013/07/23/cordova-3.html It is returning 404 Not Found Page. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CB-4614) Contact.save and Contact.remove - method signatures not documented
[ https://issues.apache.org/jira/browse/CB-4614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bas Bosman updated CB-4614: --- Component/s: Plugin Contacts Contact.save and Contact.remove - method signatures not documented -- Key: CB-4614 URL: https://issues.apache.org/jira/browse/CB-4614 Project: Apache Cordova Issue Type: Improvement Components: Docs, Plugin Contacts Affects Versions: 2.9.0 Reporter: Peter Assignee: Michael Brooks Priority: Minor The method signatures for Contact methods *save* and *remove* are not documented. Only in the examples can you see that they have parameters for onSuccess and onError callbacks. Ref http://cordova.apache.org/docs/en/2.9.0/cordova_contacts_contacts.md.html#Contact -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CB-4612) ContactName is not supported on Android 4.X?
[ https://issues.apache.org/jira/browse/CB-4612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bas Bosman updated CB-4612: --- Component/s: Plugin Contacts ContactName is not supported on Android 4.X? Key: CB-4612 URL: https://issues.apache.org/jira/browse/CB-4612 Project: Apache Cordova Issue Type: Bug Components: Android, Docs, Plugin Contacts Affects Versions: 2.9.0 Environment: Android 4.X Reporter: Shingo Toda Assignee: Joe Bowser Priority: Minor Labels: documentation Document says ContactName is supported on Android 2.X (see [http://cordova.apache.org/docs/en/2.9.0/cordova_contacts_contacts.md.html#ContactName]). But mobile-spec tests regarding to this property are passed on Android 4.2.2 emulator. What is not supported on this object? Or is this just a wrong documentation? -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CB-4611) ContactField pref property returns true in Android
[ https://issues.apache.org/jira/browse/CB-4611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bas Bosman updated CB-4611: --- Component/s: Plugin Contacts ContactField pref property returns true in Android -- Key: CB-4611 URL: https://issues.apache.org/jira/browse/CB-4611 Project: Apache Cordova Issue Type: Bug Components: Docs, Plugin Contacts Affects Versions: 2.9.0 Environment: Android 4.2 emulator Reporter: Shingo Toda Assignee: Michael Brooks Priority: Minor Labels: documentation I am looking into mobile-spec. [This document|http://cordova.apache.org/docs/en/2.9.0/cordova_contacts_contacts.md.html#ContactField] says {quote} *Android Quirks* pref: Not supported, returning false. {quote} But spec contacts.spec.11 should be able to define a ContactField object in contacts.tests.js(239) is passed, which pref is set to true. See the following. {code:title=www/autotest/tests/contacts.tests.js|borderStyle=solid} it(contacts.spec.11 should be able to define a ContactField object, function() { var contactField = new ContactField(home, 8005551212, true); expect(contactField).toBeDefined(); expect(contactField.type).toBe(home); expect(contactField.value).toBe(8005551212); expect(contactField.pref).toBe(true); }); {code} Is pref property not really supported? -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CB-4627) Incorrect code for DirectoryEntry.removeRecursively example?
[ https://issues.apache.org/jira/browse/CB-4627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bas Bosman updated CB-4627: --- Component/s: Plugin File Incorrect code for DirectoryEntry.removeRecursively example? Key: CB-4627 URL: https://issues.apache.org/jira/browse/CB-4627 Project: Apache Cordova Issue Type: Bug Components: Docs, Plugin File Affects Versions: 2.9.0 Reporter: Peter Assignee: Michael Brooks Priority: Trivial The File API guide for the DirectoryEntry.removeRecursively method says *successCallback* method is _Invoked with no parameters_ , yet the Quick Example code in the guide shows a parameter: {code} function success(parent) { console.log(Remove Recursively Succeeded); } {code} Ref: http://cordova.apache.org/docs/en/2.9.0/cordova_file_file.md.html#DirectoryEntry -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CB-4628) Incorrect code for FileEntry.remove example?
[ https://issues.apache.org/jira/browse/CB-4628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bas Bosman updated CB-4628: --- Component/s: Plugin File Incorrect code for FileEntry.remove example? Key: CB-4628 URL: https://issues.apache.org/jira/browse/CB-4628 Project: Apache Cordova Issue Type: Bug Components: Docs, Plugin File Affects Versions: 2.9.0 Reporter: Peter Assignee: Michael Brooks Priority: Trivial The File API guide for the FileEntry.remove method says *successCallback* method is _Invoked with no parameters_ , yet the Quick Example code in the guide shows a parameter: {code} function success(entry) { console.log(Removal succeeded); } {code} Ref: http://cordova.apache.org/docs/en/2.9.0/cordova_file_file.md.html#FileEntry See also CB-4626, CB-4627 -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CB-4626) Incorrect code for DirectoryEntry.remove example?
[ https://issues.apache.org/jira/browse/CB-4626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bas Bosman updated CB-4626: --- Component/s: Plugin File Incorrect code for DirectoryEntry.remove example? -- Key: CB-4626 URL: https://issues.apache.org/jira/browse/CB-4626 Project: Apache Cordova Issue Type: Bug Components: Docs, Plugin File Affects Versions: 2.9.0 Reporter: Peter Assignee: Michael Brooks Priority: Trivial The File API guide for the DirectoryEntry.remove method says *successCallback* method is _Invoked with no parameters._ , yet the Quick Example code in the guide shows a parameter: {code} function success(entry) { console.log(Removal succeeded); } {code} Ref: http://cordova.apache.org/docs/en/2.9.0/cordova_file_file.md.html#DirectoryEntry -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CB-4636) Constructor of Contact should be documented.
[ https://issues.apache.org/jira/browse/CB-4636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bas Bosman updated CB-4636: --- Component/s: Plugin Contacts Constructor of Contact should be documented. Key: CB-4636 URL: https://issues.apache.org/jira/browse/CB-4636 Project: Apache Cordova Issue Type: Improvement Components: Docs, Plugin Contacts Affects Versions: 2.9.0 Reporter: Shingo Toda Assignee: Michael Brooks Priority: Minor Constructor method of Contact is not documented but is exposed in user code. It should be documented, which will help users a lot. {code} /** * Contains information about a single contact. * @constructor * @param {DOMString} id unique identifier * @param {DOMString} displayName * @param {ContactName} name * @param {DOMString} nickname * @param {Array.ContactField} phoneNumbers array of phone numbers * @param {Array.ContactField} emails array of email addresses * @param {Array.ContactAddress} addresses array of addresses * @param {Array.ContactField} ims instant messaging user ids * @param {Array.ContactOrganization} organizations * @param {DOMString} birthday contact's birthday * @param {DOMString} note user notes about contact * @param {Array.ContactField} photos * @param {Array.ContactField} categories * @param {Array.ContactField} urls contact's web sites */ var Contact = function (id, displayName, name, nickname, phoneNumbers, emails, addresses, ims, organizations, birthday, note, photos, categories, urls) {code} -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CB-4631) MEDIA_ERR_NONE_ACTIVE is not in the document
[ https://issues.apache.org/jira/browse/CB-4631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bas Bosman updated CB-4631: --- Component/s: Plugin Media MEDIA_ERR_NONE_ACTIVE is not in the document Key: CB-4631 URL: https://issues.apache.org/jira/browse/CB-4631 Project: Apache Cordova Issue Type: Bug Components: Docs, Plugin Media Affects Versions: 2.9.0 Reporter: Shingo Toda Assignee: Michael Brooks Priority: Minor MEDIA_ERR_NONE_ACTIVE is exposed in user code but not in the documentation. This can be thrown into {{mediaError}} callback if {{media.pause()}} or {{media.stop()}} get sequentially called or if they are called before media starts. This should be explained in Media document. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CB-4637) Constructor of ContactName should be documented.
[ https://issues.apache.org/jira/browse/CB-4637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bas Bosman updated CB-4637: --- Component/s: Plugin Contacts Constructor of ContactName should be documented. Key: CB-4637 URL: https://issues.apache.org/jira/browse/CB-4637 Project: Apache Cordova Issue Type: Improvement Components: Docs, Plugin Contacts Affects Versions: 2.9.0 Reporter: Shingo Toda Assignee: Michael Brooks Priority: Minor Constructor method of ContactName is not documented but is exposed in user code. It should be documented, which will help users a lot. {code} /** * Contact name. * @constructor * @param formatted // NOTE: not part of W3C standard * @param familyName * @param givenName * @param middle * @param prefix * @param suffix */ var ContactName = function(formatted, familyName, givenName, middle, prefix, suffix) {code} -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CB-4638) Constructor of ContactField should be documented.
[ https://issues.apache.org/jira/browse/CB-4638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bas Bosman updated CB-4638: --- Component/s: Plugin Contacts Constructor of ContactField should be documented. - Key: CB-4638 URL: https://issues.apache.org/jira/browse/CB-4638 Project: Apache Cordova Issue Type: Improvement Components: Docs, Plugin Contacts Reporter: Shingo Toda Assignee: Michael Brooks Priority: Minor Constructor of ContactField is not documented but is exposed in user code. It should be documented, which will help users a lot. {code} /** * Generic contact field. * @constructor * @param {DOMString} id unique identifier, should only be set by native code // NOTE: not a W3C standard * @param type * @param value * @param pref */ var ContactField = function(type, value, pref) {code} -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CB-4640) Constructor of ContactOrganization should be documented.
[ https://issues.apache.org/jira/browse/CB-4640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bas Bosman updated CB-4640: --- Component/s: Plugin Contacts Constructor of ContactOrganization should be documented. Key: CB-4640 URL: https://issues.apache.org/jira/browse/CB-4640 Project: Apache Cordova Issue Type: Improvement Components: Docs, Plugin Contacts Affects Versions: 2.9.0 Reporter: Shingo Toda Assignee: Michael Brooks Priority: Minor Constructor method of ContactOrganization is not documented but is exposed in user code. It should be documented, which will help users a lot. {code} /** * Contact organization. * @constructor * @param {DOMString} id unique identifier, should only be set by native code // NOTE: not a W3C standard * @param name * @param dept * @param title * @param startDate * @param endDate * @param location * @param desc */ var ContactOrganization = function(pref, type, name, dept, title) {code} -- This message was sent by Atlassian JIRA (v6.1.5#6160)