[jira] [Commented] (CB-6441) Plugin frameworks not always included
[ https://issues.apache.org/jira/browse/CB-6441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13982774#comment-13982774 ] Adam George commented on CB-6441: - This issue also happens if you remove the iOS platform and then re-add it in. I.e. cordova platform add ios cordova plugin add com.phonegap.plugins.barcodescanner cordova platform remove ios cordova platform add ios The frameworks required for barcode scanner will be missing after re-adding the ios platform. Unfortunately, removing then adding the platform is something that needs to be done quite often with cordova. The `cordova platform update ios` command doesn't do a great job, and you're often better off removing the platform and adding it back again. Plugin frameworks not always included - Key: CB-6441 URL: https://issues.apache.org/jira/browse/CB-6441 Project: Apache Cordova Issue Type: Bug Components: CLI, Plugman Affects Versions: 3.4.0 Environment: iOS Reporter: Dooms Assignee: Anis Kadri Priority: Minor Several plugins specify frameworks in ios (e.g. NetworkInformation requires SystemConfiguration.framework). However these aren't always added automatically, and must be added manually. This seems to happen especially during a plugin update. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6423) (iOS) cordova.js: iOSExec() not working after upgrading from Cordova 3.0 to 3.4
[
https://issues.apache.org/jira/browse/CB-6423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13982793#comment-13982793
]
Christophe Decaux commented on CB-6423:
---
I get this issue too.
Symptom for me is that I get this during app startup:
[Error] TypeError: 'null' is not an object (evaluating
'document.body.appendChild')
createExecIframe (cordova.js, line 833)
iOSExec (cordova.js, line 1009)
getInfo (network.js, line 46)
(fonction anonyme) (network.js, line 57)
fire (cordova.js, line 750)
(fonction anonyme) (cordova.js, line 1195)
f (cordova.js, line 622)
fire (cordova.js, line 750)
(fonction anonyme) (cordova.js, line 1183)
onScriptLoadingComplete (cordova.js, line 1369)
scriptLoadedCallback (cordova.js, line 1386)
And 5 seconds later a message telling me that deviceready didn't complete
I'm seeing too this behavior on all iOS simulator platform/OS combinations
And like Joel, if I force bridgeMode to jsToNativeModes.XHR_NO_PAYLOAD,
everything is fine
(iOS) cordova.js: iOSExec() not working after upgrading from Cordova 3.0 to
3.4
---
Key: CB-6423
URL: https://issues.apache.org/jira/browse/CB-6423
Project: Apache Cordova
Issue Type: Bug
Components: CordovaJS, iOS
Affects Versions: 3.4.0
Reporter: Joel Rubio
Labels: cordovajs, ios, upgrade
Hi there,
I recently upgraded my working PhoneGap app from 3.0 to 3.4. In iOS, the app
wouldn't go past the splashscreen. It would get stuck while trying to fetch a
local file (in file:/// dir) through an XHR.
I managed to trace the problem to the iOSExec function in cordova.js. Before
the upgrade, it would determine bridgeMode the following way:
bridgeMode = navigator.userAgent.indexOf(' 4_') == -1 ?
jsToNativeModes.XHR_NO_PAYLOAD : jsToNativeModes.IFRAME_NAV;
In cordova.js 3.4 it is determined the following way:
bridgeMode = navigator.userAgent.indexOf(' 5_') == -1 ?
jsToNativeModes.IFRAME_NAV: jsToNativeModes.XHR_NO_PAYLOAD;
Notice the switch in the expressions.
This led to any iOS device with a version other than 5 not working. Using the
jsToNativeModes.IFRAME_NAV bridgeMode would lead to the default case in the
subsequent switch statement in which it determines what to do according to
the bridgeMode.
switch (bridgeMode) {
case jsToNativeModes.XHR_NO_PAYLOAD:
case jsToNativeModes.XHR_WITH_PAYLOAD:
case jsToNativeModes.XHR_OPTIONAL_PAYLOAD:
// This prevents sending an XHR when there is already one being
sent.
// This should happen only in rare circumstances (refer to unit
tests).
if (execXhr execXhr.readyState != 4) {
execXhr = null;
}
// Re-using the XHR improves exec() performance by about 10%.
execXhr = execXhr || new XMLHttpRequest();
// Changing this to a GET will make the XHR reach the URIProtocol
on 4.2.
// For some reason it still doesn't work though...
// Add a timestamp to the query param to prevent caching.
execXhr.open('HEAD', /!gap_exec? + (+new Date()), true);
if (!vcHeaderValue) {
vcHeaderValue = /.*\((.*)\)/.exec(navigator.userAgent)[1];
}
execXhr.setRequestHeader('vc', vcHeaderValue);
execXhr.setRequestHeader('rc', ++requestCount);
if (shouldBundleCommandJson()) {
execXhr.setRequestHeader('cmds',
iOSExec.nativeFetchMessages());
}
execXhr.send(null);
break;
case jsToNativeModes.IFRAME_HASH_NO_PAYLOAD:
case jsToNativeModes.IFRAME_HASH_WITH_PAYLOAD:
execHashIframe = execHashIframe || createHashIframe();
// Check if they've removed it from the DOM, and put it back if
so.
if (!execHashIframe.contentWindow) {
execHashIframe = createHashIframe();
}
// The delegate method is called only when the hash changes, so
toggle it back and forth.
hashToggle = hashToggle ^ 3;
var hashValue = '%0' + hashToggle;
if (bridgeMode === jsToNativeModes.IFRAME_HASH_WITH_PAYLOAD) {
hashValue += iOSExec.nativeFetchMessages();
}
execHashIframe.contentWindow.location.hash = hashValue;
break;
default:
execIframe = execIframe || createExecIframe();
// Check if they've removed it from the DOM, and put it back if
so.
if (!execIframe.contentWindow) {
execIframe = createExecIframe();
}
execIframe.src =
[jira] [Commented] (CB-6530) Plugins docs for v3.4 not working
[ https://issues.apache.org/jira/browse/CB-6530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13982865#comment-13982865 ] Venkata Kiran commented on CB-6530: --- I was about to report another issue bit this seemed similar. When I clicked on any plugin links on the below, I am getting a 404 page. http://cordova.apache.org/docs/en/3.4.0/cordova_plugins_pluginapis.md.html#Plugin%20APIs Looks like the inidividual plugin pages are changed to a different location. Plugins docs for v3.4 not working - Key: CB-6530 URL: https://issues.apache.org/jira/browse/CB-6530 Project: Apache Cordova Issue Type: Bug Components: Docs Affects Versions: 3.4.0 Reporter: Andrey Kurdyumov After moving plugin development to master branch, documentation for plugins no longer working. Urls pointed to https://github.com/apache/cordova-plugin-battery-status/blob/dev/doc/index.md and shoult to https://github.com/apache/cordova-plugin-battery-status/blob/master/doc/index.md -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CB-6533) Windows 8 unable to create directory where users can see files
brian johnston created CB-6533: -- Summary: Windows 8 unable to create directory where users can see files Key: CB-6533 URL: https://issues.apache.org/jira/browse/CB-6533 Project: Apache Cordova Issue Type: Bug Components: Plugin File, WP8 Affects Versions: 3.3.0 Reporter: brian johnston Assignee: Jesse MacFadyen My app relies upon users plugging in their USB cable and transferring large files from the device to their computer. The file plugin creates folders under the isolated storage. I can find no way to get files and folders where the user can find them with their computer. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CB-6534) Windows 8 Cannot use Oauth
brian johnston created CB-6534: -- Summary: Windows 8 Cannot use Oauth Key: CB-6534 URL: https://issues.apache.org/jira/browse/CB-6534 Project: Apache Cordova Issue Type: Bug Components: Plugin InAppBrowser, WP8 Affects Versions: 3.3.0 Reporter: brian johnston Assignee: Jesse MacFadyen Google's Oauth is working fine on iOS and Android. However, as I am trying to port the app to WP8 I have found it does not work on WP8. So, I replaced Google's API with Microsoft's, but that one will not prompt the user to login through the Oauth interface either. I can't give more detail because Weinre won't work with WP8 either. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CB-6535) Windows 8 does not work with Weinre
brian johnston created CB-6535: -- Summary: Windows 8 does not work with Weinre Key: CB-6535 URL: https://issues.apache.org/jira/browse/CB-6535 Project: Apache Cordova Issue Type: Bug Components: WP8 Affects Versions: 3.3.0 Reporter: brian johnston Assignee: Jesse MacFadyen WP8 connects with Weinre for a short time and then disconnects. Tried the build.phonegap.com Weinre and a local instance. Same result on each. Tried a few of the workarounds mentioned on the web, none worked. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6525) download success callback not called in 0.4.3
[ https://issues.apache.org/jira/browse/CB-6525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13983000#comment-13983000 ] Nathan commented on CB-6525: Just to confirm this is not an isolated incident. I have upgraded to the latest build from a working version to come across this exact same error. download success callback not called in 0.4.3 - Key: CB-6525 URL: https://issues.apache.org/jira/browse/CB-6525 Project: Apache Cordova Issue Type: Bug Components: Plugin File Transfer Affects Versions: 3.4.0 Environment: Cordova 3.4.1 iOS 0.4.3 of the file transfer plugin Reporter: AH I've noticed that the success callback doesn't get executed after a download is successfully completed. Specifically, if success contains a console.log, nothing is logged to the Xcode debugger even though the download has completed successfully. I can tell that the download was completed because the following message is logged in Xcode: File Transfer Finished with response code 200 transfer.download(src, localPath, success, error); I think this is an issue with version 0.4.3 of the file transfer plugin. Version 0.4.2 of the plugin running on Cordova 3.4.1 didn't have this bug. I found another possible report of this bug: http://stackoverflow.com/questions/23240807/cant-setmetadata-while-downloading-files-via-filetransfer-download-in-ios-in-ph -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (CB-6530) Plugins docs for v3.4 not working
[ https://issues.apache.org/jira/browse/CB-6530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ian Clelland reassigned CB-6530: Assignee: Ian Clelland Plugins docs for v3.4 not working - Key: CB-6530 URL: https://issues.apache.org/jira/browse/CB-6530 Project: Apache Cordova Issue Type: Bug Components: Docs Affects Versions: 3.4.0 Reporter: Andrey Kurdyumov Assignee: Ian Clelland After moving plugin development to master branch, documentation for plugins no longer working. Urls pointed to https://github.com/apache/cordova-plugin-battery-status/blob/dev/doc/index.md and shoult to https://github.com/apache/cordova-plugin-battery-status/blob/master/doc/index.md -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6530) Plugins docs for v3.4 not working
[ https://issues.apache.org/jira/browse/CB-6530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13983018#comment-13983018 ] Ian Clelland commented on CB-6530: -- This happened as soon as the dev branches were replaced with placeholder pages. The docs (3.4.0 and edge) should be updated to point to master instead. Plugins docs for v3.4 not working - Key: CB-6530 URL: https://issues.apache.org/jira/browse/CB-6530 Project: Apache Cordova Issue Type: Bug Components: Docs Affects Versions: 3.4.0 Reporter: Andrey Kurdyumov Assignee: Ian Clelland After moving plugin development to master branch, documentation for plugins no longer working. Urls pointed to https://github.com/apache/cordova-plugin-battery-status/blob/dev/doc/index.md and shoult to https://github.com/apache/cordova-plugin-battery-status/blob/master/doc/index.md -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6530) Plugins docs for v3.4 not working
[ https://issues.apache.org/jira/browse/CB-6530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13983026#comment-13983026 ] ASF subversion and git services commented on CB-6530: - Commit 1257abb89f6d85eede8c604892afe914e815ff45 in cordova-docs's branch refs/heads/master from [~iclelland] [ https://git-wip-us.apache.org/repos/asf?p=cordova-docs.git;h=1257abb ] CB-6530: Update plugin documentation locations after removing dev branch Plugins docs for v3.4 not working - Key: CB-6530 URL: https://issues.apache.org/jira/browse/CB-6530 Project: Apache Cordova Issue Type: Bug Components: Docs Affects Versions: 3.4.0 Reporter: Andrey Kurdyumov Assignee: Ian Clelland After moving plugin development to master branch, documentation for plugins no longer working. Urls pointed to https://github.com/apache/cordova-plugin-battery-status/blob/dev/doc/index.md and shoult to https://github.com/apache/cordova-plugin-battery-status/blob/master/doc/index.md -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6530) Plugins docs for v3.4 not working
[ https://issues.apache.org/jira/browse/CB-6530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13983045#comment-13983045 ] ASF subversion and git services commented on CB-6530: - Commit 88bf20f5b42eaba97846e7401ff5fabb79730e1d in cordova-docs's branch refs/heads/master from [~iclelland] [ https://git-wip-us.apache.org/repos/asf?p=cordova-docs.git;h=88bf20f ] CB-6530: Update plugin documentation locations after removing dev branch Plugins docs for v3.4 not working - Key: CB-6530 URL: https://issues.apache.org/jira/browse/CB-6530 Project: Apache Cordova Issue Type: Bug Components: Docs Affects Versions: 3.4.0 Reporter: Andrey Kurdyumov Assignee: Ian Clelland After moving plugin development to master branch, documentation for plugins no longer working. Urls pointed to https://github.com/apache/cordova-plugin-battery-status/blob/dev/doc/index.md and shoult to https://github.com/apache/cordova-plugin-battery-status/blob/master/doc/index.md -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-5816) FirefoxOS - add build script
[
https://issues.apache.org/jira/browse/CB-5816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13983048#comment-13983048
]
ASF GitHub Bot commented on CB-5816:
Github user jsoref commented on a diff in the pull request:
https://github.com/apache/cordova-firefoxos/pull/7#discussion_r12049234
--- Diff: bin/lib/create.js ---
@@ -26,6 +26,7 @@ var fs = require('fs'),
ROOT= path.join(__dirname, '..', '..'),
check_reqs = require('./check_reqs');
+
--- End diff --
no. why add a second blank line?
FirefoxOS - add build script
Key: CB-5816
URL: https://issues.apache.org/jira/browse/CB-5816
Project: Apache Cordova
Issue Type: Bug
Components: FirefoxOS
Reporter: Axel Nennker
run: cordova build firefoxos
output:
Generating config.xml from defaults for platform firefoxos
Preparing firefoxos project
Compiling app on platform firefoxos via command
/project/platforms/firefoxos/cordova/build
events.js:72
throw er; // Unhandled 'error' event
^
Error: spawn ENOENT
at errnoException (child_process.js:980:11)
at Process.ChildProcess._handle.onexit (child_process.js:771:34)
project$
expected output:
nothing
-
platforms/firefoxos/cordova/build does not exist so the cordova build
firefoxos command fails.
Please add a build script (although it does nothing)
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CB-6505) Hybrid app - issues with pre-compiled, minified assets not getting loaded
[ https://issues.apache.org/jira/browse/CB-6505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13983059#comment-13983059 ] Andrew Grieve commented on CB-6505: --- cordova-js.git is the main Cordova repo for cordova.js files. Builds from there are moved into platforms when releases happen. Hybrid app - issues with pre-compiled, minified assets not getting loaded - Key: CB-6505 URL: https://issues.apache.org/jira/browse/CB-6505 Project: Apache Cordova Issue Type: Bug Components: CordovaJS Affects Versions: 3.4.0 Environment: iOS 6.1, Heroku, Ruby-on-Rails 3.2 Reporter: Craig Payne Assignee: Andrew Grieve I have an existing RoR application, with pre-compiled and minified assets, up on Heroku. I created a Cordova app using https://github.com/cfjedimaster/Cordova-Examples.git and following the instructions I was easily able to generate an app that ran on my iPhone and scanned as expected. When I went to move the one page app's functionality into the RoR application I started running into issues where the Cordova JavaScript was generating bad paths to, especially, cordova-plugins.js. Hacking the code, I bypassed the call to findCordovaPath, hardcoding that with /assets/ - which *almost* works. On my 'local' Dev env I can use /dev-assets (the RoR default) with the non-compiled, non-minified and I see no issues with loading the files. But, switching to /assets, doing the pre-compile, and pushing to Heroku continues to fail. Either I'm missing something semi-obvious (and possibly buried in the docs), or there's a testing hole here. I can't imagine that using pre-compiled and minified assets is an uncommon occurrence, even in Hybrid apps. NOTE - this is actually on 3.4.1-0.1.0 which isn't apparently a legal version in Affects Versions yet. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CB-5671) facilitate dynamic loading of cordova plugins
[ https://issues.apache.org/jira/browse/CB-5671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Grieve resolved CB-5671. --- Resolution: Fixed The new plan of record is to add a build-time step to concatenate all of the plugin JS with cordova.js. Upon doing so, I believe this problem goes away. facilitate dynamic loading of cordova plugins - Key: CB-5671 URL: https://issues.apache.org/jira/browse/CB-5671 Project: Apache Cordova Issue Type: Improvement Components: CordovaJS Affects Versions: 3.2.0 Environment: any Reporter: Jon Whitlock Assignee: Andrew Grieve Labels: javascript Attachments: Screen Shot 2014-03-06 at 8.49.27 AM.png Problem: Cordova expects resources to be loaded off the device filesystem. 1) On iOS this is very risky due to the turnaround time pushing hotfixes through the App store. 2) In complex JS applications one needs to use a loader like require.js to manage async loading (especially on mobile) module dependancy management (as cordova does internally). 3) When integrating with many 3rd-party services like auth/social login one needs to have a public-facing page to call back to. Use case: We have a bunch of prereqs before cordova.js loads, so we have to load cordova.js using require.js. However to show localised error messages we need the preferred language from the device to know which language to show messaging in, so we need cordova loaded as part of auth prerequisites. Problematic Assumptions: a) findCordovaPath() assumes a script tag in the document loaded cordova.js -- not the case with require.js or similar. b) injectPluginScript() assumes that cordova_plugins.js is in the same dir as cordova.js So using plugins dynamically loading Cordova is terminal, unless I hack findCordovaPath() to return (in our case) the path where cordova.js is to be found -- which is defined in a JS configuration file. I think it would be more robust to define the location of those file(s) in a config file somewhere -- which could also facilitate dynamic loading of cordova. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6437) [Mobilespec] improve and add support for blackberry, wp8, windows8
[ https://issues.apache.org/jira/browse/CB-6437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13983111#comment-13983111 ] ASF GitHub Bot commented on CB-6437: Github user martincgg commented on the pull request: https://github.com/apache/cordova-mobile-spec/pull/55#issuecomment-41573670 Done, rebased on master, ready to be merged. [Mobilespec] improve and add support for blackberry, wp8, windows8 -- Key: CB-6437 URL: https://issues.apache.org/jira/browse/CB-6437 Project: Apache Cordova Issue Type: Improvement Components: BlackBerry, mobile-spec, Windows 8, WP8 Affects Versions: 3.4.0 Reporter: Martin Gonzalez Assignee: Martin Gonzalez Labels: blackberry10, mobilespec,, module, node, support, windows8, wp8 Fix For: 3.5.0 The new node module for Mobilespecs can be improved. -Adding more functionality -Supporting platforms as blackberry10, windows phone 8 and windows 8. -Add functionality to automate some process as well. -Add functionality to add platforms according to the development environment --- Android, Blackberry, iOS --- Mac. --- Android, Blackberry, Windows 8, Windows Phone 8 --- Windows 8. --- Android, Blackberry --- Linux or any other Windows OS. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-5833) --copy-from and --link-to should work when pointed to a dir that contains a www/ and config.xml
[ https://issues.apache.org/jira/browse/CB-5833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13983126#comment-13983126 ] ASF subversion and git services commented on CB-5833: - Commit eb7f6791accdb24536f253ca4300c203a93976a4 in cordova-cli's branch refs/heads/master from [~kamrik] [ https://git-wip-us.apache.org/repos/asf?p=cordova-cli.git;h=eb7f679 ] CB-5833: Copy/link to custom merges and config.xml when When using cordova create with --link-to or --copy-from /some/dir, if /some/dir cntains merges or config.xml in addition to www, they will also be copied or linked --copy-from and --link-to should work when pointed to a dir that contains a www/ and config.xml --- Key: CB-5833 URL: https://issues.apache.org/jira/browse/CB-5833 Project: Apache Cordova Issue Type: Bug Components: CLI Reporter: Andrew Grieve Assignee: Mark Koudritsky Priority: Minor The recently added --source and --link flags allow you to create a project given its www/. It would be even more useful to be able to create a project using a dir that contains config.xml, merges/ and www/. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-5833) --copy-from and --link-to should work when pointed to a dir that contains a www/ and config.xml
[ https://issues.apache.org/jira/browse/CB-5833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13983129#comment-13983129 ] ASF GitHub Bot commented on CB-5833: Github user asfgit closed the pull request at: https://github.com/apache/cordova-cli/pull/169 --copy-from and --link-to should work when pointed to a dir that contains a www/ and config.xml --- Key: CB-5833 URL: https://issues.apache.org/jira/browse/CB-5833 Project: Apache Cordova Issue Type: Bug Components: CLI Reporter: Andrew Grieve Assignee: Mark Koudritsky Priority: Minor The recently added --source and --link flags allow you to create a project given its www/. It would be even more useful to be able to create a project using a dir that contains config.xml, merges/ and www/. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6532) cdvfile file url is not working with link tag like css
[
https://issues.apache.org/jira/browse/CB-6532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13983195#comment-13983195
]
Andrew Grieve commented on CB-6532:
---
Couple questions about this:
Is it still broken if you change imgElement - fileref on the last line?
Does toURL() yield the same thing as fileSystem.root.toURL() + / + filename?
cdvfile file url is not working with link tag like css
---
Key: CB-6532
URL: https://issues.apache.org/jira/browse/CB-6532
Project: Apache Cordova
Issue Type: Bug
Components: Plugin File, Plugin File Transfer
Affects Versions: 3.4.0
Environment: iOS 7
Reporter: Patrick Dürsteler
Priority: Critical
A css downloaded with xhr and created a local url
(cdvfile://localhost/test.css) with the File API can't be used as a
stylesheet.
{code}
var filename = test.css;
var imageURL = http://apache.org/css/style.css;;
requestFileSystem(TEMPORARY, 0, function(fileSystem) {
var ft = new FileTransfer();
ft.download(imageURL, fileSystem.root.toURL() + / + filename,
function(entry) {
var fileref=document.createElement(link);
fileref.setAttribute(rel, stylesheet);
fileref.setAttribute(type, text/css);
fileref.setAttribute(href, entry.toURL());
document.head.appendChild(imgElement);
});
});
{code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CB-6437) [Mobilespec] improve and add support for blackberry, wp8, windows8
[ https://issues.apache.org/jira/browse/CB-6437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13983253#comment-13983253 ] ASF GitHub Bot commented on CB-6437: Github user martincgg commented on the pull request: https://github.com/apache/cordova-mobile-spec/pull/55#issuecomment-41587797 Merge conflict resolved [Mobilespec] improve and add support for blackberry, wp8, windows8 -- Key: CB-6437 URL: https://issues.apache.org/jira/browse/CB-6437 Project: Apache Cordova Issue Type: Improvement Components: BlackBerry, mobile-spec, Windows 8, WP8 Affects Versions: 3.4.0 Reporter: Martin Gonzalez Assignee: Martin Gonzalez Labels: blackberry10, mobilespec,, module, node, support, windows8, wp8 Fix For: 3.5.0 The new node module for Mobilespecs can be improved. -Adding more functionality -Supporting platforms as blackberry10, windows phone 8 and windows 8. -Add functionality to automate some process as well. -Add functionality to add platforms according to the development environment --- Android, Blackberry, iOS --- Mac. --- Android, Blackberry, Windows 8, Windows Phone 8 --- Windows 8. --- Android, Blackberry --- Linux or any other Windows OS. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6506) RTC: Add support for OSX
[ https://issues.apache.org/jira/browse/CB-6506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13983293#comment-13983293 ] ASF GitHub Bot commented on CB-6506: Github user shazron commented on the pull request: https://github.com/apache/cordova-cli/pull/170#issuecomment-41590320 From @shepheb on the mailing list: LGTM. There might be some reason we can't use identical flows for OSX and iOS, but there's no point in having duplicate branches to the code if they're the same right now. They can be split later if they diverge. Thread: http://callback-dev.markmail.org/thread/3k45ht6lobxgeh5z RTC: Add support for OSX Key: CB-6506 URL: https://issues.apache.org/jira/browse/CB-6506 Project: Apache Cordova Issue Type: Improvement Components: CLI, Plugman Affects Versions: 3.4.0 Reporter: Tobias Bocanegra Assignee: Tobias Bocanegra Priority: Minor The recently updated scripts and templates in cordova-osx now work with cli and plugman. suggest/request to add it to the list of platforms. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6466) WP8 filetransfer.download() should auto mkdir missing folders
[ https://issues.apache.org/jira/browse/CB-6466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13983304#comment-13983304 ] ASF subversion and git services commented on CB-6466: - Commit 2043b4e8b087f6d112883beaefbd5825de29d3dc in cordova-plugin-file-transfer's branch refs/heads/master from [~stacic] [ https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-file-transfer.git;h=2043b4e ] CB-6466 Auto-create directories in download Bringing WP8 in line with the other platforms to automatically create missing directories in filetransfer.download(). WP8 filetransfer.download() should auto mkdir missing folders - Key: CB-6466 URL: https://issues.apache.org/jira/browse/CB-6466 Project: Apache Cordova Issue Type: Bug Components: Plugin File Transfer, WP8 Affects Versions: 3.4.0 Reporter: Mike Billau Assignee: Jesse MacFadyen Windows Phone 8 implementation of FileTransfer.download() does not automatically create any missing directories when saving a file. The iOS and Android implementations do. If target = /foo/bar.jpg and /foo/ doesn't exist, WP8 should create it to bring the platform in line with iOS and Android. This mail thread shows that we've decided that FileTransfer should be slightly more than a thin wrapper on the File plugin (which has an API.) http://markmail.org/message/cxy66pe23oyguoal -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (CB-6466) WP8 filetransfer.download() should auto mkdir missing folders
[ https://issues.apache.org/jira/browse/CB-6466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse MacFadyen reassigned CB-6466: --- Assignee: Staci Cooper (was: Jesse MacFadyen) WP8 filetransfer.download() should auto mkdir missing folders - Key: CB-6466 URL: https://issues.apache.org/jira/browse/CB-6466 Project: Apache Cordova Issue Type: Bug Components: Plugin File Transfer, WP8 Affects Versions: 3.4.0 Reporter: Mike Billau Assignee: Staci Cooper Fix For: 3.5.0 Windows Phone 8 implementation of FileTransfer.download() does not automatically create any missing directories when saving a file. The iOS and Android implementations do. If target = /foo/bar.jpg and /foo/ doesn't exist, WP8 should create it to bring the platform in line with iOS and Android. This mail thread shows that we've decided that FileTransfer should be slightly more than a thin wrapper on the File plugin (which has an API.) http://markmail.org/message/cxy66pe23oyguoal -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CB-6466) WP8 filetransfer.download() should auto mkdir missing folders
[ https://issues.apache.org/jira/browse/CB-6466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse MacFadyen resolved CB-6466. - Resolution: Fixed Fix Version/s: 3.5.0 WP8 filetransfer.download() should auto mkdir missing folders - Key: CB-6466 URL: https://issues.apache.org/jira/browse/CB-6466 Project: Apache Cordova Issue Type: Bug Components: Plugin File Transfer, WP8 Affects Versions: 3.4.0 Reporter: Mike Billau Assignee: Staci Cooper Fix For: 3.5.0 Windows Phone 8 implementation of FileTransfer.download() does not automatically create any missing directories when saving a file. The iOS and Android implementations do. If target = /foo/bar.jpg and /foo/ doesn't exist, WP8 should create it to bring the platform in line with iOS and Android. This mail thread shows that we've decided that FileTransfer should be slightly more than a thin wrapper on the File plugin (which has an API.) http://markmail.org/message/cxy66pe23oyguoal -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CB-6536) package.appxmanifest has additional namespace in 8.1
Jesse MacFadyen created CB-6536: --- Summary: package.appxmanifest has additional namespace in 8.1 Key: CB-6536 URL: https://issues.apache.org/jira/browse/CB-6536 Project: Apache Cordova Issue Type: Bug Components: Windows 8 Affects Versions: 3.4.0 Reporter: Jesse MacFadyen Assignee: Jesse MacFadyen Fix For: 3.5.0 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6466) WP8 filetransfer.download() should auto mkdir missing folders
[ https://issues.apache.org/jira/browse/CB-6466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13983345#comment-13983345 ] ASF GitHub Bot commented on CB-6466: Github user stacic commented on the pull request: https://github.com/apache/cordova-plugin-file-transfer/pull/28#issuecomment-41593367 Thanks for merging for me! I'll go ahead and close. WP8 filetransfer.download() should auto mkdir missing folders - Key: CB-6466 URL: https://issues.apache.org/jira/browse/CB-6466 Project: Apache Cordova Issue Type: Bug Components: Plugin File Transfer, WP8 Affects Versions: 3.4.0 Reporter: Mike Billau Assignee: Staci Cooper Fix For: 3.5.0 Windows Phone 8 implementation of FileTransfer.download() does not automatically create any missing directories when saving a file. The iOS and Android implementations do. If target = /foo/bar.jpg and /foo/ doesn't exist, WP8 should create it to bring the platform in line with iOS and Android. This mail thread shows that we've decided that FileTransfer should be slightly more than a thin wrapper on the File plugin (which has an API.) http://markmail.org/message/cxy66pe23oyguoal -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6466) WP8 filetransfer.download() should auto mkdir missing folders
[ https://issues.apache.org/jira/browse/CB-6466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13983346#comment-13983346 ] ASF GitHub Bot commented on CB-6466: Github user stacic closed the pull request at: https://github.com/apache/cordova-plugin-file-transfer/pull/28 WP8 filetransfer.download() should auto mkdir missing folders - Key: CB-6466 URL: https://issues.apache.org/jira/browse/CB-6466 Project: Apache Cordova Issue Type: Bug Components: Plugin File Transfer, WP8 Affects Versions: 3.4.0 Reporter: Mike Billau Assignee: Staci Cooper Fix For: 3.5.0 Windows Phone 8 implementation of FileTransfer.download() does not automatically create any missing directories when saving a file. The iOS and Android implementations do. If target = /foo/bar.jpg and /foo/ doesn't exist, WP8 should create it to bring the platform in line with iOS and Android. This mail thread shows that we've decided that FileTransfer should be slightly more than a thin wrapper on the File plugin (which has an API.) http://markmail.org/message/cxy66pe23oyguoal -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CB-6536) package.appxmanifest has additional namespace in 8.1
[ https://issues.apache.org/jira/browse/CB-6536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse MacFadyen resolved CB-6536. - Resolution: Fixed package.appxmanifest has additional namespace in 8.1 Key: CB-6536 URL: https://issues.apache.org/jira/browse/CB-6536 Project: Apache Cordova Issue Type: Bug Components: Windows 8 Affects Versions: 3.4.0 Reporter: Jesse MacFadyen Assignee: Jesse MacFadyen Fix For: 3.5.0 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6536) package.appxmanifest has additional namespace in 8.1
[ https://issues.apache.org/jira/browse/CB-6536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13983349#comment-13983349 ] ASF GitHub Bot commented on CB-6536: Github user purplecabbage commented on the pull request: https://github.com/apache/cordova-cli/pull/171#issuecomment-41593880 Issue created here: https://issues.apache.org/jira/browse/CB-6536 Merged, and issue closed. package.appxmanifest has additional namespace in 8.1 Key: CB-6536 URL: https://issues.apache.org/jira/browse/CB-6536 Project: Apache Cordova Issue Type: Bug Components: Windows 8 Affects Versions: 3.4.0 Reporter: Jesse MacFadyen Assignee: Jesse MacFadyen Fix For: 3.5.0 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6500) Cordova requires arm64 architecture
[ https://issues.apache.org/jira/browse/CB-6500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13983371#comment-13983371 ] Song Zheng commented on CB-6500: Awesome. Thank you for catching this [~shazron] Cordova requires arm64 architecture --- Key: CB-6500 URL: https://issues.apache.org/jira/browse/CB-6500 Project: Apache Cordova Issue Type: Bug Components: CordovaJS, iOS Affects Versions: 3.4.0 Environment: OSX Reporter: Song Zheng Assignee: Shazron Abdullah In project settings, developers are now required to add arm64 under valid Architectures build settings. If we do not want to support arm64 or are unable to (because of other SDK dependency), our app will no longer work and get the following compile errors: undefined symbols for architecture armv7: _OBJC_CLASS_$_CDVPlugin, referenced from: _OBJC_CLASS_$_OpenTokPlugin in OpenTokPlugin.o _OBJC_METACLASS_$_CDVPlugin, referenced from: _OBJC_METACLASS_$_OpenTokPlugin in OpenTokPlugin.o ... To reproduce: 1. Create new project (Cordova create YourApp) 2. Add ios platform ( Cordova plaform add ios ) 3. Open xcode ( open YourApp/platform/ios/...xcodeproj ) 4. Change project build settings ( Valid Architectures to only armv7 - remove armv7s and arm64 ) 5. Change project build settings (Build Active Architecture Only - No ) Result: undefined symbol errors during compile time. This was a breaking change from Cordova v 3.4.0-0.1.3 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CB-6423) (iOS) cordova.js: iOSExec() not working after upgrading from Cordova 3.0 to 3.4
[
https://issues.apache.org/jira/browse/CB-6423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Grieve resolved CB-6423.
---
Resolution: Duplicate
Assignee: Andrew Grieve
Believe the issue here is that same that I just fixed in CB-5488. There is a
race condition for creating the iframe, where document.body doesn't exist yet
at times.
For now, a work around would be to put the `script src=cordova.js` tag
after body
(iOS) cordova.js: iOSExec() not working after upgrading from Cordova 3.0 to
3.4
---
Key: CB-6423
URL: https://issues.apache.org/jira/browse/CB-6423
Project: Apache Cordova
Issue Type: Bug
Components: CordovaJS, iOS
Affects Versions: 3.4.0
Reporter: Joel Rubio
Assignee: Andrew Grieve
Labels: cordovajs, ios, upgrade
Hi there,
I recently upgraded my working PhoneGap app from 3.0 to 3.4. In iOS, the app
wouldn't go past the splashscreen. It would get stuck while trying to fetch a
local file (in file:/// dir) through an XHR.
I managed to trace the problem to the iOSExec function in cordova.js. Before
the upgrade, it would determine bridgeMode the following way:
bridgeMode = navigator.userAgent.indexOf(' 4_') == -1 ?
jsToNativeModes.XHR_NO_PAYLOAD : jsToNativeModes.IFRAME_NAV;
In cordova.js 3.4 it is determined the following way:
bridgeMode = navigator.userAgent.indexOf(' 5_') == -1 ?
jsToNativeModes.IFRAME_NAV: jsToNativeModes.XHR_NO_PAYLOAD;
Notice the switch in the expressions.
This led to any iOS device with a version other than 5 not working. Using the
jsToNativeModes.IFRAME_NAV bridgeMode would lead to the default case in the
subsequent switch statement in which it determines what to do according to
the bridgeMode.
switch (bridgeMode) {
case jsToNativeModes.XHR_NO_PAYLOAD:
case jsToNativeModes.XHR_WITH_PAYLOAD:
case jsToNativeModes.XHR_OPTIONAL_PAYLOAD:
// This prevents sending an XHR when there is already one being
sent.
// This should happen only in rare circumstances (refer to unit
tests).
if (execXhr execXhr.readyState != 4) {
execXhr = null;
}
// Re-using the XHR improves exec() performance by about 10%.
execXhr = execXhr || new XMLHttpRequest();
// Changing this to a GET will make the XHR reach the URIProtocol
on 4.2.
// For some reason it still doesn't work though...
// Add a timestamp to the query param to prevent caching.
execXhr.open('HEAD', /!gap_exec? + (+new Date()), true);
if (!vcHeaderValue) {
vcHeaderValue = /.*\((.*)\)/.exec(navigator.userAgent)[1];
}
execXhr.setRequestHeader('vc', vcHeaderValue);
execXhr.setRequestHeader('rc', ++requestCount);
if (shouldBundleCommandJson()) {
execXhr.setRequestHeader('cmds',
iOSExec.nativeFetchMessages());
}
execXhr.send(null);
break;
case jsToNativeModes.IFRAME_HASH_NO_PAYLOAD:
case jsToNativeModes.IFRAME_HASH_WITH_PAYLOAD:
execHashIframe = execHashIframe || createHashIframe();
// Check if they've removed it from the DOM, and put it back if
so.
if (!execHashIframe.contentWindow) {
execHashIframe = createHashIframe();
}
// The delegate method is called only when the hash changes, so
toggle it back and forth.
hashToggle = hashToggle ^ 3;
var hashValue = '%0' + hashToggle;
if (bridgeMode === jsToNativeModes.IFRAME_HASH_WITH_PAYLOAD) {
hashValue += iOSExec.nativeFetchMessages();
}
execHashIframe.contentWindow.location.hash = hashValue;
break;
default:
execIframe = execIframe || createExecIframe();
// Check if they've removed it from the DOM, and put it back if
so.
if (!execIframe.contentWindow) {
execIframe = createExecIframe();
}
execIframe.src = gap://ready;
}
The default case did nothing.
Making it always use jsToNativeModes.XHR_NO_PAYLOAD allows my app to work
again with any iOS version but I feel like I'm losing certain advantages from
the upgrade. Which are they? Why were the Ternary Operator expressions
switched around? Which could be a possible reason why my app, which worked
just fine before the upgrade, would stop working because of this change? Is
there a better solution than the one I implemented?
Thanks,
-JR.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Resolved] (CB-6006) ms-touch-action doesn't always solve 'overscroll'
[
https://issues.apache.org/jira/browse/CB-6006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesse MacFadyen resolved CB-6006.
-
Resolution: Won't Fix
This is a limitation of the WebBrowser, and beyond our control.
ms-touch-action doesn't always solve 'overscroll'
-
Key: CB-6006
URL: https://issues.apache.org/jira/browse/CB-6006
Project: Apache Cordova
Issue Type: Bug
Components: WP8
Affects Versions: 3.3.0
Reporter: Lee Crossley
Assignee: Jesse MacFadyen
Using:
{code}
-ms-touch-action: none
{code}
on the body doesn't always prevent overscroll.
If you have an element with:
{code}
overflow: scroll
{code}
within the body, occasionally the body element itself can scroll beyond the
bounds of the html.
I've tried
{code}
-ms-scroll-chaining
{code}
etc but there doesn't seem to be a way to prevent this behaviour reliably and
have any scrollable content.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Resolved] (CB-2060) WP8 Cookies are not sent
[ https://issues.apache.org/jira/browse/CB-2060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse MacFadyen resolved CB-2060. - Resolution: Incomplete [~indiandragon] has posted a workaround. Otherwise, please post a test in order to demonstrate the issue. WP8 Cookies are not sent Key: CB-2060 URL: https://issues.apache.org/jira/browse/CB-2060 Project: Apache Cordova Issue Type: Bug Components: WP8 Reporter: Scott Keiffer Assignee: Jesse MacFadyen Cookies are not being saved or sent regardless if they are remote or locally created via javascript. This will cause issue with any website/webservice that relies on cookies for authentication (asp.net). -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6437) [Mobilespec] improve and add support for blackberry, wp8, windows8
[ https://issues.apache.org/jira/browse/CB-6437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13983408#comment-13983408 ] ASF subversion and git services commented on CB-6437: - Commit ff3a26a7761edcdaa4a3d41723d6703199edd682 in cordova-mobile-spec's branch refs/heads/master from [~cmarcelk] [ https://git-wip-us.apache.org/repos/asf?p=cordova-mobile-spec.git;h=ff3a26a ] CB-6437 fix paths for OS X [Mobilespec] improve and add support for blackberry, wp8, windows8 -- Key: CB-6437 URL: https://issues.apache.org/jira/browse/CB-6437 Project: Apache Cordova Issue Type: Improvement Components: BlackBerry, mobile-spec, Windows 8, WP8 Affects Versions: 3.4.0 Reporter: Martin Gonzalez Assignee: Martin Gonzalez Labels: blackberry10, mobilespec,, module, node, support, windows8, wp8 Fix For: 3.5.0 The new node module for Mobilespecs can be improved. -Adding more functionality -Supporting platforms as blackberry10, windows phone 8 and windows 8. -Add functionality to automate some process as well. -Add functionality to add platforms according to the development environment --- Android, Blackberry, iOS --- Mac. --- Android, Blackberry, Windows 8, Windows Phone 8 --- Windows 8. --- Android, Blackberry --- Linux or any other Windows OS. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6437) [Mobilespec] improve and add support for blackberry, wp8, windows8
[ https://issues.apache.org/jira/browse/CB-6437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13983407#comment-13983407 ] ASF subversion and git services commented on CB-6437: - Commit e7f314d919eb25669acb17f9aecefe3129575d94 in cordova-mobile-spec's branch refs/heads/master from [~martin.c.glez.glez] [ https://git-wip-us.apache.org/repos/asf?p=cordova-mobile-spec.git;h=e7f314d ] CB-6437 [Improvements support for more platforms] -Added full compatibility cross platform -Working with absolute paths -Added support for Blackberry10, Windows 8 and Windows Phone 8 -Added functionality to add platforms according to the development environment -- Android, Blackberry, iOS --- Mac. -- Android, Blackberry, Windows 8, Windows Phone 8 --- Windows 8. -- Android, Blackberry --- Linux or any other Windows OS. - Added more requirements checks - Added functionality to delete project folder if exists (recursive function) - Added functionality to locate libraries - Added function to copy with exclusion list - Added createmobilespec.bat createmobilespec.sh - Added symlink for windows Linux based OS. Changed tabs for spaces My mistake, it's done. Added logic to kill ADB.exe, apache header Apache header added to createmobilespec.cmd createmobilespec.sh - Added logic to kill ADB.exe process under windows, when locks project folder. createmobilespec cmd sh Changed comments to # in sh file Indent to 4 in Apache license header Added args logic other changes Added: -Logic to deal with arguments, to accept platforms. -Logic when no arguments are present, to fail and throw error. -Support for help argument, to show usage. Supported platforms (args): --android, --ios, --blackberry10, --wp8, --windows8. Removed: top level function for custom copy Changed: -Path directory for mobilespec, current location at cordova-coho/mobilespec. -link-to instead of copy for mobilespec project. Changes createmobilespec -Deleted top level functions. -Used optimist methods to print help. -Changes on paths. -Other minor changes. Removed, unnecessary outputs shows help when error, mobilespec peer of coho -Changed mobilespec project as cordova-coho peer. -Added usage description, to set more usage information. -Changed error outputs with help output and notice messages. [Mobilespec] improve and add support for blackberry, wp8, windows8 -- Key: CB-6437 URL: https://issues.apache.org/jira/browse/CB-6437 Project: Apache Cordova Issue Type: Improvement Components: BlackBerry, mobile-spec, Windows 8, WP8 Affects Versions: 3.4.0 Reporter: Martin Gonzalez Assignee: Martin Gonzalez Labels: blackberry10, mobilespec,, module, node, support, windows8, wp8 Fix For: 3.5.0 The new node module for Mobilespecs can be improved. -Adding more functionality -Supporting platforms as blackberry10, windows phone 8 and windows 8. -Add functionality to automate some process as well. -Add functionality to add platforms according to the development environment --- Android, Blackberry, iOS --- Mac. --- Android, Blackberry, Windows 8, Windows Phone 8 --- Windows 8. --- Android, Blackberry --- Linux or any other Windows OS. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-4602) getPreferredLanguage platform inconsistencies
[
https://issues.apache.org/jira/browse/CB-4602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13983409#comment-13983409
]
ASF GitHub Bot commented on CB-4602:
GitHub user mbillau opened a pull request:
https://github.com/apache/cordova-plugin-globalization/pull/9
Android should return BCP47 tag, not localized string
For https://issues.apache.org/jira/browse/CB-4602
I still want to test the consistency with iOS.
Return the Locale.getDefault().toString() which according to the Android
docs [1], contains a two-letter lowercase ISO language code (ISO 639-1)
followed by an underscore, followed by the two-letter uppercase country code
(ISO 3166-1). As best I can tell, these two specs (and some more) are what make
up BCP 47, therefore we should be able to assume that this will always return
BCP 47 compliant language tags.
I did notice that sometimes toString() will leave out country or language
codes if they don't exist. For example, if you set locale to be Locale.CHINESE,
then you'll get back zh - no country code. I'm not sure if this is BCP 47, or
if there is anything we can do about it.
Finally, since this changes an API, would we have to do a major bump to the
plugin version number? I thought about deprecating the old code and/or creating
a new API method but chose against that since this is a bug fix and not a
feature request. I think the version number should be bumped though...
[1] http://developer.android.com/reference/java/util/Locale.html
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/mbillau/cordova-plugin-globalization CB-4602
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cordova-plugin-globalization/pull/9.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #9
commit 64734dbd067330a8a787724a8df0a73325c96276
Author: mbillau mike.bil...@gmail.com
Date: 2014-04-28T19:02:39Z
Android should return BCP47 tag, not localized string
getPreferredLanguage platform inconsistencies
-
Key: CB-4602
URL: https://issues.apache.org/jira/browse/CB-4602
Project: Apache Cordova
Issue Type: Bug
Components: Android, Plugin Globalization
Affects Versions: 2.6.0, 3.0.0
Environment: Android
Reporter: Jon Whitlock
Assignee: Martin Gonzalez
Priority: Minor
In;
https://github.com/apache/cordova-docs/blob/master/docs/en/edge/cordova/globalization/globalization.getPreferredLanguage.md
Returns the language identifier string to the successCallback with a
properties object as a parameter. That object should have a value property
with a String value.
navigator.globalization.getPreferredLanguage(
function (language) {alert('language: ' + language.value + '\n');},
function () {alert('Error getting language\n');}
);
On Android the function doesn't seem to return an identifier as such, it
returns *a string describing the language localised to that language*, e.g.
English for English or ä¸æ–‡ for Japanese. Naturally this is less than ideal
for subsequent string operations, furthermore on that page Windows Phone 8
Quirks - Returns the ISO 639-1 two-letter code for the current language
which is an identifier, and also what I would expect (or an ISO 639-2 code,
as per http://www.loc.gov/standards/iso639-2/php/code_list.php)
Android seems to support 639-2
http://developer.android.com/reference/java/util/Locale.html#getISO3Language()
I have no idea what it returns on other platforms, but to keep client code
consistent I guess it would good if this could be normalised in the API.
Have tested this on v3.0 and 2.6, is the same.
As an aside, the locale is not really what I want here, as the user may be in
the US but have Japanese as their preferred language.
Thanks,
jon
(first go at using Jira, apols if I got something wrong!)
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CB-4692) Native GeoLocation support is not fully working
[ https://issues.apache.org/jira/browse/CB-4692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13983414#comment-13983414 ] Jesse MacFadyen commented on CB-4692: - Is this still valid [~viras] ? Native GeoLocation support is not fully working --- Key: CB-4692 URL: https://issues.apache.org/jira/browse/CB-4692 Project: Apache Cordova Issue Type: Bug Components: Plugin Geolocation, WP7, WP8 Affects Versions: 3.0.0 Reporter: Wolfgang Koller Assignee: Wolfgang Koller The current Geolocation implementation of Cordova is using the native, built in, support of Internet Explorer. However the native code does not support Altitude, AltitudeAccuracy and heading properties (they are always null). Therefor it is required to add our own implementation based on GeoCoordinateWatcher. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CB-6537) Consistently indicate `cordova ...` in errors
Josh Soref created CB-6537: -- Summary: Consistently indicate `cordova ...` in errors Key: CB-6537 URL: https://issues.apache.org/jira/browse/CB-6537 Project: Apache Cordova Issue Type: Bug Components: CLI Affects Versions: 3.4.0 Reporter: Josh Soref Assignee: Josh Soref Priority: Minor Good: $ cordova build No platforms added to this project. Please use `cordova platform add platform`. Bad: $ cordova platform add fio Platform fio not recognized as a core cordova platform. See platform list. $ cordova jlhjk Cordova does not know jlhjk; try help for a list of all the available commands. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6537) Consistently indicate `cordova ...` in errors
[ https://issues.apache.org/jira/browse/CB-6537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13983426#comment-13983426 ] ASF GitHub Bot commented on CB-6537: GitHub user jsoref opened a pull request: https://github.com/apache/cordova-cli/pull/172 CB-6537 Consistently indicate `cordova ...` in errors You can merge this pull request into a Git repository by running: $ git pull https://github.com/jsoref/cordova-cli cb_6537 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cordova-cli/pull/172.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #172 commit af0d8fa8404e1c138d575db9231c0444e2c4dd67 Author: Josh Soref jso...@blackberry.com Date: 2014-04-28T19:14:37Z CB-6537 Consistently indicate `cordova ...` in errors Consistently indicate `cordova ...` in errors - Key: CB-6537 URL: https://issues.apache.org/jira/browse/CB-6537 Project: Apache Cordova Issue Type: Bug Components: CLI Affects Versions: 3.4.0 Reporter: Josh Soref Assignee: Josh Soref Priority: Minor Good: $ cordova build No platforms added to this project. Please use `cordova platform add platform`. Bad: $ cordova platform add fio Platform fio not recognized as a core cordova platform. See platform list. $ cordova jlhjk Cordova does not know jlhjk; try help for a list of all the available commands. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6412) Add a RELEASENOTES / CHANGELOG file to WP8 repo
[ https://issues.apache.org/jira/browse/CB-6412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13983451#comment-13983451 ] ASF subversion and git services commented on CB-6412: - Commit dd34c9ab1604027f5860204b1ebd3a2005f4798d in cordova-wp8's branch refs/heads/master from [~purplecabbage] [ https://git-wip-us.apache.org/repos/asf?p=cordova-wp8.git;h=dd34c9a ] CB-6412 Include release notes in repo. Add a RELEASENOTES / CHANGELOG file to WP8 repo --- Key: CB-6412 URL: https://issues.apache.org/jira/browse/CB-6412 Project: Apache Cordova Issue Type: Task Components: WP8 Reporter: Ryan Willoughby Assignee: Jesse MacFadyen As is done for Android and iOS, there should be a releasnotes.md file aggregating the bug fixes and changes in WP8. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CB-6412) Add a RELEASENOTES / CHANGELOG file to WP8 repo
[ https://issues.apache.org/jira/browse/CB-6412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse MacFadyen resolved CB-6412. - Resolution: Fixed Add a RELEASENOTES / CHANGELOG file to WP8 repo --- Key: CB-6412 URL: https://issues.apache.org/jira/browse/CB-6412 Project: Apache Cordova Issue Type: Task Components: WP8 Reporter: Ryan Willoughby Assignee: Jesse MacFadyen As is done for Android and iOS, there should be a releasnotes.md file aggregating the bug fixes and changes in WP8. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CB-3420) InAppBrowser Option to Start Hidden
[
https://issues.apache.org/jira/browse/CB-3420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesse MacFadyen updated CB-3420:
Component/s: (was: WP8)
(was: WP7)
InAppBrowser Option to Start Hidden
---
Key: CB-3420
URL: https://issues.apache.org/jira/browse/CB-3420
Project: Apache Cordova
Issue Type: Improvement
Components: Android, BlackBerry, CordovaJS, iOS, mobile-spec, Plugin
InAppBrowser
Reporter: Andrew Grieve
Assignee: David Kemp
Priority: Minor
Fix For: 3.5.0
One common use-case for the InAppBrowser is to handle an OAuth flow. Some
flows can be done without any user interaction, so it would be great if the
InAppBrowser had an option where it would start hidden, and could later be
reveals through a JS call.
E.g.
var iab = window.open('$OAUTH_URL', 'hidden=yes');
//some time later.
iab.show();
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Created] (CB-6538) plugins.cordova.io looks awful on IE8 (Windows XP)
Josh Soref created CB-6538: -- Summary: plugins.cordova.io looks awful on IE8 (Windows XP) Key: CB-6538 URL: https://issues.apache.org/jira/browse/CB-6538 Project: Apache Cordova Issue Type: Bug Components: Registry Web Affects Versions: 3.4.0 Reporter: Josh Soref It looks nice and shiny on other browsers, but it isn't usable in IE8. According to some analysis, IE8 still has around 1/5 of the market ... -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6538) plugins.cordova.io looks awful on IE8 (Windows XP)
[ https://issues.apache.org/jira/browse/CB-6538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13983472#comment-13983472 ] Josh Soref commented on CB-6538: http://www.netmarketshare.com/browser-market-share.aspx?qprid=2qpcustomd=0 is the first random site I found listing market share. We have a product which needs to support IE8, and plugins.cordova.io is a fairly visible part of Cordova, so it'd be good for it to support IE8... plugins.cordova.io looks awful on IE8 (Windows XP) -- Key: CB-6538 URL: https://issues.apache.org/jira/browse/CB-6538 Project: Apache Cordova Issue Type: Bug Components: Registry Web Affects Versions: 3.4.0 Reporter: Josh Soref Attachments: plugins-cordova-io-ie8.png It looks nice and shiny on other browsers, but it isn't usable in IE8. According to some analysis, IE8 still has around 1/5 of the market ... -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CB-6538) plugins.cordova.io looks awful on IE8 (Windows XP)
[ https://issues.apache.org/jira/browse/CB-6538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Soref updated CB-6538: --- Attachment: plugins-cordova-io-ie8.png plugins.cordova.io in IE8 on Windows XP (you can get a VM from http://modern.ie) plugins.cordova.io looks awful on IE8 (Windows XP) -- Key: CB-6538 URL: https://issues.apache.org/jira/browse/CB-6538 Project: Apache Cordova Issue Type: Bug Components: Registry Web Affects Versions: 3.4.0 Reporter: Josh Soref Attachments: plugins-cordova-io-ie8.png It looks nice and shiny on other browsers, but it isn't usable in IE8. According to some analysis, IE8 still has around 1/5 of the market ... -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CB-4756) Silent failure when maximum number of developer applications has been reached on WP
[ https://issues.apache.org/jira/browse/CB-4756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse MacFadyen resolved CB-4756. - Resolution: Fixed This is present in the output from the cli : Error: An error occurred while running the wp8 project.Error :: Unable to instal l application. The maximum number of developer applications on this phone has been reached. Please uninstall a developer application and try again. Silent failure when maximum number of developer applications has been reached on WP - Key: CB-4756 URL: https://issues.apache.org/jira/browse/CB-4756 Project: Apache Cordova Issue Type: Improvement Components: WP7, WP8 Affects Versions: 3.0.0 Reporter: Maxime Robert Assignee: Jesse MacFadyen Priority: Minor When trying to deploy with cordova CLI on WP7 device (should be similar on WP8 but I haven't tested) and if the maximum number of developer applications on the phone has been reached, it fails silently (it says the device hasn't been found) and tries to deploy on the emulator. If I try to deploy with Visual Studio, an error message The maximum number of developer applications on this phone has been reached is displayed. The cordova CLI should display this message to inform the user why it can't deploy on the device (instead of pretending the device is not connected). -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CB-5531) WP8. File Api readAsText incorrectly handles position args
[ https://issues.apache.org/jira/browse/CB-5531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse MacFadyen resolved CB-5531. - Resolution: Fixed Merged a long ways back, but never closed the issue. WP8. File Api readAsText incorrectly handles position args -- Key: CB-5531 URL: https://issues.apache.org/jira/browse/CB-5531 Project: Apache Cordova Issue Type: Bug Components: Plugin File, WP8 Reporter: Sergey Grebnov Assignee: Sergey Grebnov Could be reproduced on mobile file spec tests below (all are failed) file.spec.88 should read sliced file: readAsText file.spec.89 should read sliced file: slice past eof file.spec.90 should read sliced file: slice to eof -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CB-6539) WinJS versions needs update for Windows 8.1
Aaron Newcomer created CB-6539: -- Summary: WinJS versions needs update for Windows 8.1 Key: CB-6539 URL: https://issues.apache.org/jira/browse/CB-6539 Project: Apache Cordova Issue Type: Bug Components: Windows 8 Affects Versions: 3.4.0, 3.3.0 Environment: Visual Studio 2013 Ultimate Reporter: Aaron Newcomer Assignee: Jesse MacFadyen Priority: Critical Cordova attempts to add WinJS if not already loaded: https://github.com/apache/cordova-js/blob/master/src/windows8/platform.js But for Windows 8.1 apps, the WinJS version has been updated from 1.0 to 2.0, and so the path to base.js becomes incorrect. It's easy enough to update the path, but then 8.0 compatibility is broken. I suppose one could attempt to load both 1.0 *and* 2.0, but this would introduce a (non-crippling) runtime error for the file that couldn't be found. The Windows 8 template project would also need to be addressed for 8.1 compatibility: https://github.com/apache/cordova-windows/tree/master/windows8/template -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CB-5731) Windows Phone 8 fails to access remote urls
[
https://issues.apache.org/jira/browse/CB-5731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesse MacFadyen resolved CB-5731.
-
Resolution: Fixed
This appears to have been fixed. Please reopen if not ...
Windows Phone 8 fails to access remote urls
---
Key: CB-5731
URL: https://issues.apache.org/jira/browse/CB-5731
Project: Apache Cordova
Issue Type: Bug
Components: WP8
Affects Versions: 3.3.0
Reporter: John McLear
Assignee: Sergey Grebnov
Attachments: BrokenXDKXHRDemo.zip
Doing a very simple:
{code:javascript}
$.get(http://google.com;, function(){alert(yay)});
{code}
Fails on Windows Phone 8.
Basically Cross domain requests don't work, this includes when an explicit
and/or wildcard exclusion is set in config.xml allowed domains
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CB-5203) Using XmlHTTPRequest.open on WP8 raises a TypeError
[
https://issues.apache.org/jira/browse/CB-5203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13983484#comment-13983484
]
ASF GitHub Bot commented on CB-5203:
Github user purplecabbage commented on the pull request:
https://github.com/apache/cordova-wp8/pull/19#issuecomment-41606953
@dotnetwise The .cs file writes js to the WebBrowser to handle XHR.
Using XmlHTTPRequest.open on WP8 raises a TypeError
---
Key: CB-5203
URL: https://issues.apache.org/jira/browse/CB-5203
Project: Apache Cordova
Issue Type: Bug
Components: weinre
Affects Versions: 3.1.0
Environment: Windows Phone 7 + 8
Windows 8, MS Visual Studio Express 2012 for Windows Phone version
11.0.60610.01 Update 3. .NET version 4.5.50709. Weinre 2.0.0-pre-HH0SN197
Reporter: Björn Andersson
Assignee: Sergey Grebnov
Fix For: 3.3.0
Using the {{cordova-app-hello-world}} code on a WP8 device, connected to the
device through weinre, trying to use XMLHTTPRequest like this:
{code:language=javascript}
var xhr = new XMLHttpRequest();
xhr.open('GET', 'js/index.js', true);
xhr.send();
console.log(xhr.responseText);
{code}
An error is raised at {{xhr.open}}: {{TypeError: Object doesn't support
property or method 'addEventListener'}}
The same code on iOS runs through and shows me the content of {{index.js}}.
Changing the call to:
{code:javascript}
var xhr = new XMLHttpRequest();
xhr._url = 'js/index.js';
xhr.send();
console.log(xhr.responseText);
{code}
Returns the expected result.
I also noticed that {{XMLHttpRequest.prototype.open}} does not match the code
in {{cordovalib\XHRHelper.cs}}:
{code:title=XMLHttpRequest.prototype.open|javascript}
function() {
var result;
callBeforeHooks(hookSite, this, arguments);
try {
result = func.apply(this, arguments);
} catch (e) {
callExceptHooks(hookSite, this, arguments, e);
throw e;
} finally {
callAfterHooks(hookSite, this, arguments, result);
}
return result;
}
{code}
GitHub repository with the code I used:
https://github.com/gaqzi/cordova-wp8-xhr-test
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Resolved] (CB-6530) Plugins docs for v3.4 not working
[ https://issues.apache.org/jira/browse/CB-6530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ian Clelland resolved CB-6530. -- Resolution: Fixed The website has been updated; docs links now point directly to the plugin registry Plugins docs for v3.4 not working - Key: CB-6530 URL: https://issues.apache.org/jira/browse/CB-6530 Project: Apache Cordova Issue Type: Bug Components: Docs Affects Versions: 3.4.0 Reporter: Andrey Kurdyumov Assignee: Ian Clelland After moving plugin development to master branch, documentation for plugins no longer working. Urls pointed to https://github.com/apache/cordova-plugin-battery-status/blob/dev/doc/index.md and shoult to https://github.com/apache/cordova-plugin-battery-status/blob/master/doc/index.md -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CB-6452) Plugins Release Apr 16, 2014
[ https://issues.apache.org/jira/browse/CB-6452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ian Clelland resolved CB-6452. -- Resolution: Fixed Plugins released! Plugins Release Apr 16, 2014 Key: CB-6452 URL: https://issues.apache.org/jira/browse/CB-6452 Project: Apache Cordova Issue Type: Task Reporter: Ian Clelland Assignee: Ian Clelland Following steps at https://github.com/apache/cordova-coho/blob/master/docs/plugins-release-process.md -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6506) RTC: Add support for OSX
[ https://issues.apache.org/jira/browse/CB-6506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13983510#comment-13983510 ] ASF GitHub Bot commented on CB-6506: Github user purplecabbage commented on the pull request: https://github.com/apache/cordova-cli/pull/170#issuecomment-41610058 I have added a VERSION file and tagged 3.5.0-dev RTC: Add support for OSX Key: CB-6506 URL: https://issues.apache.org/jira/browse/CB-6506 Project: Apache Cordova Issue Type: Improvement Components: CLI, Plugman Affects Versions: 3.4.0 Reporter: Tobias Bocanegra Assignee: Tobias Bocanegra Priority: Minor The recently updated scripts and templates in cordova-osx now work with cli and plugman. suggest/request to add it to the list of platforms. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6532) cdvfile file url is not working with link tag like css
[
https://issues.apache.org/jira/browse/CB-6532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13983509#comment-13983509
]
Ian Clelland commented on CB-6532:
--
A couple more:
* {{cdvfile://localhost/test.css}} isn't a valid cdvfile URL -- I would have
expected either {{cdvfile://localhost/temporary/test.css}} or
{{cdvfile://localhost/persistent/test.css}}. Is this actually the URL you are
seeing?
* What version of the File plugin are you using? If it's 1.0.1 or less, then
try updating to version 1.1.0, released last week. The {{entry.toURL()}} method
should now be returning a {{file:///}} URL if at all possible, which should
work as the {{href}} attribute of a {{link}} tag.
cdvfile file url is not working with link tag like css
---
Key: CB-6532
URL: https://issues.apache.org/jira/browse/CB-6532
Project: Apache Cordova
Issue Type: Bug
Components: Plugin File, Plugin File Transfer
Affects Versions: 3.4.0
Environment: iOS 7
Reporter: Patrick Dürsteler
Priority: Critical
A css downloaded with xhr and created a local url
(cdvfile://localhost/test.css) with the File API can't be used as a
stylesheet.
{code}
var filename = test.css;
var imageURL = http://apache.org/css/style.css;;
requestFileSystem(TEMPORARY, 0, function(fileSystem) {
var ft = new FileTransfer();
ft.download(imageURL, fileSystem.root.toURL() + / + filename,
function(entry) {
var fileref=document.createElement(link);
fileref.setAttribute(rel, stylesheet);
fileref.setAttribute(type, text/css);
fileref.setAttribute(href, entry.toURL());
document.head.appendChild(imgElement);
});
});
{code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (CB-6539) WinJS versions needs update for Windows 8.1
[ https://issues.apache.org/jira/browse/CB-6539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aaron Newcomer updated CB-6539: --- Environment: (was: Visual Studio 2013 Ultimate) WinJS versions needs update for Windows 8.1 --- Key: CB-6539 URL: https://issues.apache.org/jira/browse/CB-6539 Project: Apache Cordova Issue Type: Bug Components: Windows 8 Affects Versions: 3.3.0, 3.4.0 Reporter: Aaron Newcomer Assignee: Jesse MacFadyen Priority: Critical Cordova attempts to add WinJS if not already loaded: https://github.com/apache/cordova-js/blob/master/src/windows8/platform.js But for Windows 8.1 apps, the WinJS version has been updated from 1.0 to 2.0, and so the path to base.js becomes incorrect. It's easy enough to update the path, but then 8.0 compatibility is broken. I suppose one could attempt to load both 1.0 *and* 2.0, but this would introduce a (non-crippling) runtime error for the file that couldn't be found. The Windows 8 template project would also need to be addressed for 8.1 compatibility: https://github.com/apache/cordova-windows/tree/master/windows8/template -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CB-6540) Error for creating a project inside its template is confusing
Josh Soref created CB-6540:
--
Summary: Error for creating a project inside its template is
confusing
Key: CB-6540
URL: https://issues.apache.org/jira/browse/CB-6540
Project: Apache Cordova
Issue Type: Bug
Components: CLI
Affects Versions: 3.4.0
Reporter: Josh Soref
Assignee: Josh Soref
If you pass the right magic template to cli.create:
{quote}
options = \{ id: id, name: name, lib: \{} };
options.lib.www = \{id: 'custom', version: '0', uri: path.resolve(template)}}
cordova.create(dir, null, null, options, function (err) {});
{quote}
You end up reaching this code path:
{quote}
if ( www_dir.indexOf(path.resolve(config_json.lib.www.uri)) === 0 ) \{
throw new CordovaError(
'Project must not be created inside the www assets dir.' +
'\nproject dir:\t' + dir +
'\nwww assets dir:\t' + config_json.lib.www.uri
);
}
{quote}
The output is:
{quote}
\{ name: 'CordovaError',
message: 'Project must not be created inside the www assets dir.\nproject
dir:\t/private/tmp/null/y\nwww assets dir:\t/private/tmp/null' }
{quote}
Amongst the many problems:
1. The \n's and \t's aren't actually being converted into newlines and tabs
2. The message is absolutely incomprehensible (even if it wasn't garbled up by
the encoded whitespace).
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CB-6506) RTC: Add support for OSX
[ https://issues.apache.org/jira/browse/CB-6506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13983530#comment-13983530 ] ASF GitHub Bot commented on CB-6506: Github user tripodsan commented on the pull request: https://github.com/apache/cordova-cli/pull/170#issuecomment-41612738 thanks @purplecabbage. there is already a `VERSION` file in the `CordovaLib` directory. do we need both? RTC: Add support for OSX Key: CB-6506 URL: https://issues.apache.org/jira/browse/CB-6506 Project: Apache Cordova Issue Type: Improvement Components: CLI, Plugman Affects Versions: 3.4.0 Reporter: Tobias Bocanegra Assignee: Tobias Bocanegra Priority: Minor The recently updated scripts and templates in cordova-osx now work with cli and plugman. suggest/request to add it to the list of platforms. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6506) RTC: Add support for OSX
[ https://issues.apache.org/jira/browse/CB-6506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13983534#comment-13983534 ] ASF GitHub Bot commented on CB-6506: Github user purplecabbage commented on the pull request: https://github.com/apache/cordova-cli/pull/170#issuecomment-41613278 yes, I see that now. Do not need both, although I am a little confused why iOS + OSX both have them in a lib folder while every other platform has it at the repo/platform root. @purplecabbage risingj.com On Mon, Apr 28, 2014 at 1:58 PM, Tobias Bocanegra notificati...@github.comwrote: thanks @purplecabbage https://github.com/purplecabbage. there is already a VERSION file in the CordovaLib directory. do we need both? — Reply to this email directly or view it on GitHubhttps://github.com/apache/cordova-cli/pull/170#issuecomment-41612738 . RTC: Add support for OSX Key: CB-6506 URL: https://issues.apache.org/jira/browse/CB-6506 Project: Apache Cordova Issue Type: Improvement Components: CLI, Plugman Affects Versions: 3.4.0 Reporter: Tobias Bocanegra Assignee: Tobias Bocanegra Priority: Minor The recently updated scripts and templates in cordova-osx now work with cli and plugman. suggest/request to add it to the list of platforms. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CB-6541) Move VERSION file to repository root
Tobias Bocanegra created CB-6541:
Summary: Move VERSION file to repository root
Key: CB-6541
URL: https://issues.apache.org/jira/browse/CB-6541
Project: Apache Cordova
Issue Type: Improvement
Reporter: Tobias Bocanegra
Assignee: Tobias Bocanegra
The {{VERSION}} file is currently located in {{CordovaLib}} where as all other
platforms have it in the root directory.
we should align this and move it there, too.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (CB-6541) Move VERSION file to repository root
[
https://issues.apache.org/jira/browse/CB-6541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tobias Bocanegra updated CB-6541:
-
Component/s: OSX
iOS
Move VERSION file to repository root
Key: CB-6541
URL: https://issues.apache.org/jira/browse/CB-6541
Project: Apache Cordova
Issue Type: Improvement
Components: iOS, OSX
Reporter: Tobias Bocanegra
Assignee: Tobias Bocanegra
The {{VERSION}} file is currently located in {{CordovaLib}} where as all
other platforms have it in the root directory.
we should align this and move it there, too.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CB-6506) RTC: Add support for OSX
[ https://issues.apache.org/jira/browse/CB-6506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13983540#comment-13983540 ] ASF GitHub Bot commented on CB-6506: Github user tripodsan commented on the pull request: https://github.com/apache/cordova-cli/pull/170#issuecomment-41613750 makes sense. I'll (re)move the one in CordovaLib later, and fixup the respective scripts see https://issues.apache.org/jira/browse/CB-6541 RTC: Add support for OSX Key: CB-6506 URL: https://issues.apache.org/jira/browse/CB-6506 Project: Apache Cordova Issue Type: Improvement Components: CLI, Plugman Affects Versions: 3.4.0 Reporter: Tobias Bocanegra Assignee: Tobias Bocanegra Priority: Minor The recently updated scripts and templates in cordova-osx now work with cli and plugman. suggest/request to add it to the list of platforms. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6541) Move VERSION file to repository root
[
https://issues.apache.org/jira/browse/CB-6541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13983544#comment-13983544
]
Shazron Abdullah commented on CB-6541:
--
There *might* be some scripts that rely on the existing location I think - but
none in the repos themselves. Probably in cordova-coho.
Move VERSION file to repository root
Key: CB-6541
URL: https://issues.apache.org/jira/browse/CB-6541
Project: Apache Cordova
Issue Type: Improvement
Components: iOS, OSX
Reporter: Tobias Bocanegra
Assignee: Tobias Bocanegra
The {{VERSION}} file is currently located in {{CordovaLib}} where as all
other platforms have it in the root directory.
we should align this and move it there, too.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Created] (CB-6542) Delay creating project until there's some chance that it will succeed
Josh Soref created CB-6542: -- Summary: Delay creating project until there's some chance that it will succeed Key: CB-6542 URL: https://issues.apache.org/jira/browse/CB-6542 Project: Apache Cordova Issue Type: Bug Components: CLI Affects Versions: 3.4.0 Reporter: Josh Soref Assignee: Josh Soref Right now, it's very easy to try to create a project, receive an error, and as a result have a seemingly empty project directory which will refuse to be used if you want to fix the arguments to create. This is more or less because we eagerly create the .cordova/config.json file instead of lazily creating it. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6542) Delay creating project until there's some chance that it will succeed
[ https://issues.apache.org/jira/browse/CB-6542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13983549#comment-13983549 ] ASF GitHub Bot commented on CB-6542: GitHub user jsoref opened a pull request: https://github.com/apache/cordova-cli/pull/174 CB-6542 Delay creating project until there's some chance that it will work You can merge this pull request into a Git repository by running: $ git pull https://github.com/blackberry/cordova-cli cb_6542 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cordova-cli/pull/174.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #174 commit 2e99a0d6bc306f91c8186e612355e938452416d7 Author: Josh Soref jso...@blackberry.com Date: 2014-04-28T21:13:10Z CB-6542 Delay creating project until there's some chance that it will succeed Delay creating project until there's some chance that it will succeed - Key: CB-6542 URL: https://issues.apache.org/jira/browse/CB-6542 Project: Apache Cordova Issue Type: Bug Components: CLI Affects Versions: 3.4.0 Reporter: Josh Soref Assignee: Josh Soref Right now, it's very easy to try to create a project, receive an error, and as a result have a seemingly empty project directory which will refuse to be used if you want to fix the arguments to create. This is more or less because we eagerly create the .cordova/config.json file instead of lazily creating it. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6452) Plugins Release Apr 16, 2014
[ https://issues.apache.org/jira/browse/CB-6452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13983577#comment-13983577 ] ASF subversion and git services commented on CB-6452: - Commit b9363d971629ff8d6306a0d491bc53675e4e1f55 in cordova-plugin-dialogs's branch refs/heads/dev from [~iclelland] [ https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-dialogs.git;h=b9363d9 ] CB-6452 Updated version and RELEASENOTES.md for release 0.2.7 Plugins Release Apr 16, 2014 Key: CB-6452 URL: https://issues.apache.org/jira/browse/CB-6452 Project: Apache Cordova Issue Type: Task Reporter: Ian Clelland Assignee: Ian Clelland Following steps at https://github.com/apache/cordova-coho/blob/master/docs/plugins-release-process.md -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6460) Update License Headers
[ https://issues.apache.org/jira/browse/CB-6460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13983576#comment-13983576 ] ASF subversion and git services commented on CB-6460: - Commit 9ccce8c3317d64e68719b9176d1f5a780e500395 in cordova-plugin-dialogs's branch refs/heads/dev from [~iclelland] [ https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-dialogs.git;h=9ccce8c ] CB-6460: Update license headers Update License Headers -- Key: CB-6460 URL: https://issues.apache.org/jira/browse/CB-6460 Project: Apache Cordova Issue Type: Sub-task Reporter: Ian Clelland Assignee: Ian Clelland Add proper licence headers to all files missing them. This should include all documentation and plugin.xml files, since they include some creative elements. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6452) Plugins Release Apr 16, 2014
[ https://issues.apache.org/jira/browse/CB-6452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13983578#comment-13983578 ] ASF subversion and git services commented on CB-6452: - Commit 2a071b833aa742409202ccf22b1e6f5c850be1ce in cordova-plugin-dialogs's branch refs/heads/dev from [~iclelland] [ https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-dialogs.git;h=2a071b8 ] CB-6452 Incremented plugin version on dev branch. Plugins Release Apr 16, 2014 Key: CB-6452 URL: https://issues.apache.org/jira/browse/CB-6452 Project: Apache Cordova Issue Type: Task Reporter: Ian Clelland Assignee: Ian Clelland Following steps at https://github.com/apache/cordova-coho/blob/master/docs/plugins-release-process.md -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6521) Merge plugin development branches into master
[ https://issues.apache.org/jira/browse/CB-6521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13983579#comment-13983579 ] ASF subversion and git services commented on CB-6521: - Commit 3d51112bd4a8ba7855fc0fbf1e41449638f3f97b in cordova-plugin-dialogs's branch refs/heads/dev from [~iclelland] [ https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-dialogs.git;h=3d51112 ] CB-6521: Remove development branch Merge plugin development branches into master - Key: CB-6521 URL: https://issues.apache.org/jira/browse/CB-6521 Project: Apache Cordova Issue Type: Task Components: Plugin Battery Status, Plugin Camera, Plugin Console, Plugin Contacts, Plugin Device, Plugin Device Motion, Plugin Device Orientation, Plugin File, Plugin File Transfer, Plugin Geolocation, Plugin Globalization, Plugin InAppBrowser, Plugin Media, Plugin Media Capture, Plugin Network Information, Plugin SplashScreen, Plugin Statusbar, Plugin Vibration Reporter: Ian Clelland Assignee: Ian Clelland Following the mailing list discussion, all plugins development is going to take place on the master branch. Any current work on the dev branches should be merged in to master. After things settle down, the dev branch names should be deleted to prevent any accidental branching. *Update*: The dev branch is not being deleted; instead, all of the files within it are being removed, and the README is being updated to indicate that development should proceed on the master branch. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6539) WinJS versions needs update for Windows 8.1
[ https://issues.apache.org/jira/browse/CB-6539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13983615#comment-13983615 ] ASF subversion and git services commented on CB-6539: - Commit c893a47254111e26d8b11f28972793491d83c4cf in cordova-js's branch refs/heads/master from [~purplecabbage] [ https://git-wip-us.apache.org/repos/asf?p=cordova-js.git;h=c893a47 ] CB-6539 Future proof the WinJS include WinJS versions needs update for Windows 8.1 --- Key: CB-6539 URL: https://issues.apache.org/jira/browse/CB-6539 Project: Apache Cordova Issue Type: Bug Components: Windows 8 Affects Versions: 3.3.0, 3.4.0 Reporter: Aaron Newcomer Assignee: Jesse MacFadyen Priority: Critical Cordova attempts to add WinJS if not already loaded: https://github.com/apache/cordova-js/blob/master/src/windows8/platform.js But for Windows 8.1 apps, the WinJS version has been updated from 1.0 to 2.0, and so the path to base.js becomes incorrect. It's easy enough to update the path, but then 8.0 compatibility is broken. I suppose one could attempt to load both 1.0 *and* 2.0, but this would introduce a (non-crippling) runtime error for the file that couldn't be found. The Windows 8 template project would also need to be addressed for 8.1 compatibility: https://github.com/apache/cordova-windows/tree/master/windows8/template -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CB-6539) WinJS versions needs update for Windows 8.1
[ https://issues.apache.org/jira/browse/CB-6539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse MacFadyen resolved CB-6539. - Resolution: Fixed Fix Version/s: 3.5.0 updated in cordova-js, and available in 3.5.0 Other 8.1 compatability issues will be resolved when we move to officially support 8.1 WinJS versions needs update for Windows 8.1 --- Key: CB-6539 URL: https://issues.apache.org/jira/browse/CB-6539 Project: Apache Cordova Issue Type: Bug Components: Windows 8 Affects Versions: 3.3.0, 3.4.0 Reporter: Aaron Newcomer Assignee: Jesse MacFadyen Priority: Critical Fix For: 3.5.0 Cordova attempts to add WinJS if not already loaded: https://github.com/apache/cordova-js/blob/master/src/windows8/platform.js But for Windows 8.1 apps, the WinJS version has been updated from 1.0 to 2.0, and so the path to base.js becomes incorrect. It's easy enough to update the path, but then 8.0 compatibility is broken. I suppose one could attempt to load both 1.0 *and* 2.0, but this would introduce a (non-crippling) runtime error for the file that couldn't be found. The Windows 8 template project would also need to be addressed for 8.1 compatibility: https://github.com/apache/cordova-windows/tree/master/windows8/template -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CB-5108) Create platform specific bootstrap for Windows 8.1
[ https://issues.apache.org/jira/browse/CB-5108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse MacFadyen resolved CB-5108. - Resolution: Fixed This has been addressed here: https://github.com/apache/cordova-js/commit/c893a47254111e26d8b11f28972793491d83c4cf Create platform specific bootstrap for Windows 8.1 -- Key: CB-5108 URL: https://issues.apache.org/jira/browse/CB-5108 Project: Apache Cordova Issue Type: Sub-task Components: CordovaJS, Windows 8 Reporter: Maxime LUCE Assignee: Maxime LUCE Parent : [CB-5107|https://issues.apache.org/jira/browse/CB-5107] Create a new bootstrap for Windows 8.1. This new bootstrap must use WinJS 2.0 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CB-6204) cordova run windows8 - fails - add test
[ https://issues.apache.org/jira/browse/CB-6204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse MacFadyen resolved CB-6204. - Resolution: Invalid This issue contains several other issues. - wp8 + windows8 build scripts cannot currently be shared as they live in separate repos - the 'eval' method presented as a solution is not reliable - msbuild is no longer a %PATH% requirement - running from the command line has been addressed cordova run windows8 - fails - add test --- Key: CB-6204 URL: https://issues.apache.org/jira/browse/CB-6204 Project: Apache Cordova Issue Type: Bug Components: Windows 8, WP8 Affects Versions: Master Environment: Windows 8.1 Reporter: Jonathan Bond Assignee: Jesse MacFadyen Fix For: 3.5.0 Running '.\tests\testRunProject', the application installs but fails to run. I added a 'lib\common.js' which would make it easier to re-use code. Some context, first noticed that 'msbuild' wasn't in my path so I was looking for a fix. I noticed windows8 is almost fixed but not wp8 (ideally could both share the 'common.js' code). - Installing package... Found dependency package(s): F:\Jonathan\GitHub\Cordova\gde\cordova-windows\windows8\tests\TestOutput\AppPackages\CordovaApp_1.0.0.0_AnyCPU_Debug_Test\Dependencies\Microsoft.WinJS.1.0.appx Success: Your package was successfully installed. powershell . .\\cordova\lib\WindowsStoreAppUtils.ps1; Start-Locally Cordova.Example ActivateApplication: ! Get-AppxPackageManifest : Cannot validate argument on parameter 'Package'. The argument is null or empty. Provide an argument that is not null or empty, and then try the command again. At F:\Jonathan\GitHub\Cordova\gde\cordova-windows\windows8\tests\TestOutput\cordova\lib\WindowsStoreAppUtils.ps1:108 char:41 + $manifest = Get-appxpackagemanifest $package + + CategoryInfo : InvalidData: (:) [Get-AppxPackageManifest], ParameterBindingValidationException + FullyQualifiedErrorId : ParameterArgumentValidationError,Microsoft.Windows.Appx.PackageManager.Commands.GetAppxPackageManifestCommand Exception calling ActivateApplication with 4 argument(s): Value does not fall within the expected range. At F:\Jonathan\GitHub\Cordova\gde\cordova-windows\windows8\tests\TestOutput\cordova\lib\WindowsStoreAppUtils.ps1:115 char:5 + $appActivator.ActivateApplication($applicationUserModelId,$null,[StoreAppRun ... + + CategoryInfo : NotSpecified: (:) [], MethodInvocationException + FullyQualifiedErrorId : ArgumentException powershell . .\\cordova\lib\WindowsStoreAppUtils.ps1; Start-Locally Cordova.Example -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6500) Cordova requires arm64 architecture
[ https://issues.apache.org/jira/browse/CB-6500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13983704#comment-13983704 ] ASF subversion and git services commented on CB-6500: - Commit ae075907595e6d11a421df74f0f3cbdcd34627d8 in cordova-ios's branch refs/heads/master from [~shazron] [ https://git-wip-us.apache.org/repos/asf?p=cordova-ios.git;h=ae07590 ] CB-6500 - Cordova requires arm64 architecture. Removes the conditional arches in CordovaLib, and removes VALID_ARCHS (relies on default). Cordova requires arm64 architecture --- Key: CB-6500 URL: https://issues.apache.org/jira/browse/CB-6500 Project: Apache Cordova Issue Type: Bug Components: CordovaJS, iOS Affects Versions: 3.4.0 Environment: OSX Reporter: Song Zheng Assignee: Shazron Abdullah In project settings, developers are now required to add arm64 under valid Architectures build settings. If we do not want to support arm64 or are unable to (because of other SDK dependency), our app will no longer work and get the following compile errors: undefined symbols for architecture armv7: _OBJC_CLASS_$_CDVPlugin, referenced from: _OBJC_CLASS_$_OpenTokPlugin in OpenTokPlugin.o _OBJC_METACLASS_$_CDVPlugin, referenced from: _OBJC_METACLASS_$_OpenTokPlugin in OpenTokPlugin.o ... To reproduce: 1. Create new project (Cordova create YourApp) 2. Add ios platform ( Cordova plaform add ios ) 3. Open xcode ( open YourApp/platform/ios/...xcodeproj ) 4. Change project build settings ( Valid Architectures to only armv7 - remove armv7s and arm64 ) 5. Change project build settings (Build Active Architecture Only - No ) Result: undefined symbol errors during compile time. This was a breaking change from Cordova v 3.4.0-0.1.3 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CB-6500) Cordova requires arm64 architecture
[ https://issues.apache.org/jira/browse/CB-6500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shazron Abdullah resolved CB-6500. -- Resolution: Fixed Fix Version/s: 3.5.0 Cordova requires arm64 architecture --- Key: CB-6500 URL: https://issues.apache.org/jira/browse/CB-6500 Project: Apache Cordova Issue Type: Bug Components: CordovaJS, iOS Affects Versions: 3.4.0 Environment: OSX Reporter: Song Zheng Assignee: Shazron Abdullah Fix For: 3.5.0 In project settings, developers are now required to add arm64 under valid Architectures build settings. If we do not want to support arm64 or are unable to (because of other SDK dependency), our app will no longer work and get the following compile errors: undefined symbols for architecture armv7: _OBJC_CLASS_$_CDVPlugin, referenced from: _OBJC_CLASS_$_OpenTokPlugin in OpenTokPlugin.o _OBJC_METACLASS_$_CDVPlugin, referenced from: _OBJC_METACLASS_$_OpenTokPlugin in OpenTokPlugin.o ... To reproduce: 1. Create new project (Cordova create YourApp) 2. Add ios platform ( Cordova plaform add ios ) 3. Open xcode ( open YourApp/platform/ios/...xcodeproj ) 4. Change project build settings ( Valid Architectures to only armv7 - remove armv7s and arm64 ) 5. Change project build settings (Build Active Architecture Only - No ) Result: undefined symbol errors during compile time. This was a breaking change from Cordova v 3.4.0-0.1.3 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6053) DirectoryEntry.getFile() fails for relative paths
[
https://issues.apache.org/jira/browse/CB-6053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13983808#comment-13983808
]
Jesse MacFadyen commented on CB-6053:
-
This has been addressed in CB-6017
By the time if (/\?|\\|\*|\||\|||\:|\//g.test(path)) is evaluated, we are
using 'path' to store the file-name only '\' and '/' are both not possible by
this point.
DirectoryEntry.getFile() fails for relative paths
-
Key: CB-6053
URL: https://issues.apache.org/jira/browse/CB-6053
Project: Apache Cordova
Issue Type: Bug
Components: Plugin File, Windows 8
Affects Versions: 3.3.0
Environment: Windows 8
Reporter: Stepan Riha
Assignee: Jesse MacFadyen
Fix For: 3.5.0
According to the spec, DirectoryEntry.getFile() is supposed to support
specifying a relative path. However, specifying a relative path (and
option.create=false) will cause the method to fail with
{{FileError.ENCODING_ERR}}.
The culprit seems to be following code in FileProxy.getFile() - it tests for
invalid *file _name_* characters but should really be testing invalid *file
_path_* characters (i.e. it should allow {{/}}).
{code:title=FileProxy.js}
if (/\?|\\|\*|\||\|||\:|\//g.test(path)) {
fail fail(FileError.ENCODING_ERR);
return;
}
{code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Resolved] (CB-6053) DirectoryEntry.getFile() fails for relative paths
[
https://issues.apache.org/jira/browse/CB-6053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesse MacFadyen resolved CB-6053.
-
Resolution: Fixed
Fix Version/s: 3.5.0
DirectoryEntry.getFile() fails for relative paths
-
Key: CB-6053
URL: https://issues.apache.org/jira/browse/CB-6053
Project: Apache Cordova
Issue Type: Bug
Components: Plugin File, Windows 8
Affects Versions: 3.3.0
Environment: Windows 8
Reporter: Stepan Riha
Assignee: Jesse MacFadyen
Fix For: 3.5.0
According to the spec, DirectoryEntry.getFile() is supposed to support
specifying a relative path. However, specifying a relative path (and
option.create=false) will cause the method to fail with
{{FileError.ENCODING_ERR}}.
The culprit seems to be following code in FileProxy.getFile() - it tests for
invalid *file _name_* characters but should really be testing invalid *file
_path_* characters (i.e. it should allow {{/}}).
{code:title=FileProxy.js}
if (/\?|\\|\*|\||\|||\:|\//g.test(path)) {
fail fail(FileError.ENCODING_ERR);
return;
}
{code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Resolved] (CB-6017) Windows8: Unable to get file entry using relative path
[
https://issues.apache.org/jira/browse/CB-6017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesse MacFadyen resolved CB-6017.
-
Resolution: Fixed
Fix Version/s: 3.5.0
Windows8: Unable to get file entry using relative path
--
Key: CB-6017
URL: https://issues.apache.org/jira/browse/CB-6017
Project: Apache Cordova
Issue Type: Bug
Components: Plugin File, Windows 8
Affects Versions: 3.1.0
Environment: Cordova 3.1.0
Windows 8.1
Reporter: Vijay Patil
Assignee: Jesse MacFadyen
Fix For: 3.5.0
I am unable to get the file entry using relative path containing directory on
windows 8.1 device. It works fine on android device.
e.g. -
{code}
dirEntry.getFile(directory1\\file1.txt, {create: false}, successCallback,
errorCallback);
{code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Created] (CB-6543) cordova/run fails when there is no custom_rules.xml
Ningxin Hu created CB-6543: -- Summary: cordova/run fails when there is no custom_rules.xml Key: CB-6543 URL: https://issues.apache.org/jira/browse/CB-6543 Project: Apache Cordova Issue Type: Bug Components: Android Affects Versions: Master Reporter: Ningxin Hu Reproduce steps: 1. create a project as cordova-android/bin/create hello 2. remove custom_rules.xml to build project to bin cd hello; rm custom_rules.xml; cordova/build 3. run hello cordova/run Step 3 will fail with error ERROR : unable to find project ant-build directory, could not locate .apk -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6543) cordova/run fails when there is no custom_rules.xml
[ https://issues.apache.org/jira/browse/CB-6543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13983863#comment-13983863 ] Ningxin Hu commented on CB-6543: It matters since some dependent project, such as Crosswalk WebView, only works with default output dir, say bin. cordova/run fails when there is no custom_rules.xml --- Key: CB-6543 URL: https://issues.apache.org/jira/browse/CB-6543 Project: Apache Cordova Issue Type: Bug Components: Android Affects Versions: Master Reporter: Ningxin Hu Reproduce steps: 1. create a project as cordova-android/bin/create hello 2. remove custom_rules.xml to build project to bin cd hello; rm custom_rules.xml; cordova/build 3. run hello cordova/run Step 3 will fail with error ERROR : unable to find project ant-build directory, could not locate .apk -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6543) cordova/run fails when there is no custom_rules.xml
[ https://issues.apache.org/jira/browse/CB-6543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13983868#comment-13983868 ] ASF GitHub Bot commented on CB-6543: Github user huningxin commented on the pull request: https://github.com/apache/cordova-android/pull/99#issuecomment-41634753 @agrieve, PTAL. Thanks! cordova/run fails when there is no custom_rules.xml --- Key: CB-6543 URL: https://issues.apache.org/jira/browse/CB-6543 Project: Apache Cordova Issue Type: Bug Components: Android Affects Versions: Master Reporter: Ningxin Hu Reproduce steps: 1. create a project as cordova-android/bin/create hello 2. remove custom_rules.xml to build project to bin cd hello; rm custom_rules.xml; cordova/build 3. run hello cordova/run Step 3 will fail with error ERROR : unable to find project ant-build directory, could not locate .apk -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6543) cordova/run fails when there is no custom_rules.xml
[ https://issues.apache.org/jira/browse/CB-6543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13983866#comment-13983866 ] ASF GitHub Bot commented on CB-6543: GitHub user huningxin opened a pull request: https://github.com/apache/cordova-android/pull/99 CB-6543: Fix cordova/run failure when no custom_rules.xml available. You can merge this pull request into a Git repository by running: $ git pull https://github.com/huningxin/cordova-android-1 fix_custome_rules Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cordova-android/pull/99.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #99 commit 167e82f3980bd10168f0bda144dcd6b32f944b9d Author: Ningxin Hu ningxin...@intel.com Date: 2014-04-24T08:05:42Z CB-6543: Fix cordova/run failure when no custom_rules.xml available. cordova/run fails when there is no custom_rules.xml --- Key: CB-6543 URL: https://issues.apache.org/jira/browse/CB-6543 Project: Apache Cordova Issue Type: Bug Components: Android Affects Versions: Master Reporter: Ningxin Hu Reproduce steps: 1. create a project as cordova-android/bin/create hello 2. remove custom_rules.xml to build project to bin cd hello; rm custom_rules.xml; cordova/build 3. run hello cordova/run Step 3 will fail with error ERROR : unable to find project ant-build directory, could not locate .apk -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CB-6544) Windows8 - Add preference SplashScreenBackgroundColor to config.xml
Jesse MacFadyen created CB-6544: --- Summary: Windows8 - Add preference SplashScreenBackgroundColor to config.xml Key: CB-6544 URL: https://issues.apache.org/jira/browse/CB-6544 Project: Apache Cordova Issue Type: Bug Components: Windows 8 Affects Versions: 3.4.0 Reporter: Jesse MacFadyen Assignee: Jesse MacFadyen Fix For: 3.5.0 Supported by the windows8 platform only ...? -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CB-6545) Windows8 can have more than one preference from config.xml
Jesse MacFadyen created CB-6545: --- Summary: Windows8 can have more than one preference from config.xml Key: CB-6545 URL: https://issues.apache.org/jira/browse/CB-6545 Project: Apache Cordova Issue Type: Bug Components: Windows 8 Affects Versions: 3.4.0 Reporter: Jesse MacFadyen Assignee: Jesse MacFadyen Fix For: 3.5.0 Previous fix added support for backgroundcolor preference, however, adding the splashscreen image preference has made it apparent that the existing code can only support 1 preference in the xml since the @name attribute is not even used. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CB-6545) Windows8 can have more than one preference from config.xml
[ https://issues.apache.org/jira/browse/CB-6545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse MacFadyen resolved CB-6545. - Resolution: Fixed Windows8 can have more than one preference from config.xml --- Key: CB-6545 URL: https://issues.apache.org/jira/browse/CB-6545 Project: Apache Cordova Issue Type: Bug Components: Windows 8 Affects Versions: 3.4.0 Reporter: Jesse MacFadyen Assignee: Jesse MacFadyen Fix For: 3.5.0 Previous fix added support for backgroundcolor preference, however, adding the splashscreen image preference has made it apparent that the existing code can only support 1 preference in the xml since the @name attribute is not even used. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CB-6309) Windows8. Add Splash Screen img support via config.xml preference
[ https://issues.apache.org/jira/browse/CB-6309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse MacFadyen resolved CB-6309. - Resolution: Fixed Windows8. Add Splash Screen img support via config.xml preference - Key: CB-6309 URL: https://issues.apache.org/jira/browse/CB-6309 Project: Apache Cordova Issue Type: Improvement Components: CLI, Windows 8 Reporter: Sergey Grebnov Assignee: Jesse MacFadyen Right now there is no way to specify new splash screen image for Windows8 via config.xml. Propose to implement this as Android does - via special preference preference name=SplashScreen value=value / http://cordova.apache.org/docs/en/3.4.0/config_ref_images.md.html#Icons%20and%20Splash%20Screens_splash_screens_for_the_android_platform -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6544) Windows8 - Add preference SplashScreenBackgroundColor to config.xml
[ https://issues.apache.org/jira/browse/CB-6544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13983879#comment-13983879 ] ASF subversion and git services commented on CB-6544: - Commit 83c42726510fdc7ea46a418a0d2cb366e5ee807a in cordova-windows's branch refs/heads/master from [~purplecabbage] [ https://git-wip-us.apache.org/repos/asf?p=cordova-windows.git;h=83c4272 ] CB-6309 Windows8. Add Splash Screen img support via config.xml preference, CB-6544 SplashScreenBackgroundColor, CB-6545 support multiple preferences Windows8 - Add preference SplashScreenBackgroundColor to config.xml --- Key: CB-6544 URL: https://issues.apache.org/jira/browse/CB-6544 Project: Apache Cordova Issue Type: Bug Components: Windows 8 Affects Versions: 3.4.0 Reporter: Jesse MacFadyen Assignee: Jesse MacFadyen Fix For: 3.5.0 Supported by the windows8 platform only ...? -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CB-6544) Windows8 - Add preference SplashScreenBackgroundColor to config.xml
[ https://issues.apache.org/jira/browse/CB-6544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse MacFadyen resolved CB-6544. - Resolution: Fixed Windows8 - Add preference SplashScreenBackgroundColor to config.xml --- Key: CB-6544 URL: https://issues.apache.org/jira/browse/CB-6544 Project: Apache Cordova Issue Type: Bug Components: Windows 8 Affects Versions: 3.4.0 Reporter: Jesse MacFadyen Assignee: Jesse MacFadyen Fix For: 3.5.0 Supported by the windows8 platform only ...? -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6545) Windows8 can have more than one preference from config.xml
[ https://issues.apache.org/jira/browse/CB-6545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13983880#comment-13983880 ] ASF subversion and git services commented on CB-6545: - Commit 83c42726510fdc7ea46a418a0d2cb366e5ee807a in cordova-windows's branch refs/heads/master from [~purplecabbage] [ https://git-wip-us.apache.org/repos/asf?p=cordova-windows.git;h=83c4272 ] CB-6309 Windows8. Add Splash Screen img support via config.xml preference, CB-6544 SplashScreenBackgroundColor, CB-6545 support multiple preferences Windows8 can have more than one preference from config.xml --- Key: CB-6545 URL: https://issues.apache.org/jira/browse/CB-6545 Project: Apache Cordova Issue Type: Bug Components: Windows 8 Affects Versions: 3.4.0 Reporter: Jesse MacFadyen Assignee: Jesse MacFadyen Fix For: 3.5.0 Previous fix added support for backgroundcolor preference, however, adding the splashscreen image preference has made it apparent that the existing code can only support 1 preference in the xml since the @name attribute is not even used. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6309) Windows8. Add Splash Screen img support via config.xml preference
[ https://issues.apache.org/jira/browse/CB-6309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13983878#comment-13983878 ] ASF subversion and git services commented on CB-6309: - Commit 83c42726510fdc7ea46a418a0d2cb366e5ee807a in cordova-windows's branch refs/heads/master from [~purplecabbage] [ https://git-wip-us.apache.org/repos/asf?p=cordova-windows.git;h=83c4272 ] CB-6309 Windows8. Add Splash Screen img support via config.xml preference, CB-6544 SplashScreenBackgroundColor, CB-6545 support multiple preferences Windows8. Add Splash Screen img support via config.xml preference - Key: CB-6309 URL: https://issues.apache.org/jira/browse/CB-6309 Project: Apache Cordova Issue Type: Improvement Components: CLI, Windows 8 Reporter: Sergey Grebnov Assignee: Jesse MacFadyen Right now there is no way to specify new splash screen image for Windows8 via config.xml. Propose to implement this as Android does - via special preference preference name=SplashScreen value=value / http://cordova.apache.org/docs/en/3.4.0/config_ref_images.md.html#Icons%20and%20Splash%20Screens_splash_screens_for_the_android_platform -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6541) Move VERSION file to repository root
[
https://issues.apache.org/jira/browse/CB-6541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13983909#comment-13983909
]
Andrew Grieve commented on CB-6541:
---
In cordova-cli as well.
Move VERSION file to repository root
Key: CB-6541
URL: https://issues.apache.org/jira/browse/CB-6541
Project: Apache Cordova
Issue Type: Improvement
Components: iOS, OSX
Reporter: Tobias Bocanegra
Assignee: Tobias Bocanegra
The {{VERSION}} file is currently located in {{CordovaLib}} where as all
other platforms have it in the root directory.
we should align this and move it there, too.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CB-6543) cordova/run fails when there is no custom_rules.xml
[ https://issues.apache.org/jira/browse/CB-6543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13983921#comment-13983921 ] ASF subversion and git services commented on CB-6543: - Commit e6adbb0e42c19be3f8c627359079c256b33931c8 in cordova-android's branch refs/heads/master from [~ningxinhu] [ https://git-wip-us.apache.org/repos/asf?p=cordova-android.git;h=e6adbb0 ] CB-6543 Fix cordova/run failure when no custom_rules.xml available Github: Close #99 cordova/run fails when there is no custom_rules.xml --- Key: CB-6543 URL: https://issues.apache.org/jira/browse/CB-6543 Project: Apache Cordova Issue Type: Bug Components: Android Affects Versions: Master Reporter: Ningxin Hu Reproduce steps: 1. create a project as cordova-android/bin/create hello 2. remove custom_rules.xml to build project to bin cd hello; rm custom_rules.xml; cordova/build 3. run hello cordova/run Step 3 will fail with error ERROR : unable to find project ant-build directory, could not locate .apk -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6543) cordova/run fails when there is no custom_rules.xml
[ https://issues.apache.org/jira/browse/CB-6543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13983922#comment-13983922 ] ASF GitHub Bot commented on CB-6543: Github user agrieve commented on the pull request: https://github.com/apache/cordova-android/pull/99#issuecomment-41637291 LGTM! Thanks! I've merged it in. cordova/run fails when there is no custom_rules.xml --- Key: CB-6543 URL: https://issues.apache.org/jira/browse/CB-6543 Project: Apache Cordova Issue Type: Bug Components: Android Affects Versions: Master Reporter: Ningxin Hu Reproduce steps: 1. create a project as cordova-android/bin/create hello 2. remove custom_rules.xml to build project to bin cd hello; rm custom_rules.xml; cordova/build 3. run hello cordova/run Step 3 will fail with error ERROR : unable to find project ant-build directory, could not locate .apk -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CB-6543) cordova/run fails when there is no custom_rules.xml
[ https://issues.apache.org/jira/browse/CB-6543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Grieve resolved CB-6543. --- Resolution: Fixed Fixed in 3.5.0-dev cordova/run fails when there is no custom_rules.xml --- Key: CB-6543 URL: https://issues.apache.org/jira/browse/CB-6543 Project: Apache Cordova Issue Type: Bug Components: Android Affects Versions: Master Reporter: Ningxin Hu Reproduce steps: 1. create a project as cordova-android/bin/create hello 2. remove custom_rules.xml to build project to bin cd hello; rm custom_rules.xml; cordova/build 3. run hello cordova/run Step 3 will fail with error ERROR : unable to find project ant-build directory, could not locate .apk -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6543) cordova/run fails when there is no custom_rules.xml
[ https://issues.apache.org/jira/browse/CB-6543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13983924#comment-13983924 ] ASF GitHub Bot commented on CB-6543: Github user asfgit closed the pull request at: https://github.com/apache/cordova-android/pull/99 cordova/run fails when there is no custom_rules.xml --- Key: CB-6543 URL: https://issues.apache.org/jira/browse/CB-6543 Project: Apache Cordova Issue Type: Bug Components: Android Affects Versions: Master Reporter: Ningxin Hu Reproduce steps: 1. create a project as cordova-android/bin/create hello 2. remove custom_rules.xml to build project to bin cd hello; rm custom_rules.xml; cordova/build 3. run hello cordova/run Step 3 will fail with error ERROR : unable to find project ant-build directory, could not locate .apk -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CB-6546) Support allowEdit option on Android Camera
Andrew Grieve created CB-6546: - Summary: Support allowEdit option on Android Camera Key: CB-6546 URL: https://issues.apache.org/jira/browse/CB-6546 Project: Apache Cordova Issue Type: Improvement Components: Plugin Camera Reporter: Andrew Grieve Assignee: Andrew Grieve Priority: Minor Via pull request: https://github.com/apache/cordova-plugin-camera/pull/12 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6525) download success callback not called in 0.4.3
[ https://issues.apache.org/jira/browse/CB-6525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13983994#comment-13983994 ] Florence Foo commented on CB-6525: -- I am encountering the same problem for iOS. Upload callback is fine but download doesn't callback after successfully downloaded the file. download success callback not called in 0.4.3 - Key: CB-6525 URL: https://issues.apache.org/jira/browse/CB-6525 Project: Apache Cordova Issue Type: Bug Components: Plugin File Transfer Affects Versions: 3.4.0 Environment: Cordova 3.4.1 iOS 0.4.3 of the file transfer plugin Reporter: AH I've noticed that the success callback doesn't get executed after a download is successfully completed. Specifically, if success contains a console.log, nothing is logged to the Xcode debugger even though the download has completed successfully. I can tell that the download was completed because the following message is logged in Xcode: File Transfer Finished with response code 200 transfer.download(src, localPath, success, error); I think this is an issue with version 0.4.3 of the file transfer plugin. Version 0.4.2 of the plugin running on Cordova 3.4.1 didn't have this bug. I found another possible report of this bug: http://stackoverflow.com/questions/23240807/cant-setmetadata-while-downloading-files-via-filetransfer-download-in-ios-in-ph -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Comment Edited] (CB-6525) download success callback not called in 0.4.3
[ https://issues.apache.org/jira/browse/CB-6525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13983994#comment-13983994 ] Florence Foo edited comment on CB-6525 at 4/29/14 4:45 AM: --- I am encountering the same problem for iOS on FileTransfer plugin 0.4.3. Upload callback is fine but download doesn't callback after successfully downloaded the file. was (Author: flofoo): I am encountering the same problem for iOS. Upload callback is fine but download doesn't callback after successfully downloaded the file. download success callback not called in 0.4.3 - Key: CB-6525 URL: https://issues.apache.org/jira/browse/CB-6525 Project: Apache Cordova Issue Type: Bug Components: Plugin File Transfer Affects Versions: 3.4.0 Environment: Cordova 3.4.1 iOS 0.4.3 of the file transfer plugin Reporter: AH I've noticed that the success callback doesn't get executed after a download is successfully completed. Specifically, if success contains a console.log, nothing is logged to the Xcode debugger even though the download has completed successfully. I can tell that the download was completed because the following message is logged in Xcode: File Transfer Finished with response code 200 transfer.download(src, localPath, success, error); I think this is an issue with version 0.4.3 of the file transfer plugin. Version 0.4.2 of the plugin running on Cordova 3.4.1 didn't have this bug. I found another possible report of this bug: http://stackoverflow.com/questions/23240807/cant-setmetadata-while-downloading-files-via-filetransfer-download-in-ios-in-ph -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6546) Support allowEdit option on Android Camera
[ https://issues.apache.org/jira/browse/CB-6546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13984000#comment-13984000 ] ASF subversion and git services commented on CB-6546: - Commit c7d88e8b34f51919dbc2d1e2ed9ff1abcc58737d in cordova-plugin-camera's branch refs/heads/master from [~agrieve] [ https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-camera.git;h=c7d88e8 ] CB-6546 android: Add support for allowEdit Camera option GitHub: Close #12 Support allowEdit option on Android Camera -- Key: CB-6546 URL: https://issues.apache.org/jira/browse/CB-6546 Project: Apache Cordova Issue Type: Improvement Components: Plugin Camera Reporter: Andrew Grieve Assignee: Andrew Grieve Priority: Minor Via pull request: https://github.com/apache/cordova-plugin-camera/pull/12 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6546) Support allowEdit option on Android Camera
[ https://issues.apache.org/jira/browse/CB-6546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13984001#comment-13984001 ] ASF subversion and git services commented on CB-6546: - Commit d899d7a4b814c7a0bcbadba42f9d93ff2f26fab4 in cordova-plugin-camera's branch refs/heads/master from [~agrieve] [ https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-camera.git;h=d899d7a ] CB-6546 android: Fix a couple bugs with allowEdit pull request - Don't set width/height when they are not specified - photolibrary returns null from getData when image is cropped Support allowEdit option on Android Camera -- Key: CB-6546 URL: https://issues.apache.org/jira/browse/CB-6546 Project: Apache Cordova Issue Type: Improvement Components: Plugin Camera Reporter: Andrew Grieve Assignee: Andrew Grieve Priority: Minor Via pull request: https://github.com/apache/cordova-plugin-camera/pull/12 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CB-6546) Support allowEdit option on Android Camera
[ https://issues.apache.org/jira/browse/CB-6546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Grieve resolved CB-6546. --- Resolution: Fixed Included in 0.2.10-dev Note that this uses an undocumented Intent. Likely we'll get bugs about this not working on all phones. http://commonsware.com/blog/2013/01/23/no-android-does-not-have-crop-intent.html Support allowEdit option on Android Camera -- Key: CB-6546 URL: https://issues.apache.org/jira/browse/CB-6546 Project: Apache Cordova Issue Type: Improvement Components: Plugin Camera Reporter: Andrew Grieve Assignee: Andrew Grieve Priority: Minor Via pull request: https://github.com/apache/cordova-plugin-camera/pull/12 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CB-6547) wireless setting launcher plugin for android
okeke johnmary created CB-6547: --- Summary: wireless setting launcher plugin for android Key: CB-6547 URL: https://issues.apache.org/jira/browse/CB-6547 Project: Apache Cordova Issue Type: New Feature Reporter: okeke johnmary -- This message was sent by Atlassian JIRA (v6.2#6252)
