date:20140612

Javier Puerto created CB-6928:
-

 Summary: Wrong behaviour transferring cacheable content
 Key: CB-6928
 URL: https://issues.apache.org/jira/browse/CB-6928
 Project: Apache Cordova
  Issue Type: Bug
  Components: Plugin File Transfer
Affects Versions: 3.5.0
Reporter: Javier Puerto
Priority: Minor


Use case:
Transfer resources from server to the device. To avoid unnecessary use of the 
device bandwidth, the resources that exists already are checked with the 
If-Modified-Since header so server can return 304 status code and update just 
in case that is needed.

Result for Android test:
The plugin doesn't care about the status code, if the request is success, open 
the InputStream and copy the content to the file. The problem is that a HTTP 
status of 304 has no response and that leads to a corrupted file transfer.

Fix:
If status code is 304, doesn't makes sense to process the InputStream. Read the 
status code after connection and if it's 304, skip the copy process and return 
the file entity like a success transfer.

I've tested for Android only.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Resolved] (CB-6908) camera modified.jpg with resolveLocalFileSystemURL

2014-06-12 Thread Nestor PS (JIRA)


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

Nestor PS resolved CB-6908.
---

Resolution: Not a Problem

 camera modified.jpg with resolveLocalFileSystemURL
 --

 Key: CB-6908
 URL: https://issues.apache.org/jira/browse/CB-6908
 Project: Apache Cordova
  Issue Type: Bug
  Components: Plugin Camera, Plugin File
Affects Versions: 3.5.0
 Environment: Android 2.3.6
 Samsung s1 GT-I9003
Reporter: Nestor PS
Priority: Blocker
  Labels: camera, file

 I'm having problems trying to store url photos into a database from gallery.
 With resolveLocalFileSystemURL and fileEntry.toURL() and getting the full 
 path of the image with no problems. But when I get a vertical image I'm 
 getting something like:
 cache/modified.jpg with resolveLocalFileSystemURL and 
 cache/modified.jpg?  without resolveLocalFileSystemURL 
 resolveLocalFileSystemURL is not resolving the path of the modified jpg.
 Without resolveLocalFileSystemURL the path seems to be right but is not 
 persistent. If I launch the app days after all the images pointing to 
 cache/modified.jpg? are the same.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (CB-6908) camera modified.jpg with resolveLocalFileSystemURL

2014-06-12 Thread Nestor PS (JIRA)


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

Nestor PS commented on CB-6908:
---

Hi,
yes I'm requesting the image with correctOrientation equals true.
So, I have to copy the file to another location. OK..

 camera modified.jpg with resolveLocalFileSystemURL
 --

 Key: CB-6908
 URL: https://issues.apache.org/jira/browse/CB-6908
 Project: Apache Cordova
  Issue Type: Bug
  Components: Plugin Camera, Plugin File
Affects Versions: 3.5.0
 Environment: Android 2.3.6
 Samsung s1 GT-I9003
Reporter: Nestor PS
Priority: Blocker
  Labels: camera, file

 I'm having problems trying to store url photos into a database from gallery.
 With resolveLocalFileSystemURL and fileEntry.toURL() and getting the full 
 path of the image with no problems. But when I get a vertical image I'm 
 getting something like:
 cache/modified.jpg with resolveLocalFileSystemURL and 
 cache/modified.jpg?  without resolveLocalFileSystemURL 
 resolveLocalFileSystemURL is not resolving the path of the modified jpg.
 Without resolveLocalFileSystemURL the path seems to be right but is not 
 persistent. If I launch the app days after all the images pointing to 
 cache/modified.jpg? are the same.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (CB-6928) Wrong behaviour transferring cacheable content


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

Javier Puerto commented on CB-6928:
---

I've created a fix for Android as it's the platform that I've tested. The fix 
can be found in the forked repository: 
https://github.com/jpuerto/cordova-plugin-file-transfer

 Wrong behaviour transferring cacheable content
 --

 Key: CB-6928
 URL: https://issues.apache.org/jira/browse/CB-6928
 Project: Apache Cordova
  Issue Type: Bug
  Components: Plugin File Transfer
Affects Versions: 3.5.0
Reporter: Javier Puerto
Priority: Minor

 Use case:
 Transfer resources from server to the device. To avoid unnecessary use of the 
 device bandwidth, the resources that exists already are checked with the 
 If-Modified-Since header so server can return 304 status code and update 
 just in case that is needed.
 Result for Android test:
 The plugin doesn't care about the status code, if the request is success, 
 open the InputStream and copy the content to the file. The problem is that a 
 HTTP status of 304 has no response and that leads to a corrupted file 
 transfer.
 Fix:
 If status code is 304, doesn't makes sense to process the InputStream. Read 
 the status code after connection and if it's 304, skip the copy process and 
 return the file entity like a success transfer.
 I've tested for Android only.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (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:comment-tabpanelfocusedCommentId=14028990#comment-14028990
 ] 

ASF GitHub Bot commented on CB-2606:


Github user rohitagg28 commented on the pull request:

https://github.com/apache/cordova-cli/pull/126#issuecomment-45851225
  
Hi I am integrating the icon for my app as using the trailing code but I am 
unable to add splashscreen to my app ,can you suggest anything.

 icon src=/res/android/icon-36-ldpi.png  density=ldpi /
icon src=/res/android/icon-48-mdpi.png  density=mdpi /
icon src=/res/android/icon-72-hdpi.png  density=hdpi /
icon src=/res/android/icon-96-xhdpi.png density=xhdpi /


 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.2#6252)

[jira] [Created] (CB-6929) Paths containing underscores cannot be loaded with XMLHttpRequest under Android

2014-06-12 Thread Chris Barnard (JIRA)

Chris Barnard created CB-6929:
-

 Summary: Paths containing underscores cannot be loaded with 
XMLHttpRequest under Android
 Key: CB-6929
 URL: https://issues.apache.org/jira/browse/CB-6929
 Project: Apache Cordova
  Issue Type: Bug
  Components: Android
Affects Versions: 3.4.0
 Environment: Tested within Android emulator and on Android devices 
running ICS and Jelly bean.
Reporter: Chris Barnard


If I create a new Cordova app, and place a JSON file within a folder beginning 
with an underscore, (eg _data), when I try to load it with XMLHttpRequest, the 
returning data is always null.

This only seems to happen on Android.

If I take the underscore out, the file loads fine. I also tried URL encoding 
the URL when loading the file, but this made no difference.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (CB-6928) Wrong behaviour transferring cacheable content

2014-06-12 Thread ASF subversion and git services (JIRA)


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

ASF GitHub Bot commented on CB-6928:


GitHub user jpuerto opened a pull request:

https://github.com/apache/cordova-plugin-file-transfer/pull/31

CB-6928: Implements NOT_MODIFIED check downloading resources.

As described in the issue https://issues.apache.org/jira/browse/CB-6928
A 304 status code will corrupt the transferred resource. This patch checks 
the status code and if the resource is cached, return as success with no 
actions.

I've move also the OutputStream declaration to use only if it's necessary 
and avoid unnecessary extra close method call.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/jpuerto/cordova-plugin-file-transfer master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cordova-plugin-file-transfer/pull/31.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #31


commit 74709aaf12c919400a6ca24862b8598cefc1ce80
Author: Javier Puerto javier.pue...@becompany.ch
Date:   2014-06-12T08:34:42Z

CB-6928: Open output stream only if it's necessary.

commit b7a03c210dc592f2052a45272fd123e77d3d2e67
Author: Javier Puerto javier.pue...@becompany.ch
Date:   2014-06-12T08:46:34Z

CB-6928: Implements NOT_MODIFIED check downloading resources.




 Wrong behaviour transferring cacheable content
 --

 Key: CB-6928
 URL: https://issues.apache.org/jira/browse/CB-6928
 Project: Apache Cordova
  Issue Type: Bug
  Components: Plugin File Transfer
Affects Versions: 3.5.0
Reporter: Javier Puerto
Priority: Minor

 Use case:
 Transfer resources from server to the device. To avoid unnecessary use of the 
 device bandwidth, the resources that exists already are checked with the 
 If-Modified-Since header so server can return 304 status code and update 
 just in case that is needed.
 Result for Android test:
 The plugin doesn't care about the status code, if the request is success, 
 open the InputStream and copy the content to the file. The problem is that a 
 HTTP status of 304 has no response and that leads to a corrupted file 
 transfer.
 Fix:
 If status code is 304, doesn't makes sense to process the InputStream. Read 
 the status code after connection and if it's 304, skip the copy process and 
 return the file entity like a success transfer.
 I've tested for Android only.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Closed] (CB-5932) Please delete old releases from mirroring system

2014-06-12 Thread Sebb (JIRA)


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

Sebb closed CB-5932.



 Please delete old releases from mirroring system
 

 Key: CB-5932
 URL: https://issues.apache.org/jira/browse/CB-5932
 Project: Apache Cordova
  Issue Type: Bug
  Components: Website
Affects Versions: 2.9.1
Reporter: Sebb

 To reduce the load on the ASF mirrors, projects are required to delete old 
 releases [1]
 Please can you remove all non-current releases?
 Thanks!
 [1] http://www.apache.org/dev/release.html#when-to-archive



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Resolved] (CB-5932) Please delete old releases from mirroring system

2014-06-12 Thread Sebb (JIRA)


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

Sebb resolved CB-5932.
--

Resolution: Fixed

Seems this was fixed some while ago

 Please delete old releases from mirroring system
 

 Key: CB-5932
 URL: https://issues.apache.org/jira/browse/CB-5932
 Project: Apache Cordova
  Issue Type: Bug
  Components: Website
Affects Versions: 2.9.1
Reporter: Sebb

 To reduce the load on the ASF mirrors, projects are required to delete old 
 releases [1]
 Please can you remove all non-current releases?
 Thanks!
 [1] http://www.apache.org/dev/release.html#when-to-archive



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Created] (CB-6930) Tools Release June 12, 2014

2014-06-12 Thread Ian Clelland (JIRA)

Ian Clelland created CB-6930:


 Summary: Tools Release June 12, 2014
 Key: CB-6930
 URL: https://issues.apache.org/jira/browse/CB-6930
 Project: Apache Cordova
  Issue Type: Bug
  Components: CLI, CordovaLib, Plugman
Affects Versions: 3.5.0
Reporter: Ian Clelland
Assignee: Ian Clelland


Following steps at 
https://github.com/apache/cordova-coho/blob/master/docs/tools-release-process.md



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Created] (CB-6931) Audit licenses

2014-06-12 Thread Ian Clelland (JIRA)

Ian Clelland created CB-6931:


 Summary: Audit licenses
 Key: CB-6931
 URL: https://issues.apache.org/jira/browse/CB-6931
 Project: Apache Cordova
  Issue Type: Sub-task
  Components: CLI, CordovaLib, Plugman
Reporter: Ian Clelland
Assignee: Ian Clelland






--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (CB-6931) Audit licenses


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

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

Commit 5e41bfb6bfddf59851aa99c177d5bc91efbf3bc6 in cordova-plugman's branch 
refs/heads/master from [~iclelland]
[ https://git-wip-us.apache.org/repos/asf?p=cordova-plugman.git;h=5e41bfb ]

CB-6931: Fix licence headers in plugman


 Audit licenses
 --

 Key: CB-6931
 URL: https://issues.apache.org/jira/browse/CB-6931
 Project: Apache Cordova
  Issue Type: Sub-task
  Components: CLI, CordovaLib, Plugman
Reporter: Ian Clelland
Assignee: Ian Clelland





--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Created] (CB-6932) Cannot build wp8 under Chinese (Simplified) System locale

2014-06-12 Thread Vladimir Kotikov (JIRA)

Vladimir Kotikov created CB-6932:


 Summary: Cannot build wp8 under Chinese (Simplified) System locale
 Key: CB-6932
 URL: https://issues.apache.org/jira/browse/CB-6932
 Project: Apache Cordova
  Issue Type: Bug
  Components: WP8
Affects Versions: 3.6.0
 Environment: Windows 8.1, Simlified Chinese locale
Reporter: Vladimir Kotikov
Assignee: Jesse MacFadyen
 Fix For: 3.6.0


*Steps to reproduce:*
#. Bring up a node.js command prompt.
#. If cordova is not installed, install using 'npm install -g cordova'.
#. cordova create hello
#. cd hello
#. cordova platform add wp8
#. cordova build wp8

Error appears.
{{noformat}}
D:\PROJECTS\Temp\test-bom\platforms\wp8\App.xaml(1,1,1,1): error : Invalid 
character in the given encoding. Line 1, position 1. 
[D:\PROJECTS\Temp\test-bom\platforms\wp8\HelloCordova.csproj]
{{noformat}}

There is a malformed files that changed during create process for the wp8 
project under the Chinese system locale. It looks like create.js is 
interpreting the initial file header incorrectly with the Chinese system 
locale, then printing it out to the file.

Build will fail under a different System locale as well.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Updated] (CB-6932) Cannot build wp8 under Chinese (Simplified) System locale

2014-06-12 Thread Vladimir Kotikov (JIRA)

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

Vladimir Kotikov updated CB-6932:
-

Description:
*Steps to reproduce:*
#. Bring up a node.js command prompt.
#. If cordova is not installed, install using 'npm install -g cordova'.
#. cordova create hello
#. cd hello
#. cordova platform add wp8
#. cordova build wp8

Error appears.
{noformat}
D:\PROJECTS\Temp\test-bom\platforms\wp8\App.xaml(1,1,1,1): error : Invalid
character in the given encoding. Line 1, position 1.
[D:\PROJECTS\Temp\test-bom\platforms\wp8\HelloCordova.csproj]
{noformat}
There is a malformed files that changed during create process for the wp8
project under the Chinese system locale. It looks like create.js is
interpreting the initial file header incorrectly with the Chinese system
locale, then printing it out to the file.

Build will fail under a different System locale as well.

was:
*Steps to reproduce:*
#. Bring up a node.js command prompt.
#. If cordova is not installed, install using 'npm install -g cordova'.
#. cordova create hello
#. cd hello
#. cordova platform add wp8
#. cordova build wp8

Error appears.
{{noformat}}
D:\PROJECTS\Temp\test-bom\platforms\wp8\App.xaml(1,1,1,1): error : Invalid
character in the given encoding. Line 1, position 1.
[D:\PROJECTS\Temp\test-bom\platforms\wp8\HelloCordova.csproj]
{{noformat}}

There is a malformed files that changed during create process for the wp8
project under the Chinese system locale. It looks like create.js is
interpreting the initial file header incorrectly with the Chinese system
locale, then printing it out to the file.

Build will fail under a different System locale as well.

Cannot build wp8 under Chinese (Simplified) System locale
-

Key: CB-6932
URL: https://issues.apache.org/jira/browse/CB-6932
Project: Apache Cordova
Issue Type: Bug
Components: WP8
Affects Versions: 3.6.0
Environment: Windows 8.1, Simlified Chinese locale
Reporter: Vladimir Kotikov
Assignee: Jesse MacFadyen
Labels: chinese, locale, wp8
Fix For: 3.6.0

*Steps to reproduce:*
#. Bring up a node.js command prompt.
#. If cordova is not installed, install using 'npm install -g cordova'.
#. cordova create hello
#. cd hello
#. cordova platform add wp8
#. cordova build wp8
Error appears.
{noformat}
D:\PROJECTS\Temp\test-bom\platforms\wp8\App.xaml(1,1,1,1): error : Invalid
character in the given encoding. Line 1, position 1.
[D:\PROJECTS\Temp\test-bom\platforms\wp8\HelloCordova.csproj]
{noformat}
There is a malformed files that changed during create process for the wp8
project under the Chinese system locale. It looks like create.js is
interpreting the initial file header incorrectly with the Chinese system
locale, then printing it out to the file.
Build will fail under a different System locale as well.

--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (CB-6932) Cannot build wp8 under Chinese (Simplified) System locale

2014-06-12 Thread ASF subversion and git services (JIRA)


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

ASF GitHub Bot commented on CB-6932:


GitHub user vladimir-kotikov opened a pull request:

https://github.com/apache/cordova-wp8/pull/40

CB-6932 Cannot build wp8 under Chinese (Simplified) System locale

This fixes error with incorrect handling of utf-8 ecoded project files 
during create script for WP8.
Issue: [CB-6932](https://issues.apache.org/jira/browse/CB-6932)

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/MSOpenTech/cordova-wp8 CB-6932

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cordova-wp8/pull/40.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #40


commit ac097f2801d4defe5e4d445e10b7102001631a54
Author: Vladimir Kotikov v-vlk...@microsoft.com
Date:   2014-06-12T13:18:13Z

Fixes handling of UTF-8 encoded project files.




 Cannot build wp8 under Chinese (Simplified) System locale
 -

 Key: CB-6932
 URL: https://issues.apache.org/jira/browse/CB-6932
 Project: Apache Cordova
  Issue Type: Bug
  Components: WP8
Affects Versions: 3.6.0
 Environment: Windows 8.1, Simlified Chinese locale
Reporter: Vladimir Kotikov
Assignee: Jesse MacFadyen
  Labels: chinese, locale, wp8
 Fix For: 3.6.0


 *Steps to reproduce:*
 # Set Region  Administrative  Change System Locale to Chinese (Simplified, 
 China).
 # Restart machine.
 # cordova create hello
 # cd hello
 # cordova platform add wp8
 # cordova build wp8
 Error appears.
 {noformat}
 D:\PROJECTS\Temp\test-bom\platforms\wp8\App.xaml(1,1,1,1): error : Invalid 
 character in the given encoding. Line 1, position 1. 
 [D:\PROJECTS\Temp\test-bom\platforms\wp8\HelloCordova.csproj]
 {noformat}
 There is a malformed files that changed during create process for the wp8 
 project under the Chinese system locale. It looks like create.js is 
 interpreting the initial file header incorrectly with the Chinese system 
 locale, then printing it out to the file.
 Build will fail under a different System locale as well.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Updated] (CB-6932) Cannot build wp8 under Chinese (Simplified) System locale

2014-06-12 Thread Vladimir Kotikov (JIRA)

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

Vladimir Kotikov updated CB-6932:
-

Description:
*Steps to reproduce:*
# Set Region Administrative Change System Locale to Chinese (Simplified,
China).
# Restart machine.

# cordova create hello
# cd hello
# cordova platform add wp8
# cordova build wp8

Build will fail under a different System locale as well.

was:
*Steps to reproduce:*
# Bring up a node.js command prompt.
# If cordova is not installed, install using 'npm install -g cordova'.
# cordova create hello
# cd hello
# cordova platform add wp8
# cordova build wp8

Build will fail under a different System locale as well.

Cannot build wp8 under Chinese (Simplified) System locale
-

*Steps to reproduce:*
# Set Region Administrative Change System Locale to Chinese (Simplified,
China).
# Restart machine.
# cordova create hello
# cd hello
# cordova platform add wp8
# cordova build wp8
Error appears.
{noformat}
D:\PROJECTS\Temp\test-bom\platforms\wp8\App.xaml(1,1,1,1): error : Invalid
character in the given encoding. Line 1, position 1.
[D:\PROJECTS\Temp\test-bom\platforms\wp8\HelloCordova.csproj]
{noformat}
There is a malformed files that changed during create process for the wp8
project under the Chinese system locale. It looks like create.js is
interpreting the initial file header incorrectly with the Chinese system
locale, then printing it out to the file.
Build will fail under a different System locale as well.

--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (CB-4404) android:windowSoftInputMode does not work

2014-06-12 Thread Emanuele (JIRA)

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

Emanuele commented on CB-4404:
--

In the AndroidManifest.xml created with cordova platform add android the
attribute android:windowSoftInputMode=adjustPan has a wrong position.
It should be on the element activity and not on the manifest.

http://developer.android.com/guide/topics/manifest/activity-element.html#wsoft

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: Andrew Grieve

_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.2#6252)

[jira] [Commented] (CB-6931) Audit licenses


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

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

Commit 8fec9a9022492052a29a4f938ebba32d11537bd5 in cordova-lib's branch 
refs/heads/master from [~iclelland]
[ https://git-wip-us.apache.org/repos/asf?p=cordova-lib.git;h=8fec9a9 ]

CB-6931: Fix licence headers in cordova-lib


 Audit licenses
 --

 Key: CB-6931
 URL: https://issues.apache.org/jira/browse/CB-6931
 Project: Apache Cordova
  Issue Type: Sub-task
  Components: CLI, CordovaLib, Plugman
Reporter: Ian Clelland
Assignee: Ian Clelland





--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Resolved] (CB-6929) Paths containing underscores cannot be loaded with XMLHttpRequest under Android

2014-06-12 Thread Andrew Grieve (JIRA)


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

Andrew Grieve resolved CB-6929.
---

Resolution: Won't Fix
  Assignee: Andrew Grieve

An unfortunate thing indeed. It's an Android build problem where the build 
system treats leading _ as ignore this directory. You can change this 
behaviour when building from the command-line by setting the 
aapt.resource.filter ant property, but there's no way to fix it when building 
with Eclipse that I know of. 

 Paths containing underscores cannot be loaded with XMLHttpRequest under 
 Android
 ---

 Key: CB-6929
 URL: https://issues.apache.org/jira/browse/CB-6929
 Project: Apache Cordova
  Issue Type: Bug
  Components: Android
Affects Versions: 3.4.0
 Environment: Tested within Android emulator and on Android devices 
 running ICS and Jelly bean.
Reporter: Chris Barnard
Assignee: Andrew Grieve

 If I create a new Cordova app, and place a JSON file within a folder 
 beginning with an underscore, (eg _data), when I try to load it with 
 XMLHttpRequest, the returning data is always null.
 This only seems to happen on Android.
 If I take the underscore out, the file loads fine. I also tried URL encoding 
 the URL when loading the file, but this made no difference.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (CB-6929) Paths containing underscores cannot be loaded with XMLHttpRequest under Android

2014-06-12 Thread Chris Barnard (JIRA)


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

Chris Barnard commented on CB-6929:
---

Thanks - I had no idea this was a build issue! Time to re-think my folder 
naming conventions.

 Paths containing underscores cannot be loaded with XMLHttpRequest under 
 Android
 ---

 Key: CB-6929
 URL: https://issues.apache.org/jira/browse/CB-6929
 Project: Apache Cordova
  Issue Type: Bug
  Components: Android
Affects Versions: 3.4.0
 Environment: Tested within Android emulator and on Android devices 
 running ICS and Jelly bean.
Reporter: Chris Barnard
Assignee: Andrew Grieve

 If I create a new Cordova app, and place a JSON file within a folder 
 beginning with an underscore, (eg _data), when I try to load it with 
 XMLHttpRequest, the returning data is always null.
 This only seems to happen on Android.
 If I take the underscore out, the file loads fine. I also tried URL encoding 
 the URL when loading the file, but this made no difference.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (CB-6925) simulator detection should fail gracefully when no DHCP leases are present

2014-06-12 Thread ASF subversion and git services (JIRA)


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

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

Commit 8ca4044df41637fbebf39e6a3ac7a13e80cbc9c1 in cordova-blackberry's branch 
refs/heads/master from [~jsoref]
[ https://git-wip-us.apache.org/repos/asf?p=cordova-blackberry.git;h=8ca4044 ]

CB-6925 simulator detection: fail gracefully w/ no DHCP leases


 simulator detection should fail gracefully when no DHCP leases are present
 --

 Key: CB-6925
 URL: https://issues.apache.org/jira/browse/CB-6925
 Project: Apache Cordova
  Issue Type: Bug
  Components: BlackBerry
Affects Versions: 3.5.0
Reporter: Josh Soref
Assignee: Josh Soref

 if you try to use emulate and you don't have any leases, you get this error:
 project\platforms\blackberry10\cordova\lib\target-utils.js:213 
 dhcpIPs = dhcpIPs.map(function (result) { 
   ^ 
 TypeError: Cannot call method 'map' of null 
 at project\platforms\blackberry10\cordova\lib\target-utils.js 
 :213:35 
 at fs.js:266:14 
 at Object.oncomplete (fs.js:107:15) 



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (CB-6925) simulator detection should fail gracefully when no DHCP leases are present


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

ASF GitHub Bot commented on CB-6925:


Github user asfgit closed the pull request at:

https://github.com/apache/cordova-blackberry/pull/161


 simulator detection should fail gracefully when no DHCP leases are present
 --

 Key: CB-6925
 URL: https://issues.apache.org/jira/browse/CB-6925
 Project: Apache Cordova
  Issue Type: Bug
  Components: BlackBerry
Affects Versions: 3.5.0
Reporter: Josh Soref
Assignee: Josh Soref

 if you try to use emulate and you don't have any leases, you get this error:
 project\platforms\blackberry10\cordova\lib\target-utils.js:213 
 dhcpIPs = dhcpIPs.map(function (result) { 
   ^ 
 TypeError: Cannot call method 'map' of null 
 at project\platforms\blackberry10\cordova\lib\target-utils.js 
 :213:35 
 at fs.js:266:14 
 at Object.oncomplete (fs.js:107:15) 



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (CB-6928) Wrong behaviour transferring cacheable content

2014-06-12 Thread Marcel Kinard (JIRA)


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

Marcel Kinard commented on CB-6928:
---

You had asked a question on the dev list about running the tests. The tests are 
centralized in a separate repo: https://github.com/apache/cordova-mobile-spec

 Wrong behaviour transferring cacheable content
 --

 Key: CB-6928
 URL: https://issues.apache.org/jira/browse/CB-6928
 Project: Apache Cordova
  Issue Type: Bug
  Components: Plugin File Transfer
Affects Versions: 3.5.0
Reporter: Javier Puerto
Priority: Minor

 Use case:
 Transfer resources from server to the device. To avoid unnecessary use of the 
 device bandwidth, the resources that exists already are checked with the 
 If-Modified-Since header so server can return 304 status code and update 
 just in case that is needed.
 Result for Android test:
 The plugin doesn't care about the status code, if the request is success, 
 open the InputStream and copy the content to the file. The problem is that a 
 HTTP status of 304 has no response and that leads to a corrupted file 
 transfer.
 Fix:
 If status code is 304, doesn't makes sense to process the InputStream. Read 
 the status code after connection and if it's 304, skip the copy process and 
 return the file entity like a success transfer.
 I've tested for Android only.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (CB-6928) Wrong behaviour transferring cacheable content


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

Javier Puerto commented on CB-6928:
---

I see, thanks for the link. It seems like the file-transfer tests are missing. 
How shall I proceed now?

 Wrong behaviour transferring cacheable content
 --

 Key: CB-6928
 URL: https://issues.apache.org/jira/browse/CB-6928
 Project: Apache Cordova
  Issue Type: Bug
  Components: Plugin File Transfer
Affects Versions: 3.5.0
Reporter: Javier Puerto
Priority: Minor

 Use case:
 Transfer resources from server to the device. To avoid unnecessary use of the 
 device bandwidth, the resources that exists already are checked with the 
 If-Modified-Since header so server can return 304 status code and update 
 just in case that is needed.
 Result for Android test:
 The plugin doesn't care about the status code, if the request is success, 
 open the InputStream and copy the content to the file. The problem is that a 
 HTTP status of 304 has no response and that leads to a corrupted file 
 transfer.
 Fix:
 If status code is 304, doesn't makes sense to process the InputStream. Read 
 the status code after connection and if it's 304, skip the copy process and 
 return the file entity like a success transfer.
 I've tested for Android only.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Comment Edited] (CB-6928) Wrong behaviour transferring cacheable content

2014-06-12 Thread ASF subversion and git services (JIRA)


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

Javier Puerto edited comment on CB-6928 at 6/12/14 4:28 PM:


I see, thanks for the link. -It seems like the file-transfer tests are missing. 
How shall I proceed now?-
The tests for _file-transfer_ are in the _file_ directory. Seems like there's 
nothing to test the caching, I will have to write a test for the use case.


was (Author: jpuerto):
I see, thanks for the link. It seems like the file-transfer tests are missing. 
How shall I proceed now?

 Wrong behaviour transferring cacheable content
 --

 Key: CB-6928
 URL: https://issues.apache.org/jira/browse/CB-6928
 Project: Apache Cordova
  Issue Type: Bug
  Components: Plugin File Transfer
Affects Versions: 3.5.0
Reporter: Javier Puerto
Priority: Minor

 Use case:
 Transfer resources from server to the device. To avoid unnecessary use of the 
 device bandwidth, the resources that exists already are checked with the 
 If-Modified-Since header so server can return 304 status code and update 
 just in case that is needed.
 Result for Android test:
 The plugin doesn't care about the status code, if the request is success, 
 open the InputStream and copy the content to the file. The problem is that a 
 HTTP status of 304 has no response and that leads to a corrupted file 
 transfer.
 Fix:
 If status code is 304, doesn't makes sense to process the InputStream. Read 
 the status code after connection and if it's 304, skip the copy process and 
 return the file entity like a success transfer.
 I've tested for Android only.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (CB-6930) Tools Release June 12, 2014


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

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

Commit 4d7c0d1d31cc46cf39fa5b17ca718266f2a21ac7 in cordova-lib's branch 
refs/heads/0.21.5 from [~iclelland]
[ https://git-wip-us.apache.org/repos/asf?p=cordova-lib.git;h=4d7c0d1 ]

CB-6930: Update RELEASENOTES.md for release 0.21.5


 Tools Release June 12, 2014
 ---

 Key: CB-6930
 URL: https://issues.apache.org/jira/browse/CB-6930
 Project: Apache Cordova
  Issue Type: Bug
  Components: CLI, CordovaLib, Plugman
Affects Versions: 3.5.0
Reporter: Ian Clelland
Assignee: Ian Clelland

 Following steps at 
 https://github.com/apache/cordova-coho/blob/master/docs/tools-release-process.md



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (CB-6390) Android Manifest Update Suggestions

2014-06-12 Thread ASF subversion and git services (JIRA)


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

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

Commit 6f79246d1af50abd6bcf8c20f04f0912c39835ed in cordova-lib's branch 
refs/heads/0.21.5 from [~iclelland]
[ https://git-wip-us.apache.org/repos/asf?p=cordova-lib.git;h=6f79246 ]

CB-6390: Update npm-shrinkwrap.json for release 0.21.5


 Android Manifest Update Suggestions
 ---

 Key: CB-6390
 URL: https://issues.apache.org/jira/browse/CB-6390
 Project: Apache Cordova
  Issue Type: Improvement
  Components: Android
Affects Versions: 3.4.0
Reporter: Matthew Keable
Priority: Minor
  Labels: android, androidmanifest.xml

 Building a project in Cordova 3.4 I receive the following warnings from 
 Eclipse.
 1) Should explicitly set android:allowBackup to true or false (it's true by 
 default, and that can have some security implications for the application's 
 data)
 2) uses-sdk tag appears after application tag
 3) uses-permission tag appears after application tag
 Would it be possible to either set a default for android:allowBackup or 
 create a config.xml setting for it?
 Is it possible to rearrange the order in which tags are written to the 
 manifest?



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (CB-6930) Tools Release June 12, 2014

2014-06-12 Thread ASF subversion and git services (JIRA)


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

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

Commit 2bef3adbdf15fd80908a2b89b3a78d0bd5b7bc99 in cordova-plugman's branch 
refs/heads/master from [~iclelland]
[ https://git-wip-us.apache.org/repos/asf?p=cordova-plugman.git;h=2bef3ad ]

CB-6930: Updated version and RELEASENOTES.md for release 0.22.3


 Tools Release June 12, 2014
 ---

 Key: CB-6930
 URL: https://issues.apache.org/jira/browse/CB-6930
 Project: Apache Cordova
  Issue Type: Bug
  Components: CLI, CordovaLib, Plugman
Affects Versions: 3.5.0
Reporter: Ian Clelland
Assignee: Ian Clelland

 Following steps at 
 https://github.com/apache/cordova-coho/blob/master/docs/tools-release-process.md



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (CB-6390) Android Manifest Update Suggestions

2014-06-12 Thread ASF subversion and git services (JIRA)


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

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

Commit 5b9553947794be45ddd5c91d3c3afb7f0175a52a in cordova-cli's branch 
refs/heads/3.5.0-0.2.5 from [~iclelland]
[ https://git-wip-us.apache.org/repos/asf?p=cordova-cli.git;h=5b95539 ]

CB-6390: Updated version and RELEASENOTES.md for release 3.5.0-0.2.5


 Android Manifest Update Suggestions
 ---

 Key: CB-6390
 URL: https://issues.apache.org/jira/browse/CB-6390
 Project: Apache Cordova
  Issue Type: Improvement
  Components: Android
Affects Versions: 3.4.0
Reporter: Matthew Keable
Priority: Minor
  Labels: android, androidmanifest.xml

 Building a project in Cordova 3.4 I receive the following warnings from 
 Eclipse.
 1) Should explicitly set android:allowBackup to true or false (it's true by 
 default, and that can have some security implications for the application's 
 data)
 2) uses-sdk tag appears after application tag
 3) uses-permission tag appears after application tag
 Would it be possible to either set a default for android:allowBackup or 
 create a config.xml setting for it?
 Is it possible to rearrange the order in which tags are written to the 
 manifest?



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (CB-6932) Cannot build wp8 under Chinese (Simplified) System locale


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

ASF GitHub Bot commented on CB-6932:


Github user axemclion commented on a diff in the pull request:

https://github.com/apache/cordova-wp8/pull/40#discussion_r13716495
  
--- Diff: wp8/bin/create.js ---
@@ -71,16 +71,42 @@ function read(filename) {
 return s;
 }
 
+// Reads content of utf-8 encoded file, removing BOM, if exist.
+function readUTF8 (filename) {
--- End diff --

Can this be renamed as read, since this is doing read anyway. 


 Cannot build wp8 under Chinese (Simplified) System locale
 -

 Key: CB-6932
 URL: https://issues.apache.org/jira/browse/CB-6932
 Project: Apache Cordova
  Issue Type: Bug
  Components: WP8
Affects Versions: 3.6.0
 Environment: Windows 8.1, Simlified Chinese locale
Reporter: Vladimir Kotikov
Assignee: Jesse MacFadyen
  Labels: chinese, locale, wp8
 Fix For: 3.6.0


 *Steps to reproduce:*
 # Set Region  Administrative  Change System Locale to Chinese (Simplified, 
 China).
 # Restart machine.
 # cordova create hello
 # cd hello
 # cordova platform add wp8
 # cordova build wp8
 Error appears.
 {noformat}
 D:\PROJECTS\Temp\test-bom\platforms\wp8\App.xaml(1,1,1,1): error : Invalid 
 character in the given encoding. Line 1, position 1. 
 [D:\PROJECTS\Temp\test-bom\platforms\wp8\HelloCordova.csproj]
 {noformat}
 There is a malformed files that changed during create process for the wp8 
 project under the Chinese system locale. It looks like create.js is 
 interpreting the initial file header incorrectly with the Chinese system 
 locale, then printing it out to the file.
 Build will fail under a different System locale as well.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Comment Edited] (CB-4404) android:windowSoftInputMode does not work

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

Joe Bowser edited comment on CB-4404 at 6/12/14 6:13 PM:
-

OK, that doesn't fix the main problem, but thanks for pointing that out. I wish
there was an easy fix for this, but it looks like there still isn't. :(

was (Author: bowserj):
OK, that doesn't fix the main problem.

android:windowSoftInputMode does not work
-

--
This message was sent by Atlassian JIRA
(v6.2#6252)

[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=14029538#comment-14029538
]

Joe Bowser commented on CB-4404:

OK, that doesn't fix the main problem.

android:windowSoftInputMode does not work
-

--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (CB-6932) Cannot build wp8 under Chinese (Simplified) System locale


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

ASF GitHub Bot commented on CB-6932:


Github user purplecabbage commented on a diff in the pull request:

https://github.com/apache/cordova-wp8/pull/40#discussion_r13717630
  
--- Diff: wp8/bin/create.js ---
@@ -71,16 +71,42 @@ function read(filename) {
 return s;
 }
 
+// Reads content of utf-8 encoded file, removing BOM, if exist.
+function readUTF8 (filename) {
--- End diff --

I think it is fine either way.
We could also probably completely remove 'read', 'write' and 
'replaceInFile' since they are not called.


 Cannot build wp8 under Chinese (Simplified) System locale
 -

 Key: CB-6932
 URL: https://issues.apache.org/jira/browse/CB-6932
 Project: Apache Cordova
  Issue Type: Bug
  Components: WP8
Affects Versions: 3.6.0
 Environment: Windows 8.1, Simlified Chinese locale
Reporter: Vladimir Kotikov
Assignee: Jesse MacFadyen
  Labels: chinese, locale, wp8
 Fix For: 3.6.0


 *Steps to reproduce:*
 # Set Region  Administrative  Change System Locale to Chinese (Simplified, 
 China).
 # Restart machine.
 # cordova create hello
 # cd hello
 # cordova platform add wp8
 # cordova build wp8
 Error appears.
 {noformat}
 D:\PROJECTS\Temp\test-bom\platforms\wp8\App.xaml(1,1,1,1): error : Invalid 
 character in the given encoding. Line 1, position 1. 
 [D:\PROJECTS\Temp\test-bom\platforms\wp8\HelloCordova.csproj]
 {noformat}
 There is a malformed files that changed during create process for the wp8 
 project under the Chinese system locale. It looks like create.js is 
 interpreting the initial file header incorrectly with the Chinese system 
 locale, then printing it out to the file.
 Build will fail under a different System locale as well.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Created] (CB-6933) Add simulator OS version option to iOS platform run/emulate scripts

James White created CB-6933:
---

 Summary: Add simulator OS version option to iOS platform 
run/emulate scripts
 Key: CB-6933
 URL: https://issues.apache.org/jira/browse/CB-6933
 Project: Apache Cordova
  Issue Type: Improvement
  Components: CLI, iOS
Affects Versions: 3.5.0
 Environment: iOS build environment
Reporter: James White


Use case:

The existing cordova run ios --emulator and cordova emulate ios scripts 
include an option --target to specify the desired simulator configuration 
when invoking the simulator.  The simulator by default will launch with the 
latest version of the iOS being simulated.  

Adding a new option --targetos to the platform's run/emulate scripts would 
allow developers to specify which version of iOS to start the simulator with.

ie: cordova run ios --debug --emulator --target=iPhone Retina (4-inch) 
--targetos=6.1

If the --targetos option is provided to the run/emulate script being 
executed, the string --sdk value can be appended to the TARGET_FLAG 
variable that gets passed to ios-sim.




--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Updated] (CB-6933) Add simulator OS version option to iOS platform run/emulate scripts


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

James White updated CB-6933:


Description: 
Use case:

The existing cordova run ios ---emulator and cordova emulate ios scripts 
include an option --target to specify the desired simulator configuration 
when invoking the simulator.  The simulator by default will launch with the 
latest version of the iOS being simulated.  

Adding a new option --targetos to the platform's run/emulate scripts would 
allow developers to specify which version of iOS to start the simulator with.

ie: cordova run ios --debug --emulator --target=iPhone Retina (4-inch) 
--targetos=6.1

If the --targetos option is provided to the run/emulate script being 
executed, the string --sdk value can be appended to the TARGET_FLAG 
variable that gets passed to ios-sim.


  was:
Use case:

The existing cordova run ios --emulator and cordova emulate ios scripts 
include an option --target to specify the desired simulator configuration 
when invoking the simulator.  The simulator by default will launch with the 
latest version of the iOS being simulated.  

Adding a new option --targetos to the platform's run/emulate scripts would 
allow developers to specify which version of iOS to start the simulator with.

ie: cordova run ios --debug --emulator --target=iPhone Retina (4-inch) 
--targetos=6.1

If the --targetos option is provided to the run/emulate script being 
executed, the string --sdk value can be appended to the TARGET_FLAG 
variable that gets passed to ios-sim.



 Add simulator OS version option to iOS platform run/emulate scripts
 ---

 Key: CB-6933
 URL: https://issues.apache.org/jira/browse/CB-6933
 Project: Apache Cordova
  Issue Type: Improvement
  Components: CLI, iOS
Affects Versions: 3.5.0
 Environment: iOS build environment
Reporter: James White

 Use case:
 The existing cordova run ios ---emulator and cordova emulate ios scripts 
 include an option --target to specify the desired simulator configuration 
 when invoking the simulator.  The simulator by default will launch with the 
 latest version of the iOS being simulated.  
 Adding a new option --targetos to the platform's run/emulate scripts would 
 allow developers to specify which version of iOS to start the simulator with.
 ie: cordova run ios --debug --emulator --target=iPhone Retina (4-inch) 
 --targetos=6.1
 If the --targetos option is provided to the run/emulate script being 
 executed, the string --sdk value can be appended to the TARGET_FLAG 
 variable that gets passed to ios-sim.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Updated] (CB-6933) Add simulator OS version option to iOS platform run/emulate scripts


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

James White updated CB-6933:


Description: 
Use case:

The existing cordova run ios --emulator and cordova emulate ios scripts 
include an option --target to specify the desired simulator configuration 
when invoking the simulator.  The simulator by default will launch with the 
latest version of the iOS being simulated.  

Adding a new option --targetos to the platform's run/emulate scripts would 
allow developers to specify which version of iOS to start the simulator with.

ie: cordova run ios --debug --emulator --target=iPhone Retina (4-inch) 
--targetos=6.1

If the --targetos option is provided to the run/emulate script being 
executed, the string --sdk value can be appended to the TARGET_FLAG 
variable that gets passed to ios-sim.


  was:
Use case:

The existing cordova run ios ---emulator and cordova emulate ios scripts 
include an option --target to specify the desired simulator configuration 
when invoking the simulator.  The simulator by default will launch with the 
latest version of the iOS being simulated.  

Adding a new option --targetos to the platform's run/emulate scripts would 
allow developers to specify which version of iOS to start the simulator with.

ie: cordova run ios --debug --emulator --target=iPhone Retina (4-inch) 
--targetos=6.1

If the --targetos option is provided to the run/emulate script being 
executed, the string --sdk value can be appended to the TARGET_FLAG 
variable that gets passed to ios-sim.



 Add simulator OS version option to iOS platform run/emulate scripts
 ---

 Key: CB-6933
 URL: https://issues.apache.org/jira/browse/CB-6933
 Project: Apache Cordova
  Issue Type: Improvement
  Components: CLI, iOS
Affects Versions: 3.5.0
 Environment: iOS build environment
Reporter: James White

 Use case:
 The existing cordova run ios --emulator and cordova emulate ios scripts 
 include an option --target to specify the desired simulator configuration 
 when invoking the simulator.  The simulator by default will launch with the 
 latest version of the iOS being simulated.  
 Adding a new option --targetos to the platform's run/emulate scripts would 
 allow developers to specify which version of iOS to start the simulator with.
 ie: cordova run ios --debug --emulator --target=iPhone Retina (4-inch) 
 --targetos=6.1
 If the --targetos option is provided to the run/emulate script being 
 executed, the string --sdk value can be appended to the TARGET_FLAG 
 variable that gets passed to ios-sim.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Updated] (CB-6933) Add simulator OS version option to iOS platform run/emulate scripts


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

James White updated CB-6933:


Description: 
{noformat}
Use case:

The existing cordova run ios --emulator and cordova emulate ios scripts 
include an option --target to specify the desired simulator configuration 
when invoking the simulator.  The simulator by default will launch with the 
latest version of the iOS being simulated.  

Adding a new option --targetos to the platform's run/emulate scripts would 
allow developers to specify which version of iOS to start the simulator with.

ie: cordova run ios --debug --emulator --target=iPhone Retina (4-inch) 
--targetos=6.1

If the --targetos option is provided to the run/emulate script being 
executed, the string --sdk value can be appended to the TARGET_FLAG 
variable that gets passed to ios-sim.


  was:
Use case:

The existing cordova run ios --emulator and cordova emulate ios scripts 
include an option --target to specify the desired simulator configuration 
when invoking the simulator.  The simulator by default will launch with the 
latest version of the iOS being simulated.  

Adding a new option --targetos to the platform's run/emulate scripts would 
allow developers to specify which version of iOS to start the simulator with.

ie: cordova run ios --debug --emulator --target=iPhone Retina (4-inch) 
--targetos=6.1

If the --targetos option is provided to the run/emulate script being 
executed, the string --sdk value can be appended to the TARGET_FLAG 
variable that gets passed to ios-sim.



 Add simulator OS version option to iOS platform run/emulate scripts
 ---

 Key: CB-6933
 URL: https://issues.apache.org/jira/browse/CB-6933
 Project: Apache Cordova
  Issue Type: Improvement
  Components: CLI, iOS
Affects Versions: 3.5.0
 Environment: iOS build environment
Reporter: James White

 {noformat}
 Use case:
 The existing cordova run ios --emulator and cordova emulate ios scripts 
 include an option --target to specify the desired simulator configuration 
 when invoking the simulator.  The simulator by default will launch with the 
 latest version of the iOS being simulated.  
 Adding a new option --targetos to the platform's run/emulate scripts would 
 allow developers to specify which version of iOS to start the simulator with.
 ie: cordova run ios --debug --emulator --target=iPhone Retina (4-inch) 
 --targetos=6.1
 If the --targetos option is provided to the run/emulate script being 
 executed, the string --sdk value can be appended to the TARGET_FLAG 
 variable that gets passed to ios-sim.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Updated] (CB-6933) Add simulator OS version option to iOS platform run/emulate scripts


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

James White updated CB-6933:


Description: 
{noformat}
Use case:

The existing cordova run ios --emulator and cordova emulate ios scripts 
include an option --target to specify the desired simulator configuration 
when invoking the simulator.  The simulator by default will launch with the 
latest version of the iOS being simulated.  

Adding a new option --targetos to the platform's run/emulate scripts would 
allow developers to specify which version of iOS to start the simulator with.

ie: cordova run ios --debug --emulator --target=iPhone Retina (4-inch) 
--targetos=6.1

If the --targetos option is provided to the run/emulate script being 
executed, the string --sdk value can be appended to the TARGET_FLAG 
variable that gets passed to ios-sim.{/noformat}


  was:
{noformat}
Use case:

The existing cordova run ios --emulator and cordova emulate ios scripts 
include an option --target to specify the desired simulator configuration 
when invoking the simulator.  The simulator by default will launch with the 
latest version of the iOS being simulated.  

Adding a new option --targetos to the platform's run/emulate scripts would 
allow developers to specify which version of iOS to start the simulator with.

ie: cordova run ios --debug --emulator --target=iPhone Retina (4-inch) 
--targetos=6.1

If the --targetos option is provided to the run/emulate script being 
executed, the string --sdk value can be appended to the TARGET_FLAG 
variable that gets passed to ios-sim.



 Add simulator OS version option to iOS platform run/emulate scripts
 ---

 Key: CB-6933
 URL: https://issues.apache.org/jira/browse/CB-6933
 Project: Apache Cordova
  Issue Type: Improvement
  Components: CLI, iOS
Affects Versions: 3.5.0
 Environment: iOS build environment
Reporter: James White

 {noformat}
 Use case:
 The existing cordova run ios --emulator and cordova emulate ios scripts 
 include an option --target to specify the desired simulator configuration 
 when invoking the simulator.  The simulator by default will launch with the 
 latest version of the iOS being simulated.  
 Adding a new option --targetos to the platform's run/emulate scripts would 
 allow developers to specify which version of iOS to start the simulator with.
 ie: cordova run ios --debug --emulator --target=iPhone Retina (4-inch) 
 --targetos=6.1
 If the --targetos option is provided to the run/emulate script being 
 executed, the string --sdk value can be appended to the TARGET_FLAG 
 variable that gets passed to ios-sim.{/noformat}



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Updated] (CB-6933) Add simulator OS version option to iOS platform run/emulate scripts

2014-06-12 Thread ASF subversion and git services (JIRA)


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

James White updated CB-6933:


Description: 
Use case:

The existing {noformat}cordova run ios --emulator{noformat} and 
{noformat}cordova emulate ios{noformat} scripts include an option 
{noformat}--target{noformat} to specify the desired simulator configuration 
when invoking the simulator.  The simulator by default will launch with the 
latest version of the iOS being simulated.  

Adding a new option {noformat}--targetos{noformat} to the platform's 
run/emulate scripts would allow developers to specify which version of iOS to 
start the simulator with.

ie: {noformat}cordova run ios --debug --emulator --target=iPhone Retina 
(4-inch) --targetos=6.1{noformat}

If the {noformat}--targetos{noformat} option is provided to the run/emulate 
script being executed, the string {noformat}--sdk value{noformat} can be 
appended to the TARGET_FLAG variable that gets passed to ios-sim.

  was:
Use case:

{noformat}
The existing cordova run ios --emulator and cordova emulate ios scripts 
include an option --target to specify the desired simulator configuration 
when invoking the simulator.  The simulator by default will launch with the 
latest version of the iOS being simulated.  

Adding a new option --targetos to the platform's run/emulate scripts would 
allow developers to specify which version of iOS to start the simulator with.

ie: cordova run ios --debug --emulator --target=iPhone Retina (4-inch) 
--targetos=6.1

If the --targetos option is provided to the run/emulate script being 
executed, the string --sdk value can be appended to the TARGET_FLAG 
variable that gets passed to ios-sim.
{noformat}


 Add simulator OS version option to iOS platform run/emulate scripts
 ---

 Key: CB-6933
 URL: https://issues.apache.org/jira/browse/CB-6933
 Project: Apache Cordova
  Issue Type: Improvement
  Components: CLI, iOS
Affects Versions: 3.5.0
 Environment: iOS build environment
Reporter: James White

 Use case:
 The existing {noformat}cordova run ios --emulator{noformat} and 
 {noformat}cordova emulate ios{noformat} scripts include an option 
 {noformat}--target{noformat} to specify the desired simulator configuration 
 when invoking the simulator.  The simulator by default will launch with the 
 latest version of the iOS being simulated.  
 Adding a new option {noformat}--targetos{noformat} to the platform's 
 run/emulate scripts would allow developers to specify which version of iOS to 
 start the simulator with.
 ie: {noformat}cordova run ios --debug --emulator --target=iPhone Retina 
 (4-inch) --targetos=6.1{noformat}
 If the {noformat}--targetos{noformat} option is provided to the run/emulate 
 script being executed, the string {noformat}--sdk value{noformat} can be 
 appended to the TARGET_FLAG variable that gets passed to ios-sim.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[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=14029594#comment-14029594
 ] 

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

Commit 663a919ed1eb5e24c22e7ee6b0e74a29ff76345c in cordova-android's branch 
refs/heads/master from [~bowserj]
[ https://git-wip-us.apache.org/repos/asf?p=cordova-android.git;h=663a919 ]

CB-4404: Changing where android:windowSoftInputMode is in the manifest so it 
works


 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: Andrew Grieve

 _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.2#6252)

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

2014-06-12 Thread Mike Billau (JIRA)


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

Mike Billau commented on CB-5294:
-

I tested with Firefox and Chrome and both of them upload an image with the 
exact same filename as the one you select, so we are doing something different 
somewhere. At least the data gets transferred.

 File input element not opening file picker in Android 4.4
 -

 Key: CB-5294
 URL: https://issues.apache.org/jira/browse/CB-5294
 Project: Apache Cordova
  Issue Type: Bug
  Components: Android
Affects Versions: 3.1.0
 Environment: Android 4.4.2, partially fixed in Android 4.4.3
Reporter: Paul Kane
Assignee: Ian Clelland

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



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[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=14029661#comment-14029661
]

Joe Bowser commented on CB-4404:

So, now that I moved android:SoftInputMode, it seems that we can now detect
resize events with adjustResize. However, the Working as Intended bug
indicates that adjustResize doesn't work at all, so there's no way to detect
the keyboard based on what I can find. If someone has some magic code to do
this, that'd be awesome.

android:windowSoftInputMode does not work
-

--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (CB-6927) Changing the default camera direction does not do anything on Android


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

Joe Bowser commented on CB-6927:


Can you provide more information, such as which device you were using and what 
version of Android? Android uses intents to take advantage of the camera 
application that's on the phone, so some cameras may not support this option.

 Changing the default camera direction does not do anything on Android
 -

 Key: CB-6927
 URL: https://issues.apache.org/jira/browse/CB-6927
 Project: Apache Cordova
  Issue Type: Bug
  Components: Android, Plugin Camera
Reporter: Suraj Pindoria

 When using the camera plugin, I tried to change the default camera direction 
 using the option cameraDirection: Camera.Direction.FRONT but it did not 
 change.  It seems that it continues to use whatever camera direction was last 
 used.
 On iOS, you get the correct expected behavior.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (CB-6932) Cannot build wp8 under Chinese (Simplified) System locale

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

ASF GitHub Bot commented on CB-6932:

Github user asfgit closed the pull request at:

https://github.com/apache/cordova-wp8/pull/40

Cannot build wp8 under Chinese (Simplified) System locale
-

--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (CB-6532) cdvfile file url is not working with link tag like css

2014-06-12 Thread Mike DiDomizio (JIRA)


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

Mike DiDomizio commented on CB-6532:


Although I'm using Cordova 3.5, I think this issue is still around.

- Cordova 3.5.0-0.2.4
- cordova.file 1.1.0
- cordova.file-transfer 0.4.3 (with updated dependency of cordova.file =1.1.0)
- All stored persistent
- Using Ionic/AngularJS (with imgSrcSanitizationWhitelist updated) 

Android 4.1.2
- images, js work.  CSS works via Async, fonts do not

iOS 7.1.1
- images, js work.  Fonts, CSS (direct or async) does not work.

Blackberry 10.2
- Can't access file system, although could download no problem.
- I'm using Ionic and the Entry.js didn't come with a toInternalURL() method 
for the BB version.  I believe when the Entry function is called the fileSystem 
object parameter is missing the __format__ parameter.
- Can only temporarily store by local:///
- Temporarily could use images and css (via async loading).
- Not sure if it's expected with BB.  If on the device you had img 
src=myCat.png / which was a valid source.  And you downloaded a file to 
local:///myDog.png, you would call the file by img src=myDog.png / and it 
would work.
- Fonts not tested

Windows 8.0
- I believe images/js worked.  Can't remember if CSS worked.  Have not tested 
fonts.

 cdvfile file url is not working with link tag like css 
 ---

 Key: CB-6532
 URL: https://issues.apache.org/jira/browse/CB-6532
 Project: Apache Cordova
  Issue Type: Bug
  Components: Plugin File, Plugin File Transfer
Affects Versions: 3.4.0
 Environment: iOS 7 
Reporter: Patrick Dürsteler
Priority: Critical

 A css downloaded with xhr and created a local url 
 (cdvfile://localhost/test.css) with the File API can't be used as a 
 stylesheet.
 {code}
 var filename = test.css;
 var imageURL = http://apache.org/css/style.css;;
 requestFileSystem(TEMPORARY, 0, function(fileSystem) {
 var ft = new FileTransfer();
 ft.download(imageURL, fileSystem.root.toURL() + / + filename, 
 function(entry) {
  var fileref=document.createElement(link);
  fileref.setAttribute(rel, stylesheet);
  fileref.setAttribute(type, text/css);
fileref.setAttribute(href, entry.toURL());
 document.head.appendChild(imgElement);
 });
 });
 {code}



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (CB-6927) Changing the default camera direction does not do anything on Android

2014-06-12 Thread Suraj Pindoria (JIRA)


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

Suraj Pindoria commented on CB-6927:


It is a LG Nexus 4 running Android 4.4.2

 Changing the default camera direction does not do anything on Android
 -

 Key: CB-6927
 URL: https://issues.apache.org/jira/browse/CB-6927
 Project: Apache Cordova
  Issue Type: Bug
  Components: Android, Plugin Camera
Reporter: Suraj Pindoria

 When using the camera plugin, I tried to change the default camera direction 
 using the option cameraDirection: Camera.Direction.FRONT but it did not 
 change.  It seems that it continues to use whatever camera direction was last 
 used.
 On iOS, you get the correct expected behavior.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Created] (CB-6934) cordova run blackberry --target withno_ip_nor_password should complain about ip not password

2014-06-12 Thread Josh Soref (JIRA)

Josh Soref created CB-6934:
--

 Summary: cordova run blackberry --target withno_ip_nor_password 
should complain about ip not password
 Key: CB-6934
 URL: https://issues.apache.org/jira/browse/CB-6934
 Project: Apache Cordova
  Issue Type: Bug
  Components: BlackBerry
Affects Versions: 3.5.0
Reporter: Josh Soref
Assignee: Josh Soref


$ cordova run --target aa --no-query
Running command: /tmp/xb/platforms/blackberry10/cordova/run --target aa 
--no-query
No device password provided. You can omit --no-query, use --devicepass, or 
enter a value for 'password' to the target aa defined at 
~/.cordova/blackberry10.json

Here's that section:
aa: {
type: device
},

The error code wanted to complain about the IP field (it's first, and it's set, 
but it's stomped on).



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (CB-6934) cordova run blackberry --target withno_ip_nor_password should complain about ip not password

2014-06-12 Thread Josh Soref (JIRA)


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

Josh Soref commented on CB-6934:


Expected results:
IP is not defined in target aa

(That message itself can be improved...)

 cordova run blackberry --target withno_ip_nor_password should complain about 
 ip not password
 

 Key: CB-6934
 URL: https://issues.apache.org/jira/browse/CB-6934
 Project: Apache Cordova
  Issue Type: Bug
  Components: BlackBerry
Affects Versions: 3.5.0
Reporter: Josh Soref
Assignee: Josh Soref

 $ cordova run --target aa --no-query
 Running command: /tmp/xb/platforms/blackberry10/cordova/run --target aa 
 --no-query
 No device password provided. You can omit --no-query, use --devicepass, or 
 enter a value for 'password' to the target aa defined at 
 ~/.cordova/blackberry10.json
 Here's that section:
 aa: {
 type: device
 },
 The error code wanted to complain about the IP field (it's first, and it's 
 set, but it's stomped on).



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (CB-6934) cordova run blackberry --target withno_ip_nor_password should complain about ip not password