[jira] [Created] (CB-5228) beep not on windows phone8
puchen created CB-5228: -- Summary: beep not on windows phone8 Key: CB-5228 URL: https://issues.apache.org/jira/browse/CB-5228 Project: Apache Cordova Issue Type: Bug Components: Plugin Dialogs Affects Versions: 3.1.0 Environment: windows phone8 Reporter: puchen cordova-plugin-dialogs\test\notification\index.html beep test case not work! I found it's cause by not found resource notification-beep.wav. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-5122) Document supported workflows
[
https://issues.apache.org/jira/browse/CB-5122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13809023#comment-13809023
]
Mike Billau commented on CB-5122:
-
Hi Mike, thanks. I've started the first pass here:
https://github.com/apache/cordova-docs/pull/140
The only summary I have of the trade-offs is that huge thread:
http://callback.markmail.org/thread/5nr7dgkquse4gdkl
I was just going to explain the differences in the workflows at first and
encourage people to learn about both. Maybe later we can add a pros/cons
table that we can expand on as we discover them...the only problem with this is
that one person's pro is another person's con!
Regarding merges information, I reread everything and actually I think you're
right, the merges section on the Guide is pretty complete - I might change the
heading to Customize Each Platform via /merges/ just to make it easier for
people trying to see what that folder is for. However I think that this
highlights a bigger issue: that the README.md files and the various Guides
sometimes have conflicting information. I wanted to create a new JIRA item to
collapse the readme.md's into the guides - what do you think about this?
Document supported workflows
Key: CB-5122
URL: https://issues.apache.org/jira/browse/CB-5122
Project: Apache Cordova
Issue Type: Bug
Components: Docs
Affects Versions: 3.1.0
Reporter: Mike Billau
Assignee: Mike Sierra
Based on the recent discussion here [1]we should document the two different
supported Cordova workflows: using the CLI, and using plugman and bin
scripts.
Some of this documentation already exists but needs to be clarified and
improved:
{{Overview guide -- Development Paths section}}. This talks about getting
started with the CLI and then mentions that you can switch to the
platform-specific SDK tools. This section should be rewritten to make it
clear that there are two distinct workflows, and that both are okay and
supported. It could list out some pros and cons of each workflow (I'm sure we
won't have any trouble finding those ;)). It should be prescriptive in that
users should be following one of the two workflows, but it shouldn't make any
statements about which is better.
{{The Command-line Interface guide}} -- The CLI workflow guide. It
generally looks complete except for some missing functionality that is
documented in the CLI's README.md file (tests, hooks, some commands (serve),
some merges info).
{{Platform Guides -- (Platform) -- (Platform) Command-line tools}} -- Each
platform has a Command-line tools doc that explains all of the command line
tools for that project and how to use them. We need to go through these
guides and verify that they are up to date and include all of the lower level
command line tools and scripts. It should read like a tutorial in the same
way that the Command-line Interface guide does.
{{Using Plugman to Manage Plugins}} First, this guide needs to get exposed;
I can't find any way to get to this guide from the docs and even had to ask a
user how she managed to find it (a link from Plugman's readme!). This guide
needs to be expanded quite a bit; we can probably fold most/all of Plugman's
README.md file into this guide since it will be platform agnostic.
I think those are the only pieces in the docs that need to be changed.
[1] http://callback.markmail.org/thread/5nr7dgkquse4gdkl
[2]
http://cordova.apache.org/docs/en/edge/guide_overview_index.md.html#Overview
[3] http://cordova.apache.org/docs/en/edge/plugin_ref_plugman.md.html
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (CB-5122) Document supported workflows
[
https://issues.apache.org/jira/browse/CB-5122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13809030#comment-13809030
]
Marcel Kinard commented on CB-5122:
---
+1 on collapsing the README.md's into the guides. More specifically, I like the
idea that the docs for Cordova consumers (app developers) should be in
cordova-docs, and the docs for Cordova committers (us) could be in the
README.md's.
Document supported workflows
Key: CB-5122
URL: https://issues.apache.org/jira/browse/CB-5122
Project: Apache Cordova
Issue Type: Bug
Components: Docs
Affects Versions: 3.1.0
Reporter: Mike Billau
Assignee: Mike Sierra
Based on the recent discussion here [1]we should document the two different
supported Cordova workflows: using the CLI, and using plugman and bin
scripts.
Some of this documentation already exists but needs to be clarified and
improved:
{{Overview guide -- Development Paths section}}. This talks about getting
started with the CLI and then mentions that you can switch to the
platform-specific SDK tools. This section should be rewritten to make it
clear that there are two distinct workflows, and that both are okay and
supported. It could list out some pros and cons of each workflow (I'm sure we
won't have any trouble finding those ;)). It should be prescriptive in that
users should be following one of the two workflows, but it shouldn't make any
statements about which is better.
{{The Command-line Interface guide}} -- The CLI workflow guide. It
generally looks complete except for some missing functionality that is
documented in the CLI's README.md file (tests, hooks, some commands (serve),
some merges info).
{{Platform Guides -- (Platform) -- (Platform) Command-line tools}} -- Each
platform has a Command-line tools doc that explains all of the command line
tools for that project and how to use them. We need to go through these
guides and verify that they are up to date and include all of the lower level
command line tools and scripts. It should read like a tutorial in the same
way that the Command-line Interface guide does.
{{Using Plugman to Manage Plugins}} First, this guide needs to get exposed;
I can't find any way to get to this guide from the docs and even had to ask a
user how she managed to find it (a link from Plugman's readme!). This guide
needs to be expanded quite a bit; we can probably fold most/all of Plugman's
README.md file into this guide since it will be platform agnostic.
I think those are the only pieces in the docs that need to be changed.
[1] http://callback.markmail.org/thread/5nr7dgkquse4gdkl
[2]
http://cordova.apache.org/docs/en/edge/guide_overview_index.md.html#Overview
[3] http://cordova.apache.org/docs/en/edge/plugin_ref_plugman.md.html
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Assigned] (CB-5137) docs should describe how to build Cordova from Apache dist
[ https://issues.apache.org/jira/browse/CB-5137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Kinard reassigned CB-5137: - Assignee: Marcel Kinard docs should describe how to build Cordova from Apache dist -- Key: CB-5137 URL: https://issues.apache.org/jira/browse/CB-5137 Project: Apache Cordova Issue Type: Improvement Components: Docs Reporter: Marcel Kinard Assignee: Marcel Kinard Priority: Minor The docs seem to assume that Cordova was already downloaded either via npm or from a PhoneGap distribution or similar. Though the Apache Way is to distribute source code, it isn't clear to the average consumer in the docs how to get Cordova up and running from either the source zips on dist.apache.org or from the repos at git-wip-us.apache.org. This documentation should be added, perhaps as a section such as How to Obtain Cordova and/or How to Build Cordova from Source. There may be additional docs needed that describe how to bootstrap the docs (build the html from the md) if for some reason the user can't get them online at cordova.apache.org/docs. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-5214) Make mobile spec tests on WP8 to run w/o user interaction
[ https://issues.apache.org/jira/browse/CB-5214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13809137#comment-13809137 ] Sergey Grebnov commented on CB-5214: + separate pull request to contacts repo https://github.com/apache/cordova-plugin-contacts/pull/11 Make mobile spec tests on WP8 to run w/o user interaction - Key: CB-5214 URL: https://issues.apache.org/jira/browse/CB-5214 Project: Apache Cordova Issue Type: Improvement Components: mobile-spec, WP8 Reporter: Sergey Grebnov Assignee: Jesse MacFadyen Mobile spec autotests include tests which require user interaction to complete. For example, contact save api requires user to manually click on save button. This prevents the tests to be run as part of Medic test automation since test app just hangs on such api calls. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-5213) navigation.connection.type
[
https://issues.apache.org/jira/browse/CB-5213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13809141#comment-13809141
]
Janko Vukotic commented on CB-5213:
---
?xml version='1.0' encoding='utf-8'?
widget id=io.cordova.helloCordova version=2.0.0
xmlns=http://www.w3.org/ns/widgets;
nameHello Cordova/name
description
A sample Apache Cordova application that responds to the deviceready
event.
/description
author email=d...@cordova.apache.org href=http://cordova.io;
Apache Cordova Team
/author
access origin=* /
content src=index.html /
preference name=loglevel value=DEBUG /
feature name=App
param name=android-package value=org.apache.cordova.App /
/feature
feature name=NetworkStatus
param name=android-package value=org.apache.cordova.NetworkManager
/
/feature
feature name=InAppBrowser
param name=android-package
value=org.apache.cordova.inappbrowser.InAppBrowser /
/feature
/widget
navigation.connection.type
--
Key: CB-5213
URL: https://issues.apache.org/jira/browse/CB-5213
Project: Apache Cordova
Issue Type: Bug
Components: Android
Affects Versions: 3.1.0
Environment: Tested on Androids: Samsung Galaxy SII(4.1.2) and
Samsung Galaxy SIII (4.1.2)
Reporter: Janko Vukotic
Hi,
even with a dummy template code it wont work. I get this in Web console
Error initializing Network Connection: Class not found:85
I installed the plugin via plugman.
Here is the dummy code: (it alerts unknown in any case whether there is any
type of data connection or none)
!DOCTYPE HTML
html
head
script type=text/javascript charset=utf-8 src=cordova.js/script
script type=text/javascript charset=utf-8
var deviceInfo = function(){
alert(navigator.connection.type);
}
function init(){
document.addEventListener(deviceready, deviceInfo, true);
}
/script
/head
body onload=init();
/body
/html
Cheers!
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Created] (CB-5229) cordova/emulate important improvements (stderr, check ios-sim before build)
Shazron Abdullah created CB-5229: Summary: cordova/emulate important improvements (stderr, check ios-sim before build) Key: CB-5229 URL: https://issues.apache.org/jira/browse/CB-5229 Project: Apache Cordova Issue Type: Bug Components: iOS Affects Versions: Master Reporter: Shazron Abdullah Fix For: 3.2.0 1. Error messages should pipe to stderr instead of stdout. The CLI only prints out stderr messages on error 2. The ios-sim binary and version checks should happen before the build happens to prevent an unncessary build -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-5213) navigation.connection.type
[
https://issues.apache.org/jira/browse/CB-5213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13809213#comment-13809213
]
Joe Bowser commented on CB-5213:
That looks correct. Can you check your project to see if the java files
actually got installed. I can't reproduce the error on my end, but I'm
currently away from my Galaxy SII and Galaxy SIII at the moment. I think
there's some issue with the plugin actually getting installed.
navigation.connection.type
--
Key: CB-5213
URL: https://issues.apache.org/jira/browse/CB-5213
Project: Apache Cordova
Issue Type: Bug
Components: Android
Affects Versions: 3.1.0
Environment: Tested on Androids: Samsung Galaxy SII(4.1.2) and
Samsung Galaxy SIII (4.1.2)
Reporter: Janko Vukotic
Hi,
even with a dummy template code it wont work. I get this in Web console
Error initializing Network Connection: Class not found:85
I installed the plugin via plugman.
Here is the dummy code: (it alerts unknown in any case whether there is any
type of data connection or none)
!DOCTYPE HTML
html
head
script type=text/javascript charset=utf-8 src=cordova.js/script
script type=text/javascript charset=utf-8
var deviceInfo = function(){
alert(navigator.connection.type);
}
function init(){
document.addEventListener(deviceready, deviceInfo, true);
}
/script
/head
body onload=init();
/body
/html
Cheers!
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Resolved] (CB-3802) General Configuration Guide has incorrect config.xml
[
https://issues.apache.org/jira/browse/CB-3802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Billau resolved CB-3802.
-
Resolution: Fixed
I'm pretty sure this can be closed. I went through all of the API's and
verified the docs (for Android) had the correct XML and permissions:
https://issues.apache.org/jira/browse/CB-5005
General Configuration Guide has incorrect config.xml
Key: CB-3802
URL: https://issues.apache.org/jira/browse/CB-3802
Project: Apache Cordova
Issue Type: Bug
Components: Docs
Reporter: Joe Bowser
Assignee: Michael Brooks
The XML format for plugins is wrong. I'm not sure how it works across
platfomrs, but for Android it should be:
{code}
feature name=FeatureName
param name=android-package value=android.class.name /
/feature
{code}
I'm guessing it's similar on iOS, but I want to make sure it's right, which
is why I'm creating the ticket instead of just editing it on the spot.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Assigned] (CB-4390) Android Command-line Tools Section is missing few commands
[ https://issues.apache.org/jira/browse/CB-4390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Billau reassigned CB-4390: --- Assignee: Mike Billau (was: Sharif Ahmed) Android Command-line Tools Section is missing few commands -- Key: CB-4390 URL: https://issues.apache.org/jira/browse/CB-4390 Project: Apache Cordova Issue Type: Bug Components: Docs Affects Versions: 3.0.0 Reporter: Sharif Ahmed Assignee: Mike Billau Priority: Minor In the Android Command-line Tools Section the following commands documentation are missing: /bin/check_reqs /bin/update [path] /cordova/version The above are present in README but has not been update in the doc. Also, Cleaning font size is smaller than the rest. This also needs a fix. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (CB-5230) Cordova run never completes
Rick Gommers created CB-5230: Summary: Cordova run never completes Key: CB-5230 URL: https://issues.apache.org/jira/browse/CB-5230 Project: Apache Cordova Issue Type: Bug Components: Android, App Hello World, CLI Affects Versions: 3.1.0 Reporter: Rick Gommers Cordova run android command will never finish. Even with a newly created hello world app. What can I do about this? -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CB-4285) Windows cordova emulate command doesn't install project
[ https://issues.apache.org/jira/browse/CB-4285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser updated CB-4285: --- Can we clean this up? I think the initial issue has been resolved, but there may be other issues here. I haven't been able to reproduce this on Mac OS or Windows 7 Windows cordova emulate command doesn't install project --- Key: CB-4285 URL: https://issues.apache.org/jira/browse/CB-4285 Project: Apache Cordova Issue Type: Bug Components: Android, CLI Environment: Windows 7 Reporter: Lisa Seacat DeLuca Assignee: Braden Shepherdson I am able to add the android platform to a test cordova cli project and build just fine. When i go to run on an emulator the emulator opens but the project is never installed. This is the very simple case, no plugins were added. C:\workspaces\cordovacli\helloworldcordova -d emulate android cordova library for android already exists. No need to download. Continuing. Wrote out Android application name to helloworld Wrote out Android package name to com.helloworld Calling plugman.prepare for platform android Preparing android project... Processing configuration changes for plugins. Iterating over installed plugins: [] Writing out cordova_plugins.js... Running on emulator for platform android via command C:\workspaces\cordovacli\helloworld\platforms\android\cordova\run --emulator (output to fol low)... -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Comment Edited] (CB-5027) Application Error: There was a network error.
[ https://issues.apache.org/jira/browse/CB-5027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13801047#comment-13801047 ] Joe Bowser edited comment on CB-5027 at 10/30/13 4:08 PM: -- The emulator on Windows is far too slow to run this on startup. This use case is clearly not practical for anyone who uses Windows for development, especially since the Android Emulator is limited to 768 MB of RAM. I doubt that this will ever be fixed, and instead it makes sense to use the AVD manager to start the emulator first, then deploy to it using cordova run. was (Author: bowserj): The emulator on Windows is far too slow to run this on startup. This use case is clearly not practical for anyone who uses Windows for development, especially since the Android Emulator is limited to 768 MB of RAM. I doubt that this will ever be fixed, and instead it makes sense to use the AVD manager to start the emulator first, then deploy to it using cordova emulate android. Application Error: There was a network error. - Key: CB-5027 URL: https://issues.apache.org/jira/browse/CB-5027 Project: Apache Cordova Issue Type: Bug Components: Android, App Hello World, CLI Affects Versions: 3.1.0 Environment: Windows7 Reporter: Paulo Pacheco Labels: android, cordova-cli, emulate, error 1 - Install Cordova CLI 3.1.0 2 - cordova create model org,sample ModelApp 3- cordova platform add android 4- cordova build -d android 5- cordova emulate android Error in LogCat: E/CordovaWebView(3677): CordovaWebView: TIMEOUT ERROR! Error in Emulator: There was a network error. (file:///android_asset/www/index.html) Tree of project: ├───.cordova │ └───hooks │ ├───after_build │ ├───after_compile │ ├───after_docs │ ├───after_emulate │ ├───after_platform_add │ ├───after_platform_ls │ ├───after_platform_rm │ ├───after_plugin_add │ ├───after_plugin_ls │ ├───after_plugin_rm │ ├───after_prepare │ ├───after_run │ ├───before_build │ ├───before_compile │ ├───before_docs │ ├───before_emulate │ ├───before_platform_add │ ├───before_platform_ls │ ├───before_platform_rm │ ├───before_plugin_add │ ├───before_plugin_ls │ ├───before_plugin_rm │ ├───before_prepare │ └───before_run ├───merges │ └───android ├───platforms │ └───android │ ├───assets │ │ └───www │ │ └───cordova-app-hello-world-3.1.0-5683220 │ │ └───www │ │ ├───css │ │ ├───img │ │ ├───js │ │ └───res │ │ ├───icon │ │ │ ├───android │ │ │ ├───bada │ │ │ ├───bada-wac │ │ │ ├───blackberry │ │ │ ├───blackberry10 │ │ │ ├───ios │ │ │ ├───tizen │ │ │ ├───webos │ │ │ └───windows-phone │ │ └───screen │ │ ├───android │ │ ├───bada │ │ ├───bada-wac │ │ ├───blackberry │ │ ├───blackberry10 │ │ └───ios │ ├───bin │ │ ├───classes │ │ │ └───br │ │ │ └───com │ │ │ └───softplan │ │ │ └───mobilelab │ │ ├───dexedLibs │ │ └───res │ │ ├───drawable │ │ ├───drawable-hdpi │ │ ├───drawable-ldpi │ │ ├───drawable-mdpi │ │ └───drawable-xhdpi │ ├───cordova │ │ ├───lib │ │ └───node_modules │ │ ├───.bin │ │ └───shelljs │ │ ├───bin │ │ └───scripts │ ├───gen │ │ └───br │ │ └───com │ │ └───softplan │ │ └───mobilelab │ ├───libs │ ├───res │ │ ├───drawable │ │ ├───drawable-hdpi │ │ ├───drawable-ldpi │ │ ├───drawable-mdpi │ │ ├───drawable-xhdpi │ │ ├───values │ │ └───xml │ └───src │ └───br │ └───com │ └───softplan │ └───mobilelab ├───plugins └───www └───cordova-app-hello-world-3.1.0-5683220 └───www ├───css ├───img ├───js └───res ├───icon │ ├───android
[jira] [Updated] (CB-4996) Run Android Emulator gives No such file or directory error
[ https://issues.apache.org/jira/browse/CB-4996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser updated CB-4996: --- Component/s: (was: OSX) (was: Android) CLI I think this may be specific to the PhoneGap CLI, but the Cordova CLI may be affected as well. This does not affect Android's cordova/run command. Run Android Emulator gives No such file or directory error -- Key: CB-4996 URL: https://issues.apache.org/jira/browse/CB-4996 Project: Apache Cordova Issue Type: Bug Components: CLI Affects Versions: 3.0.0 Reporter: Vincentdevreede Assignee: Braden Shepherdson Priority: Minor Labels: android, emulator, mac, partition, run_on_emulator, volumes Everything is correctly set up. But when i run phonegap run android, and it is trying to install app on emulator its going to error. [error] An error occurred while emulating/deploying the android project./Volumes/Vincent de Vreede/PhoneGap/Test/platforms/android/cordova/run: line 69: /Volumes/Vincent: No such file or directory /Volumes/Vincent de Vreede/PhoneGap/Test/platforms/android/cordova/run: line 32: /Volumes/Vincent: No such file or directory /Volumes/Vincent de Vreede/PhoneGap/Test/platforms/android/cordova/run: line 36: /Volumes/Vincent: No such file or directory No devices/emulators started nor images available to start. How are we supposed to do this, then? The problem is that he dont understand that /Volumes/Vincent de Vreede/ is my directory and not /Volumes/Vincent/, soo he cant find the files. I have changed my volume name to Vincentdevreede, and now its working. So the run_on_emulator function has a bug. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-5230) Cordova run never completes
[ https://issues.apache.org/jira/browse/CB-5230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13809280#comment-13809280 ] Joe Bowser commented on CB-5230: Do you have a device attached? If not, this is most definitely a duplicate. Cordova run never completes --- Key: CB-5230 URL: https://issues.apache.org/jira/browse/CB-5230 Project: Apache Cordova Issue Type: Bug Components: Android, App Hello World, CLI Affects Versions: 3.1.0 Reporter: Rick Gommers Cordova run android command will never finish. Even with a newly created hello world app. What can I do about this? -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-5230) Cordova run never completes
[ https://issues.apache.org/jira/browse/CB-5230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13809286#comment-13809286 ] Rick Gommers commented on CB-5230: -- I have a device attached yes :) Cordova run never completes --- Key: CB-5230 URL: https://issues.apache.org/jira/browse/CB-5230 Project: Apache Cordova Issue Type: Bug Components: Android, App Hello World, CLI Affects Versions: 3.1.0 Reporter: Rick Gommers Cordova run android command will never finish. Even with a newly created hello world app. What can I do about this? -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-5198) Plugins with dependency's will fail with cordova 3.0
[ https://issues.apache.org/jira/browse/CB-5198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13809297#comment-13809297 ] ASF subversion and git services commented on CB-5198: - Commit acb6147b4a85d9d018186e422d2d3b1f08333e89 in branch refs/heads/dev from [~bhigg...@blackberry.com] [ https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-contacts.git;h=acb6147 ] CB-5198 [BlackBerry10] Update dependencies to point to registry Plugins with dependency's will fail with cordova 3.0 Key: CB-5198 URL: https://issues.apache.org/jira/browse/CB-5198 Project: Apache Cordova Issue Type: Bug Components: Plugin File Transfer, Plugin Media Capture Affects Versions: 3.0.0 Reporter: Steve Gill Fix For: 3.2.0 The two plugins above have a dependency tag that downloads from the registry. Cordova 3.0.0 doesn't have support for downloading from the registry. If someone with cordova 3.0.0 installs the file-transfer plugin (using the git url since that was the suggested way for 3.0), it will fail in installing the dependency due to lack of registry support. Suggestions Bump the major version of these plugins and set engine tag to 3.1.0 Change 3.0 docs to suggest downloading based of 3.0.0 tag instead of from master. Ex. cordova plugin add https://git-wip-us.apache.org/repos/asf/cordova-plugin-file-transfer.git#3.0.0 (I am having trouble with this right now, figuring out why) -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-5222) Add manual mobile-spec tests for Keyboard plugin org.apache.cordova.keyboard
[ https://issues.apache.org/jira/browse/CB-5222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13809304#comment-13809304 ] ASF subversion and git services commented on CB-5222: - Commit 8e60a00b10ce9770ce51e7467b37a0e298d0609a in branch refs/heads/master from [~shazron] [ https://git-wip-us.apache.org/repos/asf?p=cordova-mobile-spec.git;h=8e60a00 ] CB-5222 - ios - Add manual mobile-spec tests for Keyboard plugin org.apache.cordova.keyboard Add manual mobile-spec tests for Keyboard plugin org.apache.cordova.keyboard Key: CB-5222 URL: https://issues.apache.org/jira/browse/CB-5222 Project: Apache Cordova Issue Type: Task Components: iOS, mobile-spec, Plugins Affects Versions: Master Reporter: Shazron Abdullah Assignee: Shazron Abdullah -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (CB-5231) coho exits if the ulimit is set too low
Marcel Kinard created CB-5231: - Summary: coho exits if the ulimit is set too low Key: CB-5231 URL: https://issues.apache.org/jira/browse/CB-5231 Project: Apache Cordova Issue Type: Bug Components: Coho Reporter: Marcel Kinard Assignee: Marcel Kinard Priority: Minor Fix For: 3.2.0 If my ulimit is below 2000, any invocation of coho will not perform the command I requested. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (CB-5232) Make android include CordovaLib as a library instead of a Jar
Andrew Grieve created CB-5232: - Summary: Make android include CordovaLib as a library instead of a Jar Key: CB-5232 URL: https://issues.apache.org/jira/browse/CB-5232 Project: Apache Cordova Issue Type: Bug Components: Android Reporter: Andrew Grieve Assignee: Andrew Grieve Priority: Minor Motivation: -Works better in IntelliJ -Faster project creation -Consistent with iOS approach -Allows users to step into framework code when debugging Proof of concept is checked in at cordova-android's libproject branch. Let's wait until the 3.2.0 branch is created before merging. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-5230) Cordova run never completes
[ https://issues.apache.org/jira/browse/CB-5230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13809379#comment-13809379 ] Joe Bowser commented on CB-5230: What happens when you run -v? I'm not able to reproduce this issue on my end. Cordova run never completes --- Key: CB-5230 URL: https://issues.apache.org/jira/browse/CB-5230 Project: Apache Cordova Issue Type: Bug Components: Android, App Hello World, CLI Affects Versions: 3.1.0 Reporter: Rick Gommers Cordova run android command will never finish. Even with a newly created hello world app. What can I do about this? -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (CB-5231) coho exits if the ulimit is set too low
[ https://issues.apache.org/jira/browse/CB-5231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Kinard resolved CB-5231. --- Resolution: Cannot Reproduce Argh, suddenly I can't reproduce it anymore. The code does look fine. I'm left to assume it was an environmental issue with my local machine. coho exits if the ulimit is set too low --- Key: CB-5231 URL: https://issues.apache.org/jira/browse/CB-5231 Project: Apache Cordova Issue Type: Bug Components: Coho Reporter: Marcel Kinard Assignee: Marcel Kinard Priority: Minor Fix For: 3.2.0 If my ulimit is below 2000, any invocation of coho will not perform the command I requested. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-5122) Document supported workflows
[
https://issues.apache.org/jira/browse/CB-5122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13809385#comment-13809385
]
Mike Sierra commented on CB-5122:
-
Not sure I understand collapse, but if you mean simply copying the README
content into the doc (either one-time or dynamically), then I don't agree. The
README is scoped reference content, while what's in the doc is expository guide
content, which serves a different purpose: storytelling. Do I understand the
issue correctly?
Document supported workflows
Key: CB-5122
URL: https://issues.apache.org/jira/browse/CB-5122
Project: Apache Cordova
Issue Type: Bug
Components: Docs
Affects Versions: 3.1.0
Reporter: Mike Billau
Assignee: Mike Sierra
Based on the recent discussion here [1]we should document the two different
supported Cordova workflows: using the CLI, and using plugman and bin
scripts.
Some of this documentation already exists but needs to be clarified and
improved:
{{Overview guide -- Development Paths section}}. This talks about getting
started with the CLI and then mentions that you can switch to the
platform-specific SDK tools. This section should be rewritten to make it
clear that there are two distinct workflows, and that both are okay and
supported. It could list out some pros and cons of each workflow (I'm sure we
won't have any trouble finding those ;)). It should be prescriptive in that
users should be following one of the two workflows, but it shouldn't make any
statements about which is better.
{{The Command-line Interface guide}} -- The CLI workflow guide. It
generally looks complete except for some missing functionality that is
documented in the CLI's README.md file (tests, hooks, some commands (serve),
some merges info).
{{Platform Guides -- (Platform) -- (Platform) Command-line tools}} -- Each
platform has a Command-line tools doc that explains all of the command line
tools for that project and how to use them. We need to go through these
guides and verify that they are up to date and include all of the lower level
command line tools and scripts. It should read like a tutorial in the same
way that the Command-line Interface guide does.
{{Using Plugman to Manage Plugins}} First, this guide needs to get exposed;
I can't find any way to get to this guide from the docs and even had to ask a
user how she managed to find it (a link from Plugman's readme!). This guide
needs to be expanded quite a bit; we can probably fold most/all of Plugman's
README.md file into this guide since it will be platform agnostic.
I think those are the only pieces in the docs that need to be changed.
[1] http://callback.markmail.org/thread/5nr7dgkquse4gdkl
[2]
http://cordova.apache.org/docs/en/edge/guide_overview_index.md.html#Overview
[3] http://cordova.apache.org/docs/en/edge/plugin_ref_plugman.md.html
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (CB-5122) Document supported workflows
[
https://issues.apache.org/jira/browse/CB-5122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13809393#comment-13809393
]
Mike Sierra commented on CB-5122:
-
I'm committing some changes to clarify merges == Customization in the
header text. I can handle the other CLI changes. IMO, may need to break out
advanced CLI topics onto another page.
Document supported workflows
Key: CB-5122
URL: https://issues.apache.org/jira/browse/CB-5122
Project: Apache Cordova
Issue Type: Bug
Components: Docs
Affects Versions: 3.1.0
Reporter: Mike Billau
Assignee: Mike Sierra
Based on the recent discussion here [1]we should document the two different
supported Cordova workflows: using the CLI, and using plugman and bin
scripts.
Some of this documentation already exists but needs to be clarified and
improved:
{{Overview guide -- Development Paths section}}. This talks about getting
started with the CLI and then mentions that you can switch to the
platform-specific SDK tools. This section should be rewritten to make it
clear that there are two distinct workflows, and that both are okay and
supported. It could list out some pros and cons of each workflow (I'm sure we
won't have any trouble finding those ;)). It should be prescriptive in that
users should be following one of the two workflows, but it shouldn't make any
statements about which is better.
{{The Command-line Interface guide}} -- The CLI workflow guide. It
generally looks complete except for some missing functionality that is
documented in the CLI's README.md file (tests, hooks, some commands (serve),
some merges info).
{{Platform Guides -- (Platform) -- (Platform) Command-line tools}} -- Each
platform has a Command-line tools doc that explains all of the command line
tools for that project and how to use them. We need to go through these
guides and verify that they are up to date and include all of the lower level
command line tools and scripts. It should read like a tutorial in the same
way that the Command-line Interface guide does.
{{Using Plugman to Manage Plugins}} First, this guide needs to get exposed;
I can't find any way to get to this guide from the docs and even had to ask a
user how she managed to find it (a link from Plugman's readme!). This guide
needs to be expanded quite a bit; we can probably fold most/all of Plugman's
README.md file into this guide since it will be platform agnostic.
I think those are the only pieces in the docs that need to be changed.
[1] http://callback.markmail.org/thread/5nr7dgkquse4gdkl
[2]
http://cordova.apache.org/docs/en/edge/guide_overview_index.md.html#Overview
[3] http://cordova.apache.org/docs/en/edge/plugin_ref_plugman.md.html
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Updated] (CB-5222) Add manual mobile-spec tests for Keyboard plugin org.apache.cordova.keyboard
[ https://issues.apache.org/jira/browse/CB-5222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shazron Abdullah updated CB-5222: - Fix Version/s: 3.2.0 Add manual mobile-spec tests for Keyboard plugin org.apache.cordova.keyboard Key: CB-5222 URL: https://issues.apache.org/jira/browse/CB-5222 Project: Apache Cordova Issue Type: Task Components: iOS, mobile-spec, Plugins Affects Versions: Master Reporter: Shazron Abdullah Assignee: Shazron Abdullah Fix For: 3.2.0 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-5122) Document supported workflows
[
https://issues.apache.org/jira/browse/CB-5122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13809403#comment-13809403
]
Mike Sierra commented on CB-5122:
-
I suggest we get rid of Platform Guide instead feature a SoAndSo
Installation Guide, applicable to both CLI shell workflows, then a separate
SoAndSo Development Guide detailing the actual shell workflow, corresponding
to the current Command-line Utilities page
Document supported workflows
Key: CB-5122
URL: https://issues.apache.org/jira/browse/CB-5122
Project: Apache Cordova
Issue Type: Bug
Components: Docs
Affects Versions: 3.1.0
Reporter: Mike Billau
Assignee: Mike Sierra
Based on the recent discussion here [1]we should document the two different
supported Cordova workflows: using the CLI, and using plugman and bin
scripts.
Some of this documentation already exists but needs to be clarified and
improved:
{{Overview guide -- Development Paths section}}. This talks about getting
started with the CLI and then mentions that you can switch to the
platform-specific SDK tools. This section should be rewritten to make it
clear that there are two distinct workflows, and that both are okay and
supported. It could list out some pros and cons of each workflow (I'm sure we
won't have any trouble finding those ;)). It should be prescriptive in that
users should be following one of the two workflows, but it shouldn't make any
statements about which is better.
{{The Command-line Interface guide}} -- The CLI workflow guide. It
generally looks complete except for some missing functionality that is
documented in the CLI's README.md file (tests, hooks, some commands (serve),
some merges info).
{{Platform Guides -- (Platform) -- (Platform) Command-line tools}} -- Each
platform has a Command-line tools doc that explains all of the command line
tools for that project and how to use them. We need to go through these
guides and verify that they are up to date and include all of the lower level
command line tools and scripts. It should read like a tutorial in the same
way that the Command-line Interface guide does.
{{Using Plugman to Manage Plugins}} First, this guide needs to get exposed;
I can't find any way to get to this guide from the docs and even had to ask a
user how she managed to find it (a link from Plugman's readme!). This guide
needs to be expanded quite a bit; we can probably fold most/all of Plugman's
README.md file into this guide since it will be platform agnostic.
I think those are the only pieces in the docs that need to be changed.
[1] http://callback.markmail.org/thread/5nr7dgkquse4gdkl
[2]
http://cordova.apache.org/docs/en/edge/guide_overview_index.md.html#Overview
[3] http://cordova.apache.org/docs/en/edge/plugin_ref_plugman.md.html
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Comment Edited] (CB-5122) Document supported workflows
[
https://issues.apache.org/jira/browse/CB-5122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13809393#comment-13809393
]
Mike Sierra edited comment on CB-5122 at 10/30/13 5:50 PM:
---
I'm committing some changes to clarify merges == Customization in the
header text. I can handle the other CLI changes. IMO, may need to break out
advanced CLI topics onto another page. BTW, I thought serve was going away,
but maybe that was only ripple
was (Author: sierra):
I'm committing some changes to clarify merges == Customization in the
header text. I can handle the other CLI changes. IMO, may need to break out
advanced CLI topics onto another page.
Document supported workflows
Key: CB-5122
URL: https://issues.apache.org/jira/browse/CB-5122
Project: Apache Cordova
Issue Type: Bug
Components: Docs
Affects Versions: 3.1.0
Reporter: Mike Billau
Assignee: Mike Sierra
Based on the recent discussion here [1]we should document the two different
supported Cordova workflows: using the CLI, and using plugman and bin
scripts.
Some of this documentation already exists but needs to be clarified and
improved:
{{Overview guide -- Development Paths section}}. This talks about getting
started with the CLI and then mentions that you can switch to the
platform-specific SDK tools. This section should be rewritten to make it
clear that there are two distinct workflows, and that both are okay and
supported. It could list out some pros and cons of each workflow (I'm sure we
won't have any trouble finding those ;)). It should be prescriptive in that
users should be following one of the two workflows, but it shouldn't make any
statements about which is better.
{{The Command-line Interface guide}} -- The CLI workflow guide. It
generally looks complete except for some missing functionality that is
documented in the CLI's README.md file (tests, hooks, some commands (serve),
some merges info).
{{Platform Guides -- (Platform) -- (Platform) Command-line tools}} -- Each
platform has a Command-line tools doc that explains all of the command line
tools for that project and how to use them. We need to go through these
guides and verify that they are up to date and include all of the lower level
command line tools and scripts. It should read like a tutorial in the same
way that the Command-line Interface guide does.
{{Using Plugman to Manage Plugins}} First, this guide needs to get exposed;
I can't find any way to get to this guide from the docs and even had to ask a
user how she managed to find it (a link from Plugman's readme!). This guide
needs to be expanded quite a bit; we can probably fold most/all of Plugman's
README.md file into this guide since it will be platform agnostic.
I think those are the only pieces in the docs that need to be changed.
[1] http://callback.markmail.org/thread/5nr7dgkquse4gdkl
[2]
http://cordova.apache.org/docs/en/edge/guide_overview_index.md.html#Overview
[3] http://cordova.apache.org/docs/en/edge/plugin_ref_plugman.md.html
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (CB-5122) Document supported workflows
[
https://issues.apache.org/jira/browse/CB-5122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13809412#comment-13809412
]
Mike Sierra commented on CB-5122:
-
+1 on Plugman visibility. I have a task in the works (not yet tracked in JIRA)
to revamp the entire doc UI, where it should be well represented, but adding
the topic should be fine for now. I understand that plugman doc applies to all
platform-shell-tool workflows, and that there's no custom content for any
platform. Correct?
Document supported workflows
Key: CB-5122
URL: https://issues.apache.org/jira/browse/CB-5122
Project: Apache Cordova
Issue Type: Bug
Components: Docs
Affects Versions: 3.1.0
Reporter: Mike Billau
Assignee: Mike Sierra
Based on the recent discussion here [1]we should document the two different
supported Cordova workflows: using the CLI, and using plugman and bin
scripts.
Some of this documentation already exists but needs to be clarified and
improved:
{{Overview guide -- Development Paths section}}. This talks about getting
started with the CLI and then mentions that you can switch to the
platform-specific SDK tools. This section should be rewritten to make it
clear that there are two distinct workflows, and that both are okay and
supported. It could list out some pros and cons of each workflow (I'm sure we
won't have any trouble finding those ;)). It should be prescriptive in that
users should be following one of the two workflows, but it shouldn't make any
statements about which is better.
{{The Command-line Interface guide}} -- The CLI workflow guide. It
generally looks complete except for some missing functionality that is
documented in the CLI's README.md file (tests, hooks, some commands (serve),
some merges info).
{{Platform Guides -- (Platform) -- (Platform) Command-line tools}} -- Each
platform has a Command-line tools doc that explains all of the command line
tools for that project and how to use them. We need to go through these
guides and verify that they are up to date and include all of the lower level
command line tools and scripts. It should read like a tutorial in the same
way that the Command-line Interface guide does.
{{Using Plugman to Manage Plugins}} First, this guide needs to get exposed;
I can't find any way to get to this guide from the docs and even had to ask a
user how she managed to find it (a link from Plugman's readme!). This guide
needs to be expanded quite a bit; we can probably fold most/all of Plugman's
README.md file into this guide since it will be platform agnostic.
I think those are the only pieces in the docs that need to be changed.
[1] http://callback.markmail.org/thread/5nr7dgkquse4gdkl
[2]
http://cordova.apache.org/docs/en/edge/guide_overview_index.md.html#Overview
[3] http://cordova.apache.org/docs/en/edge/plugin_ref_plugman.md.html
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (CB-5122) Document supported workflows
[
https://issues.apache.org/jira/browse/CB-5122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13809415#comment-13809415
]
Mike Sierra commented on CB-5122:
-
Not sure I agree naming the CLI guide to CLI Workflow, if that's what you're
suggesting. It implies a parallel set of Workflow topics elsewhere.
Document supported workflows
Key: CB-5122
URL: https://issues.apache.org/jira/browse/CB-5122
Project: Apache Cordova
Issue Type: Bug
Components: Docs
Affects Versions: 3.1.0
Reporter: Mike Billau
Assignee: Mike Sierra
Based on the recent discussion here [1]we should document the two different
supported Cordova workflows: using the CLI, and using plugman and bin
scripts.
Some of this documentation already exists but needs to be clarified and
improved:
{{Overview guide -- Development Paths section}}. This talks about getting
started with the CLI and then mentions that you can switch to the
platform-specific SDK tools. This section should be rewritten to make it
clear that there are two distinct workflows, and that both are okay and
supported. It could list out some pros and cons of each workflow (I'm sure we
won't have any trouble finding those ;)). It should be prescriptive in that
users should be following one of the two workflows, but it shouldn't make any
statements about which is better.
{{The Command-line Interface guide}} -- The CLI workflow guide. It
generally looks complete except for some missing functionality that is
documented in the CLI's README.md file (tests, hooks, some commands (serve),
some merges info).
{{Platform Guides -- (Platform) -- (Platform) Command-line tools}} -- Each
platform has a Command-line tools doc that explains all of the command line
tools for that project and how to use them. We need to go through these
guides and verify that they are up to date and include all of the lower level
command line tools and scripts. It should read like a tutorial in the same
way that the Command-line Interface guide does.
{{Using Plugman to Manage Plugins}} First, this guide needs to get exposed;
I can't find any way to get to this guide from the docs and even had to ask a
user how she managed to find it (a link from Plugman's readme!). This guide
needs to be expanded quite a bit; we can probably fold most/all of Plugman's
README.md file into this guide since it will be platform agnostic.
I think those are the only pieces in the docs that need to be changed.
[1] http://callback.markmail.org/thread/5nr7dgkquse4gdkl
[2]
http://cordova.apache.org/docs/en/edge/guide_overview_index.md.html#Overview
[3] http://cordova.apache.org/docs/en/edge/plugin_ref_plugman.md.html
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (CB-5230) Cordova run never completes
[ https://issues.apache.org/jira/browse/CB-5230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13809422#comment-13809422 ] Rick Gommers commented on CB-5230: -- Cordova -v returns '3.1.0-0.2.0' Cordova run never completes --- Key: CB-5230 URL: https://issues.apache.org/jira/browse/CB-5230 Project: Apache Cordova Issue Type: Bug Components: Android, App Hello World, CLI Affects Versions: 3.1.0 Reporter: Rick Gommers Cordova run android command will never finish. Even with a newly created hello world app. What can I do about this? -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-5230) Cordova run never completes
[ https://issues.apache.org/jira/browse/CB-5230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13809424#comment-13809424 ] Joe Bowser commented on CB-5230: Sorry, I meant -d Cordova run never completes --- Key: CB-5230 URL: https://issues.apache.org/jira/browse/CB-5230 Project: Apache Cordova Issue Type: Bug Components: Android, App Hello World, CLI Affects Versions: 3.1.0 Reporter: Rick Gommers Cordova run android command will never finish. Even with a newly created hello world app. What can I do about this? -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-5230) Cordova run never completes
[
https://issues.apache.org/jira/browse/CB-5230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13809431#comment-13809431
]
Rick Gommers commented on CB-5230:
--
There you go:
Synopsis
cordova command [options]
Global Commands
create PATH [ID] [NAME] creates a cordova project in the
specified PATH, with
optional NAME and ID (reverse-dom
ain-style package name)
help . shows this syntax summary
info . print out useful information help
ful for submitting bug
reports and getting help. Create
s a info.txt file at the
base of your project
Project-Level Commands
platform(s) [{add|remove|rm} PLATFORM] .. add or remove a specified PLATFO
RM, OR
[{list|ls}] ... list all installed, available an
d unavailable platforms
plugin(s) [{add|remove|rm} PATH|URI] add or remove a plugin from the
specified PATH or URI, OR
[{ls|list}] . list all currently installed plu
gins
prepare [PLATFORM..] .. copies files for specified platf
orms, or all platforms,
so that the project is ready to
build in each SDK.
compile [PLATFORM..] .. builds the app for specified pla
tforms, or all platforms
build [PLATFORM...] ... shortcut for prepare, then compi
le
emulate [PLATFORM...] . deploys app in specified (or all
) platform emulator(s),
opening emulator if necessary
run [PLATFORM...] . deploys app on specified (or all
) platform devices, which
must be properly connected and c
onfigured in each SDK
serve PLATFORM [PORT] ... runs a local web server for the
specified platform's www/
directory, with optional port nu
mber that defaults to 8000.
(Note: you must edit the native
code to reference the server.)
Command-line Flags/Options
-v, --version . prints out this utility's versio
n
-d, --verbose . debug mode produces verbose log
output for all activity,
including output of sub-commands
cordova invokes
Example usage
$ cordova create Baz
$ cd Baz
$ cordova platform add android
$ cordova build
$ cordova serve android
Cordova run never completes
---
Key: CB-5230
URL: https://issues.apache.org/jira/browse/CB-5230
Project: Apache Cordova
Issue Type: Bug
Components: Android, App Hello World, CLI
Affects Versions: 3.1.0
Reporter: Rick Gommers
Cordova run android command will never finish. Even with a newly created
hello world app. What can I do about this?
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (CB-5230) Cordova run never completes
[ https://issues.apache.org/jira/browse/CB-5230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13809433#comment-13809433 ] Rick Gommers commented on CB-5230: -- Ah, i guess you mean running the app using -d :) Will try that. wait a moment Cordova run never completes --- Key: CB-5230 URL: https://issues.apache.org/jira/browse/CB-5230 Project: Apache Cordova Issue Type: Bug Components: Android, App Hello World, CLI Affects Versions: 3.1.0 Reporter: Rick Gommers Cordova run android command will never finish. Even with a newly created hello world app. What can I do about this? -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-3206) vibration
[ https://issues.apache.org/jira/browse/CB-3206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13809449#comment-13809449 ] Steve Gill commented on CB-3206: It is probably not needed vibration - Key: CB-3206 URL: https://issues.apache.org/jira/browse/CB-3206 Project: Apache Cordova Issue Type: Sub-task Components: FirefoxOS Affects Versions: 2.6.0 Reporter: Herm Wong Assignee: Herm Wong Fix For: 3.1.0 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Issue Comment Deleted] (CB-5230) Cordova run never completes
[
https://issues.apache.org/jira/browse/CB-5230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Gommers updated CB-5230:
-
Comment: was deleted
(was: There you go:
Synopsis
cordova command [options]
Global Commands
create PATH [ID] [NAME] creates a cordova project in the
specified PATH, with
optional NAME and ID (reverse-dom
ain-style package name)
help . shows this syntax summary
info . print out useful information help
ful for submitting bug
reports and getting help. Create
s a info.txt file at the
base of your project
Project-Level Commands
platform(s) [{add|remove|rm} PLATFORM] .. add or remove a specified PLATFO
RM, OR
[{list|ls}] ... list all installed, available an
d unavailable platforms
plugin(s) [{add|remove|rm} PATH|URI] add or remove a plugin from the
specified PATH or URI, OR
[{ls|list}] . list all currently installed plu
gins
prepare [PLATFORM..] .. copies files for specified platf
orms, or all platforms,
so that the project is ready to
build in each SDK.
compile [PLATFORM..] .. builds the app for specified pla
tforms, or all platforms
build [PLATFORM...] ... shortcut for prepare, then compi
le
emulate [PLATFORM...] . deploys app in specified (or all
) platform emulator(s),
opening emulator if necessary
run [PLATFORM...] . deploys app on specified (or all
) platform devices, which
must be properly connected and c
onfigured in each SDK
serve PLATFORM [PORT] ... runs a local web server for the
specified platform's www/
directory, with optional port nu
mber that defaults to 8000.
(Note: you must edit the native
code to reference the server.)
Command-line Flags/Options
-v, --version . prints out this utility's versio
n
-d, --verbose . debug mode produces verbose log
output for all activity,
including output of sub-commands
cordova invokes
Example usage
$ cordova create Baz
$ cd Baz
$ cordova platform add android
$ cordova build
$ cordova serve android
)
Cordova run never completes
---
Key: CB-5230
URL: https://issues.apache.org/jira/browse/CB-5230
Project: Apache Cordova
Issue Type: Bug
Components: Android, App Hello World, CLI
Affects Versions: 3.1.0
Reporter: Rick Gommers
Cordova run android command will never finish. Even with a newly created
hello world app. What can I do about this?
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (CB-5230) Cordova run never completes
[ https://issues.apache.org/jira/browse/CB-5230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13809453#comment-13809453 ] Rick Gommers commented on CB-5230: -- The build never completes. These are the last lines: Plugin org.apache.cordova.device-orientation is good to go. Ensuring plugin org.apache.cordova.dialogs is installed correctly... Plugin org.apache.cordova.dialogs is good to go. Ensuring plugin org.apache.cordova.file is installed correctly... Plugin org.apache.cordova.file is good to go. Ensuring plugin org.apache.cordova.file-transfer is installed correctly... Plugin org.apache.cordova.file-transfer is good to go. Ensuring plugin org.apache.cordova.geolocation is installed correctly... Plugin org.apache.cordova.geolocation is good to go. Ensuring plugin org.apache.cordova.globalization is installed correctly... Plugin org.apache.cordova.globalization is good to go. Ensuring plugin org.apache.cordova.media is installed correctly... Plugin org.apache.cordova.media is good to go. Ensuring plugin org.apache.cordova.media-capture is installed correctly... Plugin org.apache.cordova.media-capture is good to go. Ensuring plugin org.apache.cordova.network-information is installed correctly. .. Plugin org.apache.cordova.network-information is good to go. Ensuring plugin org.apache.cordova.splashscreen is installed correctly... Plugin org.apache.cordova.splashscreen is good to go. Ensuring plugin org.apache.cordova.vibration is installed correctly... Plugin org.apache.cordova.vibration is good to go. Wrote out Android application name to NavoSpelAlfabetV2 Wrote out Android package name to com.coolappz.NavoSpelAlfabetV2 Running app on platform android via command cmd /c C:\NetbeansProjects\NavoS pelAlfabetV2\platforms\android\cordova\run --device Buildfile: C:\NetbeansProjects\NavoSpelAlfabetV2\platforms\android\build.xml Cordova run never completes --- Key: CB-5230 URL: https://issues.apache.org/jira/browse/CB-5230 Project: Apache Cordova Issue Type: Bug Components: Android, App Hello World, CLI Affects Versions: 3.1.0 Reporter: Rick Gommers Cordova run android command will never finish. Even with a newly created hello world app. What can I do about this? -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-4890) Reference to plugins.xml should be config.xml
[
https://issues.apache.org/jira/browse/CB-4890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13809455#comment-13809455
]
Mike Billau commented on CB-4890:
-
Man, somehow this change from plugins.xml to config.xml didn't get put into
edge, 3.1, or 3.0: https://github.com/apache/cordova-docs/pull/142 for this
plugin.
Reference to plugins.xml should be config.xml
-
Key: CB-4890
URL: https://issues.apache.org/jira/browse/CB-4890
Project: Apache Cordova
Issue Type: Improvement
Components: Docs
Affects Versions: 2.9.0
Reporter: Peter
Assignee: Michael Brooks
Priority: Trivial
The Capture API documentation for Android (see Permissions section) is
still referring to plugins.xml instead of config.xml
{quote}
Permissions
Android
app/res/xml/plugins.xml
{quote}
http://cordova.apache.org/docs/en/2.9.0/cordova_media_capture_capture.md.html#Capture
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (CB-5230) Cordova run never completes
[ https://issues.apache.org/jira/browse/CB-5230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13809459#comment-13809459 ] Rick Gommers commented on CB-5230: -- Just to be clear: You can see the project is in C:\NetbeansProjects\, but I'm running the project via cli right now. This afternoon I first filled a bug with Netbeans itself: https://netbeans.org/bugzilla/show_bug.cgi?id=237819 But later on I realized this is probably a Cordova issue, because Netbeans does al the commands as they should be Cordova run never completes --- Key: CB-5230 URL: https://issues.apache.org/jira/browse/CB-5230 Project: Apache Cordova Issue Type: Bug Components: Android, App Hello World, CLI Affects Versions: 3.1.0 Reporter: Rick Gommers Cordova run android command will never finish. Even with a newly created hello world app. What can I do about this? -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-2423) FileTransfer does not set Content-Length header even if known -- unable to upload to Amazon
[
https://issues.apache.org/jira/browse/CB-2423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13809512#comment-13809512
]
Joe Bowser commented on CB-2423:
Relates to useChunkedMode logic. If this logic is removed, this may be resolved.
FileTransfer does not set Content-Length header even if known -- unable to
upload to Amazon
---
Key: CB-2423
URL: https://issues.apache.org/jira/browse/CB-2423
Project: Apache Cordova
Issue Type: Bug
Components: Android
Affects Versions: 2.4.0
Environment: Android client
Reporter: Thomas O'Dell
Assignee: Andrew Grieve
Labels: features
Original Estimate: 24h
Remaining Estimate: 24h
FileTransfer does not set the Content-Length header even when known, which
causes Amazon S3 to return HTML Code 411 (Length Required).
Adding the following lines after line 328 solves the problem:
if (fixedLength = 0) {
conn.setRequestProperty(Content-Length, +fixedLength);
}
(Haven't tested on iOS, but see that iOS does have code to set
Content-Length.)
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Updated] (CB-2423) FileTransfer does not set Content-Length header even if known -- unable to upload to Amazon
[
https://issues.apache.org/jira/browse/CB-2423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Bowser updated CB-2423:
---
Priority: Minor (was: Major)
FileTransfer does not set Content-Length header even if known -- unable to
upload to Amazon
---
Key: CB-2423
URL: https://issues.apache.org/jira/browse/CB-2423
Project: Apache Cordova
Issue Type: Bug
Components: Android
Affects Versions: 2.4.0
Environment: Android client
Reporter: Thomas O'Dell
Assignee: Andrew Grieve
Priority: Minor
Labels: features
Original Estimate: 24h
Remaining Estimate: 24h
FileTransfer does not set the Content-Length header even when known, which
causes Amazon S3 to return HTML Code 411 (Length Required).
Adding the following lines after line 328 solves the problem:
if (fixedLength = 0) {
conn.setRequestProperty(Content-Length, +fixedLength);
}
(Haven't tested on iOS, but see that iOS does have code to set
Content-Length.)
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Updated] (CB-2787) PhoneGap FileTransfer.Download more than 300 files
[
https://issues.apache.org/jira/browse/CB-2787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Bowser updated CB-2787:
---
Component/s: Plugin File Transfer
PhoneGap FileTransfer.Download more than 300 files
--
Key: CB-2787
URL: https://issues.apache.org/jira/browse/CB-2787
Project: Apache Cordova
Issue Type: Bug
Components: Android, Plugin File Transfer
Affects Versions: 2.5.0
Reporter: Cho
Assignee: Ian Clelland
I had tried to download more than 300 files and then it hit error after that.
Seems like some IO Connection was not properly closed. I wrote a small code
to test it out.
Any idea? How to file a report or get a source of phonegap to check the real
cause?
{code}
var counter = 500;
function DownloadFile() {
if (counter == 0) {
DownloadComplete();
return;
}
var ft = new FileTransfer();
var downloadUrl = source;
var dlPath = target
ft.download(downloadUrl, dlPath, function(entry) {
counter--;
UpdateProgress();
DownloadFile();
}, function(error) {
DownloadFailed();
}, true);
}
{code}
note: target and source is alright because it was it failed when the
counter goes until 300+.
{code}
03-14 08:35:09.706: E/FileTransfer(24867):
{target:target,source:source,http_status:200,code:1}
03-14 08:35:09.706: E/FileTransfer(24867): java.io.FileNotFoundException:
source: open failed: EMFILE (Too many open files)
03-14 08:35:09.706: E/FileTransfer(24867): at
libcore.io.IoBridge.open(IoBridge.java:416)
03-14 08:35:09.706: E/FileTransfer(24867): at
java.io.FileOutputStream.init(FileOutputStream.java:88)
03-14 08:35:09.706: E/FileTransfer(24867): at
java.io.FileOutputStream.init(FileOutputStream.java:73)
03-14 08:35:09.706: E/FileTransfer(24867): at
org.apache.cordova.FileTransfer$4.run(FileTransfer.java:685)
03-14 08:35:09.706: E/FileTransfer(24867): at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1076)
03-14 08:35:09.706: E/FileTransfer(24867): at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:569)
03-14 08:35:09.706: E/FileTransfer(24867): at
java.lang.Thread.run(Thread.java:856)
03-14 08:35:09.706: E/FileTransfer(24867): Caused by:
libcore.io.ErrnoException: open failed: EMFILE (Too many open files)
03-14 08:35:09.706: E/FileTransfer(24867): at
libcore.io.Posix.open(Native Method)
03-14 08:35:09.706: E/FileTransfer(24867): at
libcore.io.BlockGuardOs.open(BlockGuardOs.java:110)
03-14 08:35:09.706: E/FileTransfer(24867): at
libcore.io.IoBridge.open(IoBridge.java:400)
03-14 08:35:09.706: E/FileTransfer(24867): ... 6 more
{code}
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Updated] (CB-4029) FileTransfer: No error code for no space left
[
https://issues.apache.org/jira/browse/CB-4029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ian Clelland updated CB-4029:
-
Component/s: Plugin File Transfer
FileTransfer: No error code for no space left
---
Key: CB-4029
URL: https://issues.apache.org/jira/browse/CB-4029
Project: Apache Cordova
Issue Type: Bug
Components: Android, BlackBerry, CordovaJS, iOS, Plugin File
Transfer, WP7, WP8
Affects Versions: 2.8.0
Reporter: Vitalii Vlasiuk
Assignee: Joe Bowser
Android 2.3.6:
Steps:
1. I use device with no free space on sdcard.
2. Download some file with FileTransfer.
Result:
I have js-exception:
06-27 16:34:05.647: E/FileTransfer(2619):
{target:file:\/\/\/mnt\/sdcard\/Android\/data\...,source:http:...,http_status:200,code:3}
And java exception:
E/FileTransfer(2619): java.io.IOException: No space left on device
Expected result:
Need to add new error code for no space left.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Updated] (CB-2627) HTML File Input should support accept/source attributes
[ https://issues.apache.org/jira/browse/CB-2627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser updated CB-2627: --- Priority: Minor (was: Major) HTML File Input should support accept/source attributes --- Key: CB-2627 URL: https://issues.apache.org/jira/browse/CB-2627 Project: Apache Cordova Issue Type: New Feature Components: Android Reporter: Michael Migdol Assignee: Joe Bowser Priority: Minor [CB-2086] always opens a generic File Picker, regardless of the values passed in for the mimetypes in the accept attribute, or the source attribute. The Android Browser correctly examines these attributes and starts up an activity with either: a camera intent, a camera/image intent, a camcorder intent, a sound recorder intent, or a sound recorder/audio intent. I'm not sure what cross-pollination is allowed between the Android codebase and Cordova's, but it appears that packages/apps/Browser/src/com/android/browser/UploadHandler.java from the Android source tree contains exactly what we need to accomplish the same. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (CB-2787) PhoneGap FileTransfer.Download more than 300 files
[
https://issues.apache.org/jira/browse/CB-2787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Bowser resolved CB-2787.
Resolution: Unresolved
There's been a lot of churn, we need to re-verify if this is an issue. If you
can reproduce this on 3.1.0, please re-open.
PhoneGap FileTransfer.Download more than 300 files
--
Key: CB-2787
URL: https://issues.apache.org/jira/browse/CB-2787
Project: Apache Cordova
Issue Type: Bug
Components: Android, Plugin File Transfer
Affects Versions: 2.5.0
Reporter: Cho
Assignee: Ian Clelland
I had tried to download more than 300 files and then it hit error after that.
Seems like some IO Connection was not properly closed. I wrote a small code
to test it out.
Any idea? How to file a report or get a source of phonegap to check the real
cause?
{code}
var counter = 500;
function DownloadFile() {
if (counter == 0) {
DownloadComplete();
return;
}
var ft = new FileTransfer();
var downloadUrl = source;
var dlPath = target
ft.download(downloadUrl, dlPath, function(entry) {
counter--;
UpdateProgress();
DownloadFile();
}, function(error) {
DownloadFailed();
}, true);
}
{code}
note: target and source is alright because it was it failed when the
counter goes until 300+.
{code}
03-14 08:35:09.706: E/FileTransfer(24867):
{target:target,source:source,http_status:200,code:1}
03-14 08:35:09.706: E/FileTransfer(24867): java.io.FileNotFoundException:
source: open failed: EMFILE (Too many open files)
03-14 08:35:09.706: E/FileTransfer(24867): at
libcore.io.IoBridge.open(IoBridge.java:416)
03-14 08:35:09.706: E/FileTransfer(24867): at
java.io.FileOutputStream.init(FileOutputStream.java:88)
03-14 08:35:09.706: E/FileTransfer(24867): at
java.io.FileOutputStream.init(FileOutputStream.java:73)
03-14 08:35:09.706: E/FileTransfer(24867): at
org.apache.cordova.FileTransfer$4.run(FileTransfer.java:685)
03-14 08:35:09.706: E/FileTransfer(24867): at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1076)
03-14 08:35:09.706: E/FileTransfer(24867): at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:569)
03-14 08:35:09.706: E/FileTransfer(24867): at
java.lang.Thread.run(Thread.java:856)
03-14 08:35:09.706: E/FileTransfer(24867): Caused by:
libcore.io.ErrnoException: open failed: EMFILE (Too many open files)
03-14 08:35:09.706: E/FileTransfer(24867): at
libcore.io.Posix.open(Native Method)
03-14 08:35:09.706: E/FileTransfer(24867): at
libcore.io.BlockGuardOs.open(BlockGuardOs.java:110)
03-14 08:35:09.706: E/FileTransfer(24867): at
libcore.io.IoBridge.open(IoBridge.java:400)
03-14 08:35:09.706: E/FileTransfer(24867): ... 6 more
{code}
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Updated] (CB-4071) Capture error callback (should be an object)
[
https://issues.apache.org/jira/browse/CB-4071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ian Clelland updated CB-4071:
-
Component/s: Plugin Media Capture
Capture error callback (should be an object)
Key: CB-4071
URL: https://issues.apache.org/jira/browse/CB-4071
Project: Apache Cordova
Issue Type: Bug
Components: Android, Docs, iOS, Plugin Media Capture, Windows 8
Affects Versions: 2.9.0
Environment: All
Reporter: Jonathan Bond-Caron
Assignee: Joe Bowser
Fix For: 3.2.0
When using camera.getPicture(), the cameraError is documented as a string but
on Android iOS, it's actually an object.
On the native side in 2.7:
Android:
private static final int CAPTURE_INTERNAL_ERR = 0;
// private static final int CAPTURE_APPLICATION_BUSY = 1;
// private static final int CAPTURE_INVALID_ARGUMENT = 2;
private static final int CAPTURE_NO_MEDIA_FILES = 3;
iOS:
enum CDVCaptureError {
CAPTURE_INTERNAL_ERR = 0,
CAPTURE_APPLICATION_BUSY = 1,
CAPTURE_INVALID_ARGUMENT = 2,
CAPTURE_NO_MEDIA_FILES = 3,
CAPTURE_NOT_SUPPORTED = 20
};
Windows 8:
only string errors
Android and iOS have the same looking api on the native side, error callback
Android returns JSON: {message: '', code: int}, iOS returns JSON: {message:
'', status: int},
Looking at the javascript api, it looks like it should return a 'new
CaptureError()' on the errorCallback, is that the direction for 3.0?
Windows only sends a string as the callback error, it's difficult to know if
the user just cancelled taking a picture or what kind of specific error
occurred.
Should I look into creating a patch?
This probably affects other apis, overall I'd like to see the CaptureError()
returned more consistently instead of strings.
It would make sense to improve this in 3.0 and possibly break BC for those
expecting strings.
CaptureError() could implement 'toString()' to mitigate potential issues.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Resolved] (CB-2099) Android whitelisting only blocks documents, not resources
[ https://issues.apache.org/jira/browse/CB-2099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser resolved CB-2099. Resolution: Implemented This was documented, closing! Android whitelisting only blocks documents, not resources - Key: CB-2099 URL: https://issues.apache.org/jira/browse/CB-2099 Project: Apache Cordova Issue Type: Bug Components: Android Affects Versions: 2.2.0 Reporter: manjula fernando Assignee: Mike Sierra The Domain Whitelisting in Android works only for the href links, but not for the embedded resources (images, javascripts). If link is not whitelisted it gets opened in a new instance of native browser rather than blocking it completely. But in iOS it blocks all non-whitelisted domains. Please let me know whether this is the expected behavior in whitelisting for Android?. If so, has this been identified as a known issue and planning to be fixed in future release? Appreciate your early response on this. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CB-4571) Media Object issue with Error function
[ https://issues.apache.org/jira/browse/CB-4571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ian Clelland updated CB-4571: - Component/s: Plugin Media Media Object issue with Error function -- Key: CB-4571 URL: https://issues.apache.org/jira/browse/CB-4571 Project: Apache Cordova Issue Type: Bug Components: Android, Plugin Media Affects Versions: 3.0.0 Reporter: khushwant Singh Assignee: Joe Bowser Hi Simon/Phonegap team, I have been facing an issue with Media object while playing live streaming (shoutcast). It looks like Media object's error function does not get called if the URL fails to return valid stream (bytes) but does return status code 200 (OK). The LOG CAT clearly shows that there is an error and Media cannot be played but this error message does not get forwarded to the media error function and Media object dies silently. The error function only gets called when I try to call Media.Stop() function. I tested the same URL on Chrome, that implicitly uses HTML5 Audio object, and it seems like in case they do not get valid stream but 200 (OK), the Audio object keeps on trying and stops until it gets audio stream back. I used fiddler and can see Audio object calls the same URL again and again until it gets response with stream. So my questions here are, 1) Can we make Media object works the same way HTML5 Audio control works? 2) Can we force Media object to call error function in case there is any error (just after play). I am hoping that you can help me on this. URL *** http://radio.sgpc.net:8020/live16?1.mp3 LogCat logs 08-12 11:09:32.348: E/HTTPStream(21328): HTTPStream::receive(): recv failed, server is gone, total received: 0 bytes 08-12 11:09:32.348: E/NuHTTPDataSource(21328): NuHTTPDataSource::readAt(offset 0, size 65536) err(-1005) = internalRead() 08-12 11:09:32.348: E/NuCachedSource2(21328): source returned error -1005 08-12 11:09:32.548: E/MediaPlayer(31929): error (1, -2147483648) 08-12 11:09:32.548: E/MediaPlayer(31929): Error (1,-2147483648) 08-12 11:09:42.988: E/CordovaWebView(31929): CordovaWebView: TIMEOUT ERROR! Many Thanks, Khushwant -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CB-4796) FileTransfer Upload Progress does not work
[ https://issues.apache.org/jira/browse/CB-4796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ian Clelland updated CB-4796: - Component/s: Plugin File Transfer FileTransfer Upload Progress does not work -- Key: CB-4796 URL: https://issues.apache.org/jira/browse/CB-4796 Project: Apache Cordova Issue Type: Bug Components: Android, Plugin File Transfer Affects Versions: 3.0.0 Reporter: Christoph Pojer Assignee: Joe Bowser File Transfer Upload progress has stopped working as of version 3.0.0. I suspect it has something to do with sending the JS from a different Thread as we are also experiencing issues with the DOM not redrawing (although updating just fine) with our custom media plugin (we send JS from a different thread, see: https://github.com/auphonic/cordova-plugin-media/blob/master/src/android/AudioPlayer.java#L125 ). Please let me know if these are two separate issues and if I should create a separate issue for both but I strongly suspect that this has something to do with each other.. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (CB-3607) Make manifest - appcache file on server to work with a phonegap build app
[ https://issues.apache.org/jira/browse/CB-3607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser resolved CB-3607. Resolution: Invalid Not a cordova bug! Not sure what this means anymore! Make manifest - appcache file on server to work with a phonegap build app - Key: CB-3607 URL: https://issues.apache.org/jira/browse/CB-3607 Project: Apache Cordova Issue Type: Bug Components: Android, iOS Affects Versions: 2.7.0 Reporter: Claes Gustavsson Assignee: Simon MacDonald Why? - To make an app offline and still be able to update the content without having to submit the hole app again. The app can be updated and you just have to update the manifest file on the server and it can be offline. If you can make a manifest - appcache file to work with phonegap build without having to change anything in the app code would be great. So it would work the same way as with an webapp. Simon MacDonald said the I could assign it to him. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CB-5194) Camera.getPicture with sourceType: PHOTOLIBRARY doesn't respect correctOrientation unless targetWidth/Height also specified
[ https://issues.apache.org/jira/browse/CB-5194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ian Clelland updated CB-5194: - Component/s: Plugin Camera Camera.getPicture with sourceType: PHOTOLIBRARY doesn't respect correctOrientation unless targetWidth/Height also specified --- Key: CB-5194 URL: https://issues.apache.org/jira/browse/CB-5194 Project: Apache Cordova Issue Type: Bug Components: Android, Plugin Camera Affects Versions: 2.6.0 Environment: Galaxy S4 Reporter: Andre Asselin Priority: Minor Use Camera.getPicture() with sourceType: PHOTOLIBRARY to retrieve a picture from the library. The correctOrientation option will be ignored unless you also specify targetWidth/Height as options. The documentation doesn't state there is a dependency. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CB-3576) Add support for self-signed SSL certficates in InAppBrowser
[
https://issues.apache.org/jira/browse/CB-3576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Bowser updated CB-3576:
---
Assignee: (was: Andrew Grieve)
Add support for self-signed SSL certficates in InAppBrowser
---
Key: CB-3576
URL: https://issues.apache.org/jira/browse/CB-3576
Project: Apache Cordova
Issue Type: Improvement
Components: Android, iOS, Plugin InAppBrowser
Affects Versions: 2.7.0, 2.8.0
Environment: Android and iOS
Reporter: Montyleena
Priority: Minor
Labels: android, https, inappbrowser,, ios, ssl
Attachments: InAppBrowser.java
Local https links are blocked by default in InAppBrowser (links using a local
SSL certificate which can't be verified by a 3rd party). Ideally, user should
be given an option to proceed or cancel the request like the default
desktop/mobile browsers do.
Right now, we have to overwrite the following API in Android to access such
URLs but onReceivedSslError() function gets called only for the main PhoneGap
window browser and not for InAppBrowser.
Create a new class:
public class CustomWebViewClient extends CordovaWebViewClient {
public static final String LOG_TAG = Plugin;
public CustomWebViewClient(DroidGap ctx) {
super(ctx);
Log.d(LOG_TAG, Constructor!);
}
@Override
public void onReceivedSslError(WebView view, SslErrorHandler handler,
SslError error) {
handler.proceed();
}
}
In the main class, we use our custom class as a web view client
CordovaWebViewClient webViewClient = new CustomWebViewClient(this);
webViewClient.setWebView(this.appView);
this.appView.setWebViewClient(webViewClient);
And similar type of code needs to be written for iOS.
InAppBrowser should pick up the SSL settings from the main web view and once
we overwrite the onReceivedSslError() function, then it should allow such
URLs in the InAppBrowser too.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Updated] (CB-3576) Add support for self-signed SSL certficates in InAppBrowser
[
https://issues.apache.org/jira/browse/CB-3576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Bowser updated CB-3576:
---
Priority: Minor (was: Major)
Add support for self-signed SSL certficates in InAppBrowser
---
Key: CB-3576
URL: https://issues.apache.org/jira/browse/CB-3576
Project: Apache Cordova
Issue Type: Improvement
Components: Android, iOS, Plugin InAppBrowser
Affects Versions: 2.7.0, 2.8.0
Environment: Android and iOS
Reporter: Montyleena
Assignee: Andrew Grieve
Priority: Minor
Labels: android, https, inappbrowser,, ios, ssl
Attachments: InAppBrowser.java
Local https links are blocked by default in InAppBrowser (links using a local
SSL certificate which can't be verified by a 3rd party). Ideally, user should
be given an option to proceed or cancel the request like the default
desktop/mobile browsers do.
Right now, we have to overwrite the following API in Android to access such
URLs but onReceivedSslError() function gets called only for the main PhoneGap
window browser and not for InAppBrowser.
Create a new class:
public class CustomWebViewClient extends CordovaWebViewClient {
public static final String LOG_TAG = Plugin;
public CustomWebViewClient(DroidGap ctx) {
super(ctx);
Log.d(LOG_TAG, Constructor!);
}
@Override
public void onReceivedSslError(WebView view, SslErrorHandler handler,
SslError error) {
handler.proceed();
}
}
In the main class, we use our custom class as a web view client
CordovaWebViewClient webViewClient = new CustomWebViewClient(this);
webViewClient.setWebView(this.appView);
this.appView.setWebViewClient(webViewClient);
And similar type of code needs to be written for iOS.
InAppBrowser should pick up the SSL settings from the main web view and once
we overwrite the onReceivedSslError() function, then it should allow such
URLs in the InAppBrowser too.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Updated] (CB-5092) Geolocation - API Documentation and plugin.xml permissions mismatch
[
https://issues.apache.org/jira/browse/CB-5092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ian Clelland updated CB-5092:
-
Component/s: (was: Plugin Device Orientation)
Plugin Geolocation
Geolocation - API Documentation and plugin.xml permissions mismatch
---
Key: CB-5092
URL: https://issues.apache.org/jira/browse/CB-5092
Project: Apache Cordova
Issue Type: Bug
Components: Android, Plugin Geolocation
Affects Versions: 3.1.0
Reporter: Peter
Priority: Minor
API documentation for Geolocation
http://cordova.apache.org/docs/en/3.1.0/cordova_geolocation_geolocation.md.html#Geolocation
says that the following Android permissions are necessary
{code}
uses-permission android:name=android.permission.ACCESS_COARSE_LOCATION /
uses-permission android:name=android.permission.ACCESS_FINE_LOCATION /
uses-permission
android:name=android.permission.ACCESS_LOCATION_EXTRA_COMMANDS /
{code}
but the *cordova-plugin-geolocation* plugin does not have the
_ACCESS_LOCATION_EXTRA_COMMANDS_ in its plugins.xml
Is it missing from the plugins.xml, or is the documentation incorrect?
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Resolved] (CB-2962) phonegap doesn't call ajax callbacks when server sends 401 status
[ https://issues.apache.org/jira/browse/CB-2962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser resolved CB-2962. Resolution: Unresolved No activity, this bug has gone stale. phonegap doesn't call ajax callbacks when server sends 401 status - Key: CB-2962 URL: https://issues.apache.org/jira/browse/CB-2962 Project: Apache Cordova Issue Type: Bug Components: Android Affects Versions: 2.5.0 Reporter: Laurian Vostinar Assignee: Joe Bowser for more details see http://stackoverflow.com/questions/10305181/android-phonegap-ajax-does-not-fire-callback-for-unauthorized-401 and https://groups.google.com/forum/#!msg/phonegap/YKVGp8rRj9c/-ph6oRBOJHMJ -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CB-5092) Geolocation - API Documentation and plugin.xml permissions mismatch
[
https://issues.apache.org/jira/browse/CB-5092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ian Clelland updated CB-5092:
-
Component/s: (was: Plugin Device Orientation)
Plugin Geolocation
Geolocation - API Documentation and plugin.xml permissions mismatch
---
Key: CB-5092
URL: https://issues.apache.org/jira/browse/CB-5092
Project: Apache Cordova
Issue Type: Bug
Components: Android, Plugin Geolocation
Affects Versions: 3.1.0
Reporter: Peter
Priority: Minor
API documentation for Geolocation
http://cordova.apache.org/docs/en/3.1.0/cordova_geolocation_geolocation.md.html#Geolocation
says that the following Android permissions are necessary
{code}
uses-permission android:name=android.permission.ACCESS_COARSE_LOCATION /
uses-permission android:name=android.permission.ACCESS_FINE_LOCATION /
uses-permission
android:name=android.permission.ACCESS_LOCATION_EXTRA_COMMANDS /
{code}
but the *cordova-plugin-geolocation* plugin does not have the
_ACCESS_LOCATION_EXTRA_COMMANDS_ in its plugins.xml
Is it missing from the plugins.xml, or is the documentation incorrect?
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Resolved] (CB-3384) Resource Loading API for Android
[ https://issues.apache.org/jira/browse/CB-3384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser resolved CB-3384. Resolution: Implemented Still needs to be documented Resource Loading API for Android Key: CB-3384 URL: https://issues.apache.org/jira/browse/CB-3384 Project: Apache Cordova Issue Type: Improvement Components: Android Reporter: Andrew Grieve Assignee: Andrew Grieve Fix For: 3.2.0 Motivations: 1. Many plugins do not handle URLs correctly when they are in the form content: or file:///android_asset. 2. For the cordova-app-harness, there needs to be a way to re-route resource load requests so that the harness can load app resources while still respecting the content tag. Short Description All plugins can watch the loading of any uri's Eg: opening of files, the browser making requests to load files etc etc. In addition to watching they may assist in loading the uri's. For example, a use case here is - suppose a mimetype for a hypothetical extension .abc doesn't exist, a plugin could check the extension of a loaded uri and set the mimetype. This would now be set for all files loaded in the system. Pseudo code of the mechanism: 1. make a request 'R' to a uri. 2. loop through all plugins to see if any plugins change the request 3. if the request changes, set 'R' to this modified request and repeat step 3 4. load request 'R' and return result -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CB-3445) Move Cordova-Android Build Setup to Gradle
[ https://issues.apache.org/jira/browse/CB-3445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser updated CB-3445: --- Priority: Minor (was: Major) Move Cordova-Android Build Setup to Gradle -- Key: CB-3445 URL: https://issues.apache.org/jira/browse/CB-3445 Project: Apache Cordova Issue Type: Improvement Components: Android Reporter: Joe Bowser Assignee: Joe Bowser Priority: Minor Currently we're using ant for our setup, and our setup can break every time that the Android SDK updates and change its build.xml. However, the Android Team has created Gradle to be more robust such that it doesn't have the same problems as ant-based scripts. This also has the advantage of using Android Studio for development instead of Eclipse, and the ability for us to bundle resources, which is something we haven't been able to do before. Moving to Gradle has numerous advantages, but will break scripts, so this is to be moved in the post-3.0 timeframe. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CB-3445) Move Cordova-Android Build Setup to Gradle
[ https://issues.apache.org/jira/browse/CB-3445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser updated CB-3445: --- Fix Version/s: (was: 3.2.0) Move Cordova-Android Build Setup to Gradle -- Key: CB-3445 URL: https://issues.apache.org/jira/browse/CB-3445 Project: Apache Cordova Issue Type: Improvement Components: Android Reporter: Joe Bowser Assignee: Joe Bowser Currently we're using ant for our setup, and our setup can break every time that the Android SDK updates and change its build.xml. However, the Android Team has created Gradle to be more robust such that it doesn't have the same problems as ant-based scripts. This also has the advantage of using Android Studio for development instead of Eclipse, and the ability for us to bundle resources, which is something we haven't been able to do before. Moving to Gradle has numerous advantages, but will break scripts, so this is to be moved in the post-3.0 timeframe. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-3445) Move Cordova-Android Build Setup to Gradle
[ https://issues.apache.org/jira/browse/CB-3445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13809521#comment-13809521 ] Joe Bowser commented on CB-3445: Let's wait until Android SDK ships with Gradle before doing this. This would add another dependency. Move Cordova-Android Build Setup to Gradle -- Key: CB-3445 URL: https://issues.apache.org/jira/browse/CB-3445 Project: Apache Cordova Issue Type: Improvement Components: Android Reporter: Joe Bowser Assignee: Joe Bowser Currently we're using ant for our setup, and our setup can break every time that the Android SDK updates and change its build.xml. However, the Android Team has created Gradle to be more robust such that it doesn't have the same problems as ant-based scripts. This also has the advantage of using Android Studio for development instead of Eclipse, and the ability for us to bundle resources, which is something we haven't been able to do before. Moving to Gradle has numerous advantages, but will break scripts, so this is to be moved in the post-3.0 timeframe. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CB-3990) Implement optional GeckoView upon ./bin/create
[ https://issues.apache.org/jira/browse/CB-3990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser updated CB-3990: --- Priority: Minor (was: Major) I still can't get this to build properly. This needs more work before it's stable enough to do anything! Implement optional GeckoView upon ./bin/create -- Key: CB-3990 URL: https://issues.apache.org/jira/browse/CB-3990 Project: Apache Cordova Issue Type: Improvement Components: Android Reporter: Brian LeRoux Assignee: Joe Bowser Priority: Minor Add --use-gecko flag to ./bin/create Relevant to our interests from Mozilla's buzilla: * Bug 880107 is the tracking bug for the work. * Bug 880119 , bug 880121 and bug 880123 for discussion of improving the APIs. * bug 880118 prebuilt binaries -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CB-3187) Make FileTransfer accept a URL
[ https://issues.apache.org/jira/browse/CB-3187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser updated CB-3187: --- Summary: Make FileTransfer accept a URL (was: Stream/URI API for FileTransfer) This apparently works on iOS and Android for absolute URLs. Make FileTransfer accept a URL -- Key: CB-3187 URL: https://issues.apache.org/jira/browse/CB-3187 Project: Apache Cordova Issue Type: Improvement Components: Android, Plugin File Transfer Affects Versions: 2.6.0 Environment: Cordova 2.6.0 patched with commits from CB-2432 https://git-wip-us.apache.org/repos/asf?p=cordova-android.git;a=commit;h=b13166f5d92196ed3e1b2d2dfd4cef7242876d70 https://git-wip-us.apache.org/repos/asf?p=cordova-android.git;a=commit;h=191f31baa74d1dd99e321357c562d10f2c426f0c Reporter: Abel Muiño Assignee: Andrew Grieve The patches from CB-2432 move to the stream api to access content from the gallery, but since it is not available for FileTransfer yet, the resolved gallery items can not be easily uploaded to another service. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (CB-5233) Make resolveLocalFileSystemURL() work with asset-library:// URLs returned by the Camera API
Andrew Grieve created CB-5233: - Summary: Make resolveLocalFileSystemURL() work with asset-library:// URLs returned by the Camera API Key: CB-5233 URL: https://issues.apache.org/jira/browse/CB-5233 Project: Apache Cordova Issue Type: Bug Components: iOS, Plugin File Reporter: Andrew Grieve Assignee: Andrew Grieve Priority: Minor -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CB-3186) Make resolveLocalFileSystemURL() work with content:// URLs returned by the Camera API
[
https://issues.apache.org/jira/browse/CB-3186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Grieve updated CB-3186:
--
Summary: Make resolveLocalFileSystemURL() work with content:// URLs
returned by the Camera API (was: Exception resolving content: URIs returned
from the Gallery for Picasa pictures)
Make resolveLocalFileSystemURL() work with content:// URLs returned by the
Camera API
-
Key: CB-3186
URL: https://issues.apache.org/jira/browse/CB-3186
Project: Apache Cordova
Issue Type: Bug
Components: Android
Affects Versions: 2.6.0
Environment: Cordova 2.6.0 patched with commits from CB-2432
https://git-wip-us.apache.org/repos/asf?p=cordova-android.git;a=commit;h=b13166f5d92196ed3e1b2d2dfd4cef7242876d70
https://git-wip-us.apache.org/repos/asf?p=cordova-android.git;a=commit;h=191f31baa74d1dd99e321357c562d10f2c426f0c
Reporter: Abel Muiño
Assignee: Andrew Grieve
calling `window.resolveLocalFileSystemURI` with the returned URI results in
an error with the following log:
{noformat}
Object
File resolveLocalFileSystemURI File629493933
[content://com.google.android.gallery3d.provider/picasa/item/5825295055430535810]
processMessage failed: Message: S01 Camera629493932
scontent://com.google.android.gallery3d.provider/picasa/item/5825295055430535810
processMessage failed: Error: Error: Error calling method on NPObject.
processMessage failed: Stack: Error: Error calling method on NPObject.
at androidExec (file:///android_asset/www/native/cordova-2.6.0.js:859:48)
at file:///android_asset/www/native/cordova-2.6.0.js:6326:5
at [object Object].anonymous
(file:///android_asset/www/reporter/decks/report.js:136:23)
at [object Object].anonymous
(file:///android_asset/www/reporter/decks/report.js:3:61)
at [object Object].anonymous
(file:///android_asset/www/reporter/decks/report.js:169:19)
at [object Object].anonymous
(file:///android_asset/www/reporter/decks/report.js:3:61)
at Object.callbackFromNative
(file:///android_asset/www/native/cordova-2.6.0.js:291:54)
at processMessage
(file:///android_asset/www/native/cordova-2.6.0.js:970:21)
at Function.processMessages
(file:///android_asset/www/native/cordova-2.6.0.js:1008:17)
at pollOnce (file:///android_asset/www/native/cordova-2.6.0.js:874:17)
{noformat}
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Updated] (CB-3571) Add support for splash elements in config.xml
[
https://issues.apache.org/jira/browse/CB-3571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Bowser updated CB-3571:
---
Issue Type: Wish (was: Sub-task)
Parent: (was: CB-1108)
Add support for splash elements in config.xml
---
Key: CB-3571
URL: https://issues.apache.org/jira/browse/CB-3571
Project: Apache Cordova
Issue Type: Wish
Components: CLI
Affects Versions: Master
Reporter: Michael Brooks
Assignee: Mark Koudritsky
Similar to adding support for the {{icon}} element, we should add support
for the splash screen.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Resolved] (CB-1693) enable ability for app onload or init hook for plugin api
[ https://issues.apache.org/jira/browse/CB-1693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser resolved CB-1693. Resolution: Fixed enable ability for app onload or init hook for plugin api - Key: CB-1693 URL: https://issues.apache.org/jira/browse/CB-1693 Project: Apache Cordova Issue Type: Sub-task Components: Bada, BlackBerry, webOS, WP7 Reporter: Brian LeRoux Enable plugins to be loaded at startup in the config file. When a plugin is loaded, it calls an init function etc (which is usually the constructor of course) See callback-dev thread: http://markmail.org/thread/ecakmzk37vey4kf6 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CB-2606) Add support for icon elements in config.xml
[
https://issues.apache.org/jira/browse/CB-2606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Bowser updated CB-2606:
---
Issue Type: Wish (was: Sub-task)
Parent: (was: CB-1108)
Add support for icon elements in config.xml
-
Key: CB-2606
URL: https://issues.apache.org/jira/browse/CB-2606
Project: Apache Cordova
Issue Type: Wish
Components: Docs
Reporter: Filip Maj
Assignee: Mark Koudritsky
This feature would add support for specifying the application icon by
changing values inside the {{config.xml}} document.
Relevant details for Cordova:
- {{icon}} elements _may_ have {{width}} and {{height}} attributes
representing the preferred size of the icon in CSS pixels.
- {{icon}} elements _must_ have a {{src}} attribute, which contains a path
string relative to the {{www/}} folder (or equivalent) in the platform.
See [the Widget Spec's section on
icons|http://www.w3.org/TR/widgets/#the-icon-element-and-its-attributes] for
specifics.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Resolved] (CB-882) Cross mobile socket support
[ https://issues.apache.org/jira/browse/CB-882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser resolved CB-882. --- Resolution: Not A Problem There's a plugin for this in the registry. Cross mobile socket support --- Key: CB-882 URL: https://issues.apache.org/jira/browse/CB-882 Project: Apache Cordova Issue Type: New Feature Components: Android, Bada, CordovaJS, WP7 Reporter: Jordan Stout Assignee: Andrew Grieve Labels: features, socket, sockets I tested the use of socket.io in an iOS app and I was able to successfully communicate back and forth from mobile to desktop. All I did was grab the same socket.io script hosted from the node.js server (as a quick test)... Of course, this may be cool and all, but I'm not sure how cross mobile it is. How hard will it be to create native socket support for most (or all) devices so developers can talk to socket.io servers (or any other service) natively without including the socket.io client scripts? -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (CB-1108) Migrate config.xml to the W3C spec
[ https://issues.apache.org/jira/browse/CB-1108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser resolved CB-1108. Resolution: Incomplete Platforms have gone as far as they can. It's time to close this out and make the remaining tasks standalone. Migrate config.xml to the W3C spec -- Key: CB-1108 URL: https://issues.apache.org/jira/browse/CB-1108 Project: Apache Cordova Issue Type: New Feature Components: Android, Bada, BlackBerry, iOS, webOS, WP7 Affects Versions: 2.0.0 Reporter: Joe Bowser Assignee: Filip Maj In 2.0.0, we decided that config.xml should exist in some form. Unfortunately, that form has nothing to do with the W3C version. We should try to move towards the W3C version wherever possible. Android was the only one to actually have a config.xml added, mostly because creating this file was trivial. If this is not technically possible, the xml file should be changed back to cordova.xml. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (CB-4102) mobilespec filetransfer.spec.7 fails on file://android_asset/... (not in whitelist)
[ https://issues.apache.org/jira/browse/CB-4102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser resolved CB-4102. Resolution: Cannot Reproduce We can't make this fail anymore. Closing! mobilespec filetransfer.spec.7 fails on file://android_asset/... (not in whitelist) --- Key: CB-4102 URL: https://issues.apache.org/jira/browse/CB-4102 Project: Apache Cordova Issue Type: Bug Components: Android, mobile-spec, Plugin File Transfer Affects Versions: 3.0.0 Environment: Confirmed on Galaxy Nexus, Nexus 7 Reporter: David Kemp Assignee: Andrew Grieve file:///android_asset/... is blocked at the white list, but also cannot be handled by the okhttp module. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-5093) CLI builds version number inconsitently between iOS and Android
[ https://issues.apache.org/jira/browse/CB-5093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13809553#comment-13809553 ] Joe Bowser commented on CB-5093: Not sure where this needs to be fixed, but I'll look at the platform scripts first to see what the correct behaviour should be. CLI builds version number inconsitently between iOS and Android --- Key: CB-5093 URL: https://issues.apache.org/jira/browse/CB-5093 Project: Apache Cordova Issue Type: Bug Components: Android, CLI, iOS Affects Versions: 3.1.0 Reporter: Adam George Assignee: Joe Bowser I'm hoping this issue isn't just my ignorance, but I'm finding the app version number generation via the CLI to be inconsistent and odd. iOS and Android both support a version number (which is what is displayed in the app stores), as well as another string, which most people use as a build number. E.g. for iOS: Myapp-Info.plist: Bundle versions string, short: 1.0.0 (this is what will show in the app store) Bundle version: 0.0.3(this is some other build number) Android: AndroidManifest.xml: android:versionCode=1 android:versionName=0.0.3 versionName is what shows in the stores, and versionCode is typically used like a build number (as far as I can tell). My point is, in the cordova.xml, I only have the ability to set one of these version numbers. There is only a single version attribute. But we need two attributes, so we can set both version strings via the CLI. Secondly, how the version attribute is applied when building via the CLI is inconsistent. On iOS it's updating the build number, and not even touching the main version number that users will see in the store. Whereas Android has what I would expect as the correct behaviour. Anyway, please let me know if I've misunderstood anything. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Assigned] (CB-5093) CLI builds version number inconsitently between iOS and Android
[ https://issues.apache.org/jira/browse/CB-5093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser reassigned CB-5093: -- Assignee: Joe Bowser CLI builds version number inconsitently between iOS and Android --- Key: CB-5093 URL: https://issues.apache.org/jira/browse/CB-5093 Project: Apache Cordova Issue Type: Bug Components: Android, CLI, iOS Affects Versions: 3.1.0 Reporter: Adam George Assignee: Joe Bowser I'm hoping this issue isn't just my ignorance, but I'm finding the app version number generation via the CLI to be inconsistent and odd. iOS and Android both support a version number (which is what is displayed in the app stores), as well as another string, which most people use as a build number. E.g. for iOS: Myapp-Info.plist: Bundle versions string, short: 1.0.0 (this is what will show in the app store) Bundle version: 0.0.3(this is some other build number) Android: AndroidManifest.xml: android:versionCode=1 android:versionName=0.0.3 versionName is what shows in the stores, and versionCode is typically used like a build number (as far as I can tell). My point is, in the cordova.xml, I only have the ability to set one of these version numbers. There is only a single version attribute. But we need two attributes, so we can set both version strings via the CLI. Secondly, how the version attribute is applied when building via the CLI is inconsistent. On iOS it's updating the build number, and not even touching the main version number that users will see in the store. Whereas Android has what I would expect as the correct behaviour. Anyway, please let me know if I've misunderstood anything. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Assigned] (CB-5216) Can't hide the softkeyboard on Android
[ https://issues.apache.org/jira/browse/CB-5216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser reassigned CB-5216: -- Assignee: Joe Bowser Can't hide the softkeyboard on Android -- Key: CB-5216 URL: https://issues.apache.org/jira/browse/CB-5216 Project: Apache Cordova Issue Type: Bug Components: Android Affects Versions: 3.0.0, 3.1.0 Environment: Android 4.1.2, Jquerymobile, Reporter: Matias Stanislavsky Assignee: Joe Bowser We Can't hide the keyboard if a user clicks on a next button without entering anything. We've tried with a blur(), but it doesn't seem to be working. The keyboard doesn't hide. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-4805) Update cordova/run and cordova/lib/install-device to use latest ios-deploy for iOS 7
[ https://issues.apache.org/jira/browse/CB-4805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13809554#comment-13809554 ] ASF subversion and git services commented on CB-4805: - Commit 5a194a96bedf4470856eac6c1913c7c406ca64ae in branch refs/heads/master from [~shazron] [ https://git-wip-us.apache.org/repos/asf?p=cordova-ios.git;h=5a194a9 ] CB-4805 (refis) Update cordova/run and cordova/lib/install-device to use latest ios-deploy for iOS 7 Update cordova/run and cordova/lib/install-device to use latest ios-deploy for iOS 7 Key: CB-4805 URL: https://issues.apache.org/jira/browse/CB-4805 Project: Apache Cordova Issue Type: Task Components: iOS Affects Versions: Master Reporter: Shazron Abdullah Assignee: Shazron Abdullah Labels: ios7 Fix For: 3.2.0 See CB-4804 Update the required version in the scripts -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Assigned] (CB-5210) utc_offset is different for Android and iOS in the same timezone
[ https://issues.apache.org/jira/browse/CB-5210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser reassigned CB-5210: -- Assignee: Joe Bowser utc_offset is different for Android and iOS in the same timezone Key: CB-5210 URL: https://issues.apache.org/jira/browse/CB-5210 Project: Apache Cordova Issue Type: Bug Components: Android, iOS Affects Versions: 3.0.0 Environment: iOS 6.0.1, Android 4.2.2 Reporter: Ewan Summers Assignee: Joe Bowser Labels: features If you set both phones to the EST timezone (or any negative timezone) you'll notice that the values for utc_offset in a call to navigator.globalization.getDatePattern don't match for iOS and Android. However I briefly tested with positive offsets and they appeared to be the same for both devices. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Assigned] (CB-5046) Create defaults.xml that contains platform config.xml defaults for IOS
[ https://issues.apache.org/jira/browse/CB-5046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser reassigned CB-5046: -- Assignee: Braden Shepherdson Create defaults.xml that contains platform config.xml defaults for IOS -- Key: CB-5046 URL: https://issues.apache.org/jira/browse/CB-5046 Project: Apache Cordova Issue Type: Sub-task Components: iOS Reporter: Jeffrey Heifetz Assignee: Braden Shepherdson -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CB-5047) Create defaults.xml that contains platform config.xml defaults for Android
[ https://issues.apache.org/jira/browse/CB-5047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser updated CB-5047: --- Assignee: Braden Shepherdson (was: Joe Bowser) Create defaults.xml that contains platform config.xml defaults for Android -- Key: CB-5047 URL: https://issues.apache.org/jira/browse/CB-5047 Project: Apache Cordova Issue Type: Sub-task Components: Android Reporter: Jeffrey Heifetz Assignee: Braden Shepherdson Priority: Critical -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Assigned] (CB-5047) Create defaults.xml that contains platform config.xml defaults for Android
[ https://issues.apache.org/jira/browse/CB-5047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser reassigned CB-5047: -- Assignee: Joe Bowser Create defaults.xml that contains platform config.xml defaults for Android -- Key: CB-5047 URL: https://issues.apache.org/jira/browse/CB-5047 Project: Apache Cordova Issue Type: Sub-task Components: Android Reporter: Jeffrey Heifetz Assignee: Joe Bowser Priority: Critical -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CB-5047) Create defaults.xml that contains platform config.xml defaults for Android
[ https://issues.apache.org/jira/browse/CB-5047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser updated CB-5047: --- Priority: Critical (was: Major) Create defaults.xml that contains platform config.xml defaults for Android -- Key: CB-5047 URL: https://issues.apache.org/jira/browse/CB-5047 Project: Apache Cordova Issue Type: Sub-task Components: Android Reporter: Jeffrey Heifetz Priority: Critical -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (CB-4775) Rewrite Android's update script in node
[ https://issues.apache.org/jira/browse/CB-4775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Grieve resolved CB-4775. --- Resolution: Fixed https://git-wip-us.apache.org/repos/asf?p=cordova-android.git;a=commit;h=7c446b222d0c66dd9d2a23ef695a09d42669a9d3 Rewrite Android's update script in node --- Key: CB-4775 URL: https://issues.apache.org/jira/browse/CB-4775 Project: Apache Cordova Issue Type: Bug Components: Android Reporter: Andrew Grieve Assignee: Andrew Grieve And have it share logic with Create script. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CB-4605) Custom URL scheme support in config.xml
[ https://issues.apache.org/jira/browse/CB-4605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser updated CB-4605: --- Component/s: CLI The AndroidManifest.xml has to be changed for this to happen. There's also questions about app state, and Bundle handling. Custom URL scheme support in config.xml --- Key: CB-4605 URL: https://issues.apache.org/jira/browse/CB-4605 Project: Apache Cordova Issue Type: New Feature Components: Android, CLI, iOS Affects Versions: 3.0.0 Reporter: Kenneth Miles Assignee: Joe Bowser Priority: Minor Labels: features Original Estimate: 120h Remaining Estimate: 120h Phonegap supports Custom URL Schemes through config.xml, but functionality does not appear to be in Cordova. See “Custom URL Schemes” section @ https://build.phonegap.com/docs/config-xml -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CB-4667) Create projects compatible to Android Studio
[ https://issues.apache.org/jira/browse/CB-4667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser updated CB-4667: --- Priority: Minor (was: Major) Create projects compatible to Android Studio Key: CB-4667 URL: https://issues.apache.org/jira/browse/CB-4667 Project: Apache Cordova Issue Type: Wish Components: Android, CLI Affects Versions: 3.0.0 Environment: Windows 7, Android, Android Studio. Reporter: Venkata Kiran Assignee: Joe Bowser Priority: Minor Labels: features Right now there is no way to import the Cordova Android project created using cordova cli into Android Studio. It has to be imported first into Eclipse, and then export it to be compatible with Android Studio and then import into Android Studio. It would be good if the project can be directly imported into Android Studio -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-4404) android:windowSoftInputMode does not work
[
https://issues.apache.org/jira/browse/CB-4404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13809576#comment-13809576
]
Joe Bowser commented on CB-4404:
Here's a possible workaround. I'll bang my head against this and see if I can
make this work:
http://stackoverflow.com/questions/7417123/android-how-to-adjust-layout-in-full-screen-mode-when-softkeyboard-is-visible/19494006#19494006
android:windowSoftInputMode does not work
-
Key: CB-4404
URL: https://issues.apache.org/jira/browse/CB-4404
Project: Apache Cordova
Issue Type: Bug
Components: Android
Affects Versions: 2.9.0
Environment: * Mac OS 10.7.5
* Android 4.1.2 and 4.2.2 emulator using Intel's x86 images
Reporter: Daniel Trebbien
Assignee: Joe Bowser
_I recently posted a description of this issue to the phonegap group at
[https://groups.google.com/d/topic/phonegap/J-h0lt68x0g/discussion]._
I am testing out PhoneGap 2.9.0 in the Android emulator (using Intel's x86
images), and I am seeing the issue that the android:windowSoftInputMode
setting is not having an effect. By default, the setting is set to
adjustPan in the generated project, but when I actually focus a text
input, the soft keyboard appears on top of the app, but does not pan the
main window, and the input is usually hidden beneath the keyboard as a
result.
Steps to reproduce:
# Create a new PhoneGap 2.9.0 project using the {{cordova create}} utility.
Add the 'android' platform.
# Open the project in Eclipse.
# Edit {{index.html}} to add {{brbrbrbrbrbrbrinput
placeholder=Text box}} below the {{h1Apache Cordova/h1}} heading.
# Run the app in Android 4.1.2 or 4.2.2 emulator.
# Tap the input and notice that the soft keyboard is placed over the app
and the input is hidden beneath.
# Try changing the android:windowSoftInputMode setting in
{{AndroidManifest.xml}} to adjustResize, reload the app, and notice that
the app is not resized when the input receives keyboard focus.
I am seeing this problem in Android 4.1.2 and 4.2.2 emulator. In Android
4.0.3 emulator, the app pans as expected.
The strange thing is that if I load the www/ files in the Browser and focus
the input, then the window is resized to fit the soft keyboard like normal.
This seems to imply that android:windowSoftInputMode works fine in the
emulator, but there is some issue in PhoneGap that is preventing it from
working.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Created] (CB-5234) Add update script for ffos
Steve Gill created CB-5234: -- Summary: Add update script for ffos Key: CB-5234 URL: https://issues.apache.org/jira/browse/CB-5234 Project: Apache Cordova Issue Type: Bug Reporter: Steve Gill Assignee: Steve Gill Fix For: 3.2.0 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CB-611) Logging levels
[ https://issues.apache.org/jira/browse/CB-611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser updated CB-611: -- Component/s: (was: Android) This isn't applicable to Android, we never had a console.log plugin. Logging levels -- Key: CB-611 URL: https://issues.apache.org/jira/browse/CB-611 Project: Apache Cordova Issue Type: Sub-task Components: BlackBerry, CordovaJS, iOS, WP7 Affects Versions: Master Environment: Run Cordova/PhoneGap with Cordova-SQLitePlugin and some other plugins Reporter: Chris Brody Assignee: Patrick Mueller Fix For: Master Original Estimate: 48h Remaining Estimate: 48h I got a pull request on my Cordova-SQLitePlugin with a special logging function that is only logging when built as a debug version. I believe this issue should be solved in the core with a log function that is only logging when built as a debug version. Ideally a logging facility with multiple log levels. Please forgive me if this has already been done somewhere. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CB-200) FileTransfer should support uploading multiple files in one HTTP request
[ https://issues.apache.org/jira/browse/CB-200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser updated CB-200: -- Priority: Trivial (was: Major) FileTransfer should support uploading multiple files in one HTTP request Key: CB-200 URL: https://issues.apache.org/jira/browse/CB-200 Project: Apache Cordova Issue Type: Improvement Components: Android, Bada, BlackBerry, CordovaJS, Docs, iOS, mobile-spec, Qt, webOS, WP7 Affects Versions: 1.3.0 Environment: Windows XP, Android, Lenovo ThinkPad Reporter: Matt Accola Assignee: Andrew Grieve Priority: Trivial FileTransfer only allows one file to be uploaded at a time. Should allow multiple files to be uploaded at once. This might be necessary if the server-side service requires all files to be submitted at once to ensure any operations on the files are atomic. This question has been asked on the phonegap Google Group, http://groups.google.com/group/phonegap/browse_thread/thread/bdc40098c2954870. (Update: Since this requires a UI change for parity, I've added more components and moved it out of 1.7. This should be added to the Roadmap, so I'm leaving it assigned to myself so I'm reminded to do this - Joe) -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Assigned] (CB-5133) saveToPhotoAlbum throws exception on android
[
https://issues.apache.org/jira/browse/CB-5133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Bowser reassigned CB-5133:
--
Assignee: Joe Bowser
saveToPhotoAlbum throws exception on android
Key: CB-5133
URL: https://issues.apache.org/jira/browse/CB-5133
Project: Apache Cordova
Issue Type: Bug
Components: Android
Affects Versions: 3.1.0
Environment: android 2.3.7
Reporter: Petr Šimon
Assignee: Joe Bowser
trying:
{code}
navigator.camera.getPicture( onCameraSuccess, onCameraError,
{saveToPhotoAlbum: true });
{code}
{code}
10-20 16:21:07.778: E/(19552): can't open
'file:///mnt/sdcard/DCIM/Camera/1382257264583.jpg'
10-20 16:21:07.898: E/MediaScannerService(19552): Exception in handleMessage
10-20 16:21:07.898: E/MediaScannerService(19552):
java.lang.IllegalStateException: Unable to create new file:
file:///mnt/sdcard/DCIM/Camera/1382257264583.jpg
10-20 16:21:07.898: E/MediaScannerService(19552): at
com.android.providers.media.MediaProvider.ensureFile(MediaProvider.java:1880)
10-20 16:21:07.898: E/MediaScannerService(19552): at
com.android.providers.media.MediaProvider.insertInternal(MediaProvider.java:1990)
10-20 16:21:07.898: E/MediaScannerService(19552): at
com.android.providers.media.MediaProvider.insert(MediaProvider.java:1921)
10-20 16:21:07.898: E/MediaScannerService(19552): at
android.content.ContentProvider$Transport.insert(ContentProvider.java:198)
10-20 16:21:07.898: E/MediaScannerService(19552): at
android.media.MediaScanner$MyMediaScannerClient.endFile(MediaScanner.java:787)
10-20 16:21:07.898: E/MediaScannerService(19552): at
android.media.MediaScanner$MyMediaScannerClient.doScanFile(MediaScanner.java:525)
10-20 16:21:07.898: E/MediaScannerService(19552): at
android.media.MediaScanner.scanSingleFile(MediaScanner.java:1236)
10-20 16:21:07.898: E/MediaScannerService(19552): at
com.android.providers.media.MediaScannerService.scanFile(MediaScannerService.java:200)
10-20 16:21:07.898: E/MediaScannerService(19552): at
com.android.providers.media.MediaScannerService.access$100(MediaScannerService.java:48)
10-20 16:21:07.898: E/MediaScannerService(19552): at
com.android.providers.media.MediaScannerService$ServiceHandler.handleMessage(MediaScannerService.java:244)
10-20 16:21:07.898: E/MediaScannerService(19552): at
android.os.Handler.dispatchMessage(Handler.java:99)
10-20 16:21:07.898: E/MediaScannerService(19552): at
android.os.Looper.loop(Looper.java:130)
10-20 16:21:07.898: E/MediaScannerService(19552): at
com.android.providers.media.MediaScannerService.run(MediaScannerService.java:188)
10-20 16:21:07.898: E/MediaScannerService(19552): at
java.lang.Thread.run(Thread.java:1019)
{code}
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Assigned] (CB-5078) App crashes on samsung galaxy s3 with android 4.0.4 when using plugin that opens a new activity (camera,gallery,voice recorder, etc.)
[ https://issues.apache.org/jira/browse/CB-5078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser reassigned CB-5078: -- Assignee: Joe Bowser App crashes on samsung galaxy s3 with android 4.0.4 when using plugin that opens a new activity (camera,gallery,voice recorder, etc.) - Key: CB-5078 URL: https://issues.apache.org/jira/browse/CB-5078 Project: Apache Cordova Issue Type: Bug Components: Android, Plugin Camera, Plugin Media Capture Affects Versions: 3.0.0 Environment: samsung galaxy s3 with android 4.0.4. the app is based on phonegap 3.0.0 Reporter: Shay Stern Assignee: Joe Bowser Labels: android, plugin when using phonegap API for camera, media capture etc, or any other plugin which opens a new android activity, the main app restart itself. it happens also on an hello world app, so it doesn't happen because of high memory consumption app, or any internal defect. the defect is reproducible only on Samsung galaxy s3 with android version 4.0.4. it wasn't reproducible on Samsung galaxy s2 with 4.0.4 or Samsung galaxy s3 with 4.1.2. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Assigned] (CB-5213) navigation.connection.type
[
https://issues.apache.org/jira/browse/CB-5213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Bowser reassigned CB-5213:
--
Assignee: Joe Bowser
navigation.connection.type
--
Key: CB-5213
URL: https://issues.apache.org/jira/browse/CB-5213
Project: Apache Cordova
Issue Type: Bug
Components: Android
Affects Versions: 3.1.0
Environment: Tested on Androids: Samsung Galaxy SII(4.1.2) and
Samsung Galaxy SIII (4.1.2)
Reporter: Janko Vukotic
Assignee: Joe Bowser
Hi,
even with a dummy template code it wont work. I get this in Web console
Error initializing Network Connection: Class not found:85
I installed the plugin via plugman.
Here is the dummy code: (it alerts unknown in any case whether there is any
type of data connection or none)
!DOCTYPE HTML
html
head
script type=text/javascript charset=utf-8 src=cordova.js/script
script type=text/javascript charset=utf-8
var deviceInfo = function(){
alert(navigator.connection.type);
}
function init(){
document.addEventListener(deviceready, deviceInfo, true);
}
/script
/head
body onload=init();
/body
/html
Cheers!
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Resolved] (CB-5027) Application Error: There was a network error.
[ https://issues.apache.org/jira/browse/CB-5027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser resolved CB-5027. Resolution: Won't Fix We can't fix the Android Emulator. :( Application Error: There was a network error. - Key: CB-5027 URL: https://issues.apache.org/jira/browse/CB-5027 Project: Apache Cordova Issue Type: Bug Components: Android, App Hello World, CLI Affects Versions: 3.1.0 Environment: Windows7 Reporter: Paulo Pacheco Labels: android, cordova-cli, emulate, error 1 - Install Cordova CLI 3.1.0 2 - cordova create model org,sample ModelApp 3- cordova platform add android 4- cordova build -d android 5- cordova emulate android Error in LogCat: E/CordovaWebView(3677): CordovaWebView: TIMEOUT ERROR! Error in Emulator: There was a network error. (file:///android_asset/www/index.html) Tree of project: ├───.cordova │ └───hooks │ ├───after_build │ ├───after_compile │ ├───after_docs │ ├───after_emulate │ ├───after_platform_add │ ├───after_platform_ls │ ├───after_platform_rm │ ├───after_plugin_add │ ├───after_plugin_ls │ ├───after_plugin_rm │ ├───after_prepare │ ├───after_run │ ├───before_build │ ├───before_compile │ ├───before_docs │ ├───before_emulate │ ├───before_platform_add │ ├───before_platform_ls │ ├───before_platform_rm │ ├───before_plugin_add │ ├───before_plugin_ls │ ├───before_plugin_rm │ ├───before_prepare │ └───before_run ├───merges │ └───android ├───platforms │ └───android │ ├───assets │ │ └───www │ │ └───cordova-app-hello-world-3.1.0-5683220 │ │ └───www │ │ ├───css │ │ ├───img │ │ ├───js │ │ └───res │ │ ├───icon │ │ │ ├───android │ │ │ ├───bada │ │ │ ├───bada-wac │ │ │ ├───blackberry │ │ │ ├───blackberry10 │ │ │ ├───ios │ │ │ ├───tizen │ │ │ ├───webos │ │ │ └───windows-phone │ │ └───screen │ │ ├───android │ │ ├───bada │ │ ├───bada-wac │ │ ├───blackberry │ │ ├───blackberry10 │ │ └───ios │ ├───bin │ │ ├───classes │ │ │ └───br │ │ │ └───com │ │ │ └───softplan │ │ │ └───mobilelab │ │ ├───dexedLibs │ │ └───res │ │ ├───drawable │ │ ├───drawable-hdpi │ │ ├───drawable-ldpi │ │ ├───drawable-mdpi │ │ └───drawable-xhdpi │ ├───cordova │ │ ├───lib │ │ └───node_modules │ │ ├───.bin │ │ └───shelljs │ │ ├───bin │ │ └───scripts │ ├───gen │ │ └───br │ │ └───com │ │ └───softplan │ │ └───mobilelab │ ├───libs │ ├───res │ │ ├───drawable │ │ ├───drawable-hdpi │ │ ├───drawable-ldpi │ │ ├───drawable-mdpi │ │ ├───drawable-xhdpi │ │ ├───values │ │ └───xml │ └───src │ └───br │ └───com │ └───softplan │ └───mobilelab ├───plugins └───www └───cordova-app-hello-world-3.1.0-5683220 └───www ├───css ├───img ├───js └───res ├───icon │ ├───android │ ├───bada │ ├───bada-wac │ ├───blackberry │ ├───blackberry10 │ ├───ios │ ├───tizen │ ├───webos │ └───windows-phone └───screen ├───android ├───bada ├───bada-wac ├───blackberry ├───blackberry10 └───ios -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (CB-4285) Windows cordova emulate command doesn't install project
[ https://issues.apache.org/jira/browse/CB-4285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser resolved CB-4285. Resolution: Fixed Emulate works for me on Windows, if there are other issues here, please re-file them. Windows cordova emulate command doesn't install project --- Key: CB-4285 URL: https://issues.apache.org/jira/browse/CB-4285 Project: Apache Cordova Issue Type: Bug Components: Android, CLI Environment: Windows 7 Reporter: Lisa Seacat DeLuca Assignee: Braden Shepherdson I am able to add the android platform to a test cordova cli project and build just fine. When i go to run on an emulator the emulator opens but the project is never installed. This is the very simple case, no plugins were added. C:\workspaces\cordovacli\helloworldcordova -d emulate android cordova library for android already exists. No need to download. Continuing. Wrote out Android application name to helloworld Wrote out Android package name to com.helloworld Calling plugman.prepare for platform android Preparing android project... Processing configuration changes for plugins. Iterating over installed plugins: [] Writing out cordova_plugins.js... Running on emulator for platform android via command C:\workspaces\cordovacli\helloworld\platforms\android\cordova\run --emulator (output to fol low)... -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-5222) Add manual mobile-spec tests for Keyboard plugin org.apache.cordova.keyboard
[ https://issues.apache.org/jira/browse/CB-5222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13809603#comment-13809603 ] ASF subversion and git services commented on CB-5222: - Commit 4aa92445fb61c0ff6e98a44e6304928ebb8ac88e in branch refs/heads/master from [~shazron] [ https://git-wip-us.apache.org/repos/asf?p=cordova-mobile-spec.git;h=4aa9244 ] CB-5222 - add check for Keyboard plugin being installed Add manual mobile-spec tests for Keyboard plugin org.apache.cordova.keyboard Key: CB-5222 URL: https://issues.apache.org/jira/browse/CB-5222 Project: Apache Cordova Issue Type: Task Components: iOS, mobile-spec, Plugins Affects Versions: Master Reporter: Shazron Abdullah Assignee: Shazron Abdullah Fix For: 3.2.0 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-5122) Document supported workflows
[
https://issues.apache.org/jira/browse/CB-5122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13809643#comment-13809643
]
Mike Billau commented on CB-5122:
-
bq. Not sure I understand collapse, but if you mean simply copying the
README content into the doc (either one-time or dynamically), then I don't
agree.
The problem with the README.md files is that sometimes there will be duplicated
information in either the README or some guide, such as most of the
cordova-android README.md being duplicated in the Android Platform Guide, or
missing information, such as the registry commands and proxy settings for
cordova-cli being located only in the CLI's README.md.
bq. I suggest we get rid of Platform Guide instead feature a SoAndSo
Installation Guide, applicable to both CLI shell workflows...
I think that we definitely need to revamp the individual Platform Guides and
remove any workflow related information. It should just talk about how to
install the platform SDKs and anything else common to both workflows (getting
signing keys, etc.) It should say something like Now that you have installed
**Platform X** SDK, you can create an app using either _link to CLI guide_ or
_link to plugman guide_
bq. ...then a separate SoAndSo Development Guide detailing the actual shell
workflow, corresponding to the current Command-line Utilities page
If you are suggesting multiple guides for each platform (Android Development
Guide, iOS Development Guide) then I think I agree. The problem will be not
reproducing the plugman documentation. I think we should have a high level
Using Plugman guide that details all of the common pieces of the shell
workflow and plugman API (the missing counterpart to The Command-line
Interface guide). Then we can add any platform-specific steps or information
for this shell workflow in these platform-specific SoAndSo Development Guide
- such as logging capabilities, anything unique in the Command-line Utilities
section, and all of the information about loading a project into an IDE. Then
go back to the Using Plugman guide and insert a bunch of warning and
pointers.
bq. Not sure I agree naming the CLI guide to CLI Workflow, if that's what
you're suggesting. It implies a parallel set of Workflow topics elsewhere.
Agree. I'm not trying to suggest we call it the CLI Workflow, I was just
using that phrase because that's what we were all throwing around on the ML. I
do think that this guide is sorely lacking a parallel doc though, but that will
be rectified when we expand the Using Plugman guide.
Document supported workflows
Key: CB-5122
URL: https://issues.apache.org/jira/browse/CB-5122
Project: Apache Cordova
Issue Type: Bug
Components: Docs
Affects Versions: 3.1.0
Reporter: Mike Billau
Assignee: Mike Sierra
Based on the recent discussion here [1]we should document the two different
supported Cordova workflows: using the CLI, and using plugman and bin
scripts.
Some of this documentation already exists but needs to be clarified and
improved:
{{Overview guide -- Development Paths section}}. This talks about getting
started with the CLI and then mentions that you can switch to the
platform-specific SDK tools. This section should be rewritten to make it
clear that there are two distinct workflows, and that both are okay and
supported. It could list out some pros and cons of each workflow (I'm sure we
won't have any trouble finding those ;)). It should be prescriptive in that
users should be following one of the two workflows, but it shouldn't make any
statements about which is better.
{{The Command-line Interface guide}} -- The CLI workflow guide. It
generally looks complete except for some missing functionality that is
documented in the CLI's README.md file (tests, hooks, some commands (serve),
some merges info).
{{Platform Guides -- (Platform) -- (Platform) Command-line tools}} -- Each
platform has a Command-line tools doc that explains all of the command line
tools for that project and how to use them. We need to go through these
guides and verify that they are up to date and include all of the lower level
command line tools and scripts. It should read like a tutorial in the same
way that the Command-line Interface guide does.
{{Using Plugman to Manage Plugins}} First, this guide needs to get exposed;
I can't find any way to get to this guide from the docs and even had to ask a
user how she managed to find it (a link from Plugman's readme!). This guide
needs to be expanded quite a bit; we can probably fold most/all of Plugman's
README.md file into this guide since it will be platform agnostic.
I think those are the only pieces in the docs that need to be changed.
[1]
[jira] [Commented] (CB-4890) Reference to plugins.xml should be config.xml
[
https://issues.apache.org/jira/browse/CB-4890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13809690#comment-13809690
]
ASF subversion and git services commented on CB-4890:
-
Commit 23fa7310f81ad198bdf2b2fcf6892a37bd589fa4 in branch refs/heads/master
from [~mrbillau]
[ https://git-wip-us.apache.org/repos/asf?p=cordova-docs.git;h=23fa731 ]
CB-4890: fix edge and backport to 3.0, 3.1
Reference to plugins.xml should be config.xml
-
Key: CB-4890
URL: https://issues.apache.org/jira/browse/CB-4890
Project: Apache Cordova
Issue Type: Improvement
Components: Docs
Affects Versions: 2.9.0
Reporter: Peter
Assignee: Michael Brooks
Priority: Trivial
The Capture API documentation for Android (see Permissions section) is
still referring to plugins.xml instead of config.xml
{quote}
Permissions
Android
app/res/xml/plugins.xml
{quote}
http://cordova.apache.org/docs/en/2.9.0/cordova_media_capture_capture.md.html#Capture
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (CB-4890) Reference to plugins.xml should be config.xml
[
https://issues.apache.org/jira/browse/CB-4890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13809692#comment-13809692
]
Michael Brooks commented on CB-4890:
Nice catch.
Reference to plugins.xml should be config.xml
-
Key: CB-4890
URL: https://issues.apache.org/jira/browse/CB-4890
Project: Apache Cordova
Issue Type: Improvement
Components: Docs
Affects Versions: 2.9.0
Reporter: Peter
Assignee: Michael Brooks
Priority: Trivial
The Capture API documentation for Android (see Permissions section) is
still referring to plugins.xml instead of config.xml
{quote}
Permissions
Android
app/res/xml/plugins.xml
{quote}
http://cordova.apache.org/docs/en/2.9.0/cordova_media_capture_capture.md.html#Capture
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Resolved] (CB-4890) Reference to plugins.xml should be config.xml
[
https://issues.apache.org/jira/browse/CB-4890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Billau resolved CB-4890.
-
Resolution: Fixed
Reference to plugins.xml should be config.xml
-
Key: CB-4890
URL: https://issues.apache.org/jira/browse/CB-4890
Project: Apache Cordova
Issue Type: Improvement
Components: Docs
Affects Versions: 2.9.0
Reporter: Peter
Assignee: Michael Brooks
Priority: Trivial
The Capture API documentation for Android (see Permissions section) is
still referring to plugins.xml instead of config.xml
{quote}
Permissions
Android
app/res/xml/plugins.xml
{quote}
http://cordova.apache.org/docs/en/2.9.0/cordova_media_capture_capture.md.html#Capture
--
This message was sent by Atlassian JIRA
(v6.1#6144)
