[jira] [Commented] (CB-12528) Remove silly existSync replacement
[ https://issues.apache.org/jira/browse/CB-12528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15895529#comment-15895529 ] ASF GitHub Bot commented on CB-12528: - Github user codecov-io commented on the issue: https://github.com/apache/cordova-lib/pull/524 # [Codecov](https://codecov.io/gh/apache/cordova-lib/pull/524?src=pr=h1) Report > Merging [#524](https://codecov.io/gh/apache/cordova-lib/pull/524?src=pr=desc) into [master](https://codecov.io/gh/apache/cordova-lib/commit/b0402b9e51bf2d97488fedd39d13348b29f81c3c?src=pr=desc) will **decrease** coverage by `-0.02%`. > The diff coverage is `100%`. ```diff @@Coverage Diff @@ ## master #524 +/- ## == - Coverage81.9% 81.88% -0.02% == Files 68 68 Lines5504 5498 -6 Branches 1090 1090 == - Hits 4508 4502 -6 Misses996 996 ``` | [Impacted Files](https://codecov.io/gh/apache/cordova-lib/pull/524?src=pr=tree) | Coverage Δ | | |---|---|---| | [cordova-lib/src/util/npm-helper.js](https://codecov.io/gh/apache/cordova-lib/compare/b0402b9e51bf2d97488fedd39d13348b29f81c3c...62d491f3ff107ab03957ded15603667bf68e692f?src=pr=tree#diff-Y29yZG92YS1saWIvc3JjL3V0aWwvbnBtLWhlbHBlci5qcw==) | `95.65% <100%> (ø)` | :white_check_mark: | | [cordova-lib/src/cordova/util.js](https://codecov.io/gh/apache/cordova-lib/compare/b0402b9e51bf2d97488fedd39d13348b29f81c3c...62d491f3ff107ab03957ded15603667bf68e692f?src=pr=tree#diff-Y29yZG92YS1saWIvc3JjL2NvcmRvdmEvdXRpbC5qcw==) | `97.2% <100%> (-0.08%)` | :x: | -- [Continue to review full report at Codecov](https://codecov.io/gh/apache/cordova-lib/pull/524?src=pr=continue). > **Legend** - [Click here to learn more](https://docs.codecov.io/docs/codecov-delta) > `Δ = absolute (impact)`, `ø = not affected`, `? = missing data` > Powered by [Codecov](https://codecov.io/gh/apache/cordova-lib/pull/524?src=pr=footer). Last update [b0402b9...62d491f](https://codecov.io/gh/apache/cordova-lib/compare/b0402b9e51bf2d97488fedd39d13348b29f81c3c...62d491f3ff107ab03957ded15603667bf68e692f?src=pr=footer=lastupdated). Read the [comment docs](https://docs.codecov.io/docs/pull-request-comments). > Remove silly existSync replacement > -- > > Key: CB-12528 > URL: https://issues.apache.org/jira/browse/CB-12528 > Project: Apache Cordova > Issue Type: Bug > Components: CordovaCommon >Reporter: Jesse MacFadyen >Assignee: Jesse MacFadyen > > Remove bunk claim that existsSync is deprecated, so our own implementation is > provided... > It is not deprecated, our implementation appears to be unused. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-12532) coho prepare-plugins-release doesn't update version in releasenotes
[ https://issues.apache.org/jira/browse/CB-12532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Filip Maj resolved CB-12532. Resolution: Fixed > coho prepare-plugins-release doesn't update version in releasenotes > --- > > Key: CB-12532 > URL: https://issues.apache.org/jira/browse/CB-12532 > Project: Apache Cordova > Issue Type: Sub-task > Components: Coho >Reporter: Steve Gill >Assignee: Filip Maj > > the new plugins releaser asks you to pick the version to set after you curate > the release notes. This way you can use the release notes to determine if the > version should stay as a patch or be a minor or major bump. During this step, > it will correctly update plugin.xml, tests/plugin.xml and package.json but it > won't update the Releasenotes.md with the correct version. See > https://github.com/apache/cordova-plugin-contacts/commit/2ca42958e394984f00c76150becb3ae0a3242f98 -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-12532) coho prepare-plugins-release doesn't update version in releasenotes
[ https://issues.apache.org/jira/browse/CB-12532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15895506#comment-15895506 ] ASF subversion and git services commented on CB-12532: -- Commit 6c982b3f5056e416977d4653aa6a76ca37e59962 in cordova-coho's branch refs/heads/plugins-releaser from filmaj [ https://git-wip-us.apache.org/repos/asf?p=cordova-coho.git;h=6c982b3 ] CB-12532: if a new version is selected for a plugin to be released, ensure it is interpolated properly in the release notes. REGEX > coho prepare-plugins-release doesn't update version in releasenotes > --- > > Key: CB-12532 > URL: https://issues.apache.org/jira/browse/CB-12532 > Project: Apache Cordova > Issue Type: Sub-task > Components: Coho >Reporter: Steve Gill >Assignee: Filip Maj > > the new plugins releaser asks you to pick the version to set after you curate > the release notes. This way you can use the release notes to determine if the > version should stay as a patch or be a minor or major bump. During this step, > it will correctly update plugin.xml, tests/plugin.xml and package.json but it > won't update the Releasenotes.md with the correct version. See > https://github.com/apache/cordova-plugin-contacts/commit/2ca42958e394984f00c76150becb3ae0a3242f98 -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-12536) plugins releaser should ensure to update release branches as well
[ https://issues.apache.org/jira/browse/CB-12536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Filip Maj resolved CB-12536. Resolution: Fixed > plugins releaser should ensure to update release branches as well > - > > Key: CB-12536 > URL: https://issues.apache.org/jira/browse/CB-12536 > Project: Apache Cordova > Issue Type: Sub-task > Components: Coho >Reporter: Filip Maj >Assignee: Filip Maj > > before we tag and merge things into release branches, ensure to update said > branches! we currently only tell coho to update the master branch > specifically. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-12536) plugins releaser should ensure to update release branches as well
[ https://issues.apache.org/jira/browse/CB-12536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15895503#comment-15895503 ] ASF subversion and git services commented on CB-12536: -- Commit c4e092dd557f4e00778af8b0faab8b7ff2106de5 in cordova-coho's branch refs/heads/plugins-releaser from filmaj [ https://git-wip-us.apache.org/repos/asf?p=cordova-coho.git;h=c4e092d ] CB-12536: make sure to update the release branch if it is detected to already exist for a given plugin to be released. > plugins releaser should ensure to update release branches as well > - > > Key: CB-12536 > URL: https://issues.apache.org/jira/browse/CB-12536 > Project: Apache Cordova > Issue Type: Sub-task > Components: Coho >Reporter: Filip Maj >Assignee: Filip Maj > > before we tag and merge things into release branches, ensure to update said > branches! we currently only tell coho to update the master branch > specifically. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-12537) plugins releaser should work with brand new plugins repositories instead of dev's working repos
[ https://issues.apache.org/jira/browse/CB-12537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Filip Maj resolved CB-12537. Resolution: Fixed > plugins releaser should work with brand new plugins repositories instead of > dev's working repos > --- > > Key: CB-12537 > URL: https://issues.apache.org/jira/browse/CB-12537 > Project: Apache Cordova > Issue Type: Sub-task > Components: Coho >Reporter: Filip Maj >Assignee: Filip Maj > > We don't want to be munging dev repo states destructively. Better to set > aside fresh clones. Might take a while though :/ > What if the flow was composed of two parts? Like so: > 1. A 'should I auto-detect which plugins need a release, or do you want to > specify those manually?' question > 2. A 'do you want me to use an existing working directory of plugin repos, or > should i clone them fresh?' question > Then the resulting four options are: > - need to work with an existing set of repos, and update the repos, and > auto-detect which ones need a release > - need to work with an existing set of repos, but want to manually specify > which plugins to release, and only update those > - need to create a new directory, clone all the plugin repos, and > auto-detect which ones need a release > - need to create a new directory and clone only the specified plugins to > release -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-12537) plugins releaser should work with brand new plugins repositories instead of dev's working repos
[ https://issues.apache.org/jira/browse/CB-12537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15895492#comment-15895492 ] ASF subversion and git services commented on CB-12537: -- Commit f73674e47daf38825fb2d5413baba86f7737657a in cordova-coho's branch refs/heads/plugins-releaser from filmaj [ https://git-wip-us.apache.org/repos/asf?p=cordova-coho.git;h=f73674e ] CB-12537: Give RM option of using a fresh working directory to clone repos in. > plugins releaser should work with brand new plugins repositories instead of > dev's working repos > --- > > Key: CB-12537 > URL: https://issues.apache.org/jira/browse/CB-12537 > Project: Apache Cordova > Issue Type: Sub-task > Components: Coho >Reporter: Filip Maj >Assignee: Filip Maj > > We don't want to be munging dev repo states destructively. Better to set > aside fresh clones. Might take a while though :/ > What if the flow was composed of two parts? Like so: > 1. A 'should I auto-detect which plugins need a release, or do you want to > specify those manually?' question > 2. A 'do you want me to use an existing working directory of plugin repos, or > should i clone them fresh?' question > Then the resulting four options are: > - need to work with an existing set of repos, and update the repos, and > auto-detect which ones need a release > - need to work with an existing set of repos, but want to manually specify > which plugins to release, and only update those > - need to create a new directory, clone all the plugin repos, and > auto-detect which ones need a release > - need to create a new directory and clone only the specified plugins to > release -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Comment Edited] (CB-12316) Rename Entitlements-Debug.plist and Entitlements-Release.plist to have a .entitlements extension instead
[ https://issues.apache.org/jira/browse/CB-12316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15895440#comment-15895440 ] Shazron Abdullah edited comment on CB-12316 at 3/4/17 2:34 AM: --- I did the rename, but Xcode creates a new entitlements file in the Target when I add a capability in the Capabilities tab, while the one specified in build.xcconfig is for the Project. Xcode creates a <>.entitlements file. was (Author: shazron): I did the rename, but Xcode creates a new entitlements file in the Target, while the one specified in build.xcconfig is for the Project. Xcode creates a <>.entitlements file. > Rename Entitlements-Debug.plist and Entitlements-Release.plist to have a > .entitlements extension instead > > > Key: CB-12316 > URL: https://issues.apache.org/jira/browse/CB-12316 > Project: Apache Cordova > Issue Type: Bug > Components: iOS >Reporter: Shazron Abdullah >Assignee: Shazron Abdullah > Fix For: cordova-ios@4.4.0 > > > This would go in a minor update of cordova-ios. > See: > https://issues.apache.org/jira/browse/CB-11854?focusedCommentId=15770323=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15770323 > Not sure if it will be worth it. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Comment Edited] (CB-12316) Rename Entitlements-Debug.plist and Entitlements-Release.plist to have a .entitlements extension instead
[
https://issues.apache.org/jira/browse/CB-12316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15895440#comment-15895440
]
Shazron Abdullah edited comment on CB-12316 at 3/4/17 2:33 AM:
---
I did the rename, but Xcode creates a new entitlements file in the Target,
while the one specified in build.xcconfig is for the Project. Xcode creates a
<>.entitlements file.
was (Author: shazron):
I did the rename, but Xcode creates a new entitlements file in the Target,
while the one specified in build.xcconfig is for the Project. Xcode creates a
{PROJECTNAME}.entitlements file.
> Rename Entitlements-Debug.plist and Entitlements-Release.plist to have a
> .entitlements extension instead
>
>
> Key: CB-12316
> URL: https://issues.apache.org/jira/browse/CB-12316
> Project: Apache Cordova
> Issue Type: Bug
> Components: iOS
>Reporter: Shazron Abdullah
>Assignee: Shazron Abdullah
> Fix For: cordova-ios@4.4.0
>
>
> This would go in a minor update of cordova-ios.
> See:
> https://issues.apache.org/jira/browse/CB-11854?focusedCommentId=15770323=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15770323
> Not sure if it will be worth it.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-12536) plugins releaser should ensure to update release branches as well
[ https://issues.apache.org/jira/browse/CB-12536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Filip Maj updated CB-12536: --- Description: before we tag and merge things into release branches, ensure to update said branches! we currently only tell coho to update the master branch specifically. (was: before we tag and merge things into release branches, ensure to update said branches!) > plugins releaser should ensure to update release branches as well > - > > Key: CB-12536 > URL: https://issues.apache.org/jira/browse/CB-12536 > Project: Apache Cordova > Issue Type: Sub-task > Components: Coho >Reporter: Filip Maj >Assignee: Filip Maj > > before we tag and merge things into release branches, ensure to update said > branches! we currently only tell coho to update the master branch > specifically. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-12537) plugins releaser should work with brand new plugins repositories instead of dev's working repos
[ https://issues.apache.org/jira/browse/CB-12537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Filip Maj updated CB-12537: --- Description: We don't want to be munging dev repo states destructively. Better to set aside fresh clones. Might take a while though :/ What if the flow was composed of two parts? Like so: 1. A 'should I auto-detect which plugins need a release, or do you want to specify those manually?' question 2. A 'do you want me to use an existing working directory of plugin repos, or should i clone them fresh?' question Then the resulting four options are: - need to work with an existing set of repos, and update the repos, and auto-detect which ones need a release - need to work with an existing set of repos, but want to manually specify which plugins to release, and only update those - need to create a new directory, clone all the plugin repos, and auto-detect which ones need a release - need to create a new directory and clone only the specified plugins to release was:We don't want to be munging dev repo states destructively. Better to set aside fresh clones. Might take a while though :/ > plugins releaser should work with brand new plugins repositories instead of > dev's working repos > --- > > Key: CB-12537 > URL: https://issues.apache.org/jira/browse/CB-12537 > Project: Apache Cordova > Issue Type: Sub-task > Components: Coho >Reporter: Filip Maj >Assignee: Filip Maj > > We don't want to be munging dev repo states destructively. Better to set > aside fresh clones. Might take a while though :/ > What if the flow was composed of two parts? Like so: > 1. A 'should I auto-detect which plugins need a release, or do you want to > specify those manually?' question > 2. A 'do you want me to use an existing working directory of plugin repos, or > should i clone them fresh?' question > Then the resulting four options are: > - need to work with an existing set of repos, and update the repos, and > auto-detect which ones need a release > - need to work with an existing set of repos, but want to manually specify > which plugins to release, and only update those > - need to create a new directory, clone all the plugin repos, and > auto-detect which ones need a release > - need to create a new directory and clone only the specified plugins to > release -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-12538) plugins releaser should give release manager the option of automatically merging master into an existing release branch being updated
[ https://issues.apache.org/jira/browse/CB-12538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15895183#comment-15895183 ] ASF subversion and git services commented on CB-12538: -- Commit 2f043a33f9b80ae493ed3ec316823ef30d297310 in cordova-coho's branch refs/heads/plugins-releaser from filmaj [ https://git-wip-us.apache.org/repos/asf?p=cordova-coho.git;h=2f043a3 ] CB-12538: give release manager option of automatically merging master into release branch in the case the release branch already exists. > plugins releaser should give release manager the option of automatically > merging master into an existing release branch being updated > - > > Key: CB-12538 > URL: https://issues.apache.org/jira/browse/CB-12538 > Project: Apache Cordova > Issue Type: Sub-task > Components: Coho >Reporter: Filip Maj >Assignee: Filip Maj > > Doing so manually slows the process down. Give the RM the option of doing it. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-12538) plugins releaser should give release manager the option of automatically merging master into an existing release branch being updated
[ https://issues.apache.org/jira/browse/CB-12538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Filip Maj resolved CB-12538. Resolution: Fixed > plugins releaser should give release manager the option of automatically > merging master into an existing release branch being updated > - > > Key: CB-12538 > URL: https://issues.apache.org/jira/browse/CB-12538 > Project: Apache Cordova > Issue Type: Sub-task > Components: Coho >Reporter: Filip Maj >Assignee: Filip Maj > > Doing so manually slows the process down. Give the RM the option of doing it. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-12519) Plugins Release, Tue Feb 28 2017
[ https://issues.apache.org/jira/browse/CB-12519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15895121#comment-15895121 ] ASF subversion and git services commented on CB-12519: -- Commit 50c2e8195006e07aa485bb2221990446b2e93997 in cordova-plugin-file-transfer's branch refs/heads/1.6.x from [~stevegill] [ https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-file-transfer.git;h=50c2e81 ] CB-12519 fixed issue with tests/plugin.xml > Plugins Release, Tue Feb 28 2017 > > > Key: CB-12519 > URL: https://issues.apache.org/jira/browse/CB-12519 > Project: Apache Cordova > Issue Type: Task > Components: AllPlugins >Reporter: Steve Gill >Assignee: Steve Gill > > Following steps at > https://github.com/apache/cordova-coho/blob/master/docs/plugins-release-process.md -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Assigned] (CB-12538) plugins releaser should give release manager the option of automatically merging master into an existing release branch being updated
[ https://issues.apache.org/jira/browse/CB-12538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Filip Maj reassigned CB-12538: -- Assignee: Filip Maj > plugins releaser should give release manager the option of automatically > merging master into an existing release branch being updated > - > > Key: CB-12538 > URL: https://issues.apache.org/jira/browse/CB-12538 > Project: Apache Cordova > Issue Type: Sub-task > Components: Coho >Reporter: Filip Maj >Assignee: Filip Maj > > Doing so manually slows the process down. Give the RM the option of doing it. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Created] (CB-12540) basic vetting of previously-existing release JIRA issue for plugin releaser
Filip Maj created CB-12540:
--
Summary: basic vetting of previously-existing release JIRA issue
for plugin releaser
Key: CB-12540
URL: https://issues.apache.org/jira/browse/CB-12540
Project: Apache Cordova
Issue Type: Sub-task
Components: Coho
Reporter: Filip Maj
Assignee: Filip Maj
Priority: Minor
if the RM provides a previously-existing JIRA issue, ensure it has the right
component ({{AllPlugins}}).
[~stevegill] any other vetting of the JIRA issue the plugin releaser should do?
And what if the JIRA issue does not pass the 'requirements'? Do we prompt the
release manager if they want the JIRA issue updated? Or do we error and exit?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Created] (CB-12539) better release note linting for plugin releaser
Filip Maj created CB-12539:
--
Summary: better release note linting for plugin releaser
Key: CB-12539
URL: https://issues.apache.org/jira/browse/CB-12539
Project: Apache Cordova
Issue Type: Sub-task
Components: Coho
Reporter: Filip Maj
Assignee: Filip Maj
Some formattings uncovered during the one release process I watched
[~stevegill] run through:
- bold: + optional , i.e. *iOS 10.0*
- {{plugin.xml}} should be backticked
- platform names at the start of a commit message in parentheses, e.g.
{{(ios)}} should be changed to *iOS:*
- plugin names, camel-cased and monospaced/backticked: {{InAppBrowser}}
- monospace official repo names, i.e. {{cordova-android}}
[~stevegill] if you have any other specific kinds of formating you do, please
let us know here.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Created] (CB-12538) plugins releaser should give release manager the option of automatically merging master into an existing release branch being updated
Filip Maj created CB-12538: -- Summary: plugins releaser should give release manager the option of automatically merging master into an existing release branch being updated Key: CB-12538 URL: https://issues.apache.org/jira/browse/CB-12538 Project: Apache Cordova Issue Type: Sub-task Components: Coho Reporter: Filip Maj Doing so manually slows the process down. Give the RM the option of doing it. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Created] (CB-12537) plugins releaser should work with brand new plugins repositories instead of dev's working repos
Filip Maj created CB-12537: -- Summary: plugins releaser should work with brand new plugins repositories instead of dev's working repos Key: CB-12537 URL: https://issues.apache.org/jira/browse/CB-12537 Project: Apache Cordova Issue Type: Sub-task Components: Coho Reporter: Filip Maj Assignee: Filip Maj We don't want to be munging dev repo states destructively. Better to set aside fresh clones. Might take a while though :/ -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Created] (CB-12536) plugins releaser should ensure to update release branches as well
Filip Maj created CB-12536: -- Summary: plugins releaser should ensure to update release branches as well Key: CB-12536 URL: https://issues.apache.org/jira/browse/CB-12536 Project: Apache Cordova Issue Type: Sub-task Components: Coho Reporter: Filip Maj Assignee: Filip Maj before we tag and merge things into release branches, ensure to update said branches! -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Created] (CB-12535) cordova plugin release automation
Filip Maj created CB-12535: -- Summary: cordova plugin release automation Key: CB-12535 URL: https://issues.apache.org/jira/browse/CB-12535 Project: Apache Cordova Issue Type: New Feature Components: Coho Reporter: Filip Maj Assignee: Filip Maj It would be good to automate as many of the parts of the cordova plugins release steps (documented here: https://github.com/apache/cordova-coho/blob/master/docs/plugins-release-process.md). There is a branch with the work in progress: https://github.com/apache/cordova-coho/blob/plugins-releaser/ -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-12532) coho prepare-plugins-release doesn't update version in releasenotes
[ https://issues.apache.org/jira/browse/CB-12532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Filip Maj updated CB-12532: --- Labels: plugins-releaser (was: ) > coho prepare-plugins-release doesn't update version in releasenotes > --- > > Key: CB-12532 > URL: https://issues.apache.org/jira/browse/CB-12532 > Project: Apache Cordova > Issue Type: Bug > Components: Coho >Reporter: Steve Gill >Assignee: Filip Maj > > the new plugins releaser asks you to pick the version to set after you curate > the release notes. This way you can use the release notes to determine if the > version should stay as a patch or be a minor or major bump. During this step, > it will correctly update plugin.xml, tests/plugin.xml and package.json but it > won't update the Releasenotes.md with the correct version. See > https://github.com/apache/cordova-plugin-contacts/commit/2ca42958e394984f00c76150becb3ae0a3242f98 -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-12532) coho prepare-plugins-release doesn't update version in releasenotes
[ https://issues.apache.org/jira/browse/CB-12532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Filip Maj updated CB-12532: --- Labels: (was: plugins-releaser) > coho prepare-plugins-release doesn't update version in releasenotes > --- > > Key: CB-12532 > URL: https://issues.apache.org/jira/browse/CB-12532 > Project: Apache Cordova > Issue Type: Bug > Components: Coho >Reporter: Steve Gill >Assignee: Filip Maj > > the new plugins releaser asks you to pick the version to set after you curate > the release notes. This way you can use the release notes to determine if the > version should stay as a patch or be a minor or major bump. During this step, > it will correctly update plugin.xml, tests/plugin.xml and package.json but it > won't update the Releasenotes.md with the correct version. See > https://github.com/apache/cordova-plugin-contacts/commit/2ca42958e394984f00c76150becb3ae0a3242f98 -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-12413) Unable to properly sign app with a trusted certificate
[ https://issues.apache.org/jira/browse/CB-12413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse MacFadyen resolved CB-12413. -- Resolution: Workaround Geoffrey has provided a workaround. WP8 is deprecated. Closing to focus on windows-uwp issues. > Unable to properly sign app with a trusted certificate > -- > > Key: CB-12413 > URL: https://issues.apache.org/jira/browse/CB-12413 > Project: Apache Cordova > Issue Type: Bug > Components: WP8 (deprecated) >Affects Versions: 6.0.0 >Reporter: jason Hammond >Priority: Blocker > Labels: certificate, phonegap-build, windows-phone-81 > > I've followed the steps listed here: > http://docs.phonegap.com/phonegap-build/signing/windows/#winphone8 > but am still being told that my app isn't properly signed. > Reason: > Ask the developer for a new app package. This one isn't signed with a trusted > certificate (0x800B0100) -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-8905) Support for Windows Phone Silverlight 8.1 app
[ https://issues.apache.org/jira/browse/CB-8905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse MacFadyen resolved CB-8905. - Resolution: Won't Fix WP8 is deprecated. Closing to focus on windows-uwp issues. > Support for Windows Phone Silverlight 8.1 app > - > > Key: CB-8905 > URL: https://issues.apache.org/jira/browse/CB-8905 > Project: Apache Cordova > Issue Type: New Feature > Components: WP8 (deprecated) >Affects Versions: 3.6.0 >Reporter: Shubhankar Hazarika > Labels: windows, windows-phone-81 > > I am building an app with Cordova 3.5.0 with sqlitePlugin with WP8. The > project is running quite well with WP8. But i also need to build my app in > WP8.1. I have achieved it by retargeting it to WP8.1. But sqlite is not > working here. I have installed sqlite plugin through nuget sqlite-net and > sqlite-wp8-net for WP8 app. I have tried to find if there any templates > available for Cordova WP 8.1. But could not find any success yet. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-6566) Windows 8 cannot read files
[ https://issues.apache.org/jira/browse/CB-6566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse MacFadyen resolved CB-6566. - Resolution: Won't Fix WP8 is deprecated. Closing to focus on windows-uwp issues. > Windows 8 cannot read files > --- > > Key: CB-6566 > URL: https://issues.apache.org/jira/browse/CB-6566 > Project: Apache Cordova > Issue Type: Bug > Components: WP8 (deprecated) >Reporter: brian johnston >Assignee: Jesse MacFadyen > > The getFile fileEntry object comes back OK, except the values of fullPath, > toNativeUrl and toURL are identical. I already reported that. However, the > fileEntry.isFile says "true" so I assumed something was there. However when > I pass that fileEntry into a FileReader object and try to use reader to read > the file I get the following results: > reader.readAsArrayBuffer and reader.readAsDataURL both throw a > TYPE_MISMATCH_ERR. I saw in the docs that readAsArrayBuffer is not supported > on WP8, but I figured I'd try it anyway. > I got an error message on reader.readAsBinaryString saying that method is > missing. I'm not surprised about that since the HTML spec says it is > deprecated anyway. > I also got a fileEntry back from window.resolveLocalFileSystemURI (had to put > '///' in front of the folder and file name to get it to work) and tried to > use that. It gave the same results. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-9169) encodingType seem only have JPG file
[
https://issues.apache.org/jira/browse/CB-9169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesse MacFadyen updated CB-9169:
Component/s: (was: Android)
> encodingType seem only have JPG file
>
>
> Key: CB-9169
> URL: https://issues.apache.org/jira/browse/CB-9169
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugin Camera, WP8 (deprecated)
>Affects Versions: 5.0.1
> Environment: I am using Cordova Cli 5.0 with all latest core plugin
> iOS
>Reporter: Colin Bau
>Assignee: Jesse MacFadyen
> Labels: Triaged, camera, wp8
>
> according to this
> https://github.com/apache/cordova-plugin-camera
> I am using
> {code:javascript}
> { destinationType : Camera.DestinationType.FILE_URL,
> sourceType : Camera.PictureSourceType.CAMERA,
> encodingType: Camera.EncodingType.JPEG,
> targetWidth: 100,
> targetHeight: 100,
> saveToPhotoAlbum: TRUE }
> {code}
> no mater which the encodingType's value is "Camera.EncodingType.JPEG" OR
> "Camera.EncodingType.PNG"
> finally the output file is xxx.jpg
> Android iOS WP8 all have this situation
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-9838) es6 Shims in Window Phone Universal
[ https://issues.apache.org/jira/browse/CB-9838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse MacFadyen resolved CB-9838. - Resolution: Won't Fix You should not need a shim in windows-uwp. WP8 is deprecated. > es6 Shims in Window Phone Universal > --- > > Key: CB-9838 > URL: https://issues.apache.org/jira/browse/CB-9838 > Project: Apache Cordova > Issue Type: Bug > Components: Windows, WP8 (deprecated) >Affects Versions: 5.3.2 > Environment: Build = Windows 8.1 Visual Studio 2015 Community > Cordova Project = Windows Phone Universal >Reporter: DeanB > Labels: build, windows > > I have a test project using es6-shim (v0.33.6), Cordova 5.3.3 and Windows > Phone (Universal). > I am getting errors when I add es6 shims to my project: Files testing > es6-shim.js and core-js. > I get the following error when I test on Windows Phone Universal: > SCRIPT5007: Unhandled exception at line 221, column 7 in > ms-appx-web://test/www/scripts/lib/es6-shim/es6-shim.js > 0x800a138f - JavaScript runtime error: Unable to get property 'toString' of > undefined or null reference > es6-shim.js (221,7) > Cordova Mobile(Android) and Web(Chrome, IE, Firefox) are working well. > Here's the bare code I used to isolate es6-shim. > > > > > > > Hello, your application is ready! > > > I contacted the creator of es6-shim and he seems to think this is a Cordova > issue: > https://github.com/paulmillr/es6-shim/issues/364 -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-3351) Support for mutual SSL (on Ajax calls)
[ https://issues.apache.org/jira/browse/CB-3351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse MacFadyen resolved CB-3351. - Resolution: Won't Fix WP8 is deprecated. Closing to focus on windows-uwp issues. > Support for mutual SSL (on Ajax calls) > --- > > Key: CB-3351 > URL: https://issues.apache.org/jira/browse/CB-3351 > Project: Apache Cordova > Issue Type: New Feature > Components: BlackBerry, WP8 (deprecated) >Affects Versions: 2.6.0 >Reporter: Eloy Gonzalez > Labels: clientcertificate, mutualSSL, ssl > > In some situations, two-factor authentication is required, and client > certificates (a X.509 certificate with a 1.3.6.1.5.5.7.3.2 enhanced key > usage) are a popular choice as a first factor. With mutual SSL, the client > verifies the server's identity (server authentication) and the server > verifies the client's identity (client authentication). Unfortunately, > Cordova does not support mutual SSL. > This issue is relate to CB-2669, but not only for iOS -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-4692) Native GeoLocation support is not fully working
[ https://issues.apache.org/jira/browse/CB-4692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse MacFadyen resolved CB-4692. - Resolution: Won't Fix WP8 is deprecated. Closing to focus on windows-uwp issues. > Native GeoLocation support is not fully working > --- > > Key: CB-4692 > URL: https://issues.apache.org/jira/browse/CB-4692 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin Geolocation, WP8 (deprecated) >Affects Versions: 3.0.0 >Reporter: Wolfgang Koller >Assignee: Wolfgang Koller > Labels: triaged, wp8 > > The current Geolocation implementation of Cordova is using the native, built > in, support of Internet Explorer. > However the native code does not support Altitude, AltitudeAccuracy and > heading properties (they are always null). > Therefor it is required to add our own implementation based on > GeoCoordinateWatcher. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-4798) Built in geolocation breaks the continuous background execution
[
https://issues.apache.org/jira/browse/CB-4798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesse MacFadyen resolved CB-4798.
-
Resolution: Won't Fix
WP8 is deprecated. Closing to focus on windows-uwp issues.
> Built in geolocation breaks the continuous background execution
> ---
>
> Key: CB-4798
> URL: https://issues.apache.org/jira/browse/CB-4798
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugin Geolocation, WP8 (deprecated)
>Affects Versions: 3.0.0
>Reporter: Jonathan Naguin
>Assignee: Jesse MacFadyen
> Labels: background, geolocation, triaged, wp8
>
> The current Geolocation implementation of Cordova is using the built-in on
> Internet Explorer 10.
> This implementation breaks the possibility of run the application on
> background.
> After running a simple code as:
> {code:javascript}
> navigator.geolocation.getCurrentPosition(gps.onSuccess, gps.onError, {
> enableHighAccuracy: true,
> timeout: 3000
> });
> {code}
> And pushing the Home button, the app is deactivated instead of receiving the
> RunningInBackground event (reason: ApplicationAction).
> I tried with a C# native implentation of Geolocation and solves the problem.
> Related with: https://issues.apache.org/jira/browse/CB-4692
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-7806) Add Windows platform to a project on any workstation OS
[ https://issues.apache.org/jira/browse/CB-7806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse MacFadyen resolved CB-7806. - Resolution: Fixed This was done > Add Windows platform to a project on any workstation OS > --- > > Key: CB-7806 > URL: https://issues.apache.org/jira/browse/CB-7806 > Project: Apache Cordova > Issue Type: Sub-task > Components: Windows, WP8 (deprecated) >Reporter: Edna Morales >Priority: Minor > > You should be able to add the Windows platform to a project even if you are > on an unsupported operating system and/or can't build. This will require > changing where the check requirements script is called. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-7138) Tests to verify plugin follows the spec
[ https://issues.apache.org/jira/browse/CB-7138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15894907#comment-15894907 ] Jesse MacFadyen commented on CB-7138: - What is the status of this [~eymorale]? I am cleaning up anything that mentions WP8 ... > Tests to verify plugin follows the spec > --- > > Key: CB-7138 > URL: https://issues.apache.org/jira/browse/CB-7138 > Project: Apache Cordova > Issue Type: Sub-task > Components: Android, BlackBerry, iOS, Plugin Vibration, WP8 > (deprecated) >Reporter: Edna Morales >Assignee: Edna Morales >Priority: Minor > Labels: w3c > > Add tests to verify that plugin vibration follows the w3c spec -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-10230) [WP8] Out of memory exception thrown when console.log added to cordova/exec function
[
https://issues.apache.org/jira/browse/CB-10230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesse MacFadyen resolved CB-10230.
--
Resolution: Invalid
You should never do this, not sure why anyone ever would ...
You are basically introducing an error and claiming it is an issue.
> [WP8] Out of memory exception thrown when console.log added to cordova/exec
> function
>
>
> Key: CB-10230
> URL: https://issues.apache.org/jira/browse/CB-10230
> Project: Apache Cordova
> Issue Type: Bug
> Components: WP8 (deprecated)
>Affects Versions: 3.8.2
>Reporter: Malumbo Chipeta
>Assignee: Jesse MacFadyen
>Priority: Minor
>
> 1. Create a new WP8 Cordova project in Visual Studio (I used the 2015 version)
> 2. Press F5 to start debugging the project
> 3. Notice that the project runs without any issues
> 4. Stop debugging
> 5. Open cordova.js
> 6. Search for 'window.external.Notify'
> 7. Insert 'console.log("Command: " + command);' before Notify is called
> 8. Press F5
> 9. Notice that an out of memory exception is thrown (console.log calls
> cordova/exec which in turns calls console.log again, so an infinite loop is
> entered, and the loop is only broken when the out of memory exception is
> thrown)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-5366) WP8 Media plugin gives Warnings when compiling
[ https://issues.apache.org/jira/browse/CB-5366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse MacFadyen resolved CB-5366. - Resolution: Won't Fix Assignee: Jesse MacFadyen WP8 is deprecated, focusing on windows-uwp going forwards. > WP8 Media plugin gives Warnings when compiling > -- > > Key: CB-5366 > URL: https://issues.apache.org/jira/browse/CB-5366 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin Media, WP8 (deprecated) >Affects Versions: Master, 3.2.0 > Environment: Windows 8 Pro x64 >Reporter: Carlos Santana >Assignee: Jesse MacFadyen >Priority: Minor > > When installing media plugin and then doing a build it gives the user > warnings. > To reproduce: > cordova create mobile-spec > cd mobile-spec > cordova platform add wp8 > cordova plugin add org.apache.cordova.media > cordova build -d > Warnings below: > Plugins\org.apache.cordova.media\AudioPlayer.cs(168,13): warning CS0612: > 'WPCordovaClassLib.Cordova.Commands.BaseCommand.InvokeCustomScript(WPCordovaClassLib.Cordova.ScriptCallback, > bool)' is obsolete > > [C:\Users\Carlos\Desktop\GitHub\cordova32\wp8-mobilespec\platforms\wp8\HelloCordova.csproj] -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-7092) [WP8][cordova-plugin-media] it gets multiple times to error callback, when an invalid file name is provided
[
https://issues.apache.org/jira/browse/CB-7092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesse MacFadyen resolved CB-7092.
-
Resolution: Won't Fix
Assignee: Jesse MacFadyen
WP8 is deprecated, focusing on windows-uwp going forwards.
> [WP8][cordova-plugin-media] it gets multiple times to error callback, when an
> invalid file name is provided
> ---
>
> Key: CB-7092
> URL: https://issues.apache.org/jira/browse/CB-7092
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugin Media, WP8 (deprecated)
>Affects Versions: 3.5.0
>Reporter: Martin Gonzalez
>Assignee: Jesse MacFadyen
> Labels: WP8, media
> Fix For: 3.6.0
>
>
> When an invalid file name is provided to create a new Media object, the error
> callback it goes crazy, throwing the same error multiple times and getting to
> the same callback multiple times instead of one error notification or
> walk-through.
> E.g:
> badMedia = new Media("invalid.file.name", callback, errorcallack);
> It gets stuck in errorcallback for some time, before move on.
> Found porting mobilespec test to new plugin test framework, this behavior it
> was found trying to use the error callback object to complete the test,
> instead of set a timeout to determine if that callback it was called or not.
> This behavior it can be only reproduced under Windows Phone 8.
> Android works pretty fine, and without this issue.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-10116) Wrong config in WP8 Templete for Large Icon support
[ https://issues.apache.org/jira/browse/CB-10116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse MacFadyen resolved CB-10116. -- Resolution: Won't Fix WP8 is deprecated, focusing on windows-uwp going forwards. > Wrong config in WP8 Templete for Large Icon support > --- > > Key: CB-10116 > URL: https://issues.apache.org/jira/browse/CB-10116 > Project: Apache Cordova > Issue Type: Bug > Components: WP8 (deprecated) >Affects Versions: 3.5.0 >Reporter: Julien ROY >Assignee: Jesse MacFadyen >Priority: Trivial > > On WP8, large tile (icon on home) are not supported (can't configure large > image) but it is possible to use large tile. It display large tile with the > default color. > > This is due to a wrong value in the WMAppManifest.xml file in the WP8 > template (/template/Properties/). > The actual value is false and it should be False. > false -> False -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-6862) WP getNumberPattern 'positive' and 'negative' bad return values
[ https://issues.apache.org/jira/browse/CB-6862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse MacFadyen resolved CB-6862. - Resolution: Won't Fix Assignee: Jesse MacFadyen (was: Staci Cooper) WP8 is deprecated, focusing on windows-uwp going forwards. > WP getNumberPattern 'positive' and 'negative' bad return values > --- > > Key: CB-6862 > URL: https://issues.apache.org/jira/browse/CB-6862 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin Globalization, WP8 (deprecated) >Affects Versions: 3.5.0 >Reporter: Staci Cooper >Assignee: Jesse MacFadyen >Priority: Minor > Labels: triaged, wp8 > > getNumberPattern.positive and getNumberPattern.negative should return "the > symbol[s] to use for numbers when parsing and > formatting". For the en-US locale, that should be "" and "-", respectively. > On wp8, these return integers corresponding to the negative/positive > 'patterns' (ie: 1, corresponding to "-n"). -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-6956) cordova platform update wp8 fails
[ https://issues.apache.org/jira/browse/CB-6956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse MacFadyen resolved CB-6956. - Resolution: Won't Fix Assignee: Jesse MacFadyen WP8 is deprecated, focusing on windows-uwp going forwards. > cordova platform update wp8 fails > - > > Key: CB-6956 > URL: https://issues.apache.org/jira/browse/CB-6956 > Project: Apache Cordova > Issue Type: Bug > Components: WP8 (deprecated) >Affects Versions: 3.2.0, 3.3.0, 3.4.0, 3.5.0 > Environment: Windows / WP8 >Reporter: DotNetWise >Assignee: Jesse MacFadyen >Priority: Minor > Labels: cli, update, wp8 > Original Estimate: 3h > Remaining Estimate: 3h > > https://github.com/phonegap/phonegap-cli/issues/235#issuecomment-46311294 -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-12235) CLONE - "media-capture" bugs with WP8.1
[ https://issues.apache.org/jira/browse/CB-12235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse MacFadyen resolved CB-12235. -- Resolution: Won't Fix WP8 is deprecated, focusing on windows-uwp going forwards. > CLONE - "media-capture" bugs with WP8.1 > --- > > Key: CB-12235 > URL: https://issues.apache.org/jira/browse/CB-12235 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin Media Capture, WP8 (deprecated) >Affects Versions: 3.7.0, 3.6.3, 3.7.1 > Environment: I using WP8.1 with phonegap 3.6.3 and all latest core > plugin...(media-capture 1.0.0) >Reporter: sunday menace >Assignee: Jesse MacFadyen > Labels: media-capture > > this is my original screenshot > http://www.littlebau.com/20141013_wp/01.png > issue 1 > when I execute > navigator.device.capture.captureAudio(captureSuccess, captureError, options); > it will show this > http://www.littlebau.com/20141013_wp/02.png > if I press "start"，the duration will run，but if I press "take"...nothing real > happened > if I press the hardware "backbutton"，but it will not trigger the > "captureError" callback > issue 2 > when I execute > navigator.device.capture.captureImage(captureSuccess, captureError, options); > it will show the user interface to do some function > but... > if I press the "backbutton"，it although trigger the "captureError" > callback，but get the "error.code" => undefined > issue 3 > when I execute > navigator.device.capture.captureVideo(captureSuccess, captureError, options); > it will show the user interface to do some function > http://www.littlebau.com/20141013_wp/03.png > but... > if I press "record" button，sometimes it will become black screen > http://www.littlebau.com/20141013_wp/04.png > and when change back to my app，my webview become so strang and very small > (immediately press the "backbutton" will cause the same situation) > http://www.littlebau.com/20141013_wp/05.png -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-11005) Wrong version number in windows phone manifest xml
[ https://issues.apache.org/jira/browse/CB-11005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse MacFadyen resolved CB-11005. -- Resolution: Won't Fix Assignee: Jesse MacFadyen WP8 is deprecated, focusing on windows-uwp going forwards. > Wrong version number in windows phone manifest xml > -- > > Key: CB-11005 > URL: https://issues.apache.org/jira/browse/CB-11005 > Project: Apache Cordova > Issue Type: Bug > Components: WP8 (deprecated) >Affects Versions: 3.5.0, 4.3.0, 3.8.1 > Environment: Windows Phone 8.1 >Reporter: Johan Meijer >Assignee: Jesse MacFadyen > Labels: build, easytest, triaged, wp8 > Original Estimate: 24h > Remaining Estimate: 24h > > When I enter "1.0.36" in the version attribute of my widget element in my > config.xml, it ends up as "1.0.3.0" in the Windows Phone manifest xml. > What goes in: > >... > > What comes out: > > > ... > >... > -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-7099) [WP8][cordova-plugin-media] status callback it is reached several times in the same statement
[
https://issues.apache.org/jira/browse/CB-7099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesse MacFadyen resolved CB-7099.
-
Resolution: Won't Fix
Assignee: Jesse MacFadyen
WP8 is deprecated, focusing on windows-uwp going forwards.
> [WP8][cordova-plugin-media] status callback it is reached several times in
> the same statement
> -
>
> Key: CB-7099
> URL: https://issues.apache.org/jira/browse/CB-7099
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugin Media, WP8 (deprecated)
>Affects Versions: 3.5.0
>Reporter: Martin Gonzalez
>Assignee: Jesse MacFadyen
> Labels: WP8, media
> Fix For: 3.6.0
>
>
> The optional status callback in a Media object, it is reached multiple times
> in the same statement, even with the same status code.
> E.g:
> var media= new Media("http://url/to/media/file.mp3",successCallback,
> fail.bind(null, done), statuschange);
> The status change callback function it is reached several times, even with
> the same status code, if at the beginning is stopped, if the state changes to
> a different status code like running, it won't stop to reach and walk-through
> the same callback reporting the same status code.
> This behavior it can be only reproduced over Windows Phone 8. The right
> behavior it supposed to that status callback it would be called only if the
> status is changed.
> The issue was found porting tests to plugin-test-framework CB-6963.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-6317) App getting cut at top or bottom and extra space in landscape view ( windows phone )
[ https://issues.apache.org/jira/browse/CB-6317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse MacFadyen resolved CB-6317. - Resolution: Won't Fix WP8 is deprecated, focusing on windows-uwp going forwards. > App getting cut at top or bottom and extra space in landscape view ( windows > phone ) > > > Key: CB-6317 > URL: https://issues.apache.org/jira/browse/CB-6317 > Project: Apache Cordova > Issue Type: Bug > Components: WP8 (deprecated) >Affects Versions: 3.4.0 > Environment: windows 8.1 OS, Visual Studio 2013 >Reporter: prateek rangineni >Assignee: Jesse MacFadyen > Labels: space, viewport, windows-phone > > App getting cut at top or bottom and extra space in landscape view ( windows > phone ) > I'm using sencha touch 2.3.1 and cordova 3.4.0.I made 2 apps which are > working fine in android and ios devices. It's working fine in all the > browsers ( including IE ) through IIS. > I ported the same apps to windows phone. > Now, when I see it in the phone, I can see that the top part is getting cut > in the beginning and then it shifts down a bit after sometime, but now, the > bottom tabbar is getting cut. > Also, in the landscape view, I can see an extra white space below my bottom > tabbar. > Please help me resolve this issue. > Also, I've created a small sample app to check again and I'm getting the same > issue. > Please note that the top part is getting cut in the beginning and when I > touch the tabbar in landscape mode, it shifts down. But the bottom tab get's > cut now. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-8981) Adding New Image Element to config.xml for WP8
[ https://issues.apache.org/jira/browse/CB-8981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse MacFadyen resolved CB-8981. - Resolution: Won't Fix WP8 is deprecated, focusing on windows-uwp going forwards. > Adding New Image Element to config.xml for WP8 > -- > > Key: CB-8981 > URL: https://issues.apache.org/jira/browse/CB-8981 > Project: Apache Cordova > Issue Type: Sub-task > Components: CLI, CordovaLib, WP8 (deprecated) >Affects Versions: Master > Environment: WP8 >Reporter: Karen Tran >Assignee: Karen Tran > > Based on the parent task, create a new image element tag to copy the image > from src to the correct directory with the given name. > Example: > -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-11971) File transfer not working for windows phone more then 2MB file size
[ https://issues.apache.org/jira/browse/CB-11971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse MacFadyen resolved CB-11971. -- Resolution: Won't Fix WP8 is deprecated, focusing on windows-uwp going forwards. > File transfer not working for windows phone more then 2MB file size > --- > > Key: CB-11971 > URL: https://issues.apache.org/jira/browse/CB-11971 > Project: Apache Cordova > Issue Type: Bug > Components: WP8 (deprecated) >Affects Versions: 3.5.0 > Environment: Windows phone >Reporter: Naitik Patel > Labels: windows > Original Estimate: 96h > Remaining Estimate: 96h > > File transfer not working for windows phone more then 2MB file size when it's > working with Android and IOS -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-6214) [WP8] No Image-File transfer possible from "captured Image cache"
[
https://issues.apache.org/jira/browse/CB-6214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesse MacFadyen resolved CB-6214.
-
Resolution: Won't Fix
WP8 is deprecated, focusing on windows-uwp going forwards.
> [WP8] No Image-File transfer possible from "captured Image cache"
> -
>
> Key: CB-6214
> URL: https://issues.apache.org/jira/browse/CB-6214
> Project: Apache Cordova
> Issue Type: Bug
> Components: WP8 (deprecated)
>Affects Versions: 3.4.0
>Reporter: Lars
>Assignee: Jesse MacFadyen
>Priority: Critical
>
> mimeType="image/jpeg"
> Break with ERROR Code = 1
> Logfile:
> Var Image -> [object HTMLImageElement]
> imageURI -> x-wmapp0:/.///CapturedImagesCache/WP_20140310_007.jpg
> options =
> ["x-wmapp0:\/.\/\/\/CapturedImagesCache\/WP_20140310_007.jpg","http:\/\/xxx.xxx.xx\/x\/sendtest.php","file","114-3-8-54-7488ID.jpg","image\/jpeg","{}","true","false","null","1","POST","FileTransfer1069846908"]
> The thread 0xd50 has exited with code 259 (0x103).
> An exception of type 'System.NotSupportedException' occurred in
> mscorlib.ni.dll and wasn't handled before a managed/native boundary
> An exception of type 'System.Security.SecurityException' occurred in
> mscorlib.ni.dll and wasn't handled before a managed/native boundary
> An error has occurred: Code = 1
> upload error source http://XXX.XXX.XXX//sendtest.php
> upload error target x-wmapp0:/.///CapturedImagesCache/WP_20140310_007.jpg
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-6036) FileTransfer multiple files doesn't work on WP8
[ https://issues.apache.org/jira/browse/CB-6036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse MacFadyen resolved CB-6036. - Resolution: Won't Fix WP8 is deprecated, focusing on windows-uwp going forwards. > FileTransfer multiple files doesn't work on WP8 > --- > > Key: CB-6036 > URL: https://issues.apache.org/jira/browse/CB-6036 > Project: Apache Cordova > Issue Type: Bug > Components: WP8 (deprecated) >Affects Versions: 3.3.0 >Reporter: André van der Plas >Assignee: Jesse MacFadyen > Labels: FileTransfer, WP8 > > I was trying to upload multiple photos on my WP8 testing device, but the > files weren't sent. > It worked on my ios and android environments though. Also posting one photo > did work on the WP8 device. > After debugging I found out that inside the FileTransfer plugin there was a > problem with the callback id's not being used correctly. The moment one > thread finished uploading, multiple threads started using the same callback > id. > In the end I fixed this issue by adding a (probably missing parameter) inside > the ReadCallback method. I changed > DispatchCommandResult(new PluginResult(PluginResult.Status.OK, new > FileUploadResult(bytesSent, (long)response.StatusCode, responseString))); > Into > DispatchCommandResult(new PluginResult(PluginResult.Status.OK, new > FileUploadResult(bytesSent, (long)response.StatusCode, responseString)), > reqState.options.CallbackId); -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-6906) App shifting up after using virtual keyboard ( windows phone 8.1 only )
[ https://issues.apache.org/jira/browse/CB-6906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse MacFadyen resolved CB-6906. - Resolution: Won't Fix WP8 is deprecated, focusing on windows-uwp going forwards. > App shifting up after using virtual keyboard ( windows phone 8.1 only ) > --- > > Key: CB-6906 > URL: https://issues.apache.org/jira/browse/CB-6906 > Project: Apache Cordova > Issue Type: Bug > Components: WP8 (deprecated) >Affects Versions: 3.4.0, 3.5.0 > Environment: Window 8.1 Pro X64, phonegap 3.5, sencha touch 2.3.1 >Reporter: wei jiang >Assignee: Jesse MacFadyen > Attachments: 22.png, 33.png, oC2Nj.png > > > I'm using sencha touch 2.3.1 and cordova 3.5.0 frameworks to develop my apps. > My apps are working fine in all the platforms including windows phone 8. > I tried running the app on windows phone 8.1, but now, after using a virtual > keyboard, the entire app shifts up and doesn't retract back when I'm done > with the keyboard. > Is there any easy way to resolve this? -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-6839) Fix upgrade scripts
[
https://issues.apache.org/jira/browse/CB-6839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesse MacFadyen resolved CB-6839.
-
Resolution: Won't Fix
WP8 is deprecated, focusing on windows-uwp going forwards.
> Fix upgrade scripts
> ---
>
> Key: CB-6839
> URL: https://issues.apache.org/jira/browse/CB-6839
> Project: Apache Cordova
> Issue Type: Bug
> Components: WP8 (deprecated)
>Affects Versions: 3.3.0, 3.4.0, 3.5.0
> Environment: /cordova-wp8/wp8/bin/update.js
>Reporter: Michael Brooks
>Assignee: Jesse MacFadyen
>
> The platform upgrade script for wp8 throws a file exception.
> The error is present in versions {{3.3.0}}, {{3.4.0}}, and {{3.5.0}}.
> The specific upgrade script is: {{/cordova-wp8/wp8/bin/update.js}}.
> It would be nice to see this updated for 3.6.0 because a quick-and-easy
> upgrade path ensures that users can stay current with our projects rapid
> release cycle.
> Until it is fixed, users can generate a new WP8 3.5.0 project, copy the
> platform assets, and diff to ensure that there were no unintentional changes.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-6901) [WP8][cordova-plugin-file] filesystem: null after use IsolatedStorageFile.MoveDirectory
[
https://issues.apache.org/jira/browse/CB-6901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesse MacFadyen resolved CB-6901.
-
Resolution: Won't Fix
WP8 is deprecated, focusing on windows-uwp going forwards.
> [WP8][cordova-plugin-file] filesystem: null after use
> IsolatedStorageFile.MoveDirectory
> ---
>
> Key: CB-6901
> URL: https://issues.apache.org/jira/browse/CB-6901
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugin File
>Affects Versions: 3.5.0
> Environment: Windows 8.1
>Reporter: Martin Gonzalez
>Assignee: Jesse MacFadyen
> Labels: WP8
> Fix For: 3.6.0
>
>
> Using the File plugin, faced a problem trying to move a directory using the
> plugin, specifically the moveTo (aka TransferTo on native) , I've found out
> that the problem is not that the directory is not moved, the problem is that
> after this line is executed:
> https://github.com/apache/cordova-plugin-file/blob/master/src/wp/File.cs#L1412
> isoFile.MoveDirectory(currentPath, newPath);
> The DispatchCommandResult sends the entry file with the CallbackID, but the
> problem is that the information about the filesystem is missing.
> This situation it doesn't happen when isoFile.MoveFile(newPath),
> IsolatedStorageFile.CreateDirectory(path) or
> IsolatedStorageFile.CreateFile(path) are used the filesystem information it
> remains with those but not with MoveDirectory.
> During the 67 test and several others, it uses the filesystem information of
> the recent moved directory to determine if the file exists, and when it gets
> to GeFileOrDirectory on the options this is the array obtained:
> "[null,"file1","{\"create\":false}","File619232322"]"
> When Create or MoveFile:
> "["\/\/entry,move.dsp.srcDir","file1","{\"create\":false}","File619232322"]"
> From the JS side object:
> MoveDirectory:
> {"isFile":false, "isDirectory":true, "name" : "entry.move.dsp.dstDir",
> "filesystem":null, "nativeURL":null}
> MoveFile:
> {"isFile":true, "isDirectory":false, "name" : "entry.move.dsp.dstDir",
> "filesystem":"", "nativeURL":null}
> That's the reason why some automated tests on the MoveTo section are failing.
> Tested on Windows Phone 8 and 8.1, emulator and device. Same behavior.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-6946) Side stripes on WP8
[
https://issues.apache.org/jira/browse/CB-6946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesse MacFadyen resolved CB-6946.
-
Resolution: Won't Fix
WP8 is deprecated, focusing on windows-uwp going forwards.
> Side stripes on WP8
> ---
>
> Key: CB-6946
> URL: https://issues.apache.org/jira/browse/CB-6946
> Project: Apache Cordova
> Issue Type: Bug
> Components: WP8 (deprecated)
>Affects Versions: 3.3.0, 3.5.0
> Environment: Nokia Lumia 920, Windows Phone 8 with latest updates
> index.html:
>
>
>
> Application20
>
>
>
>
>
>
>
> html,
> body,
> .dx-viewport {
> height: 100%;
> }
> html {
> background-color: red !important;
> /*height: calc(100% + 1px);*/
> }
> body {
> background-color: green !important;
> }
> body {
> margin: 0;
> padding: 0;
> }
> .dx-viewport {
> background-color: black !important;
> }
>
>
>
>
>
>
>Reporter: Alexander Bulychev
>Assignee: Jesse MacFadyen
>
> To reproduce
> 1. swipe up
> 2. change orientation to horizontal (green stripe from at bottom)
> 3. swipe down (red stripe from at top)
> video:
> http://www.youtube.com/watch?v=X860Qs-UVUc
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-7488) WP8.1 Emulators do not appear in CordovaDeploy
[ https://issues.apache.org/jira/browse/CB-7488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse MacFadyen resolved CB-7488. - Resolution: Won't Fix WP8 is deprecated, focusing on windows-uwp going forwards. > WP8.1 Emulators do not appear in CordovaDeploy > -- > > Key: CB-7488 > URL: https://issues.apache.org/jira/browse/CB-7488 > Project: Apache Cordova > Issue Type: Bug > Components: WP8 (deprecated) >Reporter: Ross Gerbasi >Assignee: Jesse MacFadyen > > It is very possible this is not a bug and is simply not a feature of WP8. Is > there a WP8.1? > I was able to open the solution in VSE 2013 and build it to a 8.1 emulator > that way, but trying to run 'cordova emulate wp8' will fail if you only have > the 8.1 emulators installed (no 8.0 emulators). > Running 'CordovaDeploy -devices' will only return 1 entry for Device -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-7749) Windows phone memory exception
[ https://issues.apache.org/jira/browse/CB-7749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse MacFadyen resolved CB-7749. - Resolution: Incomplete > Windows phone memory exception > -- > > Key: CB-7749 > URL: https://issues.apache.org/jira/browse/CB-7749 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin Contacts >Affects Versions: 3.5.0 > Environment: Windows phone 8, windows phone 8.1 >Reporter: nico >Assignee: Jesse MacFadyen > Labels: wp8, wp8.1 > > We received crash reports from windows phones reporting. They reported the > problem function was: > appid_ni!WPCordovaClassLib.Cordova.Commands.Contacts.contacts_SearchCompleted. > The exception type was: CLR_EXCEPTION_System.OutOfMemoryException. It > appears as if the search contacts may have a memory leak in the windows > phone arena. We use the Contacts.find option of the plugin only. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-7771) "media-capture" bugs with WP8.1
[ https://issues.apache.org/jira/browse/CB-7771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse MacFadyen resolved CB-7771. - Resolution: Won't Fix WP8 is deprecated, focusing on windows-uwp going forwards. > "media-capture" bugs with WP8.1 > --- > > Key: CB-7771 > URL: https://issues.apache.org/jira/browse/CB-7771 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin Media Capture, WP8 (deprecated) >Affects Versions: 3.7.0, 3.6.3, 3.7.1 > Environment: I using WP8.1 with phonegap 3.6.3 and all latest core > plugin...(media-capture 1.0.0) >Reporter: Colin Bau >Assignee: Jesse MacFadyen > Labels: media-capture > > this is my original screenshot > http://www.littlebau.com/20141013_wp/01.png > issue 1 > when I execute > navigator.device.capture.captureAudio(captureSuccess, captureError, options); > it will show this > http://www.littlebau.com/20141013_wp/02.png > if I press "start"，the duration will run，but if I press "take"...nothing real > happened > if I press the hardware "backbutton"，but it will not trigger the > "captureError" callback > issue 2 > when I execute > navigator.device.capture.captureImage(captureSuccess, captureError, options); > it will show the user interface to do some function > but... > if I press the "backbutton"，it although trigger the "captureError" > callback，but get the "error.code" => undefined > issue 3 > when I execute > navigator.device.capture.captureVideo(captureSuccess, captureError, options); > it will show the user interface to do some function > http://www.littlebau.com/20141013_wp/03.png > but... > if I press "record" button，sometimes it will become black screen > http://www.littlebau.com/20141013_wp/04.png > and when change back to my app，my webview become so strang and very small > (immediately press the "backbutton" will cause the same situation) > http://www.littlebau.com/20141013_wp/05.png -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-8504) wp8 build failed on cordova 4.2.0 via CLI
[ https://issues.apache.org/jira/browse/CB-8504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse MacFadyen resolved CB-8504. - Resolution: Won't Fix WP8 is deprecated, focusing on windows-uwp going forwards. > wp8 build failed on cordova 4.2.0 via CLI > - > > Key: CB-8504 > URL: https://issues.apache.org/jira/browse/CB-8504 > Project: Apache Cordova > Issue Type: Bug > Components: WP8 (deprecated) >Affects Versions: 3.5.0, 4.1.3 > Environment: OS= Windows 8 64 bit. >Reporter: Vaibhav Matle >Assignee: Jesse MacFadyen > Labels: build > Original Estimate: 264h > Remaining Estimate: 264h > > I have installed cordova 4.2.0, VS 2012 express for windows phone. OS is > windows 8,64 bit.I am able to create project, add wp8 platform via cordova > CLI. But when I am buidling the project via CLI, I get error as > "e:\590331\TCL\TCLProject>cordova build Running command: > e:\590331\TCL\TCLProject\platforms\wp8\cordova\build.bat ERROR: MSBuild tools > not found ERROR building one of the platforms: Error: > e:\590331\TCL\TCLProject\platforms\w p8\cordova\build.bat: Command failed > with exit code 2 You may not have the required environment or OS to build > this project" > I checked my folder C:\Windows\Microsoft.NET\Framework\v4.0.30319 and also > C:\WIndows\Microsoft.NET\Framework64\v4.0.30319 and I can see I do have > MSBuild in the two paths. > But when I am building project by cordova CLI, above error comes. I tried > with all cordova 3.5, 3.6, 4.0, 4.2. But getting same error again and again. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-8008) [wp8] Icons & splash assets not copied into platform folder
[ https://issues.apache.org/jira/browse/CB-8008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse MacFadyen resolved CB-8008. - Resolution: Won't Fix WP8 is deprecated, focusing on windows-uwp going forwards. > [wp8] Icons & splash assets not copied into platform folder > --- > > Key: CB-8008 > URL: https://issues.apache.org/jira/browse/CB-8008 > Project: Apache Cordova > Issue Type: Bug > Components: WP8 (deprecated) >Affects Versions: 4.0.0 > Environment: Windows Pro 8 >Reporter: Gabriel Montes >Assignee: Jesse MacFadyen >Priority: Minor > > The documentation at > http://cordova.apache.org/docs/en/4.0.0/config_ref_images.md.html specifies > how to set icons and splash for wp8 platform. In addition, > http://msdn.microsoft.com/en-us/library/dn757053.aspx adds information on the > res folder. > Following that information, created a res folder in the root of the project, > at the same level as platforms folder, with icons/wp8 and screens/wp8 folders > inside containing the images. The main config.xml was updated with the > following code: > >height="62" /> >height="173" /> >height="800"/> > > After cordova prepare wp8 or cordova build wp8, the config.xml in the > platform/wp8 folder is updated but neither the icons not the splash images > are copied. The default ones are still being used. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-8937) Windows Phone 8 - 2 Plash Screens
[ https://issues.apache.org/jira/browse/CB-8937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse MacFadyen resolved CB-8937. - Resolution: Won't Fix WP8 is deprecated. > Windows Phone 8 - 2 Plash Screens > - > > Key: CB-8937 > URL: https://issues.apache.org/jira/browse/CB-8937 > Project: Apache Cordova > Issue Type: Bug > Components: WP8 (deprecated) >Reporter: Baltazar >Assignee: Jesse MacFadyen > Labels: wp8.1 > > Using Splash Screen in Windows Phone appears 2 splashs. > The first is Ok, The second is big to fit in screen. > My config.xml > > height="99" /> > height="159" /> > height="1280"/> > > Any Solution? -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Closed] (CB-9288) [WP8] DisallowOverscroll parameter does not have any effect
[ https://issues.apache.org/jira/browse/CB-9288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse MacFadyen closed CB-9288. --- Resolution: Won't Fix WP8 is deprecated. > [WP8] DisallowOverscroll parameter does not have any effect > --- > > Key: CB-9288 > URL: https://issues.apache.org/jira/browse/CB-9288 > Project: Apache Cordova > Issue Type: Bug > Components: WP8 (deprecated) >Reporter: Manuel Carrasco Moñino >Assignee: Jesse MacFadyen > > 1- Create a new phonegap app. > 2- Deploy the app in a WP either with 'Phonegap Developer App' or after > building it. > 3- swipe one finger down, and you can see over-scrolling effect happening at > the top. > 4- modify config.xml setting the preference value DisallowOverscroll to true. > 5- reload the app, and over-scrolling continues. > As additional information: following the same process in a iOS device, #4 > fixes overscrolling. > IMO this is an important issue since this issue prevents the app look as > native. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-11526) util.js creates directory if required (side effect)
[ https://issues.apache.org/jira/browse/CB-11526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse MacFadyen resolved CB-11526. -- Resolution: Fixed merged > util.js creates directory if required (side effect) > --- > > Key: CB-11526 > URL: https://issues.apache.org/jira/browse/CB-11526 > Project: Apache Cordova > Issue Type: Bug > Components: CordovaLib >Reporter: Jesse MacFadyen >Assignee: Jesse MacFadyen > > cordova-lib/src/cordova/util.js cannot be used without it creating the > directory. > https://github.com/apache/cordova-lib/blob/master/cordova-lib/src/cordova/util.js#L41 -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-12522) Remove node 0.x support in CI
[ https://issues.apache.org/jira/browse/CB-12522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shazron Abdullah resolved CB-12522. --- Resolution: Fixed > Remove node 0.x support in CI > - > > Key: CB-12522 > URL: https://issues.apache.org/jira/browse/CB-12522 > Project: Apache Cordova > Issue Type: Bug > Components: iOS >Reporter: Shazron Abdullah >Assignee: Shazron Abdullah > Fix For: cordova-ios@4.4.0 > > > Remove node 0.x support in the Travis and AppVeyor CI yml -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-12522) Remove node 0.x support in CI
[ https://issues.apache.org/jira/browse/CB-12522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15894833#comment-15894833 ] ASF subversion and git services commented on CB-12522: -- Commit b64ef86175f59fac7eb48c95294b46318128914c in cordova-ios's branch refs/heads/master from [~shazron] [ https://git-wip-us.apache.org/repos/asf?p=cordova-ios.git;h=b64ef86 ] CB-12522 - Remove node 0.x support in CI This closes #292 > Remove node 0.x support in CI > - > > Key: CB-12522 > URL: https://issues.apache.org/jira/browse/CB-12522 > Project: Apache Cordova > Issue Type: Bug > Components: iOS >Reporter: Shazron Abdullah >Assignee: Shazron Abdullah > Fix For: cordova-ios@4.4.0 > > > Remove node 0.x support in the Travis and AppVeyor CI yml -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-12522) Remove node 0.x support in CI
[ https://issues.apache.org/jira/browse/CB-12522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15894834#comment-15894834 ] ASF GitHub Bot commented on CB-12522: - Github user asfgit closed the pull request at: https://github.com/apache/cordova-ios/pull/292 > Remove node 0.x support in CI > - > > Key: CB-12522 > URL: https://issues.apache.org/jira/browse/CB-12522 > Project: Apache Cordova > Issue Type: Bug > Components: iOS >Reporter: Shazron Abdullah >Assignee: Shazron Abdullah > Fix For: cordova-ios@4.4.0 > > > Remove node 0.x support in the Travis and AppVeyor CI yml -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-12523) Remove iOS 8 support
[ https://issues.apache.org/jira/browse/CB-12523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15894830#comment-15894830 ] ASF GitHub Bot commented on CB-12523: - Github user shazron commented on the issue: https://github.com/apache/cordova-ios/pull/293 Travis CI: Looks like the iOS Simulator was never even run, and it failed. Tested it locally again and it works. Flaky CI (esp since it took over 24 hours before this was run on CI) @jcesarmobile looks like the tests even pass with that 8.0 value in. Which tells me that value was never tested in the first place? (bad test) > Remove iOS 8 support > > > Key: CB-12523 > URL: https://issues.apache.org/jira/browse/CB-12523 > Project: Apache Cordova > Issue Type: Bug > Components: iOS >Reporter: Shazron Abdullah >Assignee: Shazron Abdullah > Fix For: cordova-ios@4.4.0 > > > Consensus on the dev@ list that we can drop iOS 8 support since our policy > has always been supporting the current (iOS 10) and one iOS version back. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-11605) platform update should be non-destructive
[ https://issues.apache.org/jira/browse/CB-11605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse MacFadyen resolved CB-11605. -- Resolution: Fixed Waiting on merge! > platform update should be non-destructive > - > > Key: CB-11605 > URL: https://issues.apache.org/jira/browse/CB-11605 > Project: Apache Cordova > Issue Type: Bug > Components: CordovaLib >Reporter: Jesse MacFadyen >Assignee: Jesse MacFadyen > Labels: cordova-7.0.0 > > More details here: > https://github.com/cordova/cordova-discuss/issues/50 > and here: > http://markmail.org/message/nrabt2f4kcbp6vkh -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-12315) Contacts Plugin returns same URL for all photos in array
[
https://issues.apache.org/jira/browse/CB-12315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15894820#comment-15894820
]
Jesse MacFadyen commented on CB-12315:
--
I think the safest way forward is just to update the docs, to reflect the way
it works on android.
I was able to create a contact with more than one image, by merging 2 with
separate images, but still I could not find a way to access the second image.
Personally, I don't think this issue is critical enough to warrant the heroic
effort it would take to fix it.
> Contacts Plugin returns same URL for all photos in array
>
>
> Key: CB-12315
> URL: https://issues.apache.org/jira/browse/CB-12315
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugin Contacts
>Affects Versions: 6.4.0
>Reporter: Joshua Rowe
>Assignee: Jesse MacFadyen
> Labels: android6.0, triaged
> Fix For: 6.4.0
>
>
> Example: Contact ID 1000 has three photos which are returned in an array in
> the contacts object. However, all three photo URL's are the same for each of
> the photos returned.
>
> var options = new ContactFindOptions();
> options.filter = "";
> options.multiple = true;
> options.hasPhoneNumber = true;
> var fields = ["id", "photos"];
> navigator.contacts.find(fields, ContactListSuccess, ContactListError,
> options);
> function ContactListSuccess(contacts) {
> for (var i = 0; i < contacts.length; i++) {
> console.log(contacts[i].id);
>
> for (var j = 0; j < contacts[i].photos.length; j++) {
> console.log(j + " - " + contacts[i].photos[j].value);
> }
> }
> }
> function ContactListError(error) {
> console.error(error);
> }
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-12528) Remove silly existSync replacement
[ https://issues.apache.org/jira/browse/CB-12528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse MacFadyen resolved CB-12528. -- Resolution: Fixed Waiting to be merged! > Remove silly existSync replacement > -- > > Key: CB-12528 > URL: https://issues.apache.org/jira/browse/CB-12528 > Project: Apache Cordova > Issue Type: Bug > Components: CordovaCommon >Reporter: Jesse MacFadyen >Assignee: Jesse MacFadyen > > Remove bunk claim that existsSync is deprecated, so our own implementation is > provided... > It is not deprecated, our implementation appears to be unused. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-12533) Windows Issue(Throwing Promise is undefinded error): While using new screen.orientation.lock('landscape') method only
[
https://issues.apache.org/jira/browse/CB-12533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15894422#comment-15894422
]
Alexander Sorokin commented on CB-12533:
[~purplecabbage] it looks like promise polyfill is also needed on Windows...
> Windows Issue(Throwing Promise is undefinded error): While using new
> screen.orientation.lock('landscape') method only
> -
>
> Key: CB-12533
> URL: https://issues.apache.org/jira/browse/CB-12533
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugin Screen Orientation
>Affects Versions: Master
>Reporter: Vetrivel
>Priority: Critical
>
> In my App, I have installed the "apache/cordova-plugin-screen-orientation"
> and I have set screen.orientation.lock('landscape'); to Lock Landscape view
> instead of lockOrientation method as plugin go updated few days back.App got
> crashes and trowing error "Promise is undefinded error", This issue was not
> there in Previous versions when i used old version with method
> "lockOrientation". Please let me know when i can expect the updated release
> fixing of this issue.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-12533) Windows Issue(Throwing Promise is undefinded error): While using new screen.orientation.lock('landscape') method only
[
https://issues.apache.org/jira/browse/CB-12533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15894372#comment-15894372
]
Vetrivel commented on CB-12533:
---
[~daserge] I am directly installed latest version from GitHub Url
:https://github.com/apache/cordova-plugin-screen-orientation in master it seems.
Fail Code Snippet:- In File :screenorientation.js
var p = new Promise(function(resolve, reject) {
if (screenObject.nativeLock != null) {
promiseLock = screenObject.nativeLock(orientation);
promiseLock.then(function success(res) {
resolve();
}, function error(err) {
screenObject.nativeLock = null;
resolveOrientation(orientation, resolve, reject);
});
} else {
resolveOrientation(orientation, resolve, reject);
}
})
Error Message: Unhandle exception at line 57,column 13 in
ms-appx://com/apache/cordova-plugin-screen-orientation/www/
Javascript runtime error: 'Promise is undefined'
> Windows Issue(Throwing Promise is undefinded error): While using new
> screen.orientation.lock('landscape') method only
> -
>
> Key: CB-12533
> URL: https://issues.apache.org/jira/browse/CB-12533
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugin Screen Orientation
>Affects Versions: Master
>Reporter: Vetrivel
>Priority: Critical
>
> In my App, I have installed the "apache/cordova-plugin-screen-orientation"
> and I have set screen.orientation.lock('landscape'); to Lock Landscape view
> instead of lockOrientation method as plugin go updated few days back.App got
> crashes and trowing error "Promise is undefinded error", This issue was not
> there in Previous versions when i used old version with method
> "lockOrientation". Please let me know when i can expect the updated release
> fixing of this issue.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-12534) Remote debugging is enabled on release build type for android 4.4
[
https://issues.apache.org/jira/browse/CB-12534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dani Granados updated CB-12534:
---
Priority: Critical (was: Major)
> Remote debugging is enabled on release build type for android 4.4
> -
>
> Key: CB-12534
> URL: https://issues.apache.org/jira/browse/CB-12534
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android
>Affects Versions: 6.4.0
> Environment: cordova 6.4.0
> {{cordova platform version android}}
> Installed platforms: android 6.0.0
> android studio 2.2.3
> windows 10 x64
> affects android version 4.4
>Reporter: Dani Granados
>Priority: Critical
> Labels: android
>
> While generating a release and signed apk, if it's ran on a device with kit
> kat, the remote inspection at google chrome is enabled.
> This doesn't happen on devices with android > 4.4
> Tried adding {{android:debuggable="false"}} on AndroidManifest.xml
> Also adding on main activity
> {quote}
> if(Build.VERSION.SDK_INT >= Build.VERSION_CODES.KITKAT) {}
> WebView.setWebContentsDebuggingEnabled(false);
> }
> {quote}
> But the release apk generated stills being debuggable.
> Then tried installing cordova-plugin-crosswalk-webview and found it disables
> correctly the remote inspection for release, as it should be *perse.*
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-12534) Remote debugging is enabled on release build type for android 4.4
[
https://issues.apache.org/jira/browse/CB-12534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dani Granados updated CB-12534:
---
Environment:
cordova 6.4.0
{{cordova platform version android}}
Installed platforms: android 6.0.0
android studio 2.2.3
windows 10 x64
affects android version 4.4
was:
cordova 6.4.0
`cordova platform version android`
Installed platforms: android 6.0.0
android studio 2.2.3
windows 10 x64
affects android version 4.4
> Remote debugging is enabled on release build type for android 4.4
> -
>
> Key: CB-12534
> URL: https://issues.apache.org/jira/browse/CB-12534
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android
>Affects Versions: 6.4.0
> Environment: cordova 6.4.0
> {{cordova platform version android}}
> Installed platforms: android 6.0.0
> android studio 2.2.3
> windows 10 x64
> affects android version 4.4
>Reporter: Dani Granados
> Labels: android
>
> While generating a release and signed apk, if it's ran on a device with kit
> kat, the remote inspection at google chrome is enabled.
> This doesn't happen on devices with android > 4.4
> Tried adding {{android:debuggable="false"}} on AndroidManifest.xml
> Also adding on main activity
> {quote}
> if(Build.VERSION.SDK_INT >= Build.VERSION_CODES.KITKAT) {}
> WebView.setWebContentsDebuggingEnabled(false);
> }
> {quote}
> But the release apk generated stills being debuggable.
> Then tried installing cordova-plugin-crosswalk-webview and found it disables
> correctly the remote inspection for release, as it should be *perse.*
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-12534) Remote debugging is enabled on release build type for android 4.4
[
https://issues.apache.org/jira/browse/CB-12534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dani Granados updated CB-12534:
---
Description:
While generating a release and signed apk, if it's ran on a device with kit
kat, the remote inspection at google chrome is enabled.
This doesn't happen on devices with android > 4.4
Tried adding {{android:debuggable="false"}} on AndroidManifest.xml
Also adding on main activity
{quote}
if(Build.VERSION.SDK_INT >= Build.VERSION_CODES.KITKAT) {}
WebView.setWebContentsDebuggingEnabled(false);
}
{quote}
But the release apk generated stills being debuggable.
Then tried installing cordova-plugin-crosswalk-webview and found it disables
correctly the remote inspection for release, as it should be *perse.*
was:
While generating a release and signed apk, if it's ran on a device with kit
kat, the remote inspection at google chrome is enabled.
This doesn't happen on devices with android > 4.4
Tried adding {{android:debuggable="false"}} on AndroidManifest.xml
Also adding on main activity
{{if(Build.VERSION.SDK_INT >= Build.VERSION_CODES.KITKAT) {}}
{{WebView.setWebContentsDebuggingEnabled(false);}}
{{}}}
But the release apk generated stills being debuggable.
Then tried installing cordova-plugin-crosswalk-webview and found it disables
correctly the remote inspection for release, as it should be *perse.*
> Remote debugging is enabled on release build type for android 4.4
> -
>
> Key: CB-12534
> URL: https://issues.apache.org/jira/browse/CB-12534
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android
>Affects Versions: 6.4.0
> Environment: cordova 6.4.0
> `cordova platform version android`
> Installed platforms: android 6.0.0
> android studio 2.2.3
> windows 10 x64
> affects android version 4.4
>Reporter: Dani Granados
> Labels: android
>
> While generating a release and signed apk, if it's ran on a device with kit
> kat, the remote inspection at google chrome is enabled.
> This doesn't happen on devices with android > 4.4
> Tried adding {{android:debuggable="false"}} on AndroidManifest.xml
> Also adding on main activity
> {quote}
> if(Build.VERSION.SDK_INT >= Build.VERSION_CODES.KITKAT) {}
> WebView.setWebContentsDebuggingEnabled(false);
> }
> {quote}
> But the release apk generated stills being debuggable.
> Then tried installing cordova-plugin-crosswalk-webview and found it disables
> correctly the remote inspection for release, as it should be *perse.*
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-12534) Remote debugging is enabled on release build type for android 4.4
[
https://issues.apache.org/jira/browse/CB-12534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dani Granados updated CB-12534:
---
Description:
While generating a release and signed apk, if it's ran on a device with kit
kat, the remote inspection at google chrome is enabled.
This doesn't happen on devices with android > 4.4
Tried adding {{android:debuggable="false"}} on AndroidManifest.xml
Also adding on main activity
{{
if(Build.VERSION.SDK_INT >= Build.VERSION_CODES.KITKAT) {
WebView.setWebContentsDebuggingEnabled(false);
}
}}
But the release apk generated stills being debuggable.
Then tried installing cordova-plugin-crosswalk-webview and found it disables
correctly the remote inspection for release, as it should be *perse.*
was:
While generating a release and signed apk, if it's ran on a device with kit
kat, the remote inspection at google chrome is enabled.
This doesn't happen on devices with android > 4.4
Tried adding `android:debuggable="false"` on AndroidManifest.xml
Also adding on main activity
```
if(Build.VERSION.SDK_INT >= Build.VERSION_CODES.KITKAT) {
WebView.setWebContentsDebuggingEnabled(false);
}
```
But the release apk generated stills being debuggable.
Then tried installing cordova-plugin-crosswalk-webview and found it disables
correctly the remote inspection for release, as it should be perse.
> Remote debugging is enabled on release build type for android 4.4
> -
>
> Key: CB-12534
> URL: https://issues.apache.org/jira/browse/CB-12534
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android
>Affects Versions: 6.4.0
> Environment: cordova 6.4.0
> `cordova platform version android`
> Installed platforms: android 6.0.0
> android studio 2.2.3
> windows 10 x64
> affects android version 4.4
>Reporter: Dani Granados
> Labels: android
>
> While generating a release and signed apk, if it's ran on a device with kit
> kat, the remote inspection at google chrome is enabled.
> This doesn't happen on devices with android > 4.4
> Tried adding {{android:debuggable="false"}} on AndroidManifest.xml
> Also adding on main activity
> {{
> if(Build.VERSION.SDK_INT >= Build.VERSION_CODES.KITKAT) {
> WebView.setWebContentsDebuggingEnabled(false);
> }
> }}
> But the release apk generated stills being debuggable.
> Then tried installing cordova-plugin-crosswalk-webview and found it disables
> correctly the remote inspection for release, as it should be *perse.*
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-12534) Remote debugging is enabled on release build type for android 4.4
[
https://issues.apache.org/jira/browse/CB-12534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dani Granados updated CB-12534:
---
Description:
While generating a release and signed apk, if it's ran on a device with kit
kat, the remote inspection at google chrome is enabled.
This doesn't happen on devices with android > 4.4
Tried adding {{android:debuggable="false"}} on AndroidManifest.xml
Also adding on main activity
{{if(Build.VERSION.SDK_INT >= Build.VERSION_CODES.KITKAT) {
WebView.setWebContentsDebuggingEnabled(false);
}}}
But the release apk generated stills being debuggable.
Then tried installing cordova-plugin-crosswalk-webview and found it disables
correctly the remote inspection for release, as it should be *perse.*
was:
While generating a release and signed apk, if it's ran on a device with kit
kat, the remote inspection at google chrome is enabled.
This doesn't happen on devices with android > 4.4
Tried adding {{android:debuggable="false"}} on AndroidManifest.xml
Also adding on main activity
{{
if(Build.VERSION.SDK_INT >= Build.VERSION_CODES.KITKAT) {
WebView.setWebContentsDebuggingEnabled(false);
}
}}
But the release apk generated stills being debuggable.
Then tried installing cordova-plugin-crosswalk-webview and found it disables
correctly the remote inspection for release, as it should be *perse.*
> Remote debugging is enabled on release build type for android 4.4
> -
>
> Key: CB-12534
> URL: https://issues.apache.org/jira/browse/CB-12534
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android
>Affects Versions: 6.4.0
> Environment: cordova 6.4.0
> `cordova platform version android`
> Installed platforms: android 6.0.0
> android studio 2.2.3
> windows 10 x64
> affects android version 4.4
>Reporter: Dani Granados
> Labels: android
>
> While generating a release and signed apk, if it's ran on a device with kit
> kat, the remote inspection at google chrome is enabled.
> This doesn't happen on devices with android > 4.4
> Tried adding {{android:debuggable="false"}} on AndroidManifest.xml
> Also adding on main activity
> {{if(Build.VERSION.SDK_INT >= Build.VERSION_CODES.KITKAT) {
> WebView.setWebContentsDebuggingEnabled(false);
> }}}
> But the release apk generated stills being debuggable.
> Then tried installing cordova-plugin-crosswalk-webview and found it disables
> correctly the remote inspection for release, as it should be *perse.*
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-12534) Remote debugging is enabled on release build type for android 4.4
[
https://issues.apache.org/jira/browse/CB-12534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dani Granados updated CB-12534:
---
Description:
While generating a release and signed apk, if it's ran on a device with kit
kat, the remote inspection at google chrome is enabled.
This doesn't happen on devices with android > 4.4
Tried adding {{android:debuggable="false"}} on AndroidManifest.xml
Also adding on main activity
{{if(Build.VERSION.SDK_INT >= Build.VERSION_CODES.KITKAT) {}}
{{WebView.setWebContentsDebuggingEnabled(false);}}
{{}}}
But the release apk generated stills being debuggable.
Then tried installing cordova-plugin-crosswalk-webview and found it disables
correctly the remote inspection for release, as it should be *perse.*
was:
While generating a release and signed apk, if it's ran on a device with kit
kat, the remote inspection at google chrome is enabled.
This doesn't happen on devices with android > 4.4
Tried adding {{android:debuggable="false"}} on AndroidManifest.xml
Also adding on main activity
{{if(Build.VERSION.SDK_INT >= Build.VERSION_CODES.KITKAT) {
WebView.setWebContentsDebuggingEnabled(false);
}}}
But the release apk generated stills being debuggable.
Then tried installing cordova-plugin-crosswalk-webview and found it disables
correctly the remote inspection for release, as it should be *perse.*
> Remote debugging is enabled on release build type for android 4.4
> -
>
> Key: CB-12534
> URL: https://issues.apache.org/jira/browse/CB-12534
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android
>Affects Versions: 6.4.0
> Environment: cordova 6.4.0
> `cordova platform version android`
> Installed platforms: android 6.0.0
> android studio 2.2.3
> windows 10 x64
> affects android version 4.4
>Reporter: Dani Granados
> Labels: android
>
> While generating a release and signed apk, if it's ran on a device with kit
> kat, the remote inspection at google chrome is enabled.
> This doesn't happen on devices with android > 4.4
> Tried adding {{android:debuggable="false"}} on AndroidManifest.xml
> Also adding on main activity
> {{if(Build.VERSION.SDK_INT >= Build.VERSION_CODES.KITKAT) {}}
> {{WebView.setWebContentsDebuggingEnabled(false);}}
> {{}}}
> But the release apk generated stills being debuggable.
> Then tried installing cordova-plugin-crosswalk-webview and found it disables
> correctly the remote inspection for release, as it should be *perse.*
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Created] (CB-12534) Remote debugging is enabled on release build type for android 4.4
Dani Granados created CB-12534:
--
Summary: Remote debugging is enabled on release build type for
android 4.4
Key: CB-12534
URL: https://issues.apache.org/jira/browse/CB-12534
Project: Apache Cordova
Issue Type: Bug
Components: Android
Affects Versions: 6.4.0
Environment: cordova 6.4.0
`cordova platform version android`
Installed platforms: android 6.0.0
android studio 2.2.3
windows 10 x64
affects android version 4.4
Reporter: Dani Granados
While generating a release and signed apk, if it's ran on a device with kit
kat, the remote inspection at google chrome is enabled.
This doesn't happen on devices with android > 4.4
Tried adding `android:debuggable="false"` on AndroidManifest.xml
Also adding on main activity
```
if(Build.VERSION.SDK_INT >= Build.VERSION_CODES.KITKAT) {
WebView.setWebContentsDebuggingEnabled(false);
}
```
But the release apk generated stills being debuggable.
Then tried installing cordova-plugin-crosswalk-webview and found it disables
correctly the remote inspection for release, as it should be perse.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-8661) executeScript doesn't return the a result on Windows platform
[
https://issues.apache.org/jira/browse/CB-8661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15894034#comment-15894034
]
John Little commented on CB-8661:
-
Thanks for the fix
Looking at the code I see that line 323 (similar code inside the
injectScriptFile method) is implemented like this
var result = [e.target.result];
Rather than the more protected line 296 (inside the injectScriptCode method)
var result = (e && e.target) ? [e.target.result] : [null];
Both methods call the invokeScriptAsync method which may or may not return an e
and an e.target
It might be an idea to make them both the same :D
John
> executeScript doesn't return the a result on Windows platform
> -
>
> Key: CB-8661
> URL: https://issues.apache.org/jira/browse/CB-8661
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugin InAppBrowser, Windows
> Environment: Windows 8
> Latest version of Cordova 4.3.0
> Latest version of Plugin InAppBrowser 0.6.0
>Reporter: John Little
>Assignee: Vladimir Kotikov
>
> executeScript is supposed to provide a variable to the function called when
> the script is completed as per this clip from the documentation :-
> If the injected script is of type code, the callback executes with a single
> parameter, which is the return value of the script, wrapped in an Array. For
> multi-line scripts, this is the return value of the last statement, or the
> last expression evaluated.
> When running as a Windows app the array is empty.
> Looking in the Windows InAppBrowserProxy.js file, line 230 looks like this
>op.oncomplete = function () { hasCallback && win([]); };
> So clearly no data is being passed ([]) is an empty array.
> According to the documentation from Microsoft :-
> https://msdn.microsoft.com/en-us/library/windows.ui.xaml.controls.webview.invokescriptasync.aspx
> The invokeScriptAsync function can return a string.
> So if I modify line 230 to look like this
> op.oncomplete = function (e) { hasCallback && win([e.target.result]); };
> I get a string returned to my callback function.
> You could also modify the similar line in the injectScriptFile function, as
> it also calls invokeScriptAsync.
> I need the return value because the only way to comunicate between the page
> in the IAB and the app is to poll some sessionStorage and wait for the page
> to set some data.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-12524) add plugin failing because it cannot find tools/templates
[
https://issues.apache.org/jira/browse/CB-12524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15894023#comment-15894023
]
Janusz Wiśniowski commented on CB-12524:
I also encountered the issue. It seems that latest Android SDK tools (25.3.x)
are not compatible with latest Cordova Android. I didn't test readding andorid
platform to the project, I used [a workaround suggested in the Ionic
forum|https://forum.ionicframework.com/t/error-could-not-find-gradle-wrapper-within-android-sdk/79527/5].
And BTW: {{android}} command is deprecated in the latest Android SDK in favour
of {{sdkmanager}}.
> add plugin failing because it cannot find tools/templates
> -
>
> Key: CB-12524
> URL: https://issues.apache.org/jira/browse/CB-12524
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android, App Hello World
>Affects Versions: 6.5.0
> Environment: Mac OSX 10.12.3
> Cordova 6.5.0
> Android 6.1.2
>Reporter: Gary N Griswold
>Priority: Blocker
>
> plugin add is failing because it is looking for in
> sdk/tools/templates/gradle/wrapper, but tools/templates does not exist.
> The reference to the missing templates directory is found in check_reqs.js
> line 88
> platforms/android/cordova/lib/check_reqs.js
> line 88: var wrapperDir = path.join(sdkDir, 'tools', 'templates', 'gradle',
> 'wrapper');
> Please see the
> cordova plugin add $HOME/
> Failed to install 'com-shortsands-videoplayer':CordovaError: Could not find
> gradle wrapper within Android SDK. Might need to update your Android SDK.
> Looked here:
> /Users/garygriswold/Library/Android/sdk/tools/templates/gradle/wrapper
> at Object.module.exports.check_gradle
> (/Users/garygriswold/ShortSands/VideoProto/platforms/android/cordova/lib/check_reqs.js:90:25)
> at GradleBuilder.prepEnv
> (/Users/garygriswold/ShortSands/VideoProto/platforms/android/cordova/lib/builders/GradleBuilder.js:161:23)
> at Api.module.exports.runClean
> (/Users/garygriswold/ShortSands/VideoProto/platforms/android/cordova/lib/build.js:131:20)
> at
> /Users/garygriswold/ShortSands/VideoProto/platforms/android/cordova/Api.js:394:50
> at _fulfilled
> (/Users/garygriswold/ShortSands/VideoProto/platforms/android/cordova/node_modules/q/q.js:834:54)
> at self.promiseDispatch.done
> (/Users/garygriswold/ShortSands/VideoProto/platforms/android/cordova/node_modules/q/q.js:863:30)
> at Promise.promise.promiseDispatch
> (/Users/garygriswold/ShortSands/VideoProto/platforms/android/cordova/node_modules/q/q.js:796:13)
> at
> /Users/garygriswold/ShortSands/VideoProto/platforms/android/cordova/node_modules/q/q.js:604:44
> at runSingle
> (/Users/garygriswold/ShortSands/VideoProto/platforms/android/cordova/node_modules/q/q.js:137:13)
> at flush
> (/Users/garygriswold/ShortSands/VideoProto/platforms/android/cordova/node_modules/q/q.js:125:13)
> Error: Could not find gradle wrapper within Android SDK. Might need to update
> your Android SDK.
> Looked here:
> /Users/garygriswold/Library/Android/sdk/tools/templates/gradle/wrapper
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-12533) Windows Issue(Throwing Promise is undefinded error): While using new screen.orientation.lock('landscape') method only
[
https://issues.apache.org/jira/browse/CB-12533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15894016#comment-15894016
]
Sergey Shakhnazarov commented on CB-12533:
--
[~vetri50ster] what is the plugin version?
Could you post the failing code snippet?
> Windows Issue(Throwing Promise is undefinded error): While using new
> screen.orientation.lock('landscape') method only
> -
>
> Key: CB-12533
> URL: https://issues.apache.org/jira/browse/CB-12533
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugin Screen Orientation
>Affects Versions: Master
>Reporter: Vetrivel
>Priority: Critical
>
> In my App, I have installed the "apache/cordova-plugin-screen-orientation"
> and I have set screen.orientation.lock('landscape'); to Lock Landscape view
> instead of lockOrientation method as plugin go updated few days back.App got
> crashes and trowing error "Promise is undefinded error", This issue was not
> there in Previous versions when i used old version with method
> "lockOrientation". Please let me know when i can expect the updated release
> fixing of this issue.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-12529) Support default 'cellular' detection into cordova-plugin-network-information for Android
[
https://issues.apache.org/jira/browse/CB-12529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15893995#comment-15893995
]
Zia Sergio commented on CB-12529:
-
Simply because in this case, we know at least that there is a connection and
that it is not an ethernet connection nor a wi-fi connection.
It is not fully "unknown", we know in this case that it is a "cellular"
connection and if some features of our app can be executed only in case of
"cellular" connection, it is so possible, even the subtype of this connection
is unknown.
Why do without this information ?
Also, to be coherent with the IOS plugin version that return "cellular" in this
case !
> Support default 'cellular' detection into cordova-plugin-network-information
> for Android
>
>
> Key: CB-12529
> URL: https://issues.apache.org/jira/browse/CB-12529
> Project: Apache Cordova
> Issue Type: Improvement
> Components: Android
>Reporter: Zia Sergio
>
> cordova-plugin-network-information/src/android/NetworkManager java class :
> Method getType() : In case of unknown cellular network detected, returned
> value is TYPE_UNKNOWN (equals "unknown" string)
> It seems it is better in this case that returns "cellular" string.
> For this simply add a constant :
> public static final String TYPE_CELL = "cellular";
> And add a 'else' statement after all 'else if' statements detecting the
> cellular connection sub-types :
> else {
> return TYPE_CELL;
> }
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Created] (CB-12533) Windows Issue(Throwing Promise is undefinded error): While using new screen.orientation.lock('landscape') method only
Vetrivel created CB-12533:
-
Summary: Windows Issue(Throwing Promise is undefinded error):
While using new screen.orientation.lock('landscape') method only
Key: CB-12533
URL: https://issues.apache.org/jira/browse/CB-12533
Project: Apache Cordova
Issue Type: Bug
Components: Plugin Screen Orientation
Affects Versions: Master
Reporter: Vetrivel
Priority: Critical
In my App, I have installed the "apache/cordova-plugin-screen-orientation" and
I have set screen.orientation.lock('landscape'); to Lock Landscape view instead
of lockOrientation method as plugin go updated few days back.App got crashes
and trowing error "Promise is undefinded error", This issue was not there in
Previous versions when i used old version with method "lockOrientation". Please
let me know when i can expect the updated release fixing of this issue.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
