[jira] [Commented] (CB-11156) Change default FadeSplashScreenDuration value
[
https://issues.apache.org/jira/browse/CB-11156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15259617#comment-15259617
]
ASF GitHub Bot commented on CB-11156:
-
GitHub user daserge opened a pull request:
https://github.com/apache/cordova-plugin-splashscreen/pull/99
CB-11156 Change default FadeSplashScreenDuration value
Updated the docs
[Jira issue](https://issues.apache.org/jira/browse/CB-11156)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/MSOpenTech/cordova-plugin-splashscreen
CB-11156
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cordova-plugin-splashscreen/pull/99.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #99
commit 8761fa779993a0feac7677a0e6f0b3439adb198a
Author: daserge
Date: 2016-04-26T15:50:39Z
CB-11156 Change default FadeSplashScreenDuration value
> Change default FadeSplashScreenDuration value
> -
>
> Key: CB-11156
> URL: https://issues.apache.org/jira/browse/CB-11156
> Project: Apache Cordova
> Issue Type: Improvement
> Components: Plugin SplashScreen
>Reporter: Sergey Shakhnazarov
>Assignee: Sergey Shakhnazarov
>Priority: Minor
>
> Current value is 3000 ms which is equal to the default {{SplashScreenDelay}}
> and it doesn't look good.
> Proposed change is setting it to 500 ms.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-11156) Change default FadeSplashScreenDuration value
[
https://issues.apache.org/jira/browse/CB-11156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15259616#comment-15259616
]
ASF GitHub Bot commented on CB-11156:
-
GitHub user daserge opened a pull request:
https://github.com/apache/cordova-windows/pull/170
CB-11156 Change default FadeSplashScreenDuration value
[Jira issue](https://issues.apache.org/jira/browse/CB-11156)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/MSOpenTech/cordova-windows CB-11156
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cordova-windows/pull/170.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #170
commit 15ca96121f69e7b81a4aed08646c4b8a49e3e2cb
Author: daserge
Date: 2016-04-26T16:14:34Z
CB-11156 Change default FadeSplashScreenDuration value
> Change default FadeSplashScreenDuration value
> -
>
> Key: CB-11156
> URL: https://issues.apache.org/jira/browse/CB-11156
> Project: Apache Cordova
> Issue Type: Improvement
> Components: Plugin SplashScreen
>Reporter: Sergey Shakhnazarov
>Assignee: Sergey Shakhnazarov
>Priority: Minor
>
> Current value is 3000 ms which is equal to the default {{SplashScreenDelay}}
> and it doesn't look good.
> Proposed change is setting it to 500 ms.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-11131) Fix TypeError: message.toUpperCase is not a function in CordovaLogger
[
https://issues.apache.org/jira/browse/CB-11131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Shakhnazarov resolved CB-11131.
--
Resolution: Fixed
> Fix TypeError: message.toUpperCase is not a function in CordovaLogger
> -
>
> Key: CB-11131
> URL: https://issues.apache.org/jira/browse/CB-11131
> Project: Apache Cordova
> Issue Type: Bug
> Components: CordovaCommon
>Reporter: Sergey Shakhnazarov
>Assignee: Sergey Shakhnazarov
>
> Such an error occurs if a non-string value is passed to CordovaLogger.log:
> {{TypeError: message.toUpperCase is not a function}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-11131) Fix TypeError: message.toUpperCase is not a function in CordovaLogger
[
https://issues.apache.org/jira/browse/CB-11131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15259585#comment-15259585
]
ASF GitHub Bot commented on CB-11131:
-
Github user asfgit closed the pull request at:
https://github.com/apache/cordova-lib/pull/431
> Fix TypeError: message.toUpperCase is not a function in CordovaLogger
> -
>
> Key: CB-11131
> URL: https://issues.apache.org/jira/browse/CB-11131
> Project: Apache Cordova
> Issue Type: Bug
> Components: CordovaCommon
>Reporter: Sergey Shakhnazarov
>Assignee: Sergey Shakhnazarov
>
> Such an error occurs if a non-string value is passed to CordovaLogger.log:
> {{TypeError: message.toUpperCase is not a function}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-11131) Fix TypeError: message.toUpperCase is not a function in CordovaLogger
[
https://issues.apache.org/jira/browse/CB-11131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15259584#comment-15259584
]
ASF subversion and git services commented on CB-11131:
--
Commit 5867657d989b136702fe2f14172661ca489573ed in cordova-lib's branch
refs/heads/master from [~daserge]
[ https://git-wip-us.apache.org/repos/asf?p=cordova-lib.git;h=5867657 ]
CB-11131 Fix TypeError: message.toUpperCase is not a function in CordovaLogger
> Fix TypeError: message.toUpperCase is not a function in CordovaLogger
> -
>
> Key: CB-11131
> URL: https://issues.apache.org/jira/browse/CB-11131
> Project: Apache Cordova
> Issue Type: Bug
> Components: CordovaCommon
>Reporter: Sergey Shakhnazarov
>Assignee: Sergey Shakhnazarov
>
> Such an error occurs if a non-string value is passed to CordovaLogger.log:
> {{TypeError: message.toUpperCase is not a function}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-11152) Kill the Android Win Builder on CI
[ https://issues.apache.org/jira/browse/CB-11152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15259126#comment-15259126 ] ASF subversion and git services commented on CB-11152: -- Commit 9a2036b8f3dde10d26877795d3b9e9ece69cef89 in cordova-medic's branch refs/heads/master from [~rakatyal] [ https://git-wip-us.apache.org/repos/asf?p=cordova-medic.git;h=9a2036b ] CB-11152: Removing the android win builder This closes #100 > Kill the Android Win Builder on CI > -- > > Key: CB-11152 > URL: https://issues.apache.org/jira/browse/CB-11152 > Project: Apache Cordova > Issue Type: Task >Reporter: Raghav Katyal >Assignee: Raghav Katyal > > It's not adding much to the value and has been flaky since a long time. It's > a good idea to get rid of it since we already have android on osx. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-11152) Kill the Android Win Builder on CI
[ https://issues.apache.org/jira/browse/CB-11152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15259127#comment-15259127 ] ASF GitHub Bot commented on CB-11152: - Github user asfgit closed the pull request at: https://github.com/apache/cordova-medic/pull/100 > Kill the Android Win Builder on CI > -- > > Key: CB-11152 > URL: https://issues.apache.org/jira/browse/CB-11152 > Project: Apache Cordova > Issue Type: Task >Reporter: Raghav Katyal >Assignee: Raghav Katyal > > It's not adding much to the value and has been flaky since a long time. It's > a good idea to get rid of it since we already have android on osx. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-11152) Kill the Android Win Builder on CI
[ https://issues.apache.org/jira/browse/CB-11152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15259001#comment-15259001 ] ASF GitHub Bot commented on CB-11152: - Github user sarangan12 commented on the pull request: https://github.com/apache/cordova-medic/pull/100#issuecomment-214899480 LGTM > Kill the Android Win Builder on CI > -- > > Key: CB-11152 > URL: https://issues.apache.org/jira/browse/CB-11152 > Project: Apache Cordova > Issue Type: Task >Reporter: Raghav Katyal >Assignee: Raghav Katyal > > It's not adding much to the value and has been flaky since a long time. It's > a good idea to get rid of it since we already have android on osx. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-11153) Use Gradle 2.8 correctly for building Android projects
[
https://issues.apache.org/jira/browse/CB-11153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15259011#comment-15259011
]
ASF subversion and git services commented on CB-11153:
--
Commit f3e0623d1de36c345c172099c0b922ad045c in cordova-android's branch
refs/heads/master from [~nikhilkh]
[ https://git-wip-us.apache.org/repos/asf?p=cordova-android.git;h=f3e0623 ]
CB-11153 Use Gradle 2.8 correctly for building Android projects
> Use Gradle 2.8 correctly for building Android projects
> --
>
> Key: CB-11153
> URL: https://issues.apache.org/jira/browse/CB-11153
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android
>Reporter: Nikhil Khandelwal
>
> In build.gradle we have this:
> {code}
> task wrapper(type: Wrapper) {
> gradleVersion = '2.8'
> }
> {code}
> However, we do not have the gradle version specified correctly in prepEnv:
> {code}
> // If the gradle distribution URL is set, make sure it points to
> version we want.
> // If it's not set, do nothing, assuming that we're using a future
> version of gradle that we don't want to mess with.
> // For some reason, using ^ and $ don't work. This does the job,
> though.
> var distributionUrlRegex = /distributionUrl.*zip/;
> /*jshint -W069 */
> var distributionUrl =
> process.env['CORDOVA_ANDROID_GRADLE_DISTRIBUTION_URL'] ||
> 'http\\://services.gradle.org/distributions/gradle-2.2.1-all.zip';
> /*jshint +W069 */
> var gradleWrapperPropertiesPath = path.join(self.root, 'gradle',
> 'wrapper', 'gradle-wrapper.properties');
> shell.chmod('u+w', gradleWrapperPropertiesPath);
> shell.sed('-i', distributionUrlRegex,
> 'distributionUrl='+distributionUrl, gradleWrapperPropertiesPath);
> {code}
> One side effect of this is that it improves build performance significantly -
> on my machine by 1 second - on a "helloworld" project.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-11153) Use Gradle 2.8 correctly for building Android projects
[
https://issues.apache.org/jira/browse/CB-11153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15259012#comment-15259012
]
ASF subversion and git services commented on CB-11153:
--
Commit 8b96081579dfaa01f61163347144aa304a5b6522 in cordova-android's branch
refs/heads/master from [~nikhilkh]
[ https://git-wip-us.apache.org/repos/asf?p=cordova-android.git;h=8b96081 ]
CB-11153 Move to gradle version 2.13
This closes #299
> Use Gradle 2.8 correctly for building Android projects
> --
>
> Key: CB-11153
> URL: https://issues.apache.org/jira/browse/CB-11153
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android
>Reporter: Nikhil Khandelwal
>
> In build.gradle we have this:
> {code}
> task wrapper(type: Wrapper) {
> gradleVersion = '2.8'
> }
> {code}
> However, we do not have the gradle version specified correctly in prepEnv:
> {code}
> // If the gradle distribution URL is set, make sure it points to
> version we want.
> // If it's not set, do nothing, assuming that we're using a future
> version of gradle that we don't want to mess with.
> // For some reason, using ^ and $ don't work. This does the job,
> though.
> var distributionUrlRegex = /distributionUrl.*zip/;
> /*jshint -W069 */
> var distributionUrl =
> process.env['CORDOVA_ANDROID_GRADLE_DISTRIBUTION_URL'] ||
> 'http\\://services.gradle.org/distributions/gradle-2.2.1-all.zip';
> /*jshint +W069 */
> var gradleWrapperPropertiesPath = path.join(self.root, 'gradle',
> 'wrapper', 'gradle-wrapper.properties');
> shell.chmod('u+w', gradleWrapperPropertiesPath);
> shell.sed('-i', distributionUrlRegex,
> 'distributionUrl='+distributionUrl, gradleWrapperPropertiesPath);
> {code}
> One side effect of this is that it improves build performance significantly -
> on my machine by 1 second - on a "helloworld" project.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-11153) Use Gradle 2.8 correctly for building Android projects
[
https://issues.apache.org/jira/browse/CB-11153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15259015#comment-15259015
]
ASF GitHub Bot commented on CB-11153:
-
Github user infil00p commented on the pull request:
https://github.com/apache/cordova-android/pull/299#issuecomment-214900265
OK, I merged this in, because I need it for something I'm working on :P
> Use Gradle 2.8 correctly for building Android projects
> --
>
> Key: CB-11153
> URL: https://issues.apache.org/jira/browse/CB-11153
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android
>Reporter: Nikhil Khandelwal
>
> In build.gradle we have this:
> {code}
> task wrapper(type: Wrapper) {
> gradleVersion = '2.8'
> }
> {code}
> However, we do not have the gradle version specified correctly in prepEnv:
> {code}
> // If the gradle distribution URL is set, make sure it points to
> version we want.
> // If it's not set, do nothing, assuming that we're using a future
> version of gradle that we don't want to mess with.
> // For some reason, using ^ and $ don't work. This does the job,
> though.
> var distributionUrlRegex = /distributionUrl.*zip/;
> /*jshint -W069 */
> var distributionUrl =
> process.env['CORDOVA_ANDROID_GRADLE_DISTRIBUTION_URL'] ||
> 'http\\://services.gradle.org/distributions/gradle-2.2.1-all.zip';
> /*jshint +W069 */
> var gradleWrapperPropertiesPath = path.join(self.root, 'gradle',
> 'wrapper', 'gradle-wrapper.properties');
> shell.chmod('u+w', gradleWrapperPropertiesPath);
> shell.sed('-i', distributionUrlRegex,
> 'distributionUrl='+distributionUrl, gradleWrapperPropertiesPath);
> {code}
> One side effect of this is that it improves build performance significantly -
> on my machine by 1 second - on a "helloworld" project.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-11153) Use Gradle 2.8 correctly for building Android projects
[
https://issues.apache.org/jira/browse/CB-11153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15259016#comment-15259016
]
ASF GitHub Bot commented on CB-11153:
-
Github user asfgit closed the pull request at:
https://github.com/apache/cordova-android/pull/299
> Use Gradle 2.8 correctly for building Android projects
> --
>
> Key: CB-11153
> URL: https://issues.apache.org/jira/browse/CB-11153
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android
>Reporter: Nikhil Khandelwal
>
> In build.gradle we have this:
> {code}
> task wrapper(type: Wrapper) {
> gradleVersion = '2.8'
> }
> {code}
> However, we do not have the gradle version specified correctly in prepEnv:
> {code}
> // If the gradle distribution URL is set, make sure it points to
> version we want.
> // If it's not set, do nothing, assuming that we're using a future
> version of gradle that we don't want to mess with.
> // For some reason, using ^ and $ don't work. This does the job,
> though.
> var distributionUrlRegex = /distributionUrl.*zip/;
> /*jshint -W069 */
> var distributionUrl =
> process.env['CORDOVA_ANDROID_GRADLE_DISTRIBUTION_URL'] ||
> 'http\\://services.gradle.org/distributions/gradle-2.2.1-all.zip';
> /*jshint +W069 */
> var gradleWrapperPropertiesPath = path.join(self.root, 'gradle',
> 'wrapper', 'gradle-wrapper.properties');
> shell.chmod('u+w', gradleWrapperPropertiesPath);
> shell.sed('-i', distributionUrlRegex,
> 'distributionUrl='+distributionUrl, gradleWrapperPropertiesPath);
> {code}
> One side effect of this is that it improves build performance significantly -
> on my machine by 1 second - on a "helloworld" project.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-11153) Use Gradle 2.8 correctly for building Android projects
[
https://issues.apache.org/jira/browse/CB-11153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15259006#comment-15259006
]
ASF GitHub Bot commented on CB-11153:
-
Github user infil00p commented on the pull request:
https://github.com/apache/cordova-android/pull/299#issuecomment-214899779
Good call on updating this to Gradle 2.13, I just updated to 2.1.0 beta,
and Android Studio just showed me a bunch of complaints about importing the
project.
> Use Gradle 2.8 correctly for building Android projects
> --
>
> Key: CB-11153
> URL: https://issues.apache.org/jira/browse/CB-11153
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android
>Reporter: Nikhil Khandelwal
>
> In build.gradle we have this:
> {code}
> task wrapper(type: Wrapper) {
> gradleVersion = '2.8'
> }
> {code}
> However, we do not have the gradle version specified correctly in prepEnv:
> {code}
> // If the gradle distribution URL is set, make sure it points to
> version we want.
> // If it's not set, do nothing, assuming that we're using a future
> version of gradle that we don't want to mess with.
> // For some reason, using ^ and $ don't work. This does the job,
> though.
> var distributionUrlRegex = /distributionUrl.*zip/;
> /*jshint -W069 */
> var distributionUrl =
> process.env['CORDOVA_ANDROID_GRADLE_DISTRIBUTION_URL'] ||
> 'http\\://services.gradle.org/distributions/gradle-2.2.1-all.zip';
> /*jshint +W069 */
> var gradleWrapperPropertiesPath = path.join(self.root, 'gradle',
> 'wrapper', 'gradle-wrapper.properties');
> shell.chmod('u+w', gradleWrapperPropertiesPath);
> shell.sed('-i', distributionUrlRegex,
> 'distributionUrl='+distributionUrl, gradleWrapperPropertiesPath);
> {code}
> One side effect of this is that it improves build performance significantly -
> on my machine by 1 second - on a "helloworld" project.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-11152) Kill the Android Win Builder on CI
[ https://issues.apache.org/jira/browse/CB-11152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15258987#comment-15258987 ] ASF GitHub Bot commented on CB-11152: - GitHub user rakatyal opened a pull request: https://github.com/apache/cordova-medic/pull/100 CB-11152: Removing the android win builder @sarangan12 , @riknoll : Please review. You can merge this pull request into a Git repository by running: $ git pull https://github.com/MSOpenTech/cordova-medic raghav/andwin Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cordova-medic/pull/100.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #100 commit ecb4bc665ef076bda008a7cf397d849432ac4e63 Author: Raghav Katyal Date: 2016-04-26T21:42:40Z CB-11152: Removing the android win builder > Kill the Android Win Builder on CI > -- > > Key: CB-11152 > URL: https://issues.apache.org/jira/browse/CB-11152 > Project: Apache Cordova > Issue Type: Task >Reporter: Raghav Katyal >Assignee: Raghav Katyal > > It's not adding much to the value and has been flaky since a long time. It's > a good idea to get rid of it since we already have android on osx. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-11158) Debugging with inappbrowser can result in a broken webview debugger
[ https://issues.apache.org/jira/browse/CB-11158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15258932#comment-15258932 ] Jimmy Thomson commented on CB-11158: Create a cordova project (I used 5.4.1) and copy the index.html and index.js files from the repro.zip into the appropriate locations in the project. Add cordova-plugin-inappbrowser (tested using 1.2.0) to the project. Build and run on android, I used the VS Android Emulator running on android 4.4. Run the app, and attach to it with a debugger. Set breakpoints on the two lines in index.js around iab.executescript, that is lines 36 and 38. Click the button in the app, and it will open a page. The first breakpoint should get hit when the page opens. Resume running, and then the bug triggers. Using Chrome to debug the webview will seem to indicate that the breakpoint is not hit, although it will move the text cursor to the start of the line with the breakpoint. No more interaction via the console or breakpoints is possible. If you use VS to debug the webview, it will appear to stop on the second breakpoint, but attempting to use the JS console will fail, and you get no mouseover information or anything. It seems that this sequence of events causes the webview to report an internal error to all debugging requests. If you do NOT set the second breakpoint, then debugging continues to work as expected, and clicking the button a second time will result in the first breakpoint being hit again successfully. > Debugging with inappbrowser can result in a broken webview debugger > --- > > Key: CB-11158 > URL: https://issues.apache.org/jira/browse/CB-11158 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin InAppBrowser >Affects Versions: 1.2.0 > Environment: Android 4.4 >Reporter: Jimmy Thomson >Priority: Minor > Attachments: repro.zip > > > When attempting to debug a callback in inappbrowser, I found that a > particular sequence of events would result in the webview no longer > responding to the debugger. The app itself appears to work, but neither > chrome nor visual studio are able to debug the app. > I am going to upload a repro file and give steps relative to the file. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-11158) Debugging with inappbrowser can result in a broken webview debugger
[ https://issues.apache.org/jira/browse/CB-11158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Thomson updated CB-11158: --- Attachment: repro.zip index.html and index.js to demonstrate the bug > Debugging with inappbrowser can result in a broken webview debugger > --- > > Key: CB-11158 > URL: https://issues.apache.org/jira/browse/CB-11158 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin InAppBrowser >Affects Versions: 1.2.0 > Environment: Android 4.4 >Reporter: Jimmy Thomson >Priority: Minor > Attachments: repro.zip > > > When attempting to debug a callback in inappbrowser, I found that a > particular sequence of events would result in the webview no longer > responding to the debugger. The app itself appears to work, but neither > chrome nor visual studio are able to debug the app. > I am going to upload a repro file and give steps relative to the file. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Created] (CB-11158) Debugging with inappbrowser can result in a broken webview debugger
Jimmy Thomson created CB-11158: -- Summary: Debugging with inappbrowser can result in a broken webview debugger Key: CB-11158 URL: https://issues.apache.org/jira/browse/CB-11158 Project: Apache Cordova Issue Type: Bug Components: Plugin InAppBrowser Affects Versions: 1.2.0 Environment: Android 4.4 Reporter: Jimmy Thomson Priority: Minor When attempting to debug a callback in inappbrowser, I found that a particular sequence of events would result in the webview no longer responding to the debugger. The app itself appears to work, but neither chrome nor visual studio are able to debug the app. I am going to upload a repro file and give steps relative to the file. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-11104) Integrate Algolia Search to cordova docs
[ https://issues.apache.org/jira/browse/CB-11104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15258872#comment-15258872 ] ASF GitHub Bot commented on CB-11104: - Github user asfgit closed the pull request at: https://github.com/apache/cordova-docs/pull/581 > Integrate Algolia Search to cordova docs > > > Key: CB-11104 > URL: https://issues.apache.org/jira/browse/CB-11104 > Project: Apache Cordova > Issue Type: Task > Components: Docs >Reporter: Sarangan Rajamanickam >Assignee: Sarangan Rajamanickam > -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-11104) Integrate Algolia Search to cordova docs
[ https://issues.apache.org/jira/browse/CB-11104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15258871#comment-15258871 ] ASF subversion and git services commented on CB-11104: -- Commit c7bcd83d8a3efb2b01f32744f05786829bb710e7 in cordova-docs's branch refs/heads/master from [~sarangan12] [ https://git-wip-us.apache.org/repos/asf?p=cordova-docs.git;h=c7bcd83 ] CB-11104: Integrate Algolia Search to cordova docs. This closes #581. > Integrate Algolia Search to cordova docs > > > Key: CB-11104 > URL: https://issues.apache.org/jira/browse/CB-11104 > Project: Apache Cordova > Issue Type: Task > Components: Docs >Reporter: Sarangan Rajamanickam >Assignee: Sarangan Rajamanickam > -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Created] (CB-11157) Anchor links in TOC are not working
Nikhil Khandelwal created CB-11157: -- Summary: Anchor links in TOC are not working Key: CB-11157 URL: https://issues.apache.org/jira/browse/CB-11157 Project: Apache Cordova Issue Type: Bug Components: Docs Reporter: Nikhil Khandelwal Priority: Minor Anchor link in TOC for this anchor is not working: http://cordova.apache.org/docs/en/latest/reference/cordova-plugin-camera/index.html#sample:-take-pictures-select-pictures-from-the-picture-library-and-get-thumbnails- -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-11136) InAppBrowser fails to close with WKWebView OAuth
[
https://issues.apache.org/jira/browse/CB-11136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15258548#comment-15258548
]
ASF GitHub Bot commented on CB-11136:
-
Github user ephemer commented on the pull request:
https://github.com/apache/cordova-plugin-inappbrowser/pull/162#issuecomment-214827853
Thank you, my pleasure.
I have thought about this a bit longer.. The main issue is that recent
Cordova changes, namely introducing WKWebView, have broken this plugin for a
significant use case, namely OAuth. The changes suggested here put the
functionality back to how it was before the internal changes broke it. I'd
prefer a different solution but until we have that I think it's important that
the plugin does what it's supposed to.
Making these changes depend on an option like `modal: false` is a bit like
providing the option `worksAsItIsSupposedTo: true`. If anything we could
provide an option `useStrictlyModalBrowser: true` or similar to opt-in to the
new WKWebView behaviour.
@jcesarsh what do you think, looking at this in that light?
> InAppBrowser fails to close with WKWebView OAuth
> -
>
> Key: CB-11136
> URL: https://issues.apache.org/jira/browse/CB-11136
> Project: Apache Cordova
> Issue Type: Bug
> Components: iOS, Plugin InAppBrowser, Plugin WKWebViewEngine
>Affects Versions: 4.1.0
> Environment: iOS 8+ with WKWebView
>Reporter: Geordie Jay
> Original Estimate: 3h
> Remaining Estimate: 3h
>
> Launching InAppBrowser from Cordova iOS Platform 4+ with its WKWebView for
> OAuth (e.g. Facebook or Google login) fails to close as it should.
> The reason is that the entire WKWebView thread seems to pause when another
> view controller is presented. This can be confirmed by inspecting the
> WKWebView session in Safari, running `window.open('http://something.com')`
> and then trying to enter another command into that Safari console.
> I made a hacky but working version of this that animated in the
> InAppBrowser's view manually, rather than 'presenting' the ViewController in
> the traditional iOS style. In that instance the WKWebView thread continues as
> normal and receives the confirmation to close the other InAppBrowser when the
> OAuth process is complete.
> Maybe there is a better way around this, but at the moment this is a big
> usability fail for all WKWebView users.
> What do you all think, is the 'not-actually-presenting' way of presenting the
> InAppBrowser acceptable? Would be happy to make a pull request along these
> lines if it is.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-11131) Fix TypeError: message.toUpperCase is not a function in CordovaLogger
[
https://issues.apache.org/jira/browse/CB-11131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15258475#comment-15258475
]
ASF GitHub Bot commented on CB-11131:
-
Github user codecov-io commented on the pull request:
https://github.com/apache/cordova-lib/pull/431#issuecomment-214814135
## [Current coverage][cc-pull] is **100%**
> Merging [#431][cc-pull] into [master][cc-base-branch] will not change
coverage
```diff
@@ master #431 diff @@
==
Files69 69
Lines 9878 9878
Methods 841841
Messages 0 0
Branches 1271 1271
==
Hits 9878 9878
Misses0 0
Partials 0 0
```
[][cc-pull]
> Powered by [Codecov](https://codecov.io?src=pr). Last updated by 1ca4804
[cc-base-branch]:
https://codecov.io/gh/apache/cordova-lib/branch/master?src=pr
[cc-pull]: https://codecov.io/gh/apache/cordova-lib/pull/431?src=pr
> Fix TypeError: message.toUpperCase is not a function in CordovaLogger
> -
>
> Key: CB-11131
> URL: https://issues.apache.org/jira/browse/CB-11131
> Project: Apache Cordova
> Issue Type: Bug
> Components: CordovaCommon
>Reporter: Sergey Shakhnazarov
>Assignee: Sergey Shakhnazarov
>
> Such an error occurs if a non-string value is passed to CordovaLogger.log:
> {{TypeError: message.toUpperCase is not a function}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-11117) Preparing platforms should skip copying files which haven't changed
[ https://issues.apache.org/jira/browse/CB-7?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15258462#comment-15258462 ] ASF GitHub Bot commented on CB-7: - Github user codecov-io commented on the pull request: https://github.com/apache/cordova-lib/pull/429#issuecomment-214812288 ## [Current coverage][cc-pull] is **100%** > Merging [#429][cc-pull] into [master][cc-base-branch] will increase coverage by **+19.90%** ```diff @@ master #429 diff @@ Files 69 69 Lines5027 9878 +4851 Methods 0841+841 Branches 971 1271+300 + Hits 4027 9878 +5851 + Misses995 0-995 + Partials5 0 -5 ``` 1. 5 files in `...dova-lib/src/cordova` were modified. [more](https://codecov.io/gh/apache/cordova-lib/commit/3abe8b389628cc0256f16fa6d66da7a460485925/changes?src=pr#636F72646F76612D6C69622F7372632F636F72646F7661) - Misses `-16` - Hits `+167` 1. 2 files (not in diff) in `...lib/src/util/windows` were modified. [more](https://codecov.io/gh/apache/cordova-lib/commit/3abe8b389628cc0256f16fa6d66da7a460485925/changes?src=pr#636F72646F76612D6C69622F7372632F7574696C2F77696E646F7773) - Misses `-52` - Partials `-1` - Hits `+383` 1. 3 files (not in diff) in `cordova-lib/src/util` were modified. [more](https://codecov.io/gh/apache/cordova-lib/commit/3abe8b389628cc0256f16fa6d66da7a460485925/changes?src=pr#636F72646F76612D6C69622F7372632F7574696C) - Misses `-10` - Hits `+55` 1. 7 files (not in diff) in `...lib/src/plugman/util` were modified. [more](https://codecov.io/gh/apache/cordova-lib/commit/3abe8b389628cc0256f16fa6d66da7a460485925/changes?src=pr#636F72646F76612D6C69622F7372632F706C75676D616E2F7574696C) - Misses `-19` - Hits `+197` 1. 3 files (not in diff) in `...src/plugman/registry` were modified. [more](https://codecov.io/gh/apache/cordova-lib/commit/3abe8b389628cc0256f16fa6d66da7a460485925/changes?src=pr#636F72646F76612D6C69622F7372632F706C75676D616E2F7265676973747279) - Misses `-9` - Hits `+142` 1. 7 files (not in diff) in `...rc/plugman/platforms` were modified. [more](https://codecov.io/gh/apache/cordova-lib/commit/3abe8b389628cc0256f16fa6d66da7a460485925/changes?src=pr#636F72646F76612D6C69622F7372632F706C75676D616E2F706C6174666F726D73) - Misses `-84` - Hits `+608` 1. 12 files (not in diff) in `...dova-lib/src/plugman` were modified. [more](https://codecov.io/gh/apache/cordova-lib/commit/3abe8b389628cc0256f16fa6d66da7a460485925/changes?src=pr#636F72646F76612D6C69622F7372632F706C75676D616E) - Misses `-261` - Hits `+1202` 1. 2 files (not in diff) in `...va-lib/src/platforms` were modified. [more](https://codecov.io/gh/apache/cordova-lib/commit/3abe8b389628cc0256f16fa6d66da7a460485925/changes?src=pr#636F72646F76612D6C69622F7372632F706C6174666F726D73) - Misses `-12` - Partials `-2` - Hits `+243` 1. 3 files (not in diff) in `...ordova-lib/src/hooks` were modified. [more](https://codecov.io/gh/apache/cordova-lib/commit/3abe8b389628cc0256f16fa6d66da7a460485925/changes?src=pr#636F72646F76612D6C69622F7372632F686F6F6B73) - Misses `-48` - Hits `+208` 1. 2 files (not in diff) in `...etadata/parserhelper` were modified. [more](https://codecov.io/gh/apache/cordova-lib/commit/3abe8b389628cc0256f16fa6d66da7a460485925/changes?src=pr#636F72646F76612D6C69622F7372632F636F72646F76612F6D657461646174612F70617273657268656C706572) - Hits `+64` [][cc-pull] > Powered by [Codecov](https://codecov.io?src=pr). Last updated by 3abe8b3 [cc-base-branch]: https://codecov.io/gh/apache/cordova-lib/branch/master?src=pr [cc-pull]: https://codecov.io/gh/apache/cordova-lib/pull/429?src=pr > Preparing platforms should skip copying files which haven't changed > --- > > Key: CB-7 > URL: https://issues.apache.org/jira/browse/CB-7 > Project: Apache Cordova > Issue Type: Improvement > Components: Android, iOS, Windows >Reporter: Jason Ginchereau >Assignee: Jason Ginchereau > > Many cordova CLI commands include a "prepare" operation, including 'cordova > build', 'cordova run', 'cordova plugin add', and more. Every time each of > those commands runs, the target platform is "prepared", which involves > copying all files from the [/www, > /platforms//platform_www, /mer
[jira] [Resolved] (CB-11133) Handle android emulator start failure
[
https://issues.apache.org/jira/browse/CB-11133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Shakhnazarov resolved CB-11133.
--
Resolution: Fixed
> Handle android emulator start failure
> -
>
> Key: CB-11133
> URL: https://issues.apache.org/jira/browse/CB-11133
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android
>Reporter: Sergey Shakhnazarov
>Assignee: Sergey Shakhnazarov
>
> An x86_64 emulator start failure due to HAXM disabled state (because of
> enabled HyperV Windows feature for example) is not caught, which makes the
> process hang in the infinite {{wait_for_emulator}} loop.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-11133) Handle android emulator start failure
[
https://issues.apache.org/jira/browse/CB-11133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15258457#comment-15258457
]
ASF GitHub Bot commented on CB-11133:
-
Github user asfgit closed the pull request at:
https://github.com/apache/cordova-android/pull/297
> Handle android emulator start failure
> -
>
> Key: CB-11133
> URL: https://issues.apache.org/jira/browse/CB-11133
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android
>Reporter: Sergey Shakhnazarov
>Assignee: Sergey Shakhnazarov
>
> An x86_64 emulator start failure due to HAXM disabled state (because of
> enabled HyperV Windows feature for example) is not caught, which makes the
> process hang in the infinite {{wait_for_emulator}} loop.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-11133) Handle android emulator start failure
[
https://issues.apache.org/jira/browse/CB-11133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15258455#comment-15258455
]
ASF subversion and git services commented on CB-11133:
--
Commit abcaee24f9bd0e680f8d06ced5e0d363d63cffb7 in cordova-android's branch
refs/heads/master from [~daserge]
[ https://git-wip-us.apache.org/repos/asf?p=cordova-android.git;h=abcaee2 ]
CB-11133 Handle android emulator start failure
> Handle android emulator start failure
> -
>
> Key: CB-11133
> URL: https://issues.apache.org/jira/browse/CB-11133
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android
>Reporter: Sergey Shakhnazarov
>Assignee: Sergey Shakhnazarov
>
> An x86_64 emulator start failure due to HAXM disabled state (because of
> enabled HyperV Windows feature for example) is not caught, which makes the
> process hang in the infinite {{wait_for_emulator}} loop.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-11131) Fix TypeError: message.toUpperCase is not a function in CordovaLogger
[
https://issues.apache.org/jira/browse/CB-11131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15258452#comment-15258452
]
ASF GitHub Bot commented on CB-11131:
-
Github user jasongin commented on the pull request:
https://github.com/apache/cordova-lib/pull/431#issuecomment-214811002
👍
> Fix TypeError: message.toUpperCase is not a function in CordovaLogger
> -
>
> Key: CB-11131
> URL: https://issues.apache.org/jira/browse/CB-11131
> Project: Apache Cordova
> Issue Type: Bug
> Components: CordovaCommon
>Reporter: Sergey Shakhnazarov
>Assignee: Sergey Shakhnazarov
>
> Such an error occurs if a non-string value is passed to CordovaLogger.log:
> {{TypeError: message.toUpperCase is not a function}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-11131) Fix TypeError: message.toUpperCase is not a function in CordovaLogger
[
https://issues.apache.org/jira/browse/CB-11131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15258449#comment-15258449
]
ASF GitHub Bot commented on CB-11131:
-
Github user daserge commented on the pull request:
https://github.com/apache/cordova-lib/pull/431#issuecomment-214810543
Updated, thanks!
> Fix TypeError: message.toUpperCase is not a function in CordovaLogger
> -
>
> Key: CB-11131
> URL: https://issues.apache.org/jira/browse/CB-11131
> Project: Apache Cordova
> Issue Type: Bug
> Components: CordovaCommon
>Reporter: Sergey Shakhnazarov
>Assignee: Sergey Shakhnazarov
>
> Such an error occurs if a non-string value is passed to CordovaLogger.log:
> {{TypeError: message.toUpperCase is not a function}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-11133) Handle android emulator start failure
[
https://issues.apache.org/jira/browse/CB-11133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15258446#comment-15258446
]
ASF GitHub Bot commented on CB-11133:
-
Github user nikhilkh commented on the pull request:
https://github.com/apache/cordova-android/pull/297#issuecomment-214810232
LGTM
> Handle android emulator start failure
> -
>
> Key: CB-11133
> URL: https://issues.apache.org/jira/browse/CB-11133
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android
>Reporter: Sergey Shakhnazarov
>Assignee: Sergey Shakhnazarov
>
> An x86_64 emulator start failure due to HAXM disabled state (because of
> enabled HyperV Windows feature for example) is not caught, which makes the
> process hang in the infinite {{wait_for_emulator}} loop.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-11153) Use Gradle 2.8 correctly for building Android projects
[
https://issues.apache.org/jira/browse/CB-11153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15258440#comment-15258440
]
ASF GitHub Bot commented on CB-11153:
-
Github user nikhilkh commented on the pull request:
https://github.com/apache/cordova-android/pull/299#issuecomment-214809471
I just ended up moving to version 2.13 which is the latest - and the perf
is even a bit better than version 2.8. I looked at Android docs and did not
find anything about one version being more compatible than other - so we should
be fine.
> Use Gradle 2.8 correctly for building Android projects
> --
>
> Key: CB-11153
> URL: https://issues.apache.org/jira/browse/CB-11153
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android
>Reporter: Nikhil Khandelwal
>
> In build.gradle we have this:
> {code}
> task wrapper(type: Wrapper) {
> gradleVersion = '2.8'
> }
> {code}
> However, we do not have the gradle version specified correctly in prepEnv:
> {code}
> // If the gradle distribution URL is set, make sure it points to
> version we want.
> // If it's not set, do nothing, assuming that we're using a future
> version of gradle that we don't want to mess with.
> // For some reason, using ^ and $ don't work. This does the job,
> though.
> var distributionUrlRegex = /distributionUrl.*zip/;
> /*jshint -W069 */
> var distributionUrl =
> process.env['CORDOVA_ANDROID_GRADLE_DISTRIBUTION_URL'] ||
> 'http\\://services.gradle.org/distributions/gradle-2.2.1-all.zip';
> /*jshint +W069 */
> var gradleWrapperPropertiesPath = path.join(self.root, 'gradle',
> 'wrapper', 'gradle-wrapper.properties');
> shell.chmod('u+w', gradleWrapperPropertiesPath);
> shell.sed('-i', distributionUrlRegex,
> 'distributionUrl='+distributionUrl, gradleWrapperPropertiesPath);
> {code}
> One side effect of this is that it improves build performance significantly -
> on my machine by 1 second - on a "helloworld" project.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-11150) CI Error - Windows Platform - Could not find XHR config file
[
https://issues.apache.org/jira/browse/CB-11150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Shakhnazarov resolved CB-11150.
--
Resolution: Fixed
> CI Error - Windows Platform - Could not find XHR config file
> -
>
> Key: CB-11150
> URL: https://issues.apache.org/jira/browse/CB-11150
> Project: Apache Cordova
> Issue Type: Bug
> Components: Windows
>Reporter: Sarangan Rajamanickam
>Assignee: Sergey Shakhnazarov
>Priority: Critical
> Labels: found-by-ci
>
> The CI builds for Windows Phone 8.1 and Windows Store 8.1 platforms are
> failing consistently. Link: https://ci.apache.org/waterfall?category=cordova
> On analysis, the failure began with this commit:
> 1.
> https://github.com/apache/cordova-windows/commit/d6988f5c863ec3ba5cde33a678a4b93badc64395
> 2. https://ci.apache.org/builders/cordova-windows-store8.1/builds/2218
> Assigning this issue to Sergey
> Error:
> Channel: Microsoft-Windows-AppHost/Admin
> Time Created: 2016-04-22T23:23:04.064399500Z
> Process ID:7476
> Document File: /www/cdvtests/index.html
> Display Name: mobilespec
> Error Description: "[Windows][cordova.js][readConfig] Could not XHR
> config.xml: {\"description\":\"The system cannot locate the resource
> specified.\\r\\n\",\"number\":-2146697211,\"stack\":\"Error: The system
> cannot locate the resource specified.\\r\\n\\n at readConfig
> (ms-appx://org.apache.mobilespec/www/cordova.js:870:9)\\n at init
> (ms-appx://org.apache.mobilespec/www/cordova.js:1517:25)\\n at Promise_ctor
> (ms-appx://microsoft.winjs.2.0/js/base.js:2025:17)\\n at makePromise
> (ms-appx://org.apache.mobilespec/www/cordova.js:1516:21)\\n at
> activationHandler (ms-appx://org.apache.mobilespec/www/cordova.js:1525:17)\\n
> at dispatchOne (ms-appx://microsoft.winjs.2.0/js/base.js:9416:25)\\n at
> dispatchEvent (ms-appx://microsoft.winjs.2.0/js/base.js:9415:21)\\n at
> drainOneEvent (ms-appx://microsoft.winjs.2.0/js/base.js:9469:13)\\n at
> drainQueue (ms-appx://microsoft.winjs.2.0/js/base.js:9486:9)\\n at
> Anonymous function (ms-appx://microsoft.winjs.2.0/js/base.js:2952:17)\"}"
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-11150) CI Error - Windows Platform - Could not find XHR config file
[
https://issues.apache.org/jira/browse/CB-11150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15258422#comment-15258422
]
ASF subversion and git services commented on CB-11150:
--
Commit 3da74166f67e439d09c5c5de48af603287207b84 in cordova-windows's branch
refs/heads/master from [~daserge]
[ https://git-wip-us.apache.org/repos/asf?p=cordova-windows.git;h=3da7416 ]
CB-11150 CI Error - Windows Platform - Could not find XHR config file
Changes config.xml path to absolute
> CI Error - Windows Platform - Could not find XHR config file
> -
>
> Key: CB-11150
> URL: https://issues.apache.org/jira/browse/CB-11150
> Project: Apache Cordova
> Issue Type: Bug
> Components: Windows
>Reporter: Sarangan Rajamanickam
>Assignee: Sergey Shakhnazarov
>Priority: Critical
> Labels: found-by-ci
>
> The CI builds for Windows Phone 8.1 and Windows Store 8.1 platforms are
> failing consistently. Link: https://ci.apache.org/waterfall?category=cordova
> On analysis, the failure began with this commit:
> 1.
> https://github.com/apache/cordova-windows/commit/d6988f5c863ec3ba5cde33a678a4b93badc64395
> 2. https://ci.apache.org/builders/cordova-windows-store8.1/builds/2218
> Assigning this issue to Sergey
> Error:
> Channel: Microsoft-Windows-AppHost/Admin
> Time Created: 2016-04-22T23:23:04.064399500Z
> Process ID:7476
> Document File: /www/cdvtests/index.html
> Display Name: mobilespec
> Error Description: "[Windows][cordova.js][readConfig] Could not XHR
> config.xml: {\"description\":\"The system cannot locate the resource
> specified.\\r\\n\",\"number\":-2146697211,\"stack\":\"Error: The system
> cannot locate the resource specified.\\r\\n\\n at readConfig
> (ms-appx://org.apache.mobilespec/www/cordova.js:870:9)\\n at init
> (ms-appx://org.apache.mobilespec/www/cordova.js:1517:25)\\n at Promise_ctor
> (ms-appx://microsoft.winjs.2.0/js/base.js:2025:17)\\n at makePromise
> (ms-appx://org.apache.mobilespec/www/cordova.js:1516:21)\\n at
> activationHandler (ms-appx://org.apache.mobilespec/www/cordova.js:1525:17)\\n
> at dispatchOne (ms-appx://microsoft.winjs.2.0/js/base.js:9416:25)\\n at
> dispatchEvent (ms-appx://microsoft.winjs.2.0/js/base.js:9415:21)\\n at
> drainOneEvent (ms-appx://microsoft.winjs.2.0/js/base.js:9469:13)\\n at
> drainQueue (ms-appx://microsoft.winjs.2.0/js/base.js:9486:9)\\n at
> Anonymous function (ms-appx://microsoft.winjs.2.0/js/base.js:2952:17)\"}"
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-11150) CI Error - Windows Platform - Could not find XHR config file
[
https://issues.apache.org/jira/browse/CB-11150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15258424#comment-15258424
]
ASF GitHub Bot commented on CB-11150:
-
Github user asfgit closed the pull request at:
https://github.com/apache/cordova-windows/pull/169
> CI Error - Windows Platform - Could not find XHR config file
> -
>
> Key: CB-11150
> URL: https://issues.apache.org/jira/browse/CB-11150
> Project: Apache Cordova
> Issue Type: Bug
> Components: Windows
>Reporter: Sarangan Rajamanickam
>Assignee: Sergey Shakhnazarov
>Priority: Critical
> Labels: found-by-ci
>
> The CI builds for Windows Phone 8.1 and Windows Store 8.1 platforms are
> failing consistently. Link: https://ci.apache.org/waterfall?category=cordova
> On analysis, the failure began with this commit:
> 1.
> https://github.com/apache/cordova-windows/commit/d6988f5c863ec3ba5cde33a678a4b93badc64395
> 2. https://ci.apache.org/builders/cordova-windows-store8.1/builds/2218
> Assigning this issue to Sergey
> Error:
> Channel: Microsoft-Windows-AppHost/Admin
> Time Created: 2016-04-22T23:23:04.064399500Z
> Process ID:7476
> Document File: /www/cdvtests/index.html
> Display Name: mobilespec
> Error Description: "[Windows][cordova.js][readConfig] Could not XHR
> config.xml: {\"description\":\"The system cannot locate the resource
> specified.\\r\\n\",\"number\":-2146697211,\"stack\":\"Error: The system
> cannot locate the resource specified.\\r\\n\\n at readConfig
> (ms-appx://org.apache.mobilespec/www/cordova.js:870:9)\\n at init
> (ms-appx://org.apache.mobilespec/www/cordova.js:1517:25)\\n at Promise_ctor
> (ms-appx://microsoft.winjs.2.0/js/base.js:2025:17)\\n at makePromise
> (ms-appx://org.apache.mobilespec/www/cordova.js:1516:21)\\n at
> activationHandler (ms-appx://org.apache.mobilespec/www/cordova.js:1525:17)\\n
> at dispatchOne (ms-appx://microsoft.winjs.2.0/js/base.js:9416:25)\\n at
> dispatchEvent (ms-appx://microsoft.winjs.2.0/js/base.js:9415:21)\\n at
> drainOneEvent (ms-appx://microsoft.winjs.2.0/js/base.js:9469:13)\\n at
> drainQueue (ms-appx://microsoft.winjs.2.0/js/base.js:9486:9)\\n at
> Anonymous function (ms-appx://microsoft.winjs.2.0/js/base.js:2952:17)\"}"
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-11150) CI Error - Windows Platform - Could not find XHR config file
[
https://issues.apache.org/jira/browse/CB-11150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15258401#comment-15258401
]
ASF GitHub Bot commented on CB-11150:
-
Github user nikhilkh commented on the pull request:
https://github.com/apache/cordova-windows/pull/169#issuecomment-214806350
LGTM. Let's get this in - as it will fix our build.
> CI Error - Windows Platform - Could not find XHR config file
> -
>
> Key: CB-11150
> URL: https://issues.apache.org/jira/browse/CB-11150
> Project: Apache Cordova
> Issue Type: Bug
> Components: Windows
>Reporter: Sarangan Rajamanickam
>Assignee: Sergey Shakhnazarov
>Priority: Critical
> Labels: found-by-ci
>
> The CI builds for Windows Phone 8.1 and Windows Store 8.1 platforms are
> failing consistently. Link: https://ci.apache.org/waterfall?category=cordova
> On analysis, the failure began with this commit:
> 1.
> https://github.com/apache/cordova-windows/commit/d6988f5c863ec3ba5cde33a678a4b93badc64395
> 2. https://ci.apache.org/builders/cordova-windows-store8.1/builds/2218
> Assigning this issue to Sergey
> Error:
> Channel: Microsoft-Windows-AppHost/Admin
> Time Created: 2016-04-22T23:23:04.064399500Z
> Process ID:7476
> Document File: /www/cdvtests/index.html
> Display Name: mobilespec
> Error Description: "[Windows][cordova.js][readConfig] Could not XHR
> config.xml: {\"description\":\"The system cannot locate the resource
> specified.\\r\\n\",\"number\":-2146697211,\"stack\":\"Error: The system
> cannot locate the resource specified.\\r\\n\\n at readConfig
> (ms-appx://org.apache.mobilespec/www/cordova.js:870:9)\\n at init
> (ms-appx://org.apache.mobilespec/www/cordova.js:1517:25)\\n at Promise_ctor
> (ms-appx://microsoft.winjs.2.0/js/base.js:2025:17)\\n at makePromise
> (ms-appx://org.apache.mobilespec/www/cordova.js:1516:21)\\n at
> activationHandler (ms-appx://org.apache.mobilespec/www/cordova.js:1525:17)\\n
> at dispatchOne (ms-appx://microsoft.winjs.2.0/js/base.js:9416:25)\\n at
> dispatchEvent (ms-appx://microsoft.winjs.2.0/js/base.js:9415:21)\\n at
> drainOneEvent (ms-appx://microsoft.winjs.2.0/js/base.js:9469:13)\\n at
> drainQueue (ms-appx://microsoft.winjs.2.0/js/base.js:9486:9)\\n at
> Anonymous function (ms-appx://microsoft.winjs.2.0/js/base.js:2952:17)\"}"
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-11136) InAppBrowser fails to close with WKWebView OAuth
[
https://issues.apache.org/jira/browse/CB-11136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15258366#comment-15258366
]
ASF GitHub Bot commented on CB-11136:
-
Github user Chun-Yang commented on the pull request:
https://github.com/apache/cordova-plugin-inappbrowser/pull/162#issuecomment-214800395
@ephemer Man you are genius! Thank you SO~~ much!
> InAppBrowser fails to close with WKWebView OAuth
> -
>
> Key: CB-11136
> URL: https://issues.apache.org/jira/browse/CB-11136
> Project: Apache Cordova
> Issue Type: Bug
> Components: iOS, Plugin InAppBrowser, Plugin WKWebViewEngine
>Affects Versions: 4.1.0
> Environment: iOS 8+ with WKWebView
>Reporter: Geordie Jay
> Original Estimate: 3h
> Remaining Estimate: 3h
>
> Launching InAppBrowser from Cordova iOS Platform 4+ with its WKWebView for
> OAuth (e.g. Facebook or Google login) fails to close as it should.
> The reason is that the entire WKWebView thread seems to pause when another
> view controller is presented. This can be confirmed by inspecting the
> WKWebView session in Safari, running `window.open('http://something.com')`
> and then trying to enter another command into that Safari console.
> I made a hacky but working version of this that animated in the
> InAppBrowser's view manually, rather than 'presenting' the ViewController in
> the traditional iOS style. In that instance the WKWebView thread continues as
> normal and receives the confirmation to close the other InAppBrowser when the
> OAuth process is complete.
> Maybe there is a better way around this, but at the moment this is a big
> usability fail for all WKWebView users.
> What do you all think, is the 'not-actually-presenting' way of presenting the
> InAppBrowser acceptable? Would be happy to make a pull request along these
> lines if it is.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-11131) Fix TypeError: message.toUpperCase is not a function in CordovaLogger
[
https://issues.apache.org/jira/browse/CB-11131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15258360#comment-15258360
]
ASF GitHub Bot commented on CB-11131:
-
Github user jasongin commented on a diff in the pull request:
https://github.com/apache/cordova-lib/pull/431#discussion_r61116509
--- Diff: cordova-common/src/CordovaLogger.js ---
@@ -209,7 +209,7 @@ function formatError(error, isVerbose) {
message = error;
}
-if(message.toUpperCase().indexOf('ERROR:') !== 0) {
+if(message && typeof message.toUpperCase === 'function' &&
message.toUpperCase().indexOf('ERROR:') !== 0) {
--- End diff --
This is fine, but I would have preferred `if (typeof message === 'string'
&& message.toUpperCase()...)`
> Fix TypeError: message.toUpperCase is not a function in CordovaLogger
> -
>
> Key: CB-11131
> URL: https://issues.apache.org/jira/browse/CB-11131
> Project: Apache Cordova
> Issue Type: Bug
> Components: CordovaCommon
>Reporter: Sergey Shakhnazarov
>Assignee: Sergey Shakhnazarov
>
> Such an error occurs if a non-string value is passed to CordovaLogger.log:
> {{TypeError: message.toUpperCase is not a function}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-10776) Add the ability to pause and resume an audio recording
[ https://issues.apache.org/jira/browse/CB-10776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon MacDonald resolved CB-10776. -- Resolution: Fixed > Add the ability to pause and resume an audio recording > -- > > Key: CB-10776 > URL: https://issues.apache.org/jira/browse/CB-10776 > Project: Apache Cordova > Issue Type: Improvement > Components: Plugin Media >Reporter: Simon MacDonald >Assignee: Simon MacDonald > Labels: Android, iOS > > You have the ability to start and stop a recording but there is no way to > pause the recording. I would like to add the functionality so that a user > could pause recording and resume it later. The output once the recoding is > stopped should be a single audio file no matter how many times the pause API > was invoked. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-10776) Add the ability to pause and resume an audio recording
[ https://issues.apache.org/jira/browse/CB-10776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15258352#comment-15258352 ] ASF subversion and git services commented on CB-10776: -- Commit b1ef73d157e6ee56ee235471cc11dca7bcd8af2a in cordova-plugin-media's branch refs/heads/master from [~macdonst] [ https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-media.git;h=b1ef73d ] CB-10776: Add the ability to pause and resume an audio recording (iOS) > Add the ability to pause and resume an audio recording > -- > > Key: CB-10776 > URL: https://issues.apache.org/jira/browse/CB-10776 > Project: Apache Cordova > Issue Type: Improvement > Components: Plugin Media >Reporter: Simon MacDonald >Assignee: Simon MacDonald > Labels: Android, iOS > > You have the ability to start and stop a recording but there is no way to > pause the recording. I would like to add the functionality so that a user > could pause recording and resume it later. The output once the recoding is > stopped should be a single audio file no matter how many times the pause API > was invoked. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-9487) Support getting amplitude for recording
[ https://issues.apache.org/jira/browse/CB-9487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15258351#comment-15258351 ] ASF subversion and git services commented on CB-9487: - Commit e4e30ae9e98df22486c3f99060a5939ad9514c2c in cordova-plugin-media's branch refs/heads/master from [~macdonst] [ https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-media.git;h=e4e30ae ] CB-9487: Don't update position when getting amplitude > Support getting amplitude for recording > --- > > Key: CB-9487 > URL: https://issues.apache.org/jira/browse/CB-9487 > Project: Apache Cordova > Issue Type: Improvement > Components: Plugin Media > Environment: Android, iOS >Reporter: Szabolcs Balogh >Assignee: Simon MacDonald > > Hi, > It would be useful to be able to get the actual amplitude during recording > (E.g. to display waveform during registration). > If you are interested to include this improvement, you can find the required > modifications (for Android and iOS) in this commit: > https://github.com/kukukk/cordova-plugin-media/commit/ee671806690219c511dea686e7e74d4939ea8d9b > Best regards, > kukukk -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-10776) Add the ability to pause and resume an audio recording
[ https://issues.apache.org/jira/browse/CB-10776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15258353#comment-15258353 ] ASF subversion and git services commented on CB-10776: -- Commit a3e639bf995a74ea3ee84d7deb7009cc91a6 in cordova-plugin-media's branch refs/heads/master from [~macdonst] [ https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-media.git;h=a3e639b ] CB-10776: Add the ability to pause and resume an audio recording (Android) > Add the ability to pause and resume an audio recording > -- > > Key: CB-10776 > URL: https://issues.apache.org/jira/browse/CB-10776 > Project: Apache Cordova > Issue Type: Improvement > Components: Plugin Media >Reporter: Simon MacDonald >Assignee: Simon MacDonald > Labels: Android, iOS > > You have the ability to start and stop a recording but there is no way to > pause the recording. I would like to add the functionality so that a user > could pause recording and resume it later. The output once the recoding is > stopped should be a single audio file no matter how many times the pause API > was invoked. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-9256) Errors in subscribed event callbacks prevent other subscribed callbacks from being invoked
[
https://issues.apache.org/jira/browse/CB-9256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15258313#comment-15258313
]
Noah NU commented on CB-9256:
-
onDeviceReady is sticky, implying the behaviour should not differ if the events
are registered after onDeviceReady has fired. I haven't been able to reproduce
the "different" behaviour, although I can confirm that an error thrown in a
onDeviceReady callback will prevent execution of all following onDeviceReady
callbacks.
This is because the thrown exception will cease execution and pass control to
the first catch block in the call stack. Since Cordova does not define any
catch block, this prevents any other device ready callbacks from executing.
This is expected behaviour, and the error should be caught and handled by the
user.
> Errors in subscribed event callbacks prevent other subscribed callbacks from
> being invoked
> --
>
> Key: CB-9256
> URL: https://issues.apache.org/jira/browse/CB-9256
> Project: Apache Cordova
> Issue Type: Bug
> Components: CordovaJS
>Reporter: Steven Wexler
>Priority: Blocker
>
> Let's say I register two callbacks for the "deviceReady" event before the
> event fires. If the first callback hits an error, the second callback will
> not be invoked
> {code}
> document.addEventListener("deviceready", function () { throw new
> Error("oops"); });
> document.addeventListener("deviceready", function () { /*never hit*/ });
> {code}
> This behavior differs if the events were registered after the event was fired.
> I think the following code should handle callbacks that fail:
> https://github.com/apache/cordova-js/blob/master/src/common/channel.js#L213
> {code}
> for (var i = 0; i < toCall.length; ++i) {
> toCall[i].apply(this, fireArgs);
> }
> {code}
> Should be something like:
> {code}
> var errors = [];
> for (var i = 0; i < toCall.length; ++i) {
> try {
> toCall[i].apply(this, fireArgs);
> } catch (e) {
> errors.push(e);
> }
> }
> for (var j = 0; j < errors.length; ++j) {
> (function (arg) {
> setTimeout(function () { throw errors[arg]; });
> })(j);
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-11156) Change default FadeSplashScreenDuration value
[
https://issues.apache.org/jira/browse/CB-11156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Shakhnazarov updated CB-11156:
-
Issue Type: Improvement (was: Bug)
> Change default FadeSplashScreenDuration value
> -
>
> Key: CB-11156
> URL: https://issues.apache.org/jira/browse/CB-11156
> Project: Apache Cordova
> Issue Type: Improvement
> Components: Plugin SplashScreen
>Reporter: Sergey Shakhnazarov
>Assignee: Sergey Shakhnazarov
>
> Current value is 3000 ms which is equal to the default {{SplashScreenDelay}}
> and it doesn't look good.
> Proposed change is setting it to 500 ms.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-11156) Change default FadeSplashScreenDuration value
[
https://issues.apache.org/jira/browse/CB-11156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Shakhnazarov updated CB-11156:
-
Priority: Minor (was: Major)
> Change default FadeSplashScreenDuration value
> -
>
> Key: CB-11156
> URL: https://issues.apache.org/jira/browse/CB-11156
> Project: Apache Cordova
> Issue Type: Improvement
> Components: Plugin SplashScreen
>Reporter: Sergey Shakhnazarov
>Assignee: Sergey Shakhnazarov
>Priority: Minor
>
> Current value is 3000 ms which is equal to the default {{SplashScreenDelay}}
> and it doesn't look good.
> Proposed change is setting it to 500 ms.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Created] (CB-11156) Change default FadeSplashScreenDuration value
Sergey Shakhnazarov created CB-11156:
Summary: Change default FadeSplashScreenDuration value
Key: CB-11156
URL: https://issues.apache.org/jira/browse/CB-11156
Project: Apache Cordova
Issue Type: Bug
Components: Plugin SplashScreen
Reporter: Sergey Shakhnazarov
Assignee: Sergey Shakhnazarov
Current value is 3000 ms which is equal to the default {{SplashScreenDelay}}
and it doesn't look good.
Proposed change is setting it to 500 ms.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-11077) backbutton does not minimize app
[ https://issues.apache.org/jira/browse/CB-11077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Shakhnazarov resolved CB-11077. -- Resolution: Fixed > backbutton does not minimize app > > > Key: CB-11077 > URL: https://issues.apache.org/jira/browse/CB-11077 > Project: Apache Cordova > Issue Type: Bug > Components: Windows >Affects Versions: 4.3.0, 4.3.2 >Reporter: Beat > Labels: cordova, docs, triaged, universal, window, > windows-phone, windows-phone-81, windows-universal > > I was always wondering why backbutton handling was not well supported on > windows-phone platform until windows@4.2.0 was released with backbutton > support [CB-8481|https://issues.apache.org/jira/browse/CB-8481]. > But currently this fix became a real problem for me since I tried to release > a new version of my application to the windows store. My application was not > approved by ms team, because it was not suspended when there is no history. > So I had to downgrade to windows@4.1.0 to get an approved application... -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-11077) backbutton does not minimize app
[ https://issues.apache.org/jira/browse/CB-11077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15258205#comment-15258205 ] ASF GitHub Bot commented on CB-11077: - Github user asfgit closed the pull request at: https://github.com/apache/cordova-docs/pull/580 > backbutton does not minimize app > > > Key: CB-11077 > URL: https://issues.apache.org/jira/browse/CB-11077 > Project: Apache Cordova > Issue Type: Bug > Components: Windows >Affects Versions: 4.3.0, 4.3.2 >Reporter: Beat > Labels: cordova, docs, triaged, universal, window, > windows-phone, windows-phone-81, windows-universal > > I was always wondering why backbutton handling was not well supported on > windows-phone platform until windows@4.2.0 was released with backbutton > support [CB-8481|https://issues.apache.org/jira/browse/CB-8481]. > But currently this fix became a real problem for me since I tried to release > a new version of my application to the windows store. My application was not > approved by ms team, because it was not suspended when there is no history. > So I had to downgrade to windows@4.1.0 to get an approved application... -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-11077) backbutton does not minimize app
[ https://issues.apache.org/jira/browse/CB-11077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15258204#comment-15258204 ] ASF subversion and git services commented on CB-11077: -- Commit 345b316d22a95a4dd31d0d926681ef2adf281c19 in cordova-docs's branch refs/heads/master from [~daserge] [ https://git-wip-us.apache.org/repos/asf?p=cordova-docs.git;h=345b316 ] CB-11077 backbutton does not minimize app > backbutton does not minimize app > > > Key: CB-11077 > URL: https://issues.apache.org/jira/browse/CB-11077 > Project: Apache Cordova > Issue Type: Bug > Components: Windows >Affects Versions: 4.3.0, 4.3.2 >Reporter: Beat > Labels: cordova, docs, triaged, universal, window, > windows-phone, windows-phone-81, windows-universal > > I was always wondering why backbutton handling was not well supported on > windows-phone platform until windows@4.2.0 was released with backbutton > support [CB-8481|https://issues.apache.org/jira/browse/CB-8481]. > But currently this fix became a real problem for me since I tried to release > a new version of my application to the windows store. My application was not > approved by ms team, because it was not suspended when there is no history. > So I had to downgrade to windows@4.1.0 to get an approved application... -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-11036) 'args.slice is not a function' when building windows with other platform
[
https://issues.apache.org/jira/browse/CB-11036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15258202#comment-15258202
]
ASF GitHub Bot commented on CB-11036:
-
Github user asfgit closed the pull request at:
https://github.com/apache/cordova-lib/pull/430
> 'args.slice is not a function' when building windows with other platform
>
>
> Key: CB-11036
> URL: https://issues.apache.org/jira/browse/CB-11036
> Project: Apache Cordova
> Issue Type: Bug
> Components: Windows
>Affects Versions: Master
> Environment: Windows
>Reporter: Alexander Sorokin
>Assignee: Sergey Shakhnazarov
> Labels: regression, triaged
>
> Repro:
> {noformat}
> cordova create foo
> cd foo
> cordova platform add android
> cordova platform add windows
> cordova build
> {noformat}
> Android will build correctly but then there will be an error:
> Error: args.slice is not a function
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-11036) 'args.slice is not a function' when building windows with other platform
[
https://issues.apache.org/jira/browse/CB-11036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15258201#comment-15258201
]
ASF subversion and git services commented on CB-11036:
--
Commit b65196413d92ca9ce904abaa6c736ea6eefe7ebf in cordova-lib's branch
refs/heads/master from [~daserge]
[ https://git-wip-us.apache.org/repos/asf?p=cordova-lib.git;h=b651964 ]
CB-11036 'args.slice is not a function' when building windows with other
platform
Avoid options obj modification as it's then passed to other platforms
> 'args.slice is not a function' when building windows with other platform
>
>
> Key: CB-11036
> URL: https://issues.apache.org/jira/browse/CB-11036
> Project: Apache Cordova
> Issue Type: Bug
> Components: Windows
>Affects Versions: Master
> Environment: Windows
>Reporter: Alexander Sorokin
>Assignee: Sergey Shakhnazarov
> Labels: regression, triaged
>
> Repro:
> {noformat}
> cordova create foo
> cd foo
> cordova platform add android
> cordova platform add windows
> cordova build
> {noformat}
> Android will build correctly but then there will be an error:
> Error: args.slice is not a function
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-11036) 'args.slice is not a function' when building windows with other platform
[
https://issues.apache.org/jira/browse/CB-11036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Shakhnazarov resolved CB-11036.
--
Resolution: Fixed
> 'args.slice is not a function' when building windows with other platform
>
>
> Key: CB-11036
> URL: https://issues.apache.org/jira/browse/CB-11036
> Project: Apache Cordova
> Issue Type: Bug
> Components: Windows
>Affects Versions: Master
> Environment: Windows
>Reporter: Alexander Sorokin
>Assignee: Sergey Shakhnazarov
> Labels: regression, triaged
>
> Repro:
> {noformat}
> cordova create foo
> cd foo
> cordova platform add android
> cordova platform add windows
> cordova build
> {noformat}
> Android will build correctly but then there will be an error:
> Error: args.slice is not a function
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-11132) Fix Error: Cannot read property 'match' of undefined in cordova-android emulator.js
[
https://issues.apache.org/jira/browse/CB-11132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Shakhnazarov resolved CB-11132.
--
Resolution: Fixed
> Fix Error: Cannot read property 'match' of undefined in cordova-android
> emulator.js
> ---
>
> Key: CB-11132
> URL: https://issues.apache.org/jira/browse/CB-11132
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android
>Reporter: Sergey Shakhnazarov
>Assignee: Sergey Shakhnazarov
>Priority: Minor
>
> {{list_images}} fails parsing corrupted emulator images:
> {noformat}
> Available Android Virtual Devices:
> Name: api22
> Device: Nexus 4 (Google)
> Path: C:\Users\user.name\.android\avd\api22.avd
> Target: Android 5.1.1 (API level 22)
> Tag/ABI: default/x86_64
> Skin: WVGA800
> The following Android Virtual Devices could not be loaded:
> Name: Nexus_5_API_23_x86
> Path: C:\Users\user.name\.android\avd\Nexus_5_API_23_x86.avd
>Error: Unknown target 'Google Inc.:Google APIs:23' in
> C:\Users\user.name\.android\avd\Nexus_5_API_23_x86.ini
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-11132) Fix Error: Cannot read property 'match' of undefined in cordova-android emulator.js
[
https://issues.apache.org/jira/browse/CB-11132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15258198#comment-15258198
]
ASF GitHub Bot commented on CB-11132:
-
Github user asfgit closed the pull request at:
https://github.com/apache/cordova-android/pull/296
> Fix Error: Cannot read property 'match' of undefined in cordova-android
> emulator.js
> ---
>
> Key: CB-11132
> URL: https://issues.apache.org/jira/browse/CB-11132
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android
>Reporter: Sergey Shakhnazarov
>Assignee: Sergey Shakhnazarov
>Priority: Minor
>
> {{list_images}} fails parsing corrupted emulator images:
> {noformat}
> Available Android Virtual Devices:
> Name: api22
> Device: Nexus 4 (Google)
> Path: C:\Users\user.name\.android\avd\api22.avd
> Target: Android 5.1.1 (API level 22)
> Tag/ABI: default/x86_64
> Skin: WVGA800
> The following Android Virtual Devices could not be loaded:
> Name: Nexus_5_API_23_x86
> Path: C:\Users\user.name\.android\avd\Nexus_5_API_23_x86.avd
>Error: Unknown target 'Google Inc.:Google APIs:23' in
> C:\Users\user.name\.android\avd\Nexus_5_API_23_x86.ini
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-11132) Fix Error: Cannot read property 'match' of undefined in cordova-android emulator.js
[
https://issues.apache.org/jira/browse/CB-11132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15258197#comment-15258197
]
ASF subversion and git services commented on CB-11132:
--
Commit 8951660393dd4babc235fd291469e2fb1dc4a22d in cordova-android's branch
refs/heads/master from [~daserge]
[ https://git-wip-us.apache.org/repos/asf?p=cordova-android.git;h=8951660 ]
CB-11132 Fix Error: Cannot read property 'match' of undefined in
cordova-android emulator.js
> Fix Error: Cannot read property 'match' of undefined in cordova-android
> emulator.js
> ---
>
> Key: CB-11132
> URL: https://issues.apache.org/jira/browse/CB-11132
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android
>Reporter: Sergey Shakhnazarov
>Assignee: Sergey Shakhnazarov
>Priority: Minor
>
> {{list_images}} fails parsing corrupted emulator images:
> {noformat}
> Available Android Virtual Devices:
> Name: api22
> Device: Nexus 4 (Google)
> Path: C:\Users\user.name\.android\avd\api22.avd
> Target: Android 5.1.1 (API level 22)
> Tag/ABI: default/x86_64
> Skin: WVGA800
> The following Android Virtual Devices could not be loaded:
> Name: Nexus_5_API_23_x86
> Path: C:\Users\user.name\.android\avd\Nexus_5_API_23_x86.avd
>Error: Unknown target 'Google Inc.:Google APIs:23' in
> C:\Users\user.name\.android\avd\Nexus_5_API_23_x86.ini
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-11153) Use Gradle 2.8 correctly for building Android projects
[
https://issues.apache.org/jira/browse/CB-11153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15258159#comment-15258159
]
ASF GitHub Bot commented on CB-11153:
-
Github user infil00p commented on the pull request:
https://github.com/apache/cordova-android/pull/299#issuecomment-214762095
Why 2.8? Why not 2.10? Is 2.10 slower than 2.8? Will this break other
users somehow?
> Use Gradle 2.8 correctly for building Android projects
> --
>
> Key: CB-11153
> URL: https://issues.apache.org/jira/browse/CB-11153
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android
>Reporter: Nikhil Khandelwal
>
> In build.gradle we have this:
> {code}
> task wrapper(type: Wrapper) {
> gradleVersion = '2.8'
> }
> {code}
> However, we do not have the gradle version specified correctly in prepEnv:
> {code}
> // If the gradle distribution URL is set, make sure it points to
> version we want.
> // If it's not set, do nothing, assuming that we're using a future
> version of gradle that we don't want to mess with.
> // For some reason, using ^ and $ don't work. This does the job,
> though.
> var distributionUrlRegex = /distributionUrl.*zip/;
> /*jshint -W069 */
> var distributionUrl =
> process.env['CORDOVA_ANDROID_GRADLE_DISTRIBUTION_URL'] ||
> 'http\\://services.gradle.org/distributions/gradle-2.2.1-all.zip';
> /*jshint +W069 */
> var gradleWrapperPropertiesPath = path.join(self.root, 'gradle',
> 'wrapper', 'gradle-wrapper.properties');
> shell.chmod('u+w', gradleWrapperPropertiesPath);
> shell.sed('-i', distributionUrlRegex,
> 'distributionUrl='+distributionUrl, gradleWrapperPropertiesPath);
> {code}
> One side effect of this is that it improves build performance significantly -
> on my machine by 1 second - on a "helloworld" project.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-11155) Add new Chrome platform to build Chrome Packaged Apps.
[
https://issues.apache.org/jira/browse/CB-11155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Hooey updated CB-11155:
-
Description:
It would be nice to be able to build a Chrome Packaged App from an existing
Cordova project. Something like the following:
{code}
cordova platform add chrome
cordova build chrome
{code}
was:
It would be nice to be able to build a Chrome Packaged App from an existing
Cordova project. Something like the following:
```
cordova platform add chrome
cordova build chrome
```
> Add new Chrome platform to build Chrome Packaged Apps.
> --
>
> Key: CB-11155
> URL: https://issues.apache.org/jira/browse/CB-11155
> Project: Apache Cordova
> Issue Type: New Feature
> Components: CLI, CordovaCommon
>Reporter: David Hooey
>Priority: Minor
>
> It would be nice to be able to build a Chrome Packaged App from an existing
> Cordova project. Something like the following:
> {code}
> cordova platform add chrome
> cordova build chrome
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Created] (CB-11155) Add new Chrome platform to build Chrome Packaged Apps.
David Hooey created CB-11155: Summary: Add new Chrome platform to build Chrome Packaged Apps. Key: CB-11155 URL: https://issues.apache.org/jira/browse/CB-11155 Project: Apache Cordova Issue Type: New Feature Components: CLI, CordovaCommon Reporter: David Hooey Priority: Minor It would be nice to be able to build a Chrome Packaged App from an existing Cordova project. Something like the following: ``` cordova platform add chrome cordova build chrome ``` -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Created] (CB-11154) Why timezone is not IANA ?
Simon Constans created CB-11154: --- Summary: Why timezone is not IANA ? Key: CB-11154 URL: https://issues.apache.org/jira/browse/CB-11154 Project: Apache Cordova Issue Type: Bug Components: Plugin Globalization Reporter: Simon Constans Hello, I don't understand why you don't return correctly the IANA timezone name? I think it's a simple information. I change my plugin for this repository: https://github.com/StyrLabs/cordova-plugin-globalization You can see commit: - for Android: https://github.com/StyrLabs/cordova-plugin-globalization/commit/b251053cc7b0fa0b055544437c8a960afedab530 - for iPhone: https://github.com/StyrLabs/cordova-plugin-globalization/commit/1a67a5a94e45ecc037b3226f96ed3d2fab114c57 Can you integrate it? Simon -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-11150) CI Error - Windows Platform - Could not find XHR config file
[
https://issues.apache.org/jira/browse/CB-11150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15258081#comment-15258081
]
ASF GitHub Bot commented on CB-11150:
-
GitHub user daserge opened a pull request:
https://github.com/apache/cordova-windows/pull/169
CB-11150 CI Error - Windows Platform - Could not find XHR config file
Changes config.xml path to absolute
[Jira issue](https://issues.apache.org/jira/browse/CB-11150)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/MSOpenTech/cordova-windows CB-11150
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cordova-windows/pull/169.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #169
commit 3da74166f67e439d09c5c5de48af603287207b84
Author: daserge
Date: 2016-04-26T10:23:49Z
CB-11150 CI Error - Windows Platform - Could not find XHR config file
Changes config.xml path to absolute
> CI Error - Windows Platform - Could not find XHR config file
> -
>
> Key: CB-11150
> URL: https://issues.apache.org/jira/browse/CB-11150
> Project: Apache Cordova
> Issue Type: Bug
> Components: Windows
>Reporter: Sarangan Rajamanickam
>Assignee: Sergey Shakhnazarov
>Priority: Critical
> Labels: found-by-ci
>
> The CI builds for Windows Phone 8.1 and Windows Store 8.1 platforms are
> failing consistently. Link: https://ci.apache.org/waterfall?category=cordova
> On analysis, the failure began with this commit:
> 1.
> https://github.com/apache/cordova-windows/commit/d6988f5c863ec3ba5cde33a678a4b93badc64395
> 2. https://ci.apache.org/builders/cordova-windows-store8.1/builds/2218
> Assigning this issue to Sergey
> Error:
> Channel: Microsoft-Windows-AppHost/Admin
> Time Created: 2016-04-22T23:23:04.064399500Z
> Process ID:7476
> Document File: /www/cdvtests/index.html
> Display Name: mobilespec
> Error Description: "[Windows][cordova.js][readConfig] Could not XHR
> config.xml: {\"description\":\"The system cannot locate the resource
> specified.\\r\\n\",\"number\":-2146697211,\"stack\":\"Error: The system
> cannot locate the resource specified.\\r\\n\\n at readConfig
> (ms-appx://org.apache.mobilespec/www/cordova.js:870:9)\\n at init
> (ms-appx://org.apache.mobilespec/www/cordova.js:1517:25)\\n at Promise_ctor
> (ms-appx://microsoft.winjs.2.0/js/base.js:2025:17)\\n at makePromise
> (ms-appx://org.apache.mobilespec/www/cordova.js:1516:21)\\n at
> activationHandler (ms-appx://org.apache.mobilespec/www/cordova.js:1525:17)\\n
> at dispatchOne (ms-appx://microsoft.winjs.2.0/js/base.js:9416:25)\\n at
> dispatchEvent (ms-appx://microsoft.winjs.2.0/js/base.js:9415:21)\\n at
> drainOneEvent (ms-appx://microsoft.winjs.2.0/js/base.js:9469:13)\\n at
> drainQueue (ms-appx://microsoft.winjs.2.0/js/base.js:9486:9)\\n at
> Anonymous function (ms-appx://microsoft.winjs.2.0/js/base.js:2952:17)\"}"
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-9528) create new core plugin to control screen orientation
[ https://issues.apache.org/jira/browse/CB-9528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15258050#comment-15258050 ] Tony Homer commented on CB-9528: The author of https://github.com/gbenvenuti/cordova-plugin-screen-orientation and I have been discussing the possibility of migrating it to a core plugin. When we work out the details, I will send a message to the dev mailing list to formally propose a plan for this. > create new core plugin to control screen orientation > > > Key: CB-9528 > URL: https://issues.apache.org/jira/browse/CB-9528 > Project: Apache Cordova > Issue Type: Improvement >Reporter: Tony Homer >Assignee: Tony Homer > > Create a new core Cordova plugin that enables the user to dynamically control > the orientation of their app. > Tentatively base interface on [the screen-orientation spec| > http://www.w3.org/TR/screen-orientation/]. > There is a precedent for this behavior being supported as part of Cordova. > Previously iOS supported a non-standard approach to controlling the > orientation dynamically (see last entry in [this section of the 5.1.1 > docs|http://cordova.apache.org/docs/en/5.1.1/config_ref_index.md.html#The%20config.xml%20File_multi_platform_preferences]). > Recent platform changes made the iOS-specific approach untenable, but it's > removal prompted a discussion about enabling this as a cross-platform feature > via a new core plugin. > See related discussion in CB-8047. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-9528) create new core plugin to control screen orientation
[ https://issues.apache.org/jira/browse/CB-9528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15258030#comment-15258030 ] Olivier Allouch commented on CB-9528: - No pb. Still, I would feel safer if this plugin was made core. > create new core plugin to control screen orientation > > > Key: CB-9528 > URL: https://issues.apache.org/jira/browse/CB-9528 > Project: Apache Cordova > Issue Type: Improvement >Reporter: Tony Homer >Assignee: Tony Homer > > Create a new core Cordova plugin that enables the user to dynamically control > the orientation of their app. > Tentatively base interface on [the screen-orientation spec| > http://www.w3.org/TR/screen-orientation/]. > There is a precedent for this behavior being supported as part of Cordova. > Previously iOS supported a non-standard approach to controlling the > orientation dynamically (see last entry in [this section of the 5.1.1 > docs|http://cordova.apache.org/docs/en/5.1.1/config_ref_index.md.html#The%20config.xml%20File_multi_platform_preferences]). > Recent platform changes made the iOS-specific approach untenable, but it's > removal prompted a discussion about enabling this as a cross-platform feature > via a new core plugin. > See related discussion in CB-8047. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-9528) create new core plugin to control screen orientation
[ https://issues.apache.org/jira/browse/CB-9528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15258009#comment-15258009 ] Tony Homer commented on CB-9528: Yes! Sorry I missed your comment before now :( > create new core plugin to control screen orientation > > > Key: CB-9528 > URL: https://issues.apache.org/jira/browse/CB-9528 > Project: Apache Cordova > Issue Type: Improvement >Reporter: Tony Homer >Assignee: Tony Homer > > Create a new core Cordova plugin that enables the user to dynamically control > the orientation of their app. > Tentatively base interface on [the screen-orientation spec| > http://www.w3.org/TR/screen-orientation/]. > There is a precedent for this behavior being supported as part of Cordova. > Previously iOS supported a non-standard approach to controlling the > orientation dynamically (see last entry in [this section of the 5.1.1 > docs|http://cordova.apache.org/docs/en/5.1.1/config_ref_index.md.html#The%20config.xml%20File_multi_platform_preferences]). > Recent platform changes made the iOS-specific approach untenable, but it's > removal prompted a discussion about enabling this as a cross-platform feature > via a new core plugin. > See related discussion in CB-8047. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-9528) create new core plugin to control screen orientation
[ https://issues.apache.org/jira/browse/CB-9528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15258008#comment-15258008 ] Tony Homer commented on CB-9528: I totally missed that comment :( Thanks for pointing it out :) > create new core plugin to control screen orientation > > > Key: CB-9528 > URL: https://issues.apache.org/jira/browse/CB-9528 > Project: Apache Cordova > Issue Type: Improvement >Reporter: Tony Homer >Assignee: Tony Homer > > Create a new core Cordova plugin that enables the user to dynamically control > the orientation of their app. > Tentatively base interface on [the screen-orientation spec| > http://www.w3.org/TR/screen-orientation/]. > There is a precedent for this behavior being supported as part of Cordova. > Previously iOS supported a non-standard approach to controlling the > orientation dynamically (see last entry in [this section of the 5.1.1 > docs|http://cordova.apache.org/docs/en/5.1.1/config_ref_index.md.html#The%20config.xml%20File_multi_platform_preferences]). > Recent platform changes made the iOS-specific approach untenable, but it's > removal prompted a discussion about enabling this as a cross-platform feature > via a new core plugin. > See related discussion in CB-8047. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-9528) create new core plugin to control screen orientation
[ https://issues.apache.org/jira/browse/CB-9528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15257933#comment-15257933 ] Olivier Allouch commented on CB-9528: - You mean, like the one from the first comment from January ? :) Anyway, that's good news. Thx > create new core plugin to control screen orientation > > > Key: CB-9528 > URL: https://issues.apache.org/jira/browse/CB-9528 > Project: Apache Cordova > Issue Type: Improvement >Reporter: Tony Homer >Assignee: Tony Homer > > Create a new core Cordova plugin that enables the user to dynamically control > the orientation of their app. > Tentatively base interface on [the screen-orientation spec| > http://www.w3.org/TR/screen-orientation/]. > There is a precedent for this behavior being supported as part of Cordova. > Previously iOS supported a non-standard approach to controlling the > orientation dynamically (see last entry in [this section of the 5.1.1 > docs|http://cordova.apache.org/docs/en/5.1.1/config_ref_index.md.html#The%20config.xml%20File_multi_platform_preferences]). > Recent platform changes made the iOS-specific approach untenable, but it's > removal prompted a discussion about enabling this as a cross-platform feature > via a new core plugin. > See related discussion in CB-8047. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-11010) Unexpected EOF while finding contacts in iPhone 6s
[ https://issues.apache.org/jira/browse/CB-11010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15257744#comment-15257744 ] Liventsev Andrey commented on CB-11010: --- I got same problem > Unexpected EOF while finding contacts in iPhone 6s > -- > > Key: CB-11010 > URL: https://issues.apache.org/jira/browse/CB-11010 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin Contacts >Affects Versions: 2.0.0 > Environment: iOS 9.2.1, iOS 9.3 in iPhone 6s >Reporter: Gowtham > Labels: iOS, mustfix, triaged > > I tried accessing the contacts using contacts plugin v2.0.1 with the > following code > var options = new ContactFindOptions(); > options.filter = ""; > options.multiple = true; > var fields = ["displayName","phoneNumbers"]; > > navigator.contacts.find(fields, gotContacts, errorHandler, options); > This throws me an SyntaxError: Unexpected EOF in iPhone 6s models. > I tested the same in iPhone 5s and iPhone 6, this works fine. Also it works > fine in iPhone 6s Simulator. > I tested in three iPhone 6s phones where the iOS is 9.3 for two phones and > 9.2.1 for one. > All three phones have contacts more than 400. > All three returned me the same error. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Closed] (CB-11147) Camera plugin Appium tests names should be more descriptive
[
https://issues.apache.org/jira/browse/CB-11147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Sorokin closed CB-11147.
--
Resolution: Fixed
> Camera plugin Appium tests names should be more descriptive
> ---
>
> Key: CB-11147
> URL: https://issues.apache.org/jira/browse/CB-11147
> Project: Apache Cordova
> Issue Type: Test
> Components: Appium, Plugin Camera
>Reporter: Alexander Sorokin
>Assignee: Alexander Sorokin
>
> Right now the tests are named like this:
> {{camera.ui.spec.5.22 Combining options}}
> which makes it really hard to understand which options of camera.getPicture()
> function were used.
> Suggested improvement is to add options description to the spec like this:
> {{camera.ui.spec.5.22 Combining options. sourceType: CAMERA, destinationType:
> FILE_URI, encodingType: PNG, allowEdit: true, correctOrientation: false}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Closed] (CB-11140) Medic Appium runner should patch app's CSP tag to allow executeAsync
[ https://issues.apache.org/jira/browse/CB-11140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Sorokin closed CB-11140. -- Resolution: Fixed > Medic Appium runner should patch app's CSP tag to allow executeAsync > > > Key: CB-11140 > URL: https://issues.apache.org/jira/browse/CB-11140 > Project: Apache Cordova > Issue Type: Task > Components: Appium, Medic >Reporter: Alexander Sorokin >Assignee: Alexander Sorokin > -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-11140) Medic Appium runner should patch app's CSP tag to allow executeAsync
[ https://issues.apache.org/jira/browse/CB-11140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15257708#comment-15257708 ] ASF GitHub Bot commented on CB-11140: - Github user asfgit closed the pull request at: https://github.com/apache/cordova-medic/pull/99 > Medic Appium runner should patch app's CSP tag to allow executeAsync > > > Key: CB-11140 > URL: https://issues.apache.org/jira/browse/CB-11140 > Project: Apache Cordova > Issue Type: Task > Components: Appium, Medic >Reporter: Alexander Sorokin >Assignee: Alexander Sorokin > -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-11140) Medic Appium runner should patch app's CSP tag to allow executeAsync
[ https://issues.apache.org/jira/browse/CB-11140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15257706#comment-15257706 ] ASF subversion and git services commented on CB-11140: -- Commit 2dcba6aa42c17310b7c4d43924fbed9c07d01239 in cordova-medic's branch refs/heads/master from [~alsorokin] [ https://git-wip-us.apache.org/repos/asf?p=cordova-medic.git;h=2dcba6a ] CB-11140 Patch CSP tag to allow Appium to execute async scripts > Medic Appium runner should patch app's CSP tag to allow executeAsync > > > Key: CB-11140 > URL: https://issues.apache.org/jira/browse/CB-11140 > Project: Apache Cordova > Issue Type: Task > Components: Appium, Medic >Reporter: Alexander Sorokin >Assignee: Alexander Sorokin > -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-11147) Camera plugin Appium tests names should be more descriptive
[
https://issues.apache.org/jira/browse/CB-11147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15257703#comment-15257703
]
ASF subversion and git services commented on CB-11147:
--
Commit 68e18a97d15835049fbfcb7b4767edb67d4c9fb3 in cordova-plugin-camera's
branch refs/heads/master from [~alsorokin]
[ https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-camera.git;h=68e18a9
]
CB-11147 Appium tests: generate descriptive spec names
> Camera plugin Appium tests names should be more descriptive
> ---
>
> Key: CB-11147
> URL: https://issues.apache.org/jira/browse/CB-11147
> Project: Apache Cordova
> Issue Type: Test
> Components: Appium, Plugin Camera
>Reporter: Alexander Sorokin
>Assignee: Alexander Sorokin
>
> Right now the tests are named like this:
> {{camera.ui.spec.5.22 Combining options}}
> which makes it really hard to understand which options of camera.getPicture()
> function were used.
> Suggested improvement is to add options description to the spec like this:
> {{camera.ui.spec.5.22 Combining options. sourceType: CAMERA, destinationType:
> FILE_URI, encodingType: PNG, allowEdit: true, correctOrientation: false}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
