[jira] [Commented] (CB-14081) Android level support not being followed
[ https://issues.apache.org/jira/browse/CB-14081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16467482#comment-16467482 ] Joe Bowser commented on CB-14081: - Build Tools Versions are not API versions. This should be closed as "Not a problem" > Android level support not being followed > > > Key: CB-14081 > URL: https://issues.apache.org/jira/browse/CB-14081 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-android, cordova-cli >Affects Versions: 6.4.0 > Environment: OS: macOS 10.12.6 > Cordova version: 8.0.0 > Cordova android: 6.4.0 > Node version: 6.9.0 > Npm version: 3.10.8 >Reporter: Victor Hugo >Assignee: Joe Bowser >Priority: Major > > Hello everyone. > *Expected behaviour:* > According to this [cordova > guide|https://cordova.apache.org/docs/en/latest/guide/platforms/android/] , > cordova-android versions 6.x.x does support 16-26 _Android Api Level_. So it > is supposed to build a cordova project with api level 20, if specified this > way. > *Actual behaviour:* > Even though, I'm not being able to build a cordova project specifying my > cdvBuildToolsVersion to 20 at build time. > Gradle build tasks warns me like this: > "_WARNING: The specified Android SDK Build Tools version (20.0.0) is > ignored, as it is below the minimum supported version (26.0.2) for Android > Gradle Plugin 3.0.0._ > _Android SDK Build Tools 26.0.2 will be used._" > > *Steps to reproduce:* > Execute: > > $ export ORG_GRADLE_PROJECT_cdvBuildToolsVersion=20 > _$ cordova build android_ > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-14036) source-file or resource-file png in plugin.xml breaks subsequent plugins for cordova-android 7
[
https://issues.apache.org/jira/browse/CB-14036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16441622#comment-16441622
]
Joe Bowser commented on CB-14036:
-
Did you test this on a new project? If you just removed the plugin, the
directory triggering the project check still remains and it'll still not work
correctly.
> source-file or resource-file png in plugin.xml breaks subsequent plugins for
> cordova-android 7
> --
>
> Key: CB-14036
> URL: https://issues.apache.org/jira/browse/CB-14036
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-android
>Affects Versions: 7.0.0
> Environment: This is the blank project that I build together with
> environment ( pasted below for reference ) -
> [https://github.com/Liam-Ryan/ionic-cordova-android-7]
>
> After setting up this project running ionic cordova plugin add
> cordova-plugin-fingerprint-aio && cordova platform add android will reproduce
> the issue.
>
> {{cli packages: @ionic/cli-utils : 1.19.2 }}
> {{ionic (Ionic CLI) : 3.20.0 }}
> {{global packages: cordova (Cordova CLI) : 8.0.0 }}
> {{local packages: @ionic/app-scripts : 3.1.8 }}
> {{Cordova Platforms : android 7.0.0 }}
> {{Ionic Framework : ionic-angular 3.9.2 }}
> {{System: Android SDK Tools : 26.1.1 Node : v8.10.0 }}
> {{npm : 5.6.0 }}
> {{OS : Windows 7 Cordova 8.0.0}}
>
>Reporter: Liam Ryan
>Assignee: Joe Bowser
>Priority: Major
> Attachments: plugin.xml
>
>
> Plugin.xml for cordova-plugin-fingerprint-aio contains tags like the
> following. I have also tried changing to resource-file. When these tags are
> present in either form then subsequent plugins seem to revert to the old
> cordova-android directory structure which causes their installation to fail
> during cordova platform add android and also hides the cause of the issue
> since there are no errors for the plugin containing these tags
> {{ target-dir="res/drawable-hdpi"/>}}
>
> {{The same tag for copying xml files works with no issues and no effect on
> subsequent plugins}}
>
> {{Example of error - Failed to install 'cordova-plugin-splashscreen': Error:
> ENOENT: no such file or directory, open
> 'E:\Development\Angular2\Cordova7\cordova7\platforms\android\AndroidManifest.xml'}}
>
> {{I'm building with latest ionic blank project ( see environment ) and the
> plugin in question is cordova-plugin-fingerprint-aio. I'm aware that this
> project is not yet cordova-android 7 compliant, I'm trying to create a pull
> request for same }}
>
> [https://github.com/NiklasMerz/cordova-plugin-fingerprint-aio/pull/94]
>
> This is the blank project that I build together with environment ( pasted
> below for reference ) - [https://github.com/Liam-Ryan/ionic-cordova-android-7]
>
> After setting up this project running ionic cordova plugin add
> cordova-plugin-fingerprint-aio && cordova platform add android will reproduce
> the issue.
>
> {{cli packages: @ionic/cli-utils : 1.19.2}}
> {{ionic (Ionic CLI) : 3.20.0}}
> {{global packages: cordova (Cordova CLI) : 8.0.0}}
> {{local packages: @ionic/app-scripts : 3.1.8}}
> {{Cordova Platforms : android 7.0.0}}
> {{Ionic Framework : ionic-angular 3.9.2}}
> {{System: Android SDK Tools : 26.1.1 Node : v8.10.0}}
> {{npm : 5.6.0}}
> {{OS : Windows 7 Cordova 8.0.0}}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-14036) source-file or resource-file png in plugin.xml breaks subsequent plugins for cordova-android 7
[
https://issues.apache.org/jira/browse/CB-14036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Bowser resolved CB-14036.
-
Resolution: Won't Fix
The problem is that you're using source-file for a resource, and this is
triggering the project check. Please delete the res directory and use
resource-file for resources instead of the source-file. For an example of how
to do this, you can look at the InAppBrowser plugin:
https://github.com/apache/cordova-plugin-inappbrowser
> source-file or resource-file png in plugin.xml breaks subsequent plugins for
> cordova-android 7
> --
>
> Key: CB-14036
> URL: https://issues.apache.org/jira/browse/CB-14036
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-android
>Affects Versions: 7.0.0
> Environment: This is the blank project that I build together with
> environment ( pasted below for reference ) -
> [https://github.com/Liam-Ryan/ionic-cordova-android-7]
>
> After setting up this project running ionic cordova plugin add
> cordova-plugin-fingerprint-aio && cordova platform add android will reproduce
> the issue.
>
> {{cli packages: @ionic/cli-utils : 1.19.2 }}
> {{ionic (Ionic CLI) : 3.20.0 }}
> {{global packages: cordova (Cordova CLI) : 8.0.0 }}
> {{local packages: @ionic/app-scripts : 3.1.8 }}
> {{Cordova Platforms : android 7.0.0 }}
> {{Ionic Framework : ionic-angular 3.9.2 }}
> {{System: Android SDK Tools : 26.1.1 Node : v8.10.0 }}
> {{npm : 5.6.0 }}
> {{OS : Windows 7 Cordova 8.0.0}}
>
>Reporter: Liam Ryan
>Assignee: Joe Bowser
>Priority: Major
>
> Plugin.xml for cordova-plugin-fingerprint-aio contains tags like the
> following. I have also tried changing to resource-file. When these tags are
> present in either form then subsequent plugins seem to revert to the old
> cordova-android directory structure which causes their installation to fail
> during cordova platform add android and also hides the cause of the issue
> since there are no errors for the plugin containing these tags
> {{ target-dir="res/drawable-hdpi"/>}}
>
> {{The same tag for copying xml files works with no issues and no effect on
> subsequent plugins}}
>
> {{Example of error - Failed to install 'cordova-plugin-splashscreen': Error:
> ENOENT: no such file or directory, open
> 'E:\Development\Angular2\Cordova7\cordova7\platforms\android\AndroidManifest.xml'}}
>
> {{I'm building with latest ionic blank project ( see environment ) and the
> plugin in question is cordova-plugin-fingerprint-aio. I'm aware that this
> project is not yet cordova-android 7 compliant, I'm trying to create a pull
> request for same }}
>
> [https://github.com/NiklasMerz/cordova-plugin-fingerprint-aio/pull/94]
>
> This is the blank project that I build together with environment ( pasted
> below for reference ) - [https://github.com/Liam-Ryan/ionic-cordova-android-7]
>
> After setting up this project running ionic cordova plugin add
> cordova-plugin-fingerprint-aio && cordova platform add android will reproduce
> the issue.
>
> {{cli packages: @ionic/cli-utils : 1.19.2}}
> {{ionic (Ionic CLI) : 3.20.0}}
> {{global packages: cordova (Cordova CLI) : 8.0.0}}
> {{local packages: @ionic/app-scripts : 3.1.8}}
> {{Cordova Platforms : android 7.0.0}}
> {{Ionic Framework : ionic-angular 3.9.2}}
> {{System: Android SDK Tools : 26.1.1 Node : v8.10.0}}
> {{npm : 5.6.0}}
> {{OS : Windows 7 Cordova 8.0.0}}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-14035) Android app crashed with "Connection InterfaceProviderSpec prevented service: content_renderer from binding interfac e: blink::mojom::BudgetService exposed by: content_bro
[ https://issues.apache.org/jira/browse/CB-14035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser updated CB-14035: Security: (was: Non-Public) Also, this isn't our code, and this isn't a security issue, so I'm going to open this one up. > Android app crashed with "Connection InterfaceProviderSpec prevented > service: content_renderer from binding interfac e: > blink::mojom::BudgetService exposed by: content_browser" > - > > Key: CB-14035 > URL: https://issues.apache.org/jira/browse/CB-14035 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-android >Affects Versions: 5.0.0 >Reporter: Sridhar Boganathan >Assignee: Joe Bowser >Priority: Major > Labels: ERROR:BudgetService.cpp > > Android application crashed due to below error > 03-24 13:34:42.182 E/chromium( 4831): [ERROR:service_manager.cc(156)] > Connection > InterfaceProviderSpec prevented service: content_renderer from binding > interfac > e: blink::mojom::BudgetService exposed by: content_browser > ... > 03-24 13:34:42.218 E/chromium( 4831): [ERROR:BudgetService.cpp(167)] Unable > to c > onnect to the Mojo BudgetService. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-13541) Error: Path must be a string. Received undefined
[
https://issues.apache.org/jira/browse/CB-13541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Bowser updated CB-13541:
Priority: Major (was: Trivial)
Not sure who set this to Trivial, it's not trivial because I don't know where
undefined comes from or how to reproduce this. I'm going to leave it open and
up the priority.
> Error: Path must be a string. Received undefined
>
>
> Key: CB-13541
> URL: https://issues.apache.org/jira/browse/CB-13541
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-android
> Environment: Kubuntu 17.04 64 bit, Gradle 3.2, Cordova Android 6.3.0,
> Cordova cli-6.3.0, Android Studio 3.0.0
>Reporter: Teguh Teknisi
>Assignee: Joe Bowser
>Priority: Major
> Labels: newbie
>
> When i try to cordiva build android, it will fail, with error:
> Error: Path must be a string. Received undefined
> I have to delete platforms/android/android.json
> to make the cordova android build to success.
> Here the error log:
> {code:java}
> sukanime@Asus-X201EV:~/AndroidStudioProjects/SaklarWiFi$ cordova build android
> Error: Path must be a string. Received undefined
> sukanime@Asus-X201EV:~/AndroidStudioProjects/SaklarWiFi$ rm
> platforms/android/android.json
> sukanime@Asus-X201EV:~/AndroidStudioProjects/SaklarWiFi$ cordova build android
> ANDROID_HOME=/home/sukanime/Android/Sdk
> JAVA_HOME=/usr/lib/jvm/java-8-oracle
> Subproject Path: CordovaLib
> The Task.leftShift(Closure) method has been deprecated and is scheduled to be
> removed in Gradle 5.0. Please use Task.doLast(Action) instead.
> at
> build_asz7izgfnstnapj05rr74ilff.run(/home/sukanime/AndroidStudioProjects/SaklarWiFi/platforms/android/build.gradle:141)
> The JavaCompile.setDependencyCacheDir() method has been deprecated and is
> scheduled to be removed in Gradle 4.0.
> Incremental java compilation is an incubating feature.
> The TaskInputs.source(Object) method has been deprecated and is scheduled to
> be removed in Gradle 4.0. Please use TaskInputs.file(Object).skipWhenEmpty()
> instead.
> :clean
> :CordovaLib:clean
> BUILD SUCCESSFUL
> Total time: 3.13 secs
> Subproject Path: CordovaLib
> Subproject Path: CordovaLib
> Running command:
> /home/sukanime/AndroidStudioProjects/SaklarWiFi/hooks/after_prepare/030_resource_files.js
> /home/sukanime/AndroidStudioProjects/SaklarWiFi
> ANDROID_HOME=/home/sukanime/Android/Sdk
> JAVA_HOME=/usr/lib/jvm/java-8-oracle
> Subproject Path: CordovaLib
> The Task.leftShift(Closure) method has been deprecated and is scheduled to be
> removed in Gradle 5.0. Please use Task.doLast(Action) instead.
> at
> build_asz7izgfnstnapj05rr74ilff.run(/home/sukanime/AndroidStudioProjects/SaklarWiFi/platforms/android/build.gradle:141)
> The JavaCompile.setDependencyCacheDir() method has been deprecated and is
> scheduled to be removed in Gradle 4.0.
> Incremental java compilation is an incubating feature.
> The TaskInputs.source(Object) method has been deprecated and is scheduled to
> be removed in Gradle 4.0. Please use TaskInputs.file(Object).skipWhenEmpty()
> instead.
> :preBuild UP-TO-DATE
> :preDebugBuild UP-TO-DATE
> :checkDebugManifest
> :preReleaseBuild UP-TO-DATE
> :CordovaLib:preBuild UP-TO-DATE
> :CordovaLib:preDebugBuild UP-TO-DATE
> :CordovaLib:checkDebugManifest
> :CordovaLib:prepareDebugDependencies
> :CordovaLib:compileDebugAidl
> :CordovaLib:compileDebugNdk UP-TO-DATE
> :CordovaLib:compileLint
> :CordovaLib:copyDebugLint UP-TO-DATE
> :CordovaLib:mergeDebugShaders
> :CordovaLib:compileDebugShaders
> :CordovaLib:generateDebugAssets
> :CordovaLib:mergeDebugAssets
> :CordovaLib:mergeDebugProguardFiles UP-TO-DATE
> :CordovaLib:packageDebugRenderscript UP-TO-DATE
> :CordovaLib:compileDebugRenderscript
> :CordovaLib:generateDebugResValues
> :CordovaLib:generateDebugResources
> :CordovaLib:packageDebugResources
> :CordovaLib:processDebugManifest
> :CordovaLib:generateDebugBuildConfig
> :CordovaLib:processDebugResources
> :CordovaLib:generateDebugSources
> :CordovaLib:incrementalDebugJavaCompilationSafeguard
> :CordovaLib:compileDebugJavaWithJavac
> :CordovaLib:compileDebugJavaWithJavac - is not incremental (e.g. outputs have
> changed, no previous execution, etc.).
> Note: Some input files use or override a deprecated API.
> Note: Recompile with -Xlint:deprecation for details.
> :CordovaLib:processDebugJavaRes UP-TO-DATE
> :CordovaLib:transformResourcesWithMergeJavaResForDebug
> :CordovaLib:transformClassesAndResourcesWithSyncLibJarsForDebug
> :CordovaLib:mergeDebugJniLibFolders
> :CordovaLib:transformNative_libsWithMergeJniLibsForDebug
> :CordovaLib:transformNative_libsWithSyncJniLibsForDebug
> :CordovaLib:bundleDebug
> :CordovaLib:preReleaseBuild UP-TO-DATE
> :CordovaLib:checkReleaseManifest
>
[jira] [Resolved] (CB-12914) Drop Support for Android JellyBean
[ https://issues.apache.org/jira/browse/CB-12914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser resolved CB-12914. - Resolution: Fixed Fix Version/s: (was: 7.0.0) 7.1.0 > Drop Support for Android JellyBean > -- > > Key: CB-12914 > URL: https://issues.apache.org/jira/browse/CB-12914 > Project: Apache Cordova > Issue Type: Improvement > Components: cordova-android >Reporter: Simon MacDonald >Assignee: Joe Bowser >Priority: Major > Labels: android-next > Fix For: 7.1.0 > > > In cordova-android 7.0.0 we will be dropping support for any Android API > level before 19 (Android KitKat). > We should update the default tempate to indicate the minSdkLevel is 19 and > check for any conditional code that checks for API level less than 19 and > adds any special cases. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-14022) Vibrate plugin does not work
[ https://issues.apache.org/jira/browse/CB-14022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16431359#comment-16431359 ] Joe Bowser commented on CB-14022: - Document it as a quirk, since it's a Chrome error. > Vibrate plugin does not work > > > Key: CB-14022 > URL: https://issues.apache.org/jira/browse/CB-14022 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-android >Affects Versions: cordova@7.0.0, cordova-android-7.0.0 >Reporter: Mahesh Kanniah >Assignee: Joe Bowser >Priority: Minor > Fix For: Master > > > navigator.vibrate does not work. > Used to work in earlier versions but just fails to work. > Tested on multiple devices running different android versions. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-14019) App lagging issue in android
[ https://issues.apache.org/jira/browse/CB-14019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser resolved CB-14019. - Resolution: Invalid Given that you literally just sent us Hello World, I don't have any information to tell you regarding your performance issues. There are thousands of things that can affect performance on Android from uncompressed images, using the wrong libraries, or having too many objects on the DOM at once. You would probably have better luck asking about performance or looking up performance tips on Stack Overflow, since this is to deal with reproducible bugs. Loading random HTML/CSS/JS into anything without optimizing it will produce a bad application whether you're using a PWA, Cordova or a WebView based competitor, and your best bet would be to start there w.r.t. performance. > App lagging issue in android > > > Key: CB-14019 > URL: https://issues.apache.org/jira/browse/CB-14019 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-android > Environment: I am using Windows 10 OS(64-bit) , RAM is 8GB , and > processor configurations are > core i3 6100 cpu @3.70GHz >Reporter: IDZ >Assignee: Joe Bowser >Priority: Major > Labels: newbie, performance, windows > Attachments: hello.zip > > > I am trying to make a cross platform app. I am using html5, js and css in > that app. I am facing an issue with android version of the app. App is > working fine on iOS but lagging in android. I tried some solutions but could > not find any.. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-14008) Cordova Build fails for android in Ubuntu machine
[
https://issues.apache.org/jira/browse/CB-14008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16424608#comment-16424608
]
Joe Bowser commented on CB-14008:
-
[~Keith3895] What version of Android Studio are you using?
> Cordova Build fails for android in Ubuntu machine
> -
>
> Key: CB-14008
> URL: https://issues.apache.org/jira/browse/CB-14008
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-android
>Affects Versions: cordova-android-7.0.0
> Environment: * Os: Ubuntu 16.04 LTS
> * node.js : 8.9.4
> * npm: 5.8.0
> * cordova: 8.0.0
> * android: 7.0.0
>Reporter: Keith Franklin jathanna
>Assignee: Joe Bowser
>Priority: Major
> Fix For: 8.0.0
>
>
> h6. I run the command ``cordova build `` and I get the error:
> ```
> Android Studio project detected
> ANDROID_HOME=/home/keith/Android/Sdk
> JAVA_HOME=/usr/lib/jvm/java-8-openjdk-amd64/
> studio
> Starting a Gradle Daemon, 1 incompatible Daemon could not be reused, use
> --status for details
> :wrapper
> BUILD SUCCESSFUL
> Total time: 3.704 secs
> Subproject Path: CordovaLib
> Subproject Path: app
> FAILURE: Build failed with an exception.
> * What went wrong:
> A problem occurred configuring project ':CordovaLib'.
> > Could not resolve all files for configuration ':CordovaLib:classpath'.
> > Could not find android-maven-gradle-plugin.jar
> (com.github.dcendents:android-maven-gradle-plugin:1.5).
> Searched in the following locations:
>
> [https://jcenter.bintray.com/com/github/dcendents/android-maven-gradle-plugin/1.5/android-maven-gradle-plugin-1.5.jar]
> * Try:
> Run with --stacktrace option to get the stack trace. Run with --info or
> --debug option to get more log output.
> * Get more help at [https://help.gradle.org|https://help.gradle.org/]
> BUILD FAILED in 0s
> (node:11046) UnhandledPromiseRejectionWarning: Unhandled promise rejection
> (rejection id: 1): Error:
> /home/keith/Documents/personal/financeTracker/mobileApp/platforms/android/gradlew:
> Command failed with exit code 1 Error output:
> FAILURE: Build failed with an exception.
> * What went wrong:
> A problem occurred configuring project ':CordovaLib'.
> > Could not resolve all files for configuration ':CordovaLib:classpath'.
> > Could not find android-maven-gradle-plugin.jar
> (com.github.dcendents:android-maven-gradle-plugin:1.5).
> Searched in the following locations:
>
> [https://jcenter.bintray.com/com/github/dcendents/android-maven-gradle-plugin/1.5/android-maven-gradle-plugin-1.5.jar]
> * Try:
> Run with --stacktrace option to get the stack trace. Run with --info or
> --debug option to get more log output.
> * Get more help at [https://help.gradle.org|https://help.gradle.org/]
> BUILD FAILED in 0s
> (node:11046) [DEP0018] DeprecationWarning: Unhandled promise rejections are
> deprecated. In the future, promise rejections that are not handled will
> terminate the Node.js process with a non-zero exit code.
> ```
>
> h5. I make the change in the ``platforms/android/CordovaLib/build.gradle``
>
> ```
> buildscript {
> repositories {
> jcenter()
> maven {
> // change "https://maven.google.com;
> url "https://plugins.gradle.org/m2/;
> }
> }
> dependencies {
> // classpath 'com.android.tools.build:gradle:3.0.1'
> // change 1.5 to 2.0
> classpath 'com.github.dcendents:android-maven-gradle-plugin:2.0'
> classpath 'com.jfrog.bintray.gradle:gradle-bintray-plugin:1.7.3'
> }
> }
> ```
> and the build works.
> ```
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-14009) Build fails on Xcode 9.3
[
https://issues.apache.org/jira/browse/CB-14009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16422835#comment-16422835
]
Joe Bowser commented on CB-14009:
-
I get this error when I create a project as well. I just go into XCode and set
up my Automatic provisioning and it works, and then it works on the Command
Line as well. For some reason, we're not configuring the signing correctly
when generating the project.
> Build fails on Xcode 9.3
>
>
> Key: CB-14009
> URL: https://issues.apache.org/jira/browse/CB-14009
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-ios
>Reporter: Doug Davies
>Assignee: Suraj Pindoria
>Priority: Major
>
> Seeing this after I update to XCode 9.3 and build through cli
> Error Domain=IDEProfileLocatorErrorDomain Code=1 “No profiles for
> ‘org.oclc.digby’ were found” UserInfo=\{NSLocalizedDescription=No profiles
> for ‘org.oclc.digby’ were found, NSLocalizedRecoverySuggestion=Xcode couldn’t
> find any iOS Ad Hoc provisioning profiles matching ‘org.oclc.digby’.
> Automatic signing is disabled and unable to generate a profile. To enable
> automatic signing, pass -allowProvisioningUpdates to xcodebuild.}
> When I bring the project up in XCode the signing is correct and not
> complaining.
> I tried adding
> “buildFlag”: [“-allowProvisioningUpdates”]
> to build.json and still not working
> Interestingly… I went into xcode and did an archive/export from there… now
> the cli works… it must set something that it needs
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-14008) Cordova Build fails for android in Ubuntu machine
[
https://issues.apache.org/jira/browse/CB-14008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Bowser updated CB-14008:
Priority: Major (was: Critical)
That's strange that the official Google Maven repository isn't working for you
and that you have to use a downgraded version of Gradle. What version of
cordova-android are you currently using with cordova 8.0.0?
> Cordova Build fails for android in Ubuntu machine
> -
>
> Key: CB-14008
> URL: https://issues.apache.org/jira/browse/CB-14008
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-android
>Affects Versions: cordova-android-7.0.0
> Environment: * Os: Ubuntu 16.04 LTS
> * node.js : 8.9.4
> * npm: 5.8.0
> * cordova: 8.0.0
> * android: 7.0.0
>Reporter: Keith Franklin jathanna
>Assignee: Joe Bowser
>Priority: Major
> Fix For: 8.0.0
>
>
> h6. I run the command ``cordova build `` and I get the error:
> ```
> Android Studio project detected
> ANDROID_HOME=/home/keith/Android/Sdk
> JAVA_HOME=/usr/lib/jvm/java-8-openjdk-amd64/
> studio
> Starting a Gradle Daemon, 1 incompatible Daemon could not be reused, use
> --status for details
> :wrapper
> BUILD SUCCESSFUL
> Total time: 3.704 secs
> Subproject Path: CordovaLib
> Subproject Path: app
> FAILURE: Build failed with an exception.
> * What went wrong:
> A problem occurred configuring project ':CordovaLib'.
> > Could not resolve all files for configuration ':CordovaLib:classpath'.
> > Could not find android-maven-gradle-plugin.jar
> (com.github.dcendents:android-maven-gradle-plugin:1.5).
> Searched in the following locations:
>
> [https://jcenter.bintray.com/com/github/dcendents/android-maven-gradle-plugin/1.5/android-maven-gradle-plugin-1.5.jar]
> * Try:
> Run with --stacktrace option to get the stack trace. Run with --info or
> --debug option to get more log output.
> * Get more help at [https://help.gradle.org|https://help.gradle.org/]
> BUILD FAILED in 0s
> (node:11046) UnhandledPromiseRejectionWarning: Unhandled promise rejection
> (rejection id: 1): Error:
> /home/keith/Documents/personal/financeTracker/mobileApp/platforms/android/gradlew:
> Command failed with exit code 1 Error output:
> FAILURE: Build failed with an exception.
> * What went wrong:
> A problem occurred configuring project ':CordovaLib'.
> > Could not resolve all files for configuration ':CordovaLib:classpath'.
> > Could not find android-maven-gradle-plugin.jar
> (com.github.dcendents:android-maven-gradle-plugin:1.5).
> Searched in the following locations:
>
> [https://jcenter.bintray.com/com/github/dcendents/android-maven-gradle-plugin/1.5/android-maven-gradle-plugin-1.5.jar]
> * Try:
> Run with --stacktrace option to get the stack trace. Run with --info or
> --debug option to get more log output.
> * Get more help at [https://help.gradle.org|https://help.gradle.org/]
> BUILD FAILED in 0s
> (node:11046) [DEP0018] DeprecationWarning: Unhandled promise rejections are
> deprecated. In the future, promise rejections that are not handled will
> terminate the Node.js process with a non-zero exit code.
> ```
>
> h5. I make the change in the ``platforms/android/CordovaLib/build.gradle``
>
> ```
> buildscript {
> repositories {
> jcenter()
> maven {
> // change "https://maven.google.com;
> url "https://plugins.gradle.org/m2/;
> }
> }
> dependencies {
> // classpath 'com.android.tools.build:gradle:3.0.1'
> // change 1.5 to 2.0
> classpath 'com.github.dcendents:android-maven-gradle-plugin:2.0'
> classpath 'com.jfrog.bintray.gradle:gradle-bintray-plugin:1.7.3'
> }
> }
> ```
> and the build works.
> ```
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-13830) Cordova-Android@7.0.0 fails to add a plugin previously removed
[
https://issues.apache.org/jira/browse/CB-13830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Bowser resolved CB-13830.
-
Resolution: Fixed
> Cordova-Android@7.0.0 fails to add a plugin previously removed
> --
>
> Key: CB-13830
> URL: https://issues.apache.org/jira/browse/CB-13830
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-android
>Affects Versions: cordova-android-7.0.0
> Environment: macOS 10.12.6
> node 9.4.0
> Cordova CLI 8.0.0
>
>Reporter: Enrico Giordani
>Assignee: Joe Bowser
>Priority: Major
>
> Removing a plugin and than adding it again, causes an error:
> {code}
> $ cordova create testapp
> $ cd testapp
> $ cordova platform add android
> Using cordova-fetch for cordova-android@~7.0.0
> Adding android project...
> Creating Cordova project for the Android platform:
> Path: platforms/android
> Package: io.cordova.hellocordova
> Name: HelloCordova
> Activity: MainActivity
> Android target: android-26
> Subproject Path: CordovaLib
> Subproject Path: app
> Android project created with cordova-android@7.0.0
> Android Studio project detected
> Android Studio project detected
> Discovered plugin "cordova-plugin-whitelist" in config.xml. Adding it to the
> project
> Installing "cordova-plugin-whitelist" for android
> This plugin is only applicable for versions of cordova-android greater than
> 4.0. If you have a previous platform version, you do *not* need this plugin
> since the whitelist will be built in.
>
> Adding cordova-plugin-whitelist to package.json
> Saved plugin info for "cordova-plugin-whitelist" to config.xml
> --save flag or autosave detected
> Saving android@~7.0.0 into config.xml file ...
> {code}
> {code}
> $ cordova plugin add cordova-plugin-camera
> Installing "cordova-plugin-camera" for android
> Android Studio project detected
> Subproject Path: CordovaLib
> Subproject Path: app
> Adding cordova-plugin-camera to package.json
> Saved plugin info for "cordova-plugin-camera" to config.xml
> {code}
> {code}
> $ cordova plugin remove cordova-plugin-camera
> Uninstalling cordova-plugin-camera from android
> Android Studio project detected
> Subproject Path: CordovaLib
> Subproject Path: app
> Removing "cordova-plugin-camera"
> Removing plugin cordova-plugin-camera from config.xml file...
> Removing cordova-plugin-camera from package.json
> {code}
> {code}
> $ cordova plugin add cordova-plugin-camera
> Installing "cordova-plugin-camera" for android
> Android Studio project detected
> Error during processing of action! Attempting to revert...
> Failed to install 'cordova-plugin-camera': CordovaError: Uh oh!
> "/Users/enrico/tmp/testapp/platforms/android/app/src/main/res/xml/provider_paths.xml"
> already exists!
> at copyNewFile
> (/Users/enrico/tmp/testapp/platforms/android/cordova/lib/pluginHandlers.js:261:45)
> at install
> (/Users/enrico/tmp/testapp/platforms/android/cordova/lib/pluginHandlers.js:51:17)
> at ActionStack.process
> (/Users/enrico/tmp/testapp/platforms/android/cordova/node_modules/cordova-common/src/ActionStack.js:56:25)
> at PluginManager.doOperation
> (/Users/enrico/tmp/testapp/platforms/android/cordova/node_modules/cordova-common/src/PluginManager.js:114:20)
> at PluginManager.addPlugin
> (/Users/enrico/tmp/testapp/platforms/android/cordova/node_modules/cordova-common/src/PluginManager.js:144:17)
> at /Users/enrico/tmp/testapp/platforms/android/cordova/Api.js:247:74
> at _fulfilled
> (/Users/enrico/tmp/testapp/platforms/android/cordova/node_modules/q/q.js:854:54)
> at self.promiseDispatch.done
> (/Users/enrico/tmp/testapp/platforms/android/cordova/node_modules/q/q.js:883:30)
> at Promise.promise.promiseDispatch
> (/Users/enrico/tmp/testapp/platforms/android/cordova/node_modules/q/q.js:816:13)
> at
> /Users/enrico/tmp/testapp/platforms/android/cordova/node_modules/q/q.js:570:49
> (node:5722) UnhandledPromiseRejectionWarning: CordovaError: Uh oh!
> "/Users/enrico/tmp/testapp/platforms/android/app/src/main/res/xml/provider_paths.xml"
> already exists!
> at copyNewFile
> (/Users/enrico/tmp/testapp/platforms/android/cordova/lib/pluginHandlers.js:261:45)
> at install
> (/Users/enrico/tmp/testapp/platforms/android/cordova/lib/pluginHandlers.js:51:17)
> at ActionStack.process
> (/Users/enrico/tmp/testapp/platforms/android/cordova/node_modules/cordova-common/src/ActionStack.js:56:25)
> at PluginManager.doOperation
> (/Users/enrico/tmp/testapp/platforms/android/cordova/node_modules/cordova-common/src/PluginManager.js:114:20)
> at PluginManager.addPlugin
> (/Users/enrico/tmp/testapp/platforms/android/cordova/node_modules/cordova-common/src/PluginManager.js:144:17)
> at /Users/enrico/tmp/testapp/platforms/android/cordova/Api.js:247:74
> at _fulfilled
>
[jira] [Resolved] (CB-13975) Android MainActivity cdvStartInBackground=true fails to fire pause event
[ https://issues.apache.org/jira/browse/CB-13975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser resolved CB-13975. - Resolution: Fixed Merged into master. Thanks! > Android MainActivity cdvStartInBackground=true fails to fire pause event > > > Key: CB-13975 > URL: https://issues.apache.org/jira/browse/CB-13975 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-android >Reporter: Rich T >Assignee: Joe Bowser >Priority: Major > Attachments: CoreAndroid.java > > > The MainActivity created from the template that adds support for starting the > app in the background via the cdvStartInBackground flag doesn't fire the > pause event. Debugging the Android code it looks like onPause is called > before the messageChannel is set so the send event is dropped. > There should probably be a pendingPause flag like the pendingResume. > The reason this is a problem is that I am using the phonegap-push-plugin to > wake the app in the background and I want to know that the app is in the > background so I can disable polling requests which are a data and battery > drain, currently I cannot do this and the app can just be sitting there in > the background consuming resources it doesn't need. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-12842) Two plugins with same provider make Android build crash
[
https://issues.apache.org/jira/browse/CB-12842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Bowser updated CB-12842:
Component/s: cordova-plugin-camera
> Two plugins with same provider make Android build crash
> ---
>
> Key: CB-12842
> URL: https://issues.apache.org/jira/browse/CB-12842
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-android, cordova-docs, cordova-plugin-camera
> Environment: cordova-android 6.2.3
>Reporter: Jan Piotrowski (Sujan)
>Priority: Major
>
> Installing two plugins (in the example
> https://github.com/apache/cordova-plugin-camera and
> https://github.com/sitewaerts/cordova-plugin-document-viewer) can create
> something like this:
> {code}
> android:exported="false" android:grantUriPermissions="true"
> android:name="android.support.v4.content.FileProvider">
> android:resource="@xml/provider_paths" />
>
> android:authorities="io.ionic.conferenceapp.DocumentViewerPlugin.fileprovider"
> android:exported="false" android:grantUriPermissions="true"
> android:name="android.support.v4.content.FileProvider">
> android:resource="@xml/documentviewer_file_paths" />
>
> {code}
> This causes the build to fail like so:
> {code}
> ionic cordova run android
> UP-TO-DATE
> :generateArmv7DebugResources UP-TO-DATE
> :mergeArmv7DebugResources
> UP-TO-DATE
> :processArmv7DebugManifest
> C:\Users\mohan\Documents\PrimusGIT\MobileApps\Demo\platforms\android\AndroidManifest.xml:16:9-18:20
> Error:
> Element provider#android.support.v4.content.FileProvider at
> AndroidManifest.xml:16:9-18:20 duplicated with element declared at
> AndroidManifest.xml:13:9-15:20
> See http://g.co/androidstudio/manifest-merger for more information about the
> manifest merger.
> :processArmv7DebugManifest FAILED
> C:\Users\mohan\Documents\PrimusGIT\MobileApps\Demo\platforms\android\AndroidManifest.xml
> Error:
> Validation failed, exiting
> BUILD FAILED
> Total time: 27.006 secs
> FAILURE: Build failed with an exception.
> * What went wrong:
> Execution failed for task ':processArmv7DebugManifest'.
> > Manifest merger failed with multiple errors, see logs
> * Try:
> Run with --stacktrace option to get the stack trace. Run with --info or
> --debug option to get more log output.
> Error: cmd: Command failed with exit code 1 Error output:
> C:\Users\mohan\Documents\PrimusGIT\MobileApps\Demo\platforms\android\AndroidManifest.xml:16:9-18:20
> Error:
> Element provider#android.support.v4.content.FileProvider at
> AndroidManifest.xml:16:9-18:20 duplicated with element declared at
> AndroidManifest.xml:13:9-15:20
> C:\Users\mohan\Documents\PrimusGIT\MobileApps\Demo\platforms\android\AndroidManifest.xml
> Error:
> Validation failed, exiting
> FAILURE: Build failed with an exception.
> * What went wrong:
> Execution failed for task ':processArmv7DebugManifest'.
> > Manifest merger failed with multiple errors, see logs
> * Try:
> Run with --stacktrace option to get the stack trace. Run with --info or
> --debug option to get more log output.
> [ERROR] Cordova encountered an error.
> You may get more insight by running the Cordova command above
> directly.
> [ERROR] An error occurred while running cordova run android (exit code 1).
> {code}
> How should this be handled?
> Forum topic where the problem originated:
> https://forum.ionicframework.com/t/ionic-plugin-document-viewer-creating-android-manifest-merger-issue-in-build/91297
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-12842) Two plugins with same provider make Android build crash
[
https://issues.apache.org/jira/browse/CB-12842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16411985#comment-16411985
]
Joe Bowser commented on CB-12842:
-
This is strictly a docs task now. We've renamed the provider.
> Two plugins with same provider make Android build crash
> ---
>
> Key: CB-12842
> URL: https://issues.apache.org/jira/browse/CB-12842
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-android, cordova-docs
> Environment: cordova-android 6.2.3
>Reporter: Jan Piotrowski (Sujan)
>Priority: Major
>
> Installing two plugins (in the example
> https://github.com/apache/cordova-plugin-camera and
> https://github.com/sitewaerts/cordova-plugin-document-viewer) can create
> something like this:
> {code}
> android:exported="false" android:grantUriPermissions="true"
> android:name="android.support.v4.content.FileProvider">
> android:resource="@xml/provider_paths" />
>
> android:authorities="io.ionic.conferenceapp.DocumentViewerPlugin.fileprovider"
> android:exported="false" android:grantUriPermissions="true"
> android:name="android.support.v4.content.FileProvider">
> android:resource="@xml/documentviewer_file_paths" />
>
> {code}
> This causes the build to fail like so:
> {code}
> ionic cordova run android
> UP-TO-DATE
> :generateArmv7DebugResources UP-TO-DATE
> :mergeArmv7DebugResources
> UP-TO-DATE
> :processArmv7DebugManifest
> C:\Users\mohan\Documents\PrimusGIT\MobileApps\Demo\platforms\android\AndroidManifest.xml:16:9-18:20
> Error:
> Element provider#android.support.v4.content.FileProvider at
> AndroidManifest.xml:16:9-18:20 duplicated with element declared at
> AndroidManifest.xml:13:9-15:20
> See http://g.co/androidstudio/manifest-merger for more information about the
> manifest merger.
> :processArmv7DebugManifest FAILED
> C:\Users\mohan\Documents\PrimusGIT\MobileApps\Demo\platforms\android\AndroidManifest.xml
> Error:
> Validation failed, exiting
> BUILD FAILED
> Total time: 27.006 secs
> FAILURE: Build failed with an exception.
> * What went wrong:
> Execution failed for task ':processArmv7DebugManifest'.
> > Manifest merger failed with multiple errors, see logs
> * Try:
> Run with --stacktrace option to get the stack trace. Run with --info or
> --debug option to get more log output.
> Error: cmd: Command failed with exit code 1 Error output:
> C:\Users\mohan\Documents\PrimusGIT\MobileApps\Demo\platforms\android\AndroidManifest.xml:16:9-18:20
> Error:
> Element provider#android.support.v4.content.FileProvider at
> AndroidManifest.xml:16:9-18:20 duplicated with element declared at
> AndroidManifest.xml:13:9-15:20
> C:\Users\mohan\Documents\PrimusGIT\MobileApps\Demo\platforms\android\AndroidManifest.xml
> Error:
> Validation failed, exiting
> FAILURE: Build failed with an exception.
> * What went wrong:
> Execution failed for task ':processArmv7DebugManifest'.
> > Manifest merger failed with multiple errors, see logs
> * Try:
> Run with --stacktrace option to get the stack trace. Run with --info or
> --debug option to get more log output.
> [ERROR] Cordova encountered an error.
> You may get more insight by running the Cordova command above
> directly.
> [ERROR] An error occurred while running cordova run android (exit code 1).
> {code}
> How should this be handled?
> Forum topic where the problem originated:
> https://forum.ionicframework.com/t/ionic-plugin-document-viewer-creating-android-manifest-merger-issue-in-build/91297
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-13026) java.lang.NoSuchMethodError: No virtual method requestPermissions([Ljava/lang/String;I)V in class Landroid/app/Activity
[
https://issues.apache.org/jira/browse/CB-13026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Bowser resolved CB-13026.
-
Resolution: Implemented
cordova-plugin-compat has been brought into cordova-android, closing this issue.
> java.lang.NoSuchMethodError: No virtual method
> requestPermissions([Ljava/lang/String;I)V in class Landroid/app/Activity
> ---
>
> Key: CB-13026
> URL: https://issues.apache.org/jira/browse/CB-13026
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-android
>Affects Versions: cordova@7.0.0
>Reporter: Alex B.
>Assignee: Joe Bowser
>Priority: Major
> Labels: bug
> Fix For: 7.0.0, 6.3.0
>
>
> h3. The problem
> Problem reproduced on Android 5.1.1 (API level 22), on all my devices which
> below API level 23
> Problematic part of code
> {code:java}
> public class HelloWorldBridge extends CordovaPlugin {
> String [] permissions = {
> Manifest.permission.CALL_PHONE,
> Manifest.permission.INSTALL_SHORTCUT };
> private static int REQUEST_CODE_PERMISSION = 0;
> @Override protected void pluginInitialize() {
> onStart();
> }
> @Override public void onStart() {
> cordova.requestPermissions(this, REQUEST_CODE_PERMISSION,
> permissions);
> }
> @Override public void onNewIntent(Intent intent) {
> cordova.getActivity().setIntent(intent);
> }
> @Override
> public void onRequestPermissionResult(int requestCode, String[]
> permissions, int[] grantResults) throws JSONException {
> super.onRequestPermissionResult(requestCode, permissions,
> grantResults);
> if (requestCode == REQUEST_CODE_PERMISSION) {
> for (int r : grantResults) {
> if (r == PackageManager.PERMISSION_DENIED) {
> return;
> }
> }
> cordova.getActivity().runOnUiThread(new Runnable() {
> @Override
> public void run() {
>Log.d(TAG, "Granted!");
> }
> });
> }
> }
> }
> {code}
> Stack trace:
> {code:java}
> java.lang.NoSuchMethodError: No virtual method
> requestPermissions([Ljava/lang/String;I)V in class Landroid/app/Activity; or
> its super classes (declaration of 'android.app.Activity' appears in
> /system/framework/framework.jar)
> at
> org.apache.cordova.CordovaInterfaceImpl.requestPermissions(CordovaInterfaceImpl.java:226)
> at org.mysample.HelloWorldBridge.initDialOnce(DialOnceBridge.java:40)
> at
> org.mysample.HelloWorldBridge.pluginInitialize(DialOnceBridge.java:27)
> at
> org.apache.cordova.CordovaPlugin.privateInitialize(CordovaPlugin.java:58)
> at org.apache.cordova.PluginManager.getPlugin(PluginManager.java:171)
> at
> org.apache.cordova.PluginManager.startupPlugins(PluginManager.java:97)
> at org.apache.cordova.PluginManager.init(PluginManager.java:86)
> at
> org.apache.cordova.CordovaWebViewImpl.init(CordovaWebViewImpl.java:115)
> at org.apache.cordova.CordovaActivity.init(CordovaActivity.java:149)
> at org.apache.cordova.CordovaActivity.loadUrl(CordovaActivity.java:224)
> at
> com.dialonce.cordova.sample.MainActivity.onCreate(MainActivity.java:39)
> at android.app.Activity.performCreate(Activity.java:6092)
> at
> android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1112)
> at
> android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2468)
> at
> android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2595)
> at android.app.ActivityThread.access$800(ActivityThread.java:178)
> at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1470)
> at android.os.Handler.dispatchMessage(Handler.java:111)
> at android.os.Looper.loop(Looper.java:194)
> at android.app.ActivityThread.main(ActivityThread.java:5631)
> at java.lang.reflect.Method.invoke(Native Method)
> at java.lang.reflect.Method.invoke(Method.java:372)
> at
> com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:963)
> at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:758)
> {code}
> h3. Investigation
> According docs [Activity.requestPermissions |
> https://developer.android.com/reference/android/app/Activity.html#requestPermissions(java.lang.String[],
> int)] this method require Android API 23
> h3. Workaround
> Wrap `requestPermissions` code with `if (Build.VERSION.SDK_INT >=
> Build.VERSION_CODES.M) { ... }`
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (CB-13104) "Error: Cannot read property 'length' of undefined" when executing "cordova run android"
[
https://issues.apache.org/jira/browse/CB-13104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Bowser resolved CB-13104.
-
Resolution: Fixed
We require Gradle as a dependency, because we're not allowed to use Gradle
Wrapper due to the ASF policy of not including JARs in our repositories.
> "Error: Cannot read property 'length' of undefined" when executing "cordova
> run android"
>
>
> Key: CB-13104
> URL: https://issues.apache.org/jira/browse/CB-13104
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-android
> Environment: Windows 7 Professional x64
> Java SDK 8u131
> npm 5.2.0
> phonegap 6.5.2
> cordova 6.5.0
> cordova android platform 6.2.3
> android studio 2.3.3
> android sdk build-tools 26
> android sdk tools 26.0.2
> android sdk platform-tools 26.0.0
> android emulator 26.1.2
> android support repository 47.0.0
>Reporter: Bryan Bale
>Assignee: Joe Bowser
>Priority: Major
>
> I've searched for solutions to this problem, and found several reports of it,
> but no solutions. Based on my many attempts to get something to work (I've
> tried phonegap, ionic, and just plain cordova), I started suspecting that
> there's a bug in the cordova android platform. All my build attempts have
> been halted at this error message:
> {{Error: Cannot read property 'length' of undefined}}
> *Replicating this issue with phonegap:*
> _I'm starting with phonegap because this is how I first encountered the
> error, and it seems to give me the most useful information with regard to
> where the error is happening._
> $ npm install -g phonegap
> npm WARN deprecated tough-cookie@2.2.2: ReDoS vulnerability parsing
> Set-Cookie https://nodesecurity.io/advisories/130
> npm WARN deprecated node-uuid@1.4.8: Use uuid module instead
>
> C:\Users\bbale\AppData\Roaming\npm\phonegap ->
> C:\Users\bbale\AppData\Roaming\npm\node_modules\phonegap\bin\phonegap.js
> + phonegap@6.5.2
>
> added 873 packages in 146.435s
>
> $ phonegap create pgHello --id "com.pghello.app" --name "pgHello" --template
> hello-world
> Creating a new cordova project.
> $ cd pgHello
> $ phonegap run android --verbose
> [phonegap] executing 'cordova platform add --save android ' ...
>
>
> Adding android project...
>
>
>
>
>
> Creating Cordova project for the Android platform:
>
>
> Path: platforms\android
>
>
> Package: com.pghello.app
>
>
> Name: pgHello
>
>
> Activity: MainActivity
>
>
> Android target: android-25
>
>
>
>
>
> Subproject Path: CordovaLib
>
>
>
[jira] [Commented] (CB-13582) Android build process outputs flawed success message
[
https://issues.apache.org/jira/browse/CB-13582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16411980#comment-16411980
]
Joe Bowser commented on CB-13582:
-
Is this still a thing? It seems that this got lost in the sea of issues.
> Android build process outputs flawed success message
>
>
> Key: CB-13582
> URL: https://issues.apache.org/jira/browse/CB-13582
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-android
>Affects Versions: 6.3.0
>Reporter: Jan Piotrowski (Sujan)
>Assignee: Joe Bowser
>Priority: Major
>
> When you build the Android platform you get a success message similar to this:
> {quote}
> [14:05:41]: ▸ BUILD SUCCESSFUL
> [14:05:41]: ▸ Total time: 3.365 secs
> Built the following apk(s):
> [14:05:42]: ▸
> /Users/sujan/.../platforms/android/build/outputs/apk/android-release.apk
> [14:05:42]: ▸
> /Users/sujan/.../platforms/android/build/outputs/apk/android-release-unsigned.apk
> {quote}
> Turns out this is (under specific conditions) not really true.
> If the build did not really sign the apk (as the parameters were missing) it
> still sometimes outputs the signed apk in this list: If you had a successful
> build that signed the apk, then another one that did _not_ you get a success
> message but the signed apk is still the old one.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-13788) Specify the minimum required version of google play services for plugins
[ https://issues.apache.org/jira/browse/CB-13788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16411977#comment-16411977 ] Joe Bowser commented on CB-13788: - [~wf9a5m75] The PR didn't seem to do anything, and the committer closed the PR. > Specify the minimum required version of google play services for plugins > > > Key: CB-13788 > URL: https://issues.apache.org/jira/browse/CB-13788 > Project: Apache Cordova > Issue Type: Improvement > Components: cordova-android >Affects Versions: cordova-android-7.0.0 >Reporter: Masashi Katsumata >Assignee: Joe Bowser >Priority: Major > Labels: patch > > Many plugins use the Google Play Services SDK, but it is really heavy. > Some developers want to specify particular versions, but not all of plugin > developers. > Some other developers don't want to update their plugin frequently, but want > to specify minimum required version. > I found this code > [https://github.com/apache/cordova-android/blob/673a6773b2f78ba76d2144c66ab7a3add78648ae/bin/templates/cordova/lib/builders/StudioBuilder.js#L177-L201] > This allows us to specify like this > ** > > But the code does not accept particular module. > * versions=">=11.8.0" />* > > In order to specify particular module, we need to change the code. > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-13975) Android MainActivity cdvStartInBackground=true fails to fire pause event
[ https://issues.apache.org/jira/browse/CB-13975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16411971#comment-16411971 ] Joe Bowser commented on CB-13975: - [~richturner] Can you submit this as a PR on GitHub? > Android MainActivity cdvStartInBackground=true fails to fire pause event > > > Key: CB-13975 > URL: https://issues.apache.org/jira/browse/CB-13975 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-android >Reporter: Rich T >Assignee: Joe Bowser >Priority: Major > Attachments: CoreAndroid.java > > > The MainActivity created from the template that adds support for starting the > app in the background via the cdvStartInBackground flag doesn't fire the > pause event. Debugging the Android code it looks like onPause is called > before the messageChannel is set so the send event is dropped. > There should probably be a pendingPause flag like the pendingResume. > The reason this is a problem is that I am using the phonegap-push-plugin to > wake the app in the background and I want to know that the app is in the > background so I can disable polling requests which are a data and battery > drain, currently I cannot do this and the app can just be sitting there in > the background consuming resources it doesn't need. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-13929) duplicate entry: android/support/v13/view/DragStartHelper$OnDragStartListener.class
[
https://issues.apache.org/jira/browse/CB-13929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Bowser resolved CB-13929.
-
Resolution: Won't Fix
This isn't an issue with Cordova, but with a third party plugin. We don't use
this support library.
> duplicate entry:
> android/support/v13/view/DragStartHelper$OnDragStartListener.class
> ---
>
> Key: CB-13929
> URL: https://issues.apache.org/jira/browse/CB-13929
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-android
>Affects Versions: cordova@7.0.0
>Reporter: Daniel Ramos
>Assignee: Joe Bowser
>Priority: Major
>
> Hello Cordova team.
>
> Today I've launched my app build in Jenkins as always, and it gives me the
> following error:
>
> {code:java}
> ...
> Note: Recompile with -Xlint:unchecked for details.
> :compileArmv7DebugNdk UP-TO-DATE
> :compileArmv7DebugSources
> :transformClassesWithJarMergingForArmv7Debug FAILED
> FAILURE: Build failed with an exception.
> * What went wrong:
> Execution failed for task ':transformClassesWithJarMergingForArmv7Debug'.
> > com.android.build.api.transform.TransformException:
> java.util.zip.ZipException: duplicate entry:
> android/support/v13/view/DragStartHelper$OnDragStartListener.class
> {code}
> I've been investigating what could have caused this issue, and the only thing
> that I can find that is different from previous builds, is an update that
> Cordova did over support-v4.
> Here is the log diff:
> [https://gist.github.com/DanielRamosAcosta/29f3223c3b8f96447814122bfc193f08]
> Cordova version & plugins:
> {code}
> "dependencies": {
> "cordova": "^7.1.0",
> "cordova-android": "^6.4.0",
> "cordova-plugin-android-permissions": "^1.0.0",
> "cordova-plugin-crosswalk-webview": "^2.3.0",
> "cordova-plugin-dbmeter": "^2.1.0",
> "cordova-plugin-screen-orientation": "^3.0.1",
> "cordova-plugin-statusbar": "^2.4.1",
> "cordova-plugin-whitelist": "^1.3.3",
> "cordova-plugin-x-socialsharing": "^5.2.1",
> "es6-promise-plugin": "^4.1.1"
> },
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-13980) Cordova Android app location.reload() causing app to halt
[ https://issues.apache.org/jira/browse/CB-13980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser resolved CB-13980. - Resolution: Cannot Reproduce Closing, since we can't reproduce this > Cordova Android app location.reload() causing app to halt > - > > Key: CB-13980 > URL: https://issues.apache.org/jira/browse/CB-13980 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-android >Affects Versions: 7.0.0, 8.0.0 > Environment: framework7.io (v1) > cordova 8 (also tested build with cordova 7) > Tested on Nexus 6p, Google Pixel 2, Samsung Galaxy s8 > Not working. >Reporter: rehan manzoor >Assignee: Joe Bowser >Priority: Major > > Cordova App was built using > framework7.io (v1) > cordova 8 (also tested build with cordova 7) > it was working fine till the latest software update from android, but now it > get stuck whenever the location.reload() is called, i tried other ways to > reload the windows e.g. > window.location.href, > location.href, > document.location.href > location.replace() > window.location.replace() > window.location.assign() > document.location.assign() > document.location.replace() > navigator.app.loadUrl() > > but all causing the app to get stuck, what I concluded from debugging it's > not the problem in function, it's maybe webview which is causing the > application to get stuck at reload. > any suggestion is appreciated. > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-13974) With cordova-android 7.x plugins with jni libraries are not backwards compatible
[
https://issues.apache.org/jira/browse/CB-13974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16406814#comment-16406814
]
Joe Bowser commented on CB-13974:
-
I'll take a look at creating a mapping for JNI. It shouldn't be that
difficult, but I really want to yank it out for 8.0
> With cordova-android 7.x plugins with jni libraries are not backwards
> compatible
>
>
> Key: CB-13974
> URL: https://issues.apache.org/jira/browse/CB-13974
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-android
>Affects Versions: cordova-android-7.0.0
>Reporter: Doug Davies
>Assignee: Joe Bowser
>Priority: Major
> Attachments: image1.png, image2.png, image3.png
>
>
> Pull down my project on GitHub
> [https://github.com/funkyvisions/manatee-tester.git]
> It uses the 3rd party plugin (manateeworks-barcodescanner-v3) which IS
> compatible with cordova-android 6.4.0.
> Execute the following:
> {code:java}
> cordova prepare
> cordova build android{code}
> You'll see everything prepares and builds fine and you can see the libraries
> (.so files and jar) end up in the correct directories in the APK (view
> through Android Studio - Build -> Analyze APK). See image1.
> Now we are going to switch to cordova-android 7.1.0.
> Execute the following:
> {code:java}
> cp package.7.json package.json
> cp config.7.xml config.xml
> rm -rf platforms plugins
> cordova prepare
> cordova build android
> {code}
> Notice it fails. This is because the plugin.xml is incorrect (although the
> error would never lead you to discover this). So let's fix it. Unfortunately,
> I tried to fork the project and apply a patch, but there seems to be a bug
> with cordova-fetch (https://issues.apache.org/jira/browse/CB-13973), so
> instead I included it locally in this project along with the patch to
> plugin.xml.
> I changed these lines in plugin.xml:
> {code:java}
> framework="true" />
> src="src/android/src/com/manateeworks/BarcodeScannerPlugin.java"
> target-dir="src/com/manateeworks" />
> target-dir="src/com/manateeworks" />
> target-dir="res/layout" />
> target-dir="res/drawable" />
> target-dir="res/drawable-hdpi" />
> target-dir="res/drawable" />
> target-dir="res/drawable" />
> target-dir="res/drawable" />
> target-dir="libs/armeabi" />
> target-dir="libs/x86" />
> target-dir="libs/armeabi-v7a" />
> target-dir="libs/arm64-v8a" />
> target-dir="libs/mips" />
> {code}
> to this:
> {code:java}
>
>
>
> target="jniLibs/mwbscanner.jar" />
>
> src="src/android/src/com/manateeworks/BarcodeScannerPlugin.java"
> target-dir="src/com/manateeworks" />
> target-dir="src/com/manateeworks" />
>
> target="res/layout/scanner.xml" />
> target="res/drawable/overlay_mw.png" />
> target="res/drawable-hdpi/overlay_mw.png" />
> target="res/drawable/flashbuttonoff.png" />
> target="res/drawable/flashbuttonon.png" />
> target="res/drawable/zoom.png" />
>
> target="jniLibs/armeabi/libBarcodeScannerLib.so" />
> target="jniLibs/x86/libBarcodeScannerLib.so" />
> target="jniLibs/armeabi-v7a/libBarcodeScannerLib.so" />
> target="jniLibs/arm64-v8a/libBarcodeScannerLib.so" />
> target="jniLibs/mips/libBarcodeScannerLib.so" />
> {code}
> Now let's switch to the forked version of the plugin and see if it works.
> Execute the following:
> {code:java}
> cp package.fork.json package.json
> cp config.fork.xml config.xml
> rm -rf platforms plugins
> cordova prepare
> cordova build android{code}
> Now you see it builds once again and the APK is correct. See image2.
> However, the directives I put in plugin.xml are not backwards compatible with
> 6.4.0. We can prove this by now switch back to cordova-android 6.4.0 and
> trying to build.
> {code:java}
> cp package.6.json package.json
> cp config.6.xml config.xml
> rm -rf platforms plugins
> cordova prepare
> cordova build android{code}
> Now look at the APK and you will see the libraries are missing. See image3.
> In order to fix this, I have to create a mix on the old config plus the new.
> See
> [https://github.com/funkyvisions/phonegap-manateeworks-v3/commit/9f3b165832141e45fa2c2e92dbf62b2300f0caf2#diff-53f390d375398624afe1cfe1125f42bf]
> I don't think this is a very good solution.
> There needs to be an approach that works with both. I wonder if this
> (https://issues.apache.org/jira/browse/CB-8781) is missing from
> cordova-android 7.1.0:
> {code:java}
> jniLibs.srcDirs = ['libs']{code}
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail:
[jira] [Resolved] (CB-11068) Application getting crashed on Android, iOS and Windows(Universal) when more than 20 images are captured using BASE64 DATA URL format.
[ https://issues.apache.org/jira/browse/CB-11068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser resolved CB-11068. - Resolution: Won't Fix I think we've been over this enough. DATA_URL is not a good way to process images, use a different method. > Application getting crashed on Android, iOS and Windows(Universal) when more > than 20 images are captured using BASE64 DATA URL format. > -- > > Key: CB-11068 > URL: https://issues.apache.org/jira/browse/CB-11068 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-plugin-camera >Affects Versions: 3.5.0 > Environment: Android, Windows and iOS mobiles >Reporter: COE >Priority: Major > Labels: android, ios, triaged, wfc, windows > > We have used Cordova for our hybrid mobile application targeting multiple > platforms with usage of Camera Plugin. After a certain no of images are > captured, the camera feature is getting crashed and application is becoming > inaccessible. Please suggest us a possible solution. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-9446) Samsung device returns null from Cursor in Camera getRealPath
[
https://issues.apache.org/jira/browse/CB-9446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Bowser resolved CB-9446.
Resolution: Cannot Reproduce
Using the FileProvider appears to have resolved these GetRealPath errors,
closing.
> Samsung device returns null from Cursor in Camera getRealPath
> -
>
> Key: CB-9446
> URL: https://issues.apache.org/jira/browse/CB-9446
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-plugin-camera
>Affects Versions: 1.2.1
> Environment: Samsung 4.1.2 GT-N8010
>Reporter: Charles Verge
>Priority: Major
> Labels: Android, samsung
> Fix For: 1.2.1
>
> Attachments: realpath.diff
>
>
> Using a Samsung Galaxy Note GT-N8010 with android 4.1.2 produces an exception
> in the Exif class. This is due to a filePath being null on line 66 of
> src/android/ExifHelper.java
> {code} new ExifInterface(filePath){code}
> This error has been introduced when the switch was made to using Cursors.
> This error did not happen in with the camera plugin bundled with Phone Gap
> 3.4.
> This has been duplicated by other developers independently
> http://stackoverflow.com/questions/30616846/phonegap-app-crash-when-take-a-new-photo-with-camera-plugin
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-13993) Show caption text over the camera
[ https://issues.apache.org/jira/browse/CB-13993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16406352#comment-16406352 ] Joe Bowser commented on CB-13993: - I rejected the PR because it was an abuse of the Toast feature, it may not work across all devices and was not cross-platform. I do not want this PR added since it may be a one-way ticket to getting our apps banned from Play. Please keep this feature to yourself, I can confidently say that we don't want this feature as you have implemented it. > Show caption text over the camera > - > > Key: CB-13993 > URL: https://issues.apache.org/jira/browse/CB-13993 > Project: Apache Cordova > Issue Type: New Feature > Components: cordova-android >Affects Versions: cordova-android-7.0.0 >Reporter: ijaj mulani >Assignee: Joe Bowser >Priority: Critical > Labels: android, camera, features > Attachments: text over camera.png > > > h1. Allow to show caption text over the camera. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-13307) Accessing Google Photos on Pixel from cordova-plugin-camera
[ https://issues.apache.org/jira/browse/CB-13307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16405430#comment-16405430 ] Joe Bowser commented on CB-13307: - Can someone with a working Pixel that's not running Android P test this? > Accessing Google Photos on Pixel from cordova-plugin-camera > --- > > Key: CB-13307 > URL: https://issues.apache.org/jira/browse/CB-13307 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-plugin-camera >Reporter: David Briglio >Priority: Major > > Currently when trying to access some photos from Google Photos, it fails to > load. Android 8.0 on Google Pixel, cordova version 6.5.0, > cordova-plugin-camera version 2.4.1. > Causes: > 1) Only mimetypes "image/jpeg" and "image/png" are accepted, all other types > are considered an invalid image. The mimetype of the image I am loading gets > set to "image/*". > 2) In FileHelper.java: when hitting the isGooglePhotosUri method, the uri > authority is compared against "com.google.android.apps.photos.content", where > the actual is "com.google.android.apps.photos.contentprovider". This causes > the logic to dismiss the image as not from Google Photos. > After applying fixes for these two areas, I am able to successfully load all > of my images. > Merge request [here|https://github.com/apache/cordova-plugin-camera/pull/286]. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-13830) Cordova-Android@7.0.0 fails to add a plugin previously removed
[
https://issues.apache.org/jira/browse/CB-13830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16405380#comment-16405380
]
Joe Bowser commented on CB-13830:
-
I'm going to lower the priority, since we're really not supposed to use
source-file for XML, but Camera is special. :/
> Cordova-Android@7.0.0 fails to add a plugin previously removed
> --
>
> Key: CB-13830
> URL: https://issues.apache.org/jira/browse/CB-13830
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-android
>Affects Versions: cordova-android-7.0.0
> Environment: macOS 10.12.6
> node 9.4.0
> Cordova CLI 8.0.0
>
>Reporter: Enrico Giordani
>Assignee: Joe Bowser
>Priority: Major
>
> Removing a plugin and than adding it again, causes an error:
> {code}
> $ cordova create testapp
> $ cd testapp
> $ cordova platform add android
> Using cordova-fetch for cordova-android@~7.0.0
> Adding android project...
> Creating Cordova project for the Android platform:
> Path: platforms/android
> Package: io.cordova.hellocordova
> Name: HelloCordova
> Activity: MainActivity
> Android target: android-26
> Subproject Path: CordovaLib
> Subproject Path: app
> Android project created with cordova-android@7.0.0
> Android Studio project detected
> Android Studio project detected
> Discovered plugin "cordova-plugin-whitelist" in config.xml. Adding it to the
> project
> Installing "cordova-plugin-whitelist" for android
> This plugin is only applicable for versions of cordova-android greater than
> 4.0. If you have a previous platform version, you do *not* need this plugin
> since the whitelist will be built in.
>
> Adding cordova-plugin-whitelist to package.json
> Saved plugin info for "cordova-plugin-whitelist" to config.xml
> --save flag or autosave detected
> Saving android@~7.0.0 into config.xml file ...
> {code}
> {code}
> $ cordova plugin add cordova-plugin-camera
> Installing "cordova-plugin-camera" for android
> Android Studio project detected
> Subproject Path: CordovaLib
> Subproject Path: app
> Adding cordova-plugin-camera to package.json
> Saved plugin info for "cordova-plugin-camera" to config.xml
> {code}
> {code}
> $ cordova plugin remove cordova-plugin-camera
> Uninstalling cordova-plugin-camera from android
> Android Studio project detected
> Subproject Path: CordovaLib
> Subproject Path: app
> Removing "cordova-plugin-camera"
> Removing plugin cordova-plugin-camera from config.xml file...
> Removing cordova-plugin-camera from package.json
> {code}
> {code}
> $ cordova plugin add cordova-plugin-camera
> Installing "cordova-plugin-camera" for android
> Android Studio project detected
> Error during processing of action! Attempting to revert...
> Failed to install 'cordova-plugin-camera': CordovaError: Uh oh!
> "/Users/enrico/tmp/testapp/platforms/android/app/src/main/res/xml/provider_paths.xml"
> already exists!
> at copyNewFile
> (/Users/enrico/tmp/testapp/platforms/android/cordova/lib/pluginHandlers.js:261:45)
> at install
> (/Users/enrico/tmp/testapp/platforms/android/cordova/lib/pluginHandlers.js:51:17)
> at ActionStack.process
> (/Users/enrico/tmp/testapp/platforms/android/cordova/node_modules/cordova-common/src/ActionStack.js:56:25)
> at PluginManager.doOperation
> (/Users/enrico/tmp/testapp/platforms/android/cordova/node_modules/cordova-common/src/PluginManager.js:114:20)
> at PluginManager.addPlugin
> (/Users/enrico/tmp/testapp/platforms/android/cordova/node_modules/cordova-common/src/PluginManager.js:144:17)
> at /Users/enrico/tmp/testapp/platforms/android/cordova/Api.js:247:74
> at _fulfilled
> (/Users/enrico/tmp/testapp/platforms/android/cordova/node_modules/q/q.js:854:54)
> at self.promiseDispatch.done
> (/Users/enrico/tmp/testapp/platforms/android/cordova/node_modules/q/q.js:883:30)
> at Promise.promise.promiseDispatch
> (/Users/enrico/tmp/testapp/platforms/android/cordova/node_modules/q/q.js:816:13)
> at
> /Users/enrico/tmp/testapp/platforms/android/cordova/node_modules/q/q.js:570:49
> (node:5722) UnhandledPromiseRejectionWarning: CordovaError: Uh oh!
> "/Users/enrico/tmp/testapp/platforms/android/app/src/main/res/xml/provider_paths.xml"
> already exists!
> at copyNewFile
> (/Users/enrico/tmp/testapp/platforms/android/cordova/lib/pluginHandlers.js:261:45)
> at install
> (/Users/enrico/tmp/testapp/platforms/android/cordova/lib/pluginHandlers.js:51:17)
> at ActionStack.process
> (/Users/enrico/tmp/testapp/platforms/android/cordova/node_modules/cordova-common/src/ActionStack.js:56:25)
> at PluginManager.doOperation
> (/Users/enrico/tmp/testapp/platforms/android/cordova/node_modules/cordova-common/src/PluginManager.js:114:20)
> at PluginManager.addPlugin
>
[jira] [Updated] (CB-13830) Cordova-Android@7.0.0 fails to add a plugin previously removed
[
https://issues.apache.org/jira/browse/CB-13830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Bowser updated CB-13830:
Priority: Major (was: Critical)
> Cordova-Android@7.0.0 fails to add a plugin previously removed
> --
>
> Key: CB-13830
> URL: https://issues.apache.org/jira/browse/CB-13830
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-android
>Affects Versions: cordova-android-7.0.0
> Environment: macOS 10.12.6
> node 9.4.0
> Cordova CLI 8.0.0
>
>Reporter: Enrico Giordani
>Assignee: Joe Bowser
>Priority: Major
>
> Removing a plugin and than adding it again, causes an error:
> {code}
> $ cordova create testapp
> $ cd testapp
> $ cordova platform add android
> Using cordova-fetch for cordova-android@~7.0.0
> Adding android project...
> Creating Cordova project for the Android platform:
> Path: platforms/android
> Package: io.cordova.hellocordova
> Name: HelloCordova
> Activity: MainActivity
> Android target: android-26
> Subproject Path: CordovaLib
> Subproject Path: app
> Android project created with cordova-android@7.0.0
> Android Studio project detected
> Android Studio project detected
> Discovered plugin "cordova-plugin-whitelist" in config.xml. Adding it to the
> project
> Installing "cordova-plugin-whitelist" for android
> This plugin is only applicable for versions of cordova-android greater than
> 4.0. If you have a previous platform version, you do *not* need this plugin
> since the whitelist will be built in.
>
> Adding cordova-plugin-whitelist to package.json
> Saved plugin info for "cordova-plugin-whitelist" to config.xml
> --save flag or autosave detected
> Saving android@~7.0.0 into config.xml file ...
> {code}
> {code}
> $ cordova plugin add cordova-plugin-camera
> Installing "cordova-plugin-camera" for android
> Android Studio project detected
> Subproject Path: CordovaLib
> Subproject Path: app
> Adding cordova-plugin-camera to package.json
> Saved plugin info for "cordova-plugin-camera" to config.xml
> {code}
> {code}
> $ cordova plugin remove cordova-plugin-camera
> Uninstalling cordova-plugin-camera from android
> Android Studio project detected
> Subproject Path: CordovaLib
> Subproject Path: app
> Removing "cordova-plugin-camera"
> Removing plugin cordova-plugin-camera from config.xml file...
> Removing cordova-plugin-camera from package.json
> {code}
> {code}
> $ cordova plugin add cordova-plugin-camera
> Installing "cordova-plugin-camera" for android
> Android Studio project detected
> Error during processing of action! Attempting to revert...
> Failed to install 'cordova-plugin-camera': CordovaError: Uh oh!
> "/Users/enrico/tmp/testapp/platforms/android/app/src/main/res/xml/provider_paths.xml"
> already exists!
> at copyNewFile
> (/Users/enrico/tmp/testapp/platforms/android/cordova/lib/pluginHandlers.js:261:45)
> at install
> (/Users/enrico/tmp/testapp/platforms/android/cordova/lib/pluginHandlers.js:51:17)
> at ActionStack.process
> (/Users/enrico/tmp/testapp/platforms/android/cordova/node_modules/cordova-common/src/ActionStack.js:56:25)
> at PluginManager.doOperation
> (/Users/enrico/tmp/testapp/platforms/android/cordova/node_modules/cordova-common/src/PluginManager.js:114:20)
> at PluginManager.addPlugin
> (/Users/enrico/tmp/testapp/platforms/android/cordova/node_modules/cordova-common/src/PluginManager.js:144:17)
> at /Users/enrico/tmp/testapp/platforms/android/cordova/Api.js:247:74
> at _fulfilled
> (/Users/enrico/tmp/testapp/platforms/android/cordova/node_modules/q/q.js:854:54)
> at self.promiseDispatch.done
> (/Users/enrico/tmp/testapp/platforms/android/cordova/node_modules/q/q.js:883:30)
> at Promise.promise.promiseDispatch
> (/Users/enrico/tmp/testapp/platforms/android/cordova/node_modules/q/q.js:816:13)
> at
> /Users/enrico/tmp/testapp/platforms/android/cordova/node_modules/q/q.js:570:49
> (node:5722) UnhandledPromiseRejectionWarning: CordovaError: Uh oh!
> "/Users/enrico/tmp/testapp/platforms/android/app/src/main/res/xml/provider_paths.xml"
> already exists!
> at copyNewFile
> (/Users/enrico/tmp/testapp/platforms/android/cordova/lib/pluginHandlers.js:261:45)
> at install
> (/Users/enrico/tmp/testapp/platforms/android/cordova/lib/pluginHandlers.js:51:17)
> at ActionStack.process
> (/Users/enrico/tmp/testapp/platforms/android/cordova/node_modules/cordova-common/src/ActionStack.js:56:25)
> at PluginManager.doOperation
> (/Users/enrico/tmp/testapp/platforms/android/cordova/node_modules/cordova-common/src/PluginManager.js:114:20)
> at PluginManager.addPlugin
> (/Users/enrico/tmp/testapp/platforms/android/cordova/node_modules/cordova-common/src/PluginManager.js:144:17)
> at /Users/enrico/tmp/testapp/platforms/android/cordova/Api.js:247:74
> at _fulfilled
>
[jira] [Commented] (CB-13830) Cordova-Android@7.0.0 fails to add a plugin previously removed
[
https://issues.apache.org/jira/browse/CB-13830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16405311#comment-16405311
]
Joe Bowser commented on CB-13830:
-
This probably deserves a point release at the very least.
> Cordova-Android@7.0.0 fails to add a plugin previously removed
> --
>
> Key: CB-13830
> URL: https://issues.apache.org/jira/browse/CB-13830
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-android
>Affects Versions: cordova-android-7.0.0
> Environment: macOS 10.12.6
> node 9.4.0
> Cordova CLI 8.0.0
>
>Reporter: Enrico Giordani
>Assignee: Joe Bowser
>Priority: Critical
>
> Removing a plugin and than adding it again, causes an error:
> {code}
> $ cordova create testapp
> $ cd testapp
> $ cordova platform add android
> Using cordova-fetch for cordova-android@~7.0.0
> Adding android project...
> Creating Cordova project for the Android platform:
> Path: platforms/android
> Package: io.cordova.hellocordova
> Name: HelloCordova
> Activity: MainActivity
> Android target: android-26
> Subproject Path: CordovaLib
> Subproject Path: app
> Android project created with cordova-android@7.0.0
> Android Studio project detected
> Android Studio project detected
> Discovered plugin "cordova-plugin-whitelist" in config.xml. Adding it to the
> project
> Installing "cordova-plugin-whitelist" for android
> This plugin is only applicable for versions of cordova-android greater than
> 4.0. If you have a previous platform version, you do *not* need this plugin
> since the whitelist will be built in.
>
> Adding cordova-plugin-whitelist to package.json
> Saved plugin info for "cordova-plugin-whitelist" to config.xml
> --save flag or autosave detected
> Saving android@~7.0.0 into config.xml file ...
> {code}
> {code}
> $ cordova plugin add cordova-plugin-camera
> Installing "cordova-plugin-camera" for android
> Android Studio project detected
> Subproject Path: CordovaLib
> Subproject Path: app
> Adding cordova-plugin-camera to package.json
> Saved plugin info for "cordova-plugin-camera" to config.xml
> {code}
> {code}
> $ cordova plugin remove cordova-plugin-camera
> Uninstalling cordova-plugin-camera from android
> Android Studio project detected
> Subproject Path: CordovaLib
> Subproject Path: app
> Removing "cordova-plugin-camera"
> Removing plugin cordova-plugin-camera from config.xml file...
> Removing cordova-plugin-camera from package.json
> {code}
> {code}
> $ cordova plugin add cordova-plugin-camera
> Installing "cordova-plugin-camera" for android
> Android Studio project detected
> Error during processing of action! Attempting to revert...
> Failed to install 'cordova-plugin-camera': CordovaError: Uh oh!
> "/Users/enrico/tmp/testapp/platforms/android/app/src/main/res/xml/provider_paths.xml"
> already exists!
> at copyNewFile
> (/Users/enrico/tmp/testapp/platforms/android/cordova/lib/pluginHandlers.js:261:45)
> at install
> (/Users/enrico/tmp/testapp/platforms/android/cordova/lib/pluginHandlers.js:51:17)
> at ActionStack.process
> (/Users/enrico/tmp/testapp/platforms/android/cordova/node_modules/cordova-common/src/ActionStack.js:56:25)
> at PluginManager.doOperation
> (/Users/enrico/tmp/testapp/platforms/android/cordova/node_modules/cordova-common/src/PluginManager.js:114:20)
> at PluginManager.addPlugin
> (/Users/enrico/tmp/testapp/platforms/android/cordova/node_modules/cordova-common/src/PluginManager.js:144:17)
> at /Users/enrico/tmp/testapp/platforms/android/cordova/Api.js:247:74
> at _fulfilled
> (/Users/enrico/tmp/testapp/platforms/android/cordova/node_modules/q/q.js:854:54)
> at self.promiseDispatch.done
> (/Users/enrico/tmp/testapp/platforms/android/cordova/node_modules/q/q.js:883:30)
> at Promise.promise.promiseDispatch
> (/Users/enrico/tmp/testapp/platforms/android/cordova/node_modules/q/q.js:816:13)
> at
> /Users/enrico/tmp/testapp/platforms/android/cordova/node_modules/q/q.js:570:49
> (node:5722) UnhandledPromiseRejectionWarning: CordovaError: Uh oh!
> "/Users/enrico/tmp/testapp/platforms/android/app/src/main/res/xml/provider_paths.xml"
> already exists!
> at copyNewFile
> (/Users/enrico/tmp/testapp/platforms/android/cordova/lib/pluginHandlers.js:261:45)
> at install
> (/Users/enrico/tmp/testapp/platforms/android/cordova/lib/pluginHandlers.js:51:17)
> at ActionStack.process
> (/Users/enrico/tmp/testapp/platforms/android/cordova/node_modules/cordova-common/src/ActionStack.js:56:25)
> at PluginManager.doOperation
> (/Users/enrico/tmp/testapp/platforms/android/cordova/node_modules/cordova-common/src/PluginManager.js:114:20)
> at PluginManager.addPlugin
> (/Users/enrico/tmp/testapp/platforms/android/cordova/node_modules/cordova-common/src/PluginManager.js:144:17)
> at
[jira] [Commented] (CB-13972) Requirements check failed for JDK 1.8 or greater
[
https://issues.apache.org/jira/browse/CB-13972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16405183#comment-16405183
]
Joe Bowser commented on CB-13972:
-
[~quarkbuddha] There's no platform on it. We really need to make it crystal
clear that Java 9 doesn't work.
> Requirements check failed for JDK 1.8 or greater
>
>
> Key: CB-13972
> URL: https://issues.apache.org/jira/browse/CB-13972
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-cli
>Affects Versions: cordova-android-7.0.0
> Environment: Windows 10 64 (10.0.16229.248)
>Reporter: John M. Wargo
>Priority: Major
>
> I've got a problem with my Java config, but the CLI reports the error then
> reports that it's deployed the app (when it hasn't).
> {{JAVA_HOME=D:\Program Files\Java\jdk-9.0.1}}
> {{(node:10316) UnhandledPromiseRejectionWarning: CordovaError: Requirements
> check failed for JDK 1.8 or greater}}
> {{ at
> D:\dev\hardware\particle\particle-garage-controller-ionic\platforms\android\cordova\lib\check_reqs.js:370:19}}
> {{ at _fulfilled
> (D:\dev\hardware\particle\particle-garage-controller-ionic\platforms\android\cordova\node_modules\q\q.js:854:54)}}
> {{ at self.promiseDispatch.done
> (D:\dev\hardware\particle\particle-garage-controller-ionic\platforms\android\cordova\node_modules\q\q.js:883:30)}}
> {{ at Promise.promise.promiseDispatch
> (D:\dev\hardware\particle\particle-garage-controller-ionic\platforms\android\cordova\node_modules\q\q.js:816:13)}}
> {{ at
> D:\dev\hardware\particle\particle-garage-controller-ionic\platforms\android\cordova\node_modules\q\q.js:624:44}}
> {{ at runSingle
> (D:\dev\hardware\particle\particle-garage-controller-ionic\platforms\android\cordova\node_modules\q\q.js:137:13)}}
> {{ at flush
> (D:\dev\hardware\particle\particle-garage-controller-ionic\platforms\android\cordova\node_modules\q\q.js:125:13)}}
> {{ at _combinedTickCallback (internal/process/next_tick.js:131:7)}}
> {{ at process._tickCallback (internal/process/next_tick.js:180:9)}}
> {{(node:10316) UnhandledPromiseRejectionWarning: Unhandled promise rejection.
> This error originated either by throwing inside of an async function without
> a catch block, or by rejecting a promise which was not handled with .catch().
> (rejection id: 1)}}
> {{(node:10316) [DEP0018] DeprecationWarning: Unhandled promise rejections are
> deprecated. In the future, promise rejections that are not handled will
> terminate the Node.js process with a non-zero exit code.}}
> {{[18:26:17] lint finished in 2.66 s}}{{[OK] Your app has been deployed.}}
> {{ Did you know you can live-reload changes from your app with --livereload?}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-13972) Requirements check failed for JDK 1.8 or greater
[
https://issues.apache.org/jira/browse/CB-13972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Bowser updated CB-13972:
Priority: Major (was: Blocker)
This is still a bug, but it really shouldn't block a release.
> Requirements check failed for JDK 1.8 or greater
>
>
> Key: CB-13972
> URL: https://issues.apache.org/jira/browse/CB-13972
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-cli
>Affects Versions: cordova-android-7.0.0
> Environment: Windows 10 64 (10.0.16229.248)
>Reporter: John M. Wargo
>Priority: Major
>
> I've got a problem with my Java config, but the CLI reports the error then
> reports that it's deployed the app (when it hasn't).
> {{JAVA_HOME=D:\Program Files\Java\jdk-9.0.1}}
> {{(node:10316) UnhandledPromiseRejectionWarning: CordovaError: Requirements
> check failed for JDK 1.8 or greater}}
> {{ at
> D:\dev\hardware\particle\particle-garage-controller-ionic\platforms\android\cordova\lib\check_reqs.js:370:19}}
> {{ at _fulfilled
> (D:\dev\hardware\particle\particle-garage-controller-ionic\platforms\android\cordova\node_modules\q\q.js:854:54)}}
> {{ at self.promiseDispatch.done
> (D:\dev\hardware\particle\particle-garage-controller-ionic\platforms\android\cordova\node_modules\q\q.js:883:30)}}
> {{ at Promise.promise.promiseDispatch
> (D:\dev\hardware\particle\particle-garage-controller-ionic\platforms\android\cordova\node_modules\q\q.js:816:13)}}
> {{ at
> D:\dev\hardware\particle\particle-garage-controller-ionic\platforms\android\cordova\node_modules\q\q.js:624:44}}
> {{ at runSingle
> (D:\dev\hardware\particle\particle-garage-controller-ionic\platforms\android\cordova\node_modules\q\q.js:137:13)}}
> {{ at flush
> (D:\dev\hardware\particle\particle-garage-controller-ionic\platforms\android\cordova\node_modules\q\q.js:125:13)}}
> {{ at _combinedTickCallback (internal/process/next_tick.js:131:7)}}
> {{ at process._tickCallback (internal/process/next_tick.js:180:9)}}
> {{(node:10316) UnhandledPromiseRejectionWarning: Unhandled promise rejection.
> This error originated either by throwing inside of an async function without
> a catch block, or by rejecting a promise which was not handled with .catch().
> (rejection id: 1)}}
> {{(node:10316) [DEP0018] DeprecationWarning: Unhandled promise rejections are
> deprecated. In the future, promise rejections that are not handled will
> terminate the Node.js process with a non-zero exit code.}}
> {{[18:26:17] lint finished in 2.66 s}}{{[OK] Your app has been deployed.}}
> {{ Did you know you can live-reload changes from your app with --livereload?}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-13972) Requirements check failed for JDK 1.8 or greater
[
https://issues.apache.org/jira/browse/CB-13972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16402654#comment-16402654
]
Joe Bowser commented on CB-13972:
-
OK, I set my JAVA_HOME and I still can't reproduce this issue. Are you sure
that Java 9 doesn't do something weird? I can rip out Java 8 and put in Java 9
and see if I can reproduce it, but if it breaks only on Java 9, I'm going to
say that's a feature and not a bug.
> Requirements check failed for JDK 1.8 or greater
>
>
> Key: CB-13972
> URL: https://issues.apache.org/jira/browse/CB-13972
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-cli
>Affects Versions: cordova-android-7.0.0
> Environment: Windows 10 64 (10.0.16229.248)
>Reporter: John M. Wargo
>Priority: Blocker
>
> I've got a problem with my Java config, but the CLI reports the error then
> reports that it's deployed the app (when it hasn't).
> {{JAVA_HOME=D:\Program Files\Java\jdk-9.0.1}}
> {{(node:10316) UnhandledPromiseRejectionWarning: CordovaError: Requirements
> check failed for JDK 1.8 or greater}}
> {{ at
> D:\dev\hardware\particle\particle-garage-controller-ionic\platforms\android\cordova\lib\check_reqs.js:370:19}}
> {{ at _fulfilled
> (D:\dev\hardware\particle\particle-garage-controller-ionic\platforms\android\cordova\node_modules\q\q.js:854:54)}}
> {{ at self.promiseDispatch.done
> (D:\dev\hardware\particle\particle-garage-controller-ionic\platforms\android\cordova\node_modules\q\q.js:883:30)}}
> {{ at Promise.promise.promiseDispatch
> (D:\dev\hardware\particle\particle-garage-controller-ionic\platforms\android\cordova\node_modules\q\q.js:816:13)}}
> {{ at
> D:\dev\hardware\particle\particle-garage-controller-ionic\platforms\android\cordova\node_modules\q\q.js:624:44}}
> {{ at runSingle
> (D:\dev\hardware\particle\particle-garage-controller-ionic\platforms\android\cordova\node_modules\q\q.js:137:13)}}
> {{ at flush
> (D:\dev\hardware\particle\particle-garage-controller-ionic\platforms\android\cordova\node_modules\q\q.js:125:13)}}
> {{ at _combinedTickCallback (internal/process/next_tick.js:131:7)}}
> {{ at process._tickCallback (internal/process/next_tick.js:180:9)}}
> {{(node:10316) UnhandledPromiseRejectionWarning: Unhandled promise rejection.
> This error originated either by throwing inside of an async function without
> a catch block, or by rejecting a promise which was not handled with .catch().
> (rejection id: 1)}}
> {{(node:10316) [DEP0018] DeprecationWarning: Unhandled promise rejections are
> deprecated. In the future, promise rejections that are not handled will
> terminate the Node.js process with a non-zero exit code.}}
> {{[18:26:17] lint finished in 2.66 s}}{{[OK] Your app has been deployed.}}
> {{ Did you know you can live-reload changes from your app with --livereload?}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-13980) Cordova Android app location.reload() causing app to halt
[ https://issues.apache.org/jira/browse/CB-13980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16402513#comment-16402513 ] Joe Bowser commented on CB-13980: - I'm not able to reproduce this with a bare-bones example. I'm testing with HelloWorld + Device plugin, which should not re-load if the WebView is being halted. I need more context for this issue, otherwise I'm going to close this as not a problem with Cordova. > Cordova Android app location.reload() causing app to halt > - > > Key: CB-13980 > URL: https://issues.apache.org/jira/browse/CB-13980 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-android >Affects Versions: 7.0.0, 8.0.0 > Environment: framework7.io (v1) > cordova 8 (also tested build with cordova 7) > Tested on Nexus 6p, Google Pixel 2, Samsung Galaxy s8 > Not working. >Reporter: rehan manzoor >Assignee: Joe Bowser >Priority: Major > > Cordova App was built using > framework7.io (v1) > cordova 8 (also tested build with cordova 7) > it was working fine till the latest software update from android, but now it > get stuck whenever the location.reload() is called, i tried other ways to > reload the windows e.g. > window.location.href, > location.href, > document.location.href > location.replace() > window.location.replace() > window.location.assign() > document.location.assign() > document.location.replace() > navigator.app.loadUrl() > > but all causing the app to get stuck, what I concluded from debugging it's > not the problem in function, it's maybe webview which is causing the > application to get stuck at reload. > any suggestion is appreciated. > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Closed] (CB-13513) Fastlane unable to disable automatic signing
[ https://issues.apache.org/jira/browse/CB-13513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser closed CB-13513. --- Resolution: Implemented The fix for this issue has been merged, closing. > Fastlane unable to disable automatic signing > - > > Key: CB-13513 > URL: https://issues.apache.org/jira/browse/CB-13513 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-ios >Affects Versions: cordova-ios 4.5.0 >Reporter: Paul Robinson >Assignee: Suraj Pindoria >Priority: Blocker > > Running `disable_automatic_code_signing` command in fastlane fails and throw > an error that the ios project is too old. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-13980) Cordova Android app location.reload() causing app to halt
[ https://issues.apache.org/jira/browse/CB-13980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser updated CB-13980: Priority: Major (was: Blocker) This could be literally anything. I would need to see a logcat of what's going on to see what's wrong with this application. > Cordova Android app location.reload() causing app to halt > - > > Key: CB-13980 > URL: https://issues.apache.org/jira/browse/CB-13980 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-android >Affects Versions: 7.0.0, 8.0.0 > Environment: framework7.io (v1) > cordova 8 (also tested build with cordova 7) > Tested on Nexus 6p, Google Pixel 2, Samsung Galaxy s8 > Not working. >Reporter: rehan manzoor >Assignee: Joe Bowser >Priority: Major > > Cordova App was built using > framework7.io (v1) > cordova 8 (also tested build with cordova 7) > it was working fine till the latest software update from android, but now it > get stuck whenever the location.reload() is called, i tried other ways to > reload the windows e.g. > window.location.href, > location.href, > document.location.href > location.replace() > window.location.replace() > window.location.assign() > document.location.assign() > document.location.replace() > navigator.app.loadUrl() > > but all causing the app to get stuck, what I concluded from debugging it's > not the problem in function, it's maybe webview which is causing the > application to get stuck at reload. > any suggestion is appreciated. > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-13978) Swift 3-4 support
[ https://issues.apache.org/jira/browse/CB-13978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser updated CB-13978: Priority: Major (was: Blocker) > Swift 3-4 support > - > > Key: CB-13978 > URL: https://issues.apache.org/jira/browse/CB-13978 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-cli, cordova-ios >Affects Versions: cordova-android-7.0.0 >Reporter: Peter >Assignee: Suraj Pindoria >Priority: Major > > I tried to transform the cordova-plugin-fcm to Swift, and i realized lots of > bugs. > 1, I cannot configure the use_targets! in the pod file, there is no flag for > it. > 2, the target device preference does not pick up the version. (it goes to > default 8) > 3, Automatically set some capabilities like Capabilities -> Background mode - > Remote notification in my workspace. I have no idea how to configure it > automatically. > The cordova build is failing, however the xcode version seems to me working: > ProcessProductPackaging "" > /Users/zetor/Library/Developer/Xcode/DerivedData/MyScoutee-eqekewxmsowscjfwgtlfqmttjzrv/Build/Intermediates.noindex/Pods.build/Debug-iphonesimulator/GoogleToolboxForMac.build/GoogleToolboxForMac.framework.xcent > cd /Users/zetor/Desktop/shared/myscoutee/frontend/platforms/ios/Pods > export > PATH="/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/usr/bin:/Applications/Xcode.app/Contents/Developer/usr/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin" > builtin-productPackagingUtility -entitlements -format xml -o > /Users/zetor/Library/Developer/Xcode/DerivedData/MyScoutee-eqekewxmsowscjfwgtlfqmttjzrv/Build/Intermediates.noindex/Pods.build/Debug-iphonesimulator/GoogleToolboxForMac.build/GoogleToolboxForMac.framework.xcent > warning: Falling back to contents of entitlements file > "Entitlements-Debug.plist" because it was modified during the build process. > Modifying the entitlements file during the build is unsupported.error: The > file "Entitlements-Debug.plist" couldn't be opened because there is no such > file. > * > ** BUILD FAILED ** > The following build commands failed: > ProcessProductPackaging "" > /Users/zetor/Library/Developer/Xcode/DerivedData/MyScoutee-eqekewxmsowscjfwgtlfqmttjzrv/Build/Intermediates.noindex/Pods.build/Debug-iphonesimulator/GoogleToolboxForMac.build/GoogleToolboxForMac.framework.xcent > (1 failure) > (node:2660) UnhandledPromiseRejectionWarning: Error code 65 for command: > xcodebuild with args: > -xcconfig,/Users/zetor/Desktop/shared/myscoutee/frontend/platforms/ios/cordova/build-debug.xcconfig,-workspace,MyScoutee.xcworkspace,-scheme,MyScoutee,-configuration,Debug,-sdk,iphonesimulator,-destination,platform=iOS > Simulator,name=iPhone > SE,build,CONFIGURATION_BUILD_DIR=/Users/zetor/Desktop/shared/myscoutee/frontend/platforms/ios/build/emulator,SHARED_PRECOMPS_DIR=/Users/zetor/Desktop/shared/myscoutee/frontend/platforms/ios/build/sharedpch > (node:2660) UnhandledPromiseRejectionWarning: Unhandled promise rejection. > This error originated either by throwing inside of an async function without > a catch block, or by rejecting a promise which was not handled with .catch(). > (rejection id: 1) > (node:2660) [DEP0018] DeprecationWarning: Unhandled promise rejections are > deprecated. In the future, promise rejections that are not handled will > terminate the Node.js process with a non-zero exit code. > 4, With swift 3.2 i was able to access the methods of the plugin, but with > swift4, the methods were unavailable. (the class has been identified) > There is a swift support plugin, but i would like to set the bridging header > once, instead of creating a new one. I have used a cocoapod-support plugin, > although it was not working. I think both of the them should be integrated > into the cordova. > I have wasted more than 10 hours to hack around the plugin config to make it > work. > 5, The cordova headers went to the emulator folder and it's not set in the > workspace. > 6, GoogleToolboxForMac framework was not accessible from command line, but it > was working under Xcode UI. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-13972) Requirements check failed for JDK 1.8 or greater
[
https://issues.apache.org/jira/browse/CB-13972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16401165#comment-16401165
]
Joe Bowser commented on CB-13972:
-
OK, I just installed on my new Windows box Cordova, and I didn't even have to
set the path to get it to work, but I did install Java 8. I'm guessing that
we're not finding javac for Java 9 here, which isn't a bad thing since Android
doesn't even work with Java 9. I can keep looking into it, but let me know if
downgrading to Java 8 fixes things.
> Requirements check failed for JDK 1.8 or greater
>
>
> Key: CB-13972
> URL: https://issues.apache.org/jira/browse/CB-13972
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-cli
>Affects Versions: cordova-android-7.0.0
> Environment: Windows 10 64 (10.0.16229.248)
>Reporter: John M. Wargo
>Priority: Blocker
>
> I've got a problem with my Java config, but the CLI reports the error then
> reports that it's deployed the app (when it hasn't).
> {{JAVA_HOME=D:\Program Files\Java\jdk-9.0.1}}
> {{(node:10316) UnhandledPromiseRejectionWarning: CordovaError: Requirements
> check failed for JDK 1.8 or greater}}
> {{ at
> D:\dev\hardware\particle\particle-garage-controller-ionic\platforms\android\cordova\lib\check_reqs.js:370:19}}
> {{ at _fulfilled
> (D:\dev\hardware\particle\particle-garage-controller-ionic\platforms\android\cordova\node_modules\q\q.js:854:54)}}
> {{ at self.promiseDispatch.done
> (D:\dev\hardware\particle\particle-garage-controller-ionic\platforms\android\cordova\node_modules\q\q.js:883:30)}}
> {{ at Promise.promise.promiseDispatch
> (D:\dev\hardware\particle\particle-garage-controller-ionic\platforms\android\cordova\node_modules\q\q.js:816:13)}}
> {{ at
> D:\dev\hardware\particle\particle-garage-controller-ionic\platforms\android\cordova\node_modules\q\q.js:624:44}}
> {{ at runSingle
> (D:\dev\hardware\particle\particle-garage-controller-ionic\platforms\android\cordova\node_modules\q\q.js:137:13)}}
> {{ at flush
> (D:\dev\hardware\particle\particle-garage-controller-ionic\platforms\android\cordova\node_modules\q\q.js:125:13)}}
> {{ at _combinedTickCallback (internal/process/next_tick.js:131:7)}}
> {{ at process._tickCallback (internal/process/next_tick.js:180:9)}}
> {{(node:10316) UnhandledPromiseRejectionWarning: Unhandled promise rejection.
> This error originated either by throwing inside of an async function without
> a catch block, or by rejecting a promise which was not handled with .catch().
> (rejection id: 1)}}
> {{(node:10316) [DEP0018] DeprecationWarning: Unhandled promise rejections are
> deprecated. In the future, promise rejections that are not handled will
> terminate the Node.js process with a non-zero exit code.}}
> {{[18:26:17] lint finished in 2.66 s}}{{[OK] Your app has been deployed.}}
> {{ Did you know you can live-reload changes from your app with --livereload?}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-13972) Requirements check failed for JDK 1.8 or greater
[
https://issues.apache.org/jira/browse/CB-13972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16400917#comment-16400917
]
Joe Bowser commented on CB-13972:
-
[~johnwargo] Java 9 doesn't play well with Android. We're fixing a docs error.
I don't know if that's related to your issue, but you should install Java 8.
> Requirements check failed for JDK 1.8 or greater
>
>
> Key: CB-13972
> URL: https://issues.apache.org/jira/browse/CB-13972
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-cli
>Affects Versions: cordova-android-7.0.0
> Environment: Windows 10 64 (10.0.16229.248)
>Reporter: John M. Wargo
>Priority: Blocker
>
> I've got a problem with my Java config, but the CLI reports the error then
> reports that it's deployed the app (when it hasn't).
> {{JAVA_HOME=D:\Program Files\Java\jdk-9.0.1}}
> {{(node:10316) UnhandledPromiseRejectionWarning: CordovaError: Requirements
> check failed for JDK 1.8 or greater}}
> {{ at
> D:\dev\hardware\particle\particle-garage-controller-ionic\platforms\android\cordova\lib\check_reqs.js:370:19}}
> {{ at _fulfilled
> (D:\dev\hardware\particle\particle-garage-controller-ionic\platforms\android\cordova\node_modules\q\q.js:854:54)}}
> {{ at self.promiseDispatch.done
> (D:\dev\hardware\particle\particle-garage-controller-ionic\platforms\android\cordova\node_modules\q\q.js:883:30)}}
> {{ at Promise.promise.promiseDispatch
> (D:\dev\hardware\particle\particle-garage-controller-ionic\platforms\android\cordova\node_modules\q\q.js:816:13)}}
> {{ at
> D:\dev\hardware\particle\particle-garage-controller-ionic\platforms\android\cordova\node_modules\q\q.js:624:44}}
> {{ at runSingle
> (D:\dev\hardware\particle\particle-garage-controller-ionic\platforms\android\cordova\node_modules\q\q.js:137:13)}}
> {{ at flush
> (D:\dev\hardware\particle\particle-garage-controller-ionic\platforms\android\cordova\node_modules\q\q.js:125:13)}}
> {{ at _combinedTickCallback (internal/process/next_tick.js:131:7)}}
> {{ at process._tickCallback (internal/process/next_tick.js:180:9)}}
> {{(node:10316) UnhandledPromiseRejectionWarning: Unhandled promise rejection.
> This error originated either by throwing inside of an async function without
> a catch block, or by rejecting a promise which was not handled with .catch().
> (rejection id: 1)}}
> {{(node:10316) [DEP0018] DeprecationWarning: Unhandled promise rejections are
> deprecated. In the future, promise rejections that are not handled will
> terminate the Node.js process with a non-zero exit code.}}
> {{[18:26:17] lint finished in 2.66 s}}{{[OK] Your app has been deployed.}}
> {{ Did you know you can live-reload changes from your app with --livereload?}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-13194) Http Requests and Same Origin Policy Problems on mobile devices
[ https://issues.apache.org/jira/browse/CB-13194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser resolved CB-13194. - Resolution: Not A Problem This is the issue tracker, not a help forum. It would be better to ask this on Stack Overflow, or on a similar forum. > Http Requests and Same Origin Policy Problems on mobile devices > --- > > Key: CB-13194 > URL: https://issues.apache.org/jira/browse/CB-13194 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-android >Affects Versions: cordova@7.0.0 >Reporter: Michael Burger >Priority: Major > Labels: security > > As so many others I have the problem with a RESTful service we are calling. > This service as so many others has an ORIGIN check. Using Cordova & Ionic > doing the request from android app set the origin to file:// which is good > for browser cors check but not good for the service, they doesn't allow this > schema for origin. As others the allow only empty origin or the same origin. > On many posts I read the wrote you can handle this with whitelist plugin or > with CSP. But I think this absolutly incorrect. With whitelist you can not > work on the origin header and CSP has nothing to do with it. > So the last few days I spend hundreds of hours and googled and tested > different solutions and different plugins. But the solution is not there and > not simple. > At the moment I'm testing cordova plugins for http and websocket requests, to > do native http and websocket calls, this is working great for the SOP problem > but there are some problems with cookies. > I tryied to found a solution on a Custom WebView where we can elimante the > Origin header from request but this was to difficult for us. > Can someone help on this problem? > I'm not the only guy which has to call a SOP protected resource over the > internet from a mobile hybrid app. Why there is no simple solution for it? -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-13962) Notification.beep and media.play working only a certain number on Android
[
https://issues.apache.org/jira/browse/CB-13962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Bowser resolved CB-13962.
-
Resolution: Won't Fix
This is a known issue, since it takes longer to play the sounds than it does
for the event loop to complete, eventually Android will kill the process that
does this.
> Notification.beep and media.play working only a certain number on Android
> -
>
> Key: CB-13962
> URL: https://issues.apache.org/jira/browse/CB-13962
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-android
> Environment: Phonegap Desktop with Blank Example
> and Phonegap Build with cli-6.5.0 but on lower versions the same
>Reporter: Marix
>Assignee: Joe Bowser
>Priority: Major
>
> Hello,
> i noticed that playing sound files and notification sound only working a
> certain number if it is played one after the other.
> Then it stoped working an i have to kill the app and restart.
>
> So i try the simplest example.
> In Phonegap Desktop the Blank example with:
> Play Beep
>
> // Beep
> function playBeep()
> { navigator.notification.beep(1); console.log("beep");
> }
>
>
> on Android 5.1.1 after 26 times stuck
> on Android 7.1.1 and 8.1 after *14* times stuck
> on iOS I did not observe that
>
>
> Now, i make a loop that beep every 2 sec.
>
> I explore that Android 7.1.1 beeping again after every 5 minutes but only
> then 14 times
>
> And i try lower versions of the cli.
> but that doesn't make any difference whether cli-6.5.0 (6.1.2) oder lower
> 4.1.1, 3.6.4 etc.
>
>
> And thats a huge problem.
> Example - a chat that can only make "pling" 14 times in 5 minutes?
>
>
> On android 7.1.1 and 8.1 is the intervall 5 minutes and beeping 14 times,
> on android 5.1.1 the intervall is 3 minutes and beeping 26 times
> and on android 4.4.2 it's beeping infinitive
>
> So what if it's not a problem from phonegap / cordova but from android
> itself??
>
> with Ionic the same - play 14 beeps only..
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-13971) Cannot Build Hello World App
[
https://issues.apache.org/jira/browse/CB-13971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Bowser resolved CB-13971.
-
Resolution: Won't Fix
This appears to be an issue with the version of Cordova that you're using. If
you're using Ionic, you need to upgrade to one that uses a later version of
Cordova, and you need to install Gradle on your system since it is now a
dependency. We no longer hook into Android Studio since relying on its copy of
gradle is not reliable and we have no idea what Google's plans are regarding
Android Studio.
> Cannot Build Hello World App
>
>
> Key: CB-13971
> URL: https://issues.apache.org/jira/browse/CB-13971
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-android
>Affects Versions: 8.0.0
> Environment: Operating System
> {quote}$ lsb_release -a
> No LSB modules are available.
> Distributor ID: Debian
> Description: Debian GNU/Linux 9.3 (stretch)
> Release: 9.3
> Codename: stretch
> {quote}
>
> Node
> {quote}$ node -v
> v9.7.1
> {quote}
>
> NPM
> {quote}$ npm -v
> 5.7.1
> {quote}
>
> Cordova
> {quote}$ cordova --version
> 8.0.0
> {quote}
>
> Android Studio About
> {quote}Android Studio 3.0.1
> Build #AI-171.4443003, built on November 9, 2017
> JRE: 1.8.0_152-release-915-b01 amd64
> JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
> Linux 4.9.0-4-amd64
> {quote}
>
> Android Studio SDK
> {quote}$ /usr/lib/android-sdk/tools/bin/sdkmanager --version
> 26.1.1
> {quote}
>
>
>Reporter: Aaron Suarez
>Assignee: Joe Bowser
>Priority: Major
>
> I followed the instructions for creating my first cordova app on
> [https://cordova.apache.org/docs/en/latest/guide/cli/index.html]
> I am running Debian 9.3 (Stretch), Node 9.7.1 and npm 5.7.1. I can build an
> android app using my Android Studio setup, but I cannot build a Cordova app.
> {quote}$ cordova requirements
> Android Studio project detected
> Requirements check results for android:
> Java JDK: installed 1.8.0
> Android SDK: installed true
> Android target: installed android-27,android-26,android-24
> Gradle: installed /opt/android-studio/gradle/gradle-4.1/bin/gradle
> {quote}
>
> I ran into the issue described here
> [https://github.com/ionic-team/ionic-cli/issues/2835] and when I changed the
> permissions of my gradle file, I no longer got the "spawn EACCES" error. I do
> get a different error though:
> {quote}$ cordova build android
> Android Studio project detected
> ANDROID_HOME=/usr/lib/android-sdk
> JAVA_HOME=/usr/lib/jvm/java-8-openjdk-amd64
> studio
> FAILURE: Build failed with an exception.
> * What went wrong:
> Could not initialize class org.codehaus.groovy.runtime.InvokerHelper
> * Try:
> Run with --stacktrace option to get the stack trace. Run with --info or
> --debug option to get more log output.
> * Get more help at https://help.gradle.org
> BUILD FAILED in 0s
> (node:29070) UnhandledPromiseRejectionWarning: Error:
> /opt/android-studio/gradle/gradle-4.1/bin/gradle: Command failed with exit
> code 1
> at ChildProcess.whenDone
> (/home/aaron/Omilia/cordova-toy/MyApp/platforms/android/cordova/node_modules/cordova-common/src/superspawn.js:169:23)
> at ChildProcess.emit (events.js:127:13)
> at maybeClose (internal/child_process.js:936:16)
> at Process.ChildProcess._handle.onexit (internal/child_process.js:220:5)
> (node:29070) UnhandledPromiseRejectionWarning: Unhandled promise rejection.
> This error originated either by throwing inside of an async function without
> a catch block, or by rejecting a promise which was not handled with .catch().
> (rejection id: 1)
> (node:29070) [DEP0018] DeprecationWarning: Unhandled promise rejections are
> deprecated. In the future, promise rejections that are not handled will
> terminate the Node.js process with a non-zero exit code.
> {quote}
> I'm not really sure where InvokerHelper is located. Are there additional
> dependencies that are not included in the tutorial that would fix this
> failure?
> Thanks,
> Aaron
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-13968) Geolocation doesn't work by default on Android with InAppBrowser
[ https://issues.apache.org/jira/browse/CB-13968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser updated CB-13968: Summary: Geolocation doesn't work by default on Android with InAppBrowser (was: Geolocation doesn't work bij default on Android) > Geolocation doesn't work by default on Android with InAppBrowser > > > Key: CB-13968 > URL: https://issues.apache.org/jira/browse/CB-13968 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-plugin-inappbrowser >Affects Versions: cordova-android-7.0.0 >Reporter: Corneel den Hartogh >Assignee: Joe Bowser >Priority: Major > > I use the cordova geolocation plugin, but from Android 6.0 (with introduction > of App Permissions) this is no longer working). My app does pop-up in the app > permission list, but when I click on the 'get current position'-button in the > app no permission request is send out. When I manually go to app permissions > and toggle the switch to on, the button in the app works. > On [https://github.com/apache/cordova-plugin-geolocation] I see some iOS > Quirks that help to make it work on iOS, what should I do to make it work on > Android? > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-13968) Geolocation doesn't work bij default on Android
[ https://issues.apache.org/jira/browse/CB-13968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser updated CB-13968: Component/s: (was: cordova-android) cordova-plugin-inappbrowser > Geolocation doesn't work bij default on Android > --- > > Key: CB-13968 > URL: https://issues.apache.org/jira/browse/CB-13968 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-plugin-inappbrowser >Affects Versions: cordova-android-7.0.0 >Reporter: Corneel den Hartogh >Assignee: Joe Bowser >Priority: Major > > I use the cordova geolocation plugin, but from Android 6.0 (with introduction > of App Permissions) this is no longer working). My app does pop-up in the app > permission list, but when I click on the 'get current position'-button in the > app no permission request is send out. When I manually go to app permissions > and toggle the switch to on, the button in the app works. > On [https://github.com/apache/cordova-plugin-geolocation] I see some iOS > Quirks that help to make it work on iOS, what should I do to make it work on > Android? > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-13968) Geolocation doesn't work bij default on Android
[ https://issues.apache.org/jira/browse/CB-13968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16399206#comment-16399206 ] Joe Bowser commented on CB-13968: - So, the bug is with InAppBrowser doing Geolocation? That's not something that we currently support, and that technically would be new functionality. We would have to add the permissions code in the InAppBrowser implementation since we don't have any present at this time. I'm going to move this issue over to InAppBrowser, since it's a plugin issue and not a cordova-android issue itself. > Geolocation doesn't work bij default on Android > --- > > Key: CB-13968 > URL: https://issues.apache.org/jira/browse/CB-13968 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-android >Affects Versions: cordova-android-7.0.0 >Reporter: Corneel den Hartogh >Assignee: Joe Bowser >Priority: Major > > I use the cordova geolocation plugin, but from Android 6.0 (with introduction > of App Permissions) this is no longer working). My app does pop-up in the app > permission list, but when I click on the 'get current position'-button in the > app no permission request is send out. When I manually go to app permissions > and toggle the switch to on, the button in the app works. > On [https://github.com/apache/cordova-plugin-geolocation] I see some iOS > Quirks that help to make it work on iOS, what should I do to make it work on > Android? > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-13974) With cordova-android 7.x plugins with jni libraries are not backwards compatible
[
https://issues.apache.org/jira/browse/CB-13974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16399201#comment-16399201
]
Joe Bowser commented on CB-13974:
-
I'm not at all surprised that this is breaking, since we've asked on Cordova
list as well as in the Cordova Slack for people to test JNI and had zero
responses last year. There probably should be something re-mapping the JNI
plugins to the new location like what we do with all our legacy plugins using
Java. I don't want to add custom path directives, since that's what we've been
doing for the past three years keeping the old project structure that keeps
breaking in Android Studio.
I can't really give an ETA on this, but you may have to publish a hook, or two
versions of the plugin. Realistically, I don't see much support for
Cordova-Android 6.x happening beyond security fixes in the near term.
> With cordova-android 7.x plugins with jni libraries are not backwards
> compatible
>
>
> Key: CB-13974
> URL: https://issues.apache.org/jira/browse/CB-13974
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-android
>Affects Versions: cordova-android-7.0.0
>Reporter: Doug Davies
>Assignee: Joe Bowser
>Priority: Major
> Attachments: image1.png, image2.png, image3.png
>
>
> Pull down my project on GitHub
> [https://github.com/funkyvisions/manatee-tester.git]
> It uses the 3rd party plugin (manateeworks-barcodescanner-v3) which IS
> compatible with cordova-android 6.4.0.
> Execute the following:
> {code:java}
> cordova prepare
> cordova build android{code}
> You'll see everything prepares and builds fine and you can see the libraries
> (.so files and jar) end up in the correct directories in the APK (view
> through Android Studio - Build -> Analyze APK). See image1.
> Now we are going to switch to cordova-android 7.1.0.
> Execute the following:
> {code:java}
> cp package.7.json package.json
> cp config.7.xml config.xml
> rm -rf platforms plugins
> cordova prepare
> cordova build android
> {code}
> Notice it fails. This is because the plugin.xml is incorrect (although the
> error would never lead you to discover this). So let's fix it. Unfortunately,
> I tried to fork the project and apply a patch, but there seems to be a bug
> with cordova-fetch (https://issues.apache.org/jira/browse/CB-13973), so
> instead I included it locally in this project along with the patch to
> plugin.xml.
> I changed these lines in plugin.xml:
> {code:java}
> framework="true" />
> src="src/android/src/com/manateeworks/BarcodeScannerPlugin.java"
> target-dir="src/com/manateeworks" />
> target-dir="src/com/manateeworks" />
> target-dir="res/layout" />
> target-dir="res/drawable" />
> target-dir="res/drawable-hdpi" />
> target-dir="res/drawable" />
> target-dir="res/drawable" />
> target-dir="res/drawable" />
> target-dir="libs/armeabi" />
> target-dir="libs/x86" />
> target-dir="libs/armeabi-v7a" />
> target-dir="libs/arm64-v8a" />
> target-dir="libs/mips" />
> {code}
> to this:
> {code:java}
>
>
>
> target="jniLibs/mwbscanner.jar" />
>
> src="src/android/src/com/manateeworks/BarcodeScannerPlugin.java"
> target-dir="src/com/manateeworks" />
> target-dir="src/com/manateeworks" />
>
> target="res/layout/scanner.xml" />
> target="res/drawable/overlay_mw.png" />
> target="res/drawable-hdpi/overlay_mw.png" />
> target="res/drawable/flashbuttonoff.png" />
> target="res/drawable/flashbuttonon.png" />
> target="res/drawable/zoom.png" />
>
> target="jniLibs/armeabi/libBarcodeScannerLib.so" />
> target="jniLibs/x86/libBarcodeScannerLib.so" />
> target="jniLibs/armeabi-v7a/libBarcodeScannerLib.so" />
> target="jniLibs/arm64-v8a/libBarcodeScannerLib.so" />
> target="jniLibs/mips/libBarcodeScannerLib.so" />
> {code}
> Now let's switch to the forked version of the plugin and see if it works.
> Execute the following:
> {code:java}
> cp package.fork.json package.json
> cp config.fork.xml config.xml
> rm -rf platforms plugins
> cordova prepare
> cordova build android{code}
> Now you see it builds once again and the APK is correct. See image2.
> However, the directives I put in plugin.xml are not backwards compatible with
> 6.4.0. We can prove this by now switch back to cordova-android 6.4.0 and
> trying to build.
> {code:java}
> cp package.6.json package.json
> cp config.6.xml config.xml
> rm -rf platforms plugins
> cordova prepare
> cordova build android{code}
> Now look at the APK and you will see the libraries are missing. See image3.
> In order to fix this, I have to create a mix on the old config plus the new.
> See
>
[jira] [Resolved] (CB-12593) FileProvider conflict in the camera plugin
[
https://issues.apache.org/jira/browse/CB-12593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Bowser resolved CB-12593.
-
Resolution: Fixed
> FileProvider conflict in the camera plugin
> --
>
> Key: CB-12593
> URL: https://issues.apache.org/jira/browse/CB-12593
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-plugin-camera
>Reporter: Connor Pearson
>Priority: Major
> Labels: android-next
>
> Version 2.3.1 of the camera plugin adds a FileProvider to the
> AndroidManifest. I already have a plugin that is doing this, so the duplicate
> entries cause a build error.
> {code}
> Element provider#android.support.v4.content.FileProvider at
> AndroidManifest.xml:19:9-21:20 duplicated with element declared at
> AndroidManifest.xml:16:9-18:20
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-13958) Android: hideCustomView() getting called immediately after iFrame YouTube Fullscreen click
[ https://issues.apache.org/jira/browse/CB-13958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser resolved CB-13958. - Resolution: Won't Fix This smells like a browser based bug, and I'm going to close it as such for right now. Without more information, I can't really do anything else with this issue. > Android: hideCustomView() getting called immediately after iFrame YouTube > Fullscreen click > -- > > Key: CB-13958 > URL: https://issues.apache.org/jira/browse/CB-13958 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-android >Affects Versions: cordova-android-7.0.0 > Environment: Sencha Touch >Reporter: Justin Henricks >Assignee: Joe Bowser >Priority: Major > > When I click on full screen on my YouTube iFrame video in my app, > hideCustomView is getting called immediately. > > My application is using the Sencha Framework and the video I am trying to > view is in the itemTpl of a DataView.List component. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Comment Edited] (CB-13958) Android: hideCustomView() getting called immediately after iFrame YouTube Fullscreen click
[ https://issues.apache.org/jira/browse/CB-13958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16396088#comment-16396088 ] Joe Bowser edited comment on CB-13958 at 3/13/18 11:06 PM: --- I'm going to need a lot more information. Are you using a third party plugin to listen for hideCustomView()? This isn't a standard part of Cordova, and is more lower-level Android code. was (Author: bowserj): I'm going to need a lot more information. Are you using a third party plugin to listen for hideCustomView()? This isn't a standard part of Cordova. > Android: hideCustomView() getting called immediately after iFrame YouTube > Fullscreen click > -- > > Key: CB-13958 > URL: https://issues.apache.org/jira/browse/CB-13958 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-android >Affects Versions: cordova-android-7.0.0 > Environment: Sencha Touch >Reporter: Justin Henricks >Assignee: Joe Bowser >Priority: Major > > When I click on full screen on my YouTube iFrame video in my app, > hideCustomView is getting called immediately. > > My application is using the Sencha Framework and the video I am trying to > view is in the itemTpl of a DataView.List component. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-13968) Geolocation doesn't work bij default on Android
[ https://issues.apache.org/jira/browse/CB-13968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser resolved CB-13968. - Resolution: Cannot Reproduce We use the browser geolocation, and all the plugin does is manage the permission for Geolocation. We're unable to reproduce this issue on our end on a Pixel 2 or a Samsung Galaxy S8. I could grab older devices and try to reproduce, but this is a very basic plugin. It's possible that your browser isn't able to get a location due to how you're calling Geolocation, and whether you're enabling high accuracy or not. > Geolocation doesn't work bij default on Android > --- > > Key: CB-13968 > URL: https://issues.apache.org/jira/browse/CB-13968 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-android >Affects Versions: cordova-android-7.0.0 >Reporter: Corneel den Hartogh >Assignee: Joe Bowser >Priority: Major > > I use the cordova geolocation plugin, but from Android 6.0 (with introduction > of App Permissions) this is no longer working). My app does pop-up in the app > permission list, but when I click on the 'get current position'-button in the > app no permission request is send out. When I manually go to app permissions > and toggle the switch to on, the button in the app works. > On [https://github.com/apache/cordova-plugin-geolocation] I see some iOS > Quirks that help to make it work on iOS, what should I do to make it work on > Android? > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Assigned] (CB-13963) Android platform guide is misleading
[ https://issues.apache.org/jira/browse/CB-13963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser reassigned CB-13963: --- Assignee: Jan Piotrowski (Sujan) (was: Joe Bowser) Close this once you accept the PR. Thanks! > Android platform guide is misleading > > > Key: CB-13963 > URL: https://issues.apache.org/jira/browse/CB-13963 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-android >Affects Versions: cordova-android-7.0.0 > Environment: windows 10 - irrelevant >Reporter: Gabe O'Leary >Assignee: Jan Piotrowski (Sujan) >Priority: Major > Attachments: image-2018-03-09-11-40-09-278.png > > > The Android Platform guide specifies to install JDK8 or later. I just wasted > a bunch of time installing and uninstall jdk9 which does not work with > cordova. > !image-2018-03-09-11-40-09-278.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-13958) Android: hideCustomView() getting called immediately after iFrame YouTube Fullscreen click
[ https://issues.apache.org/jira/browse/CB-13958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16396088#comment-16396088 ] Joe Bowser commented on CB-13958: - I'm going to need a lot more information. Are you using a third party plugin to listen for hideCustomView()? This isn't a standard part of Cordova. > Android: hideCustomView() getting called immediately after iFrame YouTube > Fullscreen click > -- > > Key: CB-13958 > URL: https://issues.apache.org/jira/browse/CB-13958 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-android >Affects Versions: cordova-android-7.0.0 > Environment: Sencha Touch >Reporter: Justin Henricks >Assignee: Joe Bowser >Priority: Major > > When I click on full screen on my YouTube iFrame video in my app, > hideCustomView is getting called immediately. > > My application is using the Sencha Framework and the video I am trying to > view is in the itemTpl of a DataView.List component. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-13923) CordovaResourceApi.java method OpenForReadResult returns a -1 length
[
https://issues.apache.org/jira/browse/CB-13923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Bowser resolved CB-13923.
-
Resolution: Fixed
> CordovaResourceApi.java method OpenForReadResult returns a -1 length
>
>
> Key: CB-13923
> URL: https://issues.apache.org/jira/browse/CB-13923
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-android
>Affects Versions: cordova-android-7.0.0
> Environment: cordova 8.0.0
> cordova-android 7.0.0
> cordova-plugin-file 6.0.1
>Reporter: Anthony Ward
>Assignee: Joe Bowser
>Priority: Major
>
> Here are details to recreate:
> [https://github.com/AnthonyWard/cordova-file-plugin-bug]
> In *cordova-android* the CordovaResourceApi.java -> OpenForReadResult method
> returns a -1 length in certain circumstances.
> This has a knock on effect to the *cordova-plugin-file* > Filesystem.java >
> readFileAtURL method, causing file corruption as each chunk effectively has
> no end.
> There is a possible fix in the plugin cordova-plugin-file already proposed
> [https://github.com/apache/cordova-plugin-file/pull/217]
> https://issues.apache.org/jira/browse/CB-13245?jql=text%20~%20%22CordovaResourceApi%22
> Or I propose it could be fixed upstream in cordova-android here:
> [https://github.com/apache/cordova-android/blob/master/framework/src/org/apache/cordova/CordovaResourceApi.java]
> In the method OpenForReadResult there is one path (in the catch) that leaves
> the length as -1 causing the defect
> try
> {
> assetFd = assetManager.openFd(assetPath);
> inputStream = assetFd.createInputStream(); length = assetFd.getLength();
> }
> catch (FileNotFoundException e)
> {
> // Will occur if the file is compressed.
> inputStream = assetManager.open(assetPath);
> }
> Adding length = inputStream.available(); in the catch fixes the issue for me,
> but I'm not a java developer so can't evaluate if that's a bad idea for
> another reason.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-13961) Cordova failed to execute aapt bug
[
https://issues.apache.org/jira/browse/CB-13961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Bowser resolved CB-13961.
-
Resolution: Won't Fix
This is a Crosswalk Error, and Crosswalk isn't supported anymore, so there's
nothing that we can do here. Sorry!
> Cordova failed to execute aapt bug
> --
>
> Key: CB-13961
> URL: https://issues.apache.org/jira/browse/CB-13961
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-android
>Affects Versions: cordova-android-7.0.0
> Environment: Windows 10
> Android target 26
> Plugins list:
> cordova-plugin-admobpro 2.31.1 "AdMob Plugin Pro"
> cordova-plugin-crosswalk-webview 2.4.0 "Crosswalk WebView Engine"
> cordova-plugin-dialogs 2.0.1 "Notification"
> cordova-plugin-extension 1.5.4 "Cordova Plugin Extension"
> cordova-plugin-file 6.0.1 "File"
> cordova-plugin-http 1.1.0 "SSL Pinning"
> cordova-plugin-vibration 3.0.1 "Vibration"
> cordova-plugin-whitelist 1.3.3 "Whitelist"
>Reporter: Marc
>Assignee: Joe Bowser
>Priority: Major
>
> I am recieveing an error on ":app:processArm64DebugResources" when building
> for android 7.0.0. The error message states "failed to execute aapt" during
> the build. This error is strange as my cordova project was working before,
> and then suddenly got this error, it is not affecting any other cordova
> projects when I build them.
> I am new to cordova so if I have missed any information please ask.
> {code:java}
> $ cordova run android --device
> You have been opted out of telemetry. To change this, run: cordova telemetry
> on.
> Android Studio project detected
> You have been opted out of telemetry. To change this, run: cordova telemetry
> on.
> Requirements check results for android:
> Java JDK: installed 1.8.0
> Android SDK: installed true
> Android target: installed android-27,android-26,android-19
> Gradle: installed C:\Program Files\Android\Android
> Studio\gradle\gradle-4.1\bin\gradle
> Requirements check results for browser:
> (node:12804) UnhandledPromiseRejectionWarning: Unhandled promise rejection
> (rejection id: 1): TypeError: Cannot read property 'forEach' of undefined
> Android Studio project detected
> ANDROID_HOME=C:\Users\user\AppData\Local\Android\Sdk
> JAVA_HOME=C:\Program Files\Java\jdk1.8.0_45
> studio
> Subproject Path: CordovaLib
> Subproject Path: app
> publishNonDefault is deprecated and has no effect anymore. All variants are
> now published.
> Configuration 'compile' in project ':app' is deprecated. Use 'implementation'
> instead.
> null
> The Task.leftShift(Closure) method has been deprecated and is scheduled to be
> removed in Gradle 5.0. Please use Task.doLast(Action) instead.
> at
> build_c29bnu6ebta03cjhtpc9mt2gp.run(C:\Users\user\Documents\Coding\Project
> Grid\grid\platforms\android\app\build.gradle:145)
> org.xwalk:xwalk_core_library:23+
> :CordovaLib:preBuild UP-TO-DATE
> :CordovaLib:preDebugBuild UP-TO-DATE
> :CordovaLib:compileDebugAidl UP-TO-DATE
> :CordovaLib:compileDebugRenderscript UP-TO-DATE
> :CordovaLib:checkDebugManifest UP-TO-DATE
> :CordovaLib:generateDebugBuildConfig UP-TO-DATE
> :CordovaLib:prepareLintJar UP-TO-DATE
> :CordovaLib:generateDebugResValues UP-TO-DATE
> :CordovaLib:generateDebugResources UP-TO-DATE
> :CordovaLib:packageDebugResources UP-TO-DATE
> :CordovaLib:platformAttrExtractor UP-TO-DATE
> :CordovaLib:processDebugManifest UP-TO-DATE
> :CordovaLib:processDebugResources UP-TO-DATE
> :CordovaLib:generateDebugSources UP-TO-DATE
> :CordovaLib:javaPreCompileDebug UP-TO-DATE
> :CordovaLib:compileDebugJavaWithJavac UP-TO-DATE
> :CordovaLib:processDebugJavaRes NO-SOURCE
> :CordovaLib:transformClassesAndResourcesWithPrepareIntermediateJarsForDebug
> UP-TO-DATE
> :app:preBuild UP-TO-DATE
> :app:preArm64DebugBuild UP-TO-DATE
> :app:compileArm64DebugAidl UP-TO-DATE
> :CordovaLib:packageDebugRenderscript NO-SOURCE
> :app:compileArm64DebugRenderscript UP-TO-DATE
> :app:checkArm64DebugManifest UP-TO-DATE
> :app:generateArm64DebugBuildConfig UP-TO-DATE
> :app:prepareLintJar UP-TO-DATE
> :CordovaLib:mergeDebugShaders UP-TO-DATE
> :CordovaLib:compileDebugShaders UP-TO-DATE
> :CordovaLib:generateDebugAssets UP-TO-DATE
> :CordovaLib:mergeDebugAssets UP-TO-DATE
> :app:mergeArm64DebugShaders UP-TO-DATE
> :app:compileArm64DebugShaders UP-TO-DATE
> :app:generateArm64DebugAssets UP-TO-DATE
> :app:mergeArm64DebugAssets UP-TO-DATE
> :app:createXwalkCommandLineFileArm64Debug
> :app:generateArm64DebugResValues UP-TO-DATE
> :app:generateArm64DebugResources UP-TO-DATE
> :app:mergeArm64DebugResources UP-TO-DATE
> :app:createArm64DebugCompatibleScreenManifests UP-TO-DATE
> :app:processArm64DebugManifest UP-TO-DATE
> :app:splitsDiscoveryTaskArm64Debug UP-TO-DATE
>
[jira] [Commented] (CB-13929) duplicate entry: android/support/v13/view/DragStartHelper$OnDragStartListener.class
[
https://issues.apache.org/jira/browse/CB-13929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16386843#comment-16386843
]
Joe Bowser commented on CB-13929:
-
There's some third party plugins there that could be including support twice
after the recent update. This is why we've been trying to avoid using the
support library in Cordova for so long, since it could easily cause problems
like this in the gradle file. Do you have the generated gradle file handy,
namely the part where it's including the different libraries?
> duplicate entry:
> android/support/v13/view/DragStartHelper$OnDragStartListener.class
> ---
>
> Key: CB-13929
> URL: https://issues.apache.org/jira/browse/CB-13929
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-android
>Affects Versions: cordova@7.0.0
>Reporter: Daniel Ramos
>Assignee: Joe Bowser
>Priority: Major
>
> Hello Cordova team.
>
> Today I've launched my app build in Jenkins as always, and it gives me the
> following error:
>
> {code:java}
> ...
> Note: Recompile with -Xlint:unchecked for details.
> :compileArmv7DebugNdk UP-TO-DATE
> :compileArmv7DebugSources
> :transformClassesWithJarMergingForArmv7Debug FAILED
> FAILURE: Build failed with an exception.
> * What went wrong:
> Execution failed for task ':transformClassesWithJarMergingForArmv7Debug'.
> > com.android.build.api.transform.TransformException:
> java.util.zip.ZipException: duplicate entry:
> android/support/v13/view/DragStartHelper$OnDragStartListener.class
> {code}
> I've been investigating what could have caused this issue, and the only thing
> that I can find that is different from previous builds, is an update that
> Cordova did over support-v4.
> Here is the log diff:
> [https://gist.github.com/DanielRamosAcosta/29f3223c3b8f96447814122bfc193f08]
> Cordova version & plugins:
> {code}
> "dependencies": {
> "cordova": "^7.1.0",
> "cordova-android": "^6.4.0",
> "cordova-plugin-android-permissions": "^1.0.0",
> "cordova-plugin-crosswalk-webview": "^2.3.0",
> "cordova-plugin-dbmeter": "^2.1.0",
> "cordova-plugin-screen-orientation": "^3.0.1",
> "cordova-plugin-statusbar": "^2.4.1",
> "cordova-plugin-whitelist": "^1.3.3",
> "cordova-plugin-x-socialsharing": "^5.2.1",
> "es6-promise-plugin": "^4.1.1"
> },
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-13943) ERR_FILE_NOT_FOUND — deep linking issue
[ https://issues.apache.org/jira/browse/CB-13943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser resolved CB-13943. - Resolution: Won't Fix This is an angular routing issue, not a Cordova issue: https://stackoverflow.com/questions/15105910/angular-ng-view-routing-not-working-in-phonegap > ERR_FILE_NOT_FOUND — deep linking issue > --- > > Key: CB-13943 > URL: https://issues.apache.org/jira/browse/CB-13943 > Project: Apache Cordova > Issue Type: Bug > Environment: Android — any > Cordova — 6.5.0 >Reporter: Arthur Mudrick >Priority: Major > Attachments: > Screenshot_2018-02-28-15-18-50-964_ru.balumates.balu.png, > Screenshot_2018-02-28-15-55-56-348_ru.balumates.balu.png > > > I use Angular with Cordova. Angular uses URL routing, e.g. `/login` for the > Login page, '/settings' for the Settings page, etc. > When Android application updates (when new application version is installed) > Cordova is like «reloads» itself or something, but the path in the address > bar was `/login` or `/users` or `/settings` etc., so, Cordova thinks it is a > folder. > Cordova throws an error — see screenshot #1 — there is a path `/www/login` > but the `/login` is just Angular's routing, not a folder to search for :) > I also tried to make Angular work with hashbang url strategy, e.g. `/#/login` > rather than `/login` — it throws another error, see screenshot #2. > So, basically Cordova behaves like a server without the `mod_rewrite` option > — it tries to find folders inside the `/www` folder. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-13947) Back button behavior doesn't revert to default when removing listeners
[ https://issues.apache.org/jira/browse/CB-13947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser updated CB-13947: Component/s: cordova-js > Back button behavior doesn't revert to default when removing listeners > -- > > Key: CB-13947 > URL: https://issues.apache.org/jira/browse/CB-13947 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-android, cordova-js >Affects Versions: cordova-android-7.0.0 >Reporter: Cedric Reichenbach >Assignee: Joe Bowser >Priority: Major > > When adding a `backbutton` event listener to `document`, Cordova disables > default back button behavior (which is usually closing the app). > Later, when removing the last event listener, it should re-enable default > behavior, but does not. > h2. Technical details > Internally, cordova seems to use a channel to handle document event listener > registrations, which should update the override state on every listener > addition/removal: > [https://github.com/apache/cordova-android/blob/eddad666ff60129bf716cee61c24d3d65741640f/bin/templates/project/assets/www/cordova.js#L1664] > However, debugging indicates that `onHasSubscribersChange` is only triggered > once, when adding a listener for the first time, but never on removal. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-13953) Cordova has a hard dependency on Gradle being on the path and JAVA_HOME being set in advance
[ https://issues.apache.org/jira/browse/CB-13953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16386576#comment-16386576 ] Joe Bowser commented on CB-13953: - The wrapper is in gitignore because Apache policy prevents us from committing the Gradle Wrapper. The reason we use wrapper.gradle is so that we can generate the wrapper. We do not plan on supporting any Gradle Wrapper customization, since we lack the ability to do so due to the ASF policy on bundling gradle. > Cordova has a hard dependency on Gradle being on the path and JAVA_HOME being > set in advance > > > Key: CB-13953 > URL: https://issues.apache.org/jira/browse/CB-13953 > Project: Apache Cordova > Issue Type: Improvement > Components: cordova-android >Affects Versions: cordova-android-7.0.0 > Environment: android build >Reporter: armin >Assignee: Joe Bowser >Priority: Minor > Original Estimate: 8h > Remaining Estimate: 8h > > Cordova is tightly coupled with the gradle executable and it is verifying it > being on the path even though the gradle wrapper is available. Also the > JAVA_HOME has to be already available or java be on the path before running > cordova commands even though these can be set during the build. > In general there are several problems with the current gradle bootstrapping > process: > * Cordova checks for gradle being on the path and fails execution if it > isn't there even though the wrapper is already generated so gradle is not > needed at that point. The wrapper files are also on .gitignore for no reason > since committing them is fairly standard practice and they could be bundled > with cordova from the beginning to avoid dependency on gradle in general and > to tie the gradle version to the cordova version. > * In general the checks inside cordova are not sufficient to determine if a > given "requirement" is available (or will be set during the build) or not, it > should be possible to continue the build even if the build-in requirement > checks fail > * The gradle wrapper is generated by Cordova instead of the user as it > should be and as it is the gradle convention -> this means any customization > process is extremely difficult and we have no control. It is understandable > to tie the gradle version to a cordova version but this version check should > be done during execution and not before so the users can manage their own > wrapper > * Cordova is using a separate gradle file for generating the wrapper and not > the actual build.gradle file -> wrapper.gradle is being used for generation > which means any configuration from build.gradle is not respected, such as > wrapper version or wrapper customization (for example we also generate the > JAVA_HOME variable into the wrapper so we would not need java or gradle on > the path at all after the initial install, as we only have a local > installations) -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-13953) Cordova has a hard dependency on Gradle being on the path and JAVA_HOME being set in advance
[ https://issues.apache.org/jira/browse/CB-13953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser resolved CB-13953. - Resolution: Won't Fix > Cordova has a hard dependency on Gradle being on the path and JAVA_HOME being > set in advance > > > Key: CB-13953 > URL: https://issues.apache.org/jira/browse/CB-13953 > Project: Apache Cordova > Issue Type: Improvement > Components: cordova-android >Affects Versions: cordova-android-7.0.0 > Environment: android build >Reporter: armin >Assignee: Joe Bowser >Priority: Minor > Original Estimate: 8h > Remaining Estimate: 8h > > Cordova is tightly coupled with the gradle executable and it is verifying it > being on the path even though the gradle wrapper is available. Also the > JAVA_HOME has to be already available or java be on the path before running > cordova commands even though these can be set during the build. > In general there are several problems with the current gradle bootstrapping > process: > * Cordova checks for gradle being on the path and fails execution if it > isn't there even though the wrapper is already generated so gradle is not > needed at that point. The wrapper files are also on .gitignore for no reason > since committing them is fairly standard practice and they could be bundled > with cordova from the beginning to avoid dependency on gradle in general and > to tie the gradle version to the cordova version. > * In general the checks inside cordova are not sufficient to determine if a > given "requirement" is available (or will be set during the build) or not, it > should be possible to continue the build even if the build-in requirement > checks fail > * The gradle wrapper is generated by Cordova instead of the user as it > should be and as it is the gradle convention -> this means any customization > process is extremely difficult and we have no control. It is understandable > to tie the gradle version to a cordova version but this version check should > be done during execution and not before so the users can manage their own > wrapper > * Cordova is using a separate gradle file for generating the wrapper and not > the actual build.gradle file -> wrapper.gradle is being used for generation > which means any configuration from build.gradle is not respected, such as > wrapper version or wrapper customization (for example we also generate the > JAVA_HOME variable into the wrapper so we would not need java or gradle on > the path at all after the initial install, as we only have a local > installations) -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-13947) Back button behavior doesn't revert to default when removing listeners
[ https://issues.apache.org/jira/browse/CB-13947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16386578#comment-16386578 ] Joe Bowser commented on CB-13947: - This sounds more like a cordova-js error than a cordova-android error. > Back button behavior doesn't revert to default when removing listeners > -- > > Key: CB-13947 > URL: https://issues.apache.org/jira/browse/CB-13947 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-android, cordova-js >Affects Versions: cordova-android-7.0.0 >Reporter: Cedric Reichenbach >Assignee: Joe Bowser >Priority: Major > > When adding a `backbutton` event listener to `document`, Cordova disables > default back button behavior (which is usually closing the app). > Later, when removing the last event listener, it should re-enable default > behavior, but does not. > h2. Technical details > Internally, cordova seems to use a channel to handle document event listener > registrations, which should update the override state on every listener > addition/removal: > [https://github.com/apache/cordova-android/blob/eddad666ff60129bf716cee61c24d3d65741640f/bin/templates/project/assets/www/cordova.js#L1664] > However, debugging indicates that `onHasSubscribersChange` is only triggered > once, when adding a listener for the first time, but never on removal. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-13840) Support Widevine in Cordova webviews
[ https://issues.apache.org/jira/browse/CB-13840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16342901#comment-16342901 ] Joe Bowser commented on CB-13840: - I do think improvements to this behaviour and making Android Permissions play nice with WebView permissions when appropriate would be a nice contribution to Cordova, but I don't think we have the bandwidth for this, especially since I'm on sabbatical right now. > Support Widevine in Cordova webviews > > > Key: CB-13840 > URL: https://issues.apache.org/jira/browse/CB-13840 > Project: Apache Cordova > Issue Type: Improvement > Components: cordova-android >Affects Versions: cordova-android-7.0.0 > Environment: I have tested with cordova-android 6.3 and 7.0 on > Android 6.0.1. >Reporter: Pierre Rudloff >Assignee: Joe Bowser >Priority: Major > > I'm developing an app that needs to play DRM media. > On Android Chrome it uses Widevine, but it does not seem to be available in > Cordova. > According to [this Chromium > ticket|https://bugs.chromium.org/p/chromium/issues/detail?id=526058] there is > a permission request that needs to be handled when creating the webview. > (As a workaround we use Crosswalk, [which does support > Widevine|https://github.com/crosswalk-project/crosswalk/pull/3147/commits/0124ee94107e3dc21c16f3748c2fee2315bbaca5], > but it is not maintained anymore...) -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-13840) Support Widevine in Cordova webviews
[ https://issues.apache.org/jira/browse/CB-13840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16342900#comment-16342900 ] Joe Bowser commented on CB-13840: - It seems that I accepted this PR, although I don't remember why since I didn't think it was going to work. That being said, the host application might have to request a permission to play this media from Android, since the original issue CB-9115 was left open since I thought Marshmallow was going to blow this up. It might make sense for a call to the plugins to be here and for the permission to be added instead, and for the original approach to be followed. I really don't like having a paper trail for this issue, and perhaps I had a mind lapse corresponding Jira discussions to GitHub discussions (I hope this migrates to GitHub issues soon), or there was something that happened on Slack (which of course is lost due to it being a free plan). > Support Widevine in Cordova webviews > > > Key: CB-13840 > URL: https://issues.apache.org/jira/browse/CB-13840 > Project: Apache Cordova > Issue Type: Improvement > Components: cordova-android >Affects Versions: cordova-android-7.0.0 > Environment: I have tested with cordova-android 6.3 and 7.0 on > Android 6.0.1. >Reporter: Pierre Rudloff >Assignee: Joe Bowser >Priority: Major > > I'm developing an app that needs to play DRM media. > On Android Chrome it uses Widevine, but it does not seem to be available in > Cordova. > According to [this Chromium > ticket|https://bugs.chromium.org/p/chromium/issues/detail?id=526058] there is > a permission request that needs to be handled when creating the webview. > (As a workaround we use Crosswalk, [which does support > Widevine|https://github.com/crosswalk-project/crosswalk/pull/3147/commits/0124ee94107e3dc21c16f3748c2fee2315bbaca5], > but it is not maintained anymore...) -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Created] (CB-13838) Use android-versions in emulator.js for picking AVD
Joe Bowser created CB-13838: --- Summary: Use android-versions in emulator.js for picking AVD Key: CB-13838 URL: https://issues.apache.org/jira/browse/CB-13838 Project: Apache Cordova Issue Type: Improvement Reporter: Joe Bowser Fix For: android-7.2 We should stop doing the same task over and over again. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-13838) Use android-versions in emulator.js for picking AVD
[ https://issues.apache.org/jira/browse/CB-13838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser updated CB-13838: Component/s: cordova-android > Use android-versions in emulator.js for picking AVD > --- > > Key: CB-13838 > URL: https://issues.apache.org/jira/browse/CB-13838 > Project: Apache Cordova > Issue Type: Improvement > Components: cordova-android >Reporter: Joe Bowser >Priority: Trivial > Fix For: android-7.2 > > > We should stop doing the same task over and over again. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-13818) Need to update android_sdk.js to Support Android 8.0
[
https://issues.apache.org/jira/browse/CB-13818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Bowser resolved CB-13818.
-
Resolution: Fixed
> Need to update android_sdk.js to Support Android 8.0
> -
>
> Key: CB-13818
> URL: https://issues.apache.org/jira/browse/CB-13818
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-android
>Affects Versions: cordova-android-7.0.0
> Environment: Cordova 7.1.0
>
>Reporter: Zhao Bin
>Assignee: Joe Bowser
>Priority: Major
> Labels: easyfix
> Fix For: cordova-android-7.0.0
>
> Attachments: android_sdk.js error.png
>
>
> Currently I am working on a Cordova project and I am migrating to the new
> Android 8.0 emulator.
> Need to update android_sdk.js to add support for Android 8.0 emulator
> cordova-android / bin / templates / cordova / lib / android_sdk.js Line 53:
> module.exports.version_string_to_api_level = {
> '4.0': 14,
> '4.0.3': 15,
> '4.1': 16,
> '4.2': 17,
> '4.3': 18,
> '4.4': 19,
> '4.4W': 20,
> '5.0': 21,
> '5.1': 22,
> '6.0': 23,
> '7.0': 24,
> '7.1.1': 25
> };
> This causes exception in emulator.js Line 210
> {color:#5fdfff}var{color}{color:#dfdfdf} project_target
> {color}{color:#ff1f7f}={color}{color:#dfdfdf}
> check_reqs.{color}{color:#9fdf2f}get_target{color}{color:#dfdfdf}().{color}{color:#5fdfff}replace{color}{color:#dfdfdf}({color}{color:#dfdf7f}'android-'{color}{color:#dfdfdf},
> {color}{color:#dfdf7f}''{color}{color:#dfdfdf});{color}
>
> {color:#33}I added '8.0': 26 in android_sdk.js and then it works.{color}
> {color:#33}module.exports.version_string_to_api_level = {
> '4.0': 14,
> '4.0.3': 15,
> '4.1': 16,
> '4.2': 17,
> '4.3': 18,
> '4.4': 19,
> '4.4W': 20,
> '5.0': 21,
> '5.1': 22,
> '6.0': 23,
> '7.0': 24,
> '7.1.1': 25,{color}
> {color:#33} '8.0': 26
> };{color}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-13818) Need to update android_sdk.js to Support Android 8.0
[
https://issues.apache.org/jira/browse/CB-13818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Bowser updated CB-13818:
Priority: Major (was: Critical)
I'm not going to say this was critical because I couldn't reproduce it, but
yeah, this did need to be done. In the long run, we should use
android-versions for this.
> Need to update android_sdk.js to Support Android 8.0
> -
>
> Key: CB-13818
> URL: https://issues.apache.org/jira/browse/CB-13818
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-android
>Affects Versions: cordova-android-7.0.0
> Environment: Cordova 7.1.0
>
>Reporter: Zhao Bin
>Assignee: Joe Bowser
>Priority: Major
> Labels: easyfix
> Fix For: cordova-android-7.0.0
>
> Attachments: android_sdk.js error.png
>
>
> Currently I am working on a Cordova project and I am migrating to the new
> Android 8.0 emulator.
> Need to update android_sdk.js to add support for Android 8.0 emulator
> cordova-android / bin / templates / cordova / lib / android_sdk.js Line 53:
> module.exports.version_string_to_api_level = {
> '4.0': 14,
> '4.0.3': 15,
> '4.1': 16,
> '4.2': 17,
> '4.3': 18,
> '4.4': 19,
> '4.4W': 20,
> '5.0': 21,
> '5.1': 22,
> '6.0': 23,
> '7.0': 24,
> '7.1.1': 25
> };
> This causes exception in emulator.js Line 210
> {color:#5fdfff}var{color}{color:#dfdfdf} project_target
> {color}{color:#ff1f7f}={color}{color:#dfdfdf}
> check_reqs.{color}{color:#9fdf2f}get_target{color}{color:#dfdfdf}().{color}{color:#5fdfff}replace{color}{color:#dfdfdf}({color}{color:#dfdf7f}'android-'{color}{color:#dfdfdf},
> {color}{color:#dfdf7f}''{color}{color:#dfdfdf});{color}
>
> {color:#33}I added '8.0': 26 in android_sdk.js and then it works.{color}
> {color:#33}module.exports.version_string_to_api_level = {
> '4.0': 14,
> '4.0.3': 15,
> '4.1': 16,
> '4.2': 17,
> '4.3': 18,
> '4.4': 19,
> '4.4W': 20,
> '5.0': 21,
> '5.1': 22,
> '6.0': 23,
> '7.0': 24,
> '7.1.1': 25,{color}
> {color:#33} '8.0': 26
> };{color}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Closed] (CB-13831) Update `android-versions` npm dependency to support Android API 27.
[
https://issues.apache.org/jira/browse/CB-13831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Bowser closed CB-13831.
---
Resolution: Fixed
> Update `android-versions` npm dependency to support Android API 27.
> ---
>
> Key: CB-13831
> URL: https://issues.apache.org/jira/browse/CB-13831
> Project: Apache Cordova
> Issue Type: Task
> Components: cordova-android
>Reporter: Jesse Rosenberger
>Assignee: Joe Bowser
>Priority: Trivial
>
> The current version of {{cordova-android}} currently bundles (via
> {{package.json}}'s {{bundledDependencies}} attribute) a version of the
> [{{android-versions}} npm|https://npm.im/android-versions] which doesn't
> support Android SDK level 27, which was officially released in the last month.
> This omission prevents the use of {{cordova run android --emulator -d}} if
> API level 27 is installed, which is the default SDK for a new installation of
> Android Studio. It also contributed to the error seen in CB-13571, though
> that will prevent the same error from occurring in the future if an
> additional SDK is released and not included in {{android-versions}}.
> While the latest version of {{android-versions}} (currently 1.3.0) does
> support level 27 (now, thanks to [this recent
> commit|https://github.com/dvoiss/android-versions/commit/230957205eeb26e569096251a32179e88a28acfc]),
> the fact that it is a so-called "bundled dependency" means the current
> version (1.2.1) is baked into the {{cordova-android}} installation tarball,
> and won't automatically respect the caret version range (`^1.2.1`) listed in
> {{cordova-android}}`s {{package.json}}, despite the lack of a
> {{package-lock.json}} (or otherwise).
> Bumping the version of {{android-versions}} in {{cordova-android}}'s
> {{package.json}} to 1.3.0 will enable the emulator to work with API level 27
> (even if there _could_ be other reasons that API level 27 causes problems).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Closed] (CB-13791) Add Android support for a footer close button.
[ https://issues.apache.org/jira/browse/CB-13791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser closed CB-13791. --- Resolution: Fixed > Add Android support for a footer close button. > -- > > Key: CB-13791 > URL: https://issues.apache.org/jira/browse/CB-13791 > Project: Apache Cordova > Issue Type: Improvement > Components: cordova-plugin-inappbrowser > Environment: Android >Reporter: Dave Alden >Priority: Minor > Labels: features, newbie > > Extending the work done in [PR > #246|https://github.com/apache/cordova-plugin-inappbrowser/pull/246] under > CB-13409, this adds support to Android for a footer close button similar to > the "Done" button on iOS. > The following options are added for Android: > * *footer* - set to "yes" to show a close button in the footer similar to > the iOS "Done" button. > The close button will appear the same as for the header hence use > _closebuttoncaption_ and _closebuttoncolor_ to set its properties. > * *footercolor* - set to a valid hex color string, for example #00ff00 or > #CC00ff00 (#aarrggbb) , and it will change the footer color from default. > Only has effect if user has _footer_ set to "yes". > Here are some example screenshots with the relevant options: > _location=yes,footer=yes_ > > !https://user-images.githubusercontent.com/2345062/33147006-2a602f88-cfbe-11e7-9580-438b07236400.png|width=300! > _location=no,footer=yes_ > > !https://user-images.githubusercontent.com/2345062/33147147-a60efaba-cfbe-11e7-8132-120179e8b43e.png|width=300! > _location=yes,footer=yes,closebuttoncaption=Done_ > > !https://user-images.githubusercontent.com/2345062/33147185-ca8d1e6c-cfbe-11e7-9646-0e1cea52abce.png|width=300! > _location=no,footer=yes,closebuttoncaption=Done,closebuttoncolor=#ff_ > > !https://user-images.githubusercontent.com/2345062/33147285-1aa7bc54-cfbf-11e7-9b9b-576f0d87ed9a.png|width=300! > _location=no,footer=yes,footercolor=#ff,closebuttoncaption=Done_ > > !https://user-images.githubusercontent.com/2345062/33147316-3ab511fe-cfbf-11e7-8b19-d1de80ad289e.png|width=300! > _location=no,footer=yes,footercolor=#00ff00,closebuttoncaption=Done,closebuttoncolor=#ff_ > > !https://user-images.githubusercontent.com/2345062/33147348-581b55c8-cfbf-11e7-9490-c61d83957079.png|width=300! > _location=no,footer=yes,footercolor=#CC00,closebuttoncaption=Done,closebuttoncolor=#00_ > > !https://user-images.githubusercontent.com/2345062/33147377-6ec46c6a-cfbf-11e7-969e-a075142133c4.png|width=300! -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-13800) Drop pre-KitKat specific code
[ https://issues.apache.org/jira/browse/CB-13800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser resolved CB-13800. - Resolution: Fixed Merged > Drop pre-KitKat specific code > - > > Key: CB-13800 > URL: https://issues.apache.org/jira/browse/CB-13800 > Project: Apache Cordova > Issue Type: Improvement > Components: cordova-android >Affects Versions: 7.0.0 >Reporter: Bas Bosman >Assignee: Bas Bosman >Priority: Minor > > With the release of cordova-android 7.0.0 the minimum API-Level was set to 19. > > There are a couple of places in the codebase where we have specific logic for > older API-levels, which are now no longer needed and therefore can be removed. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Closed] (CB-12453) "cordova run --list" throws error when there's a space in user name
[ https://issues.apache.org/jira/browse/CB-12453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser closed CB-12453. --- Resolution: Fixed This got merged in months ago. WTF? > "cordova run --list" throws error when there's a space in user name > --- > > Key: CB-12453 > URL: https://issues.apache.org/jira/browse/CB-12453 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-android, cordova-cli >Affects Versions: 6.4.0, 6.5.0 > Environment: Windows 10 64 bit, cordova version 6.5 (not in list?) CLI >Reporter: Yousif Touma >Priority: Major > Labels: cli, list-devices, windows10 > > When trying to list available devices to run on, cordova throws an error if > the user has a space in user name -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Comment Edited] (CB-13684) Not be able to sign apk with 6.4.0 and 7.0.0 without specifying passwords in build.json
[
https://issues.apache.org/jira/browse/CB-13684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16332759#comment-16332759
]
Joe Bowser edited comment on CB-13684 at 1/19/18 7:04 PM:
--
[~danielcooper_xyz] The keyPassword argument does not exist, and you can't pass
the password through command line arguments this way. Right now there's no way
for this to be skipped, and you have to provide it via the build.json in the
top-level of the project.
If you're using a Stand-Alone Android Project, you could just write to the
release-signing.properties file directly and put the passwords there before
executing the build. Below is my build.json from recreating the WeatherApp to
try and reproduce the bug:
{code:java}
{ "android": { "release": { "keystore": "keystore", "alias": "alias1",
"storePassword": "password", "password": "password" } } }
{code}
And here's the release-signing .properties when I use the command line to try
and generate this file:
{noformat}
# This file is automatically generated. # Do not modify this file -- YOUR
CHANGES WILL BE ERASED!
key.store=../../keystore
key.alias=alias1
key.store.password=password
{noformat}
This is obviously missing the much-needed key.alias.password, which will allow
the build to work.
was (Author: bowserj):
[~danielcooper_xyz] The keyPassword argument does not exist, and you can't pass
the password through command line arguments this way. Right now there's no way
for this to be skipped, and you have to provide it via the build.json in the
top-level of the project.
If you're using a Stand-Alone Android Project, you could just write to the
release-signing.properties file directly and put the passwords there before
executing the build.
> Not be able to sign apk with 6.4.0 and 7.0.0 without specifying passwords in
> build.json
> ---
>
> Key: CB-13684
> URL: https://issues.apache.org/jira/browse/CB-13684
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-android
>Reporter: Kevin Lot
>Assignee: Joe Bowser
>Priority: Major
>
> Since 6.4.0, sign APK without specify passwords in config file does not work.
> Cause gradle 4.1.0 has this issue [#2826] - Use SwingBuilder in customize
> task on Android studio throw java.awt.HeadlessException.
> ([link|https://github.com/gradle/gradle/issues/2826]).
> If you don't specify passwords in config file to sign your APK, compilation
> launches a window with SwingBuilder to prompt passwords.
> {code:java}
> def doPromptForPassword(msg) {
> if (System.console() == null) {
> def ret = null
> new SwingBuilder().edt {
> dialog(modal: true, title: 'Enter password', alwaysOnTop: true,
> resizable: false, locationRelativeTo: null, pack: true, show: true) {
> vbox {
> label(text: msg)
> def input = passwordField()
> button(defaultButton: true, text: 'OK', actionPerformed: {
> ret = input.password;
> dispose();
> })
> }
> }
> }
> if (!ret) {
> throw new GradleException('User canceled build')
> }
> return new String(ret)
> } else {
> return System.console().readPassword('\n' + msg);
> }
> }
> {code}
> On Linux Mint 18.3 and MacOs High sierra, even in terminal, System.console()
> return null and compilation crashes due to gradle issue.
> Thanks for help.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-13684) Not be able to sign apk with 6.4.0 and 7.0.0 without specifying passwords in build.json
[
https://issues.apache.org/jira/browse/CB-13684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16332759#comment-16332759
]
Joe Bowser commented on CB-13684:
-
[~danielcooper_xyz] The keyPassword argument does not exist, and you can't pass
the password through command line arguments this way. Right now there's no way
for this to be skipped, and you have to provide it via the build.json in the
top-level of the project.
If you're using a Stand-Alone Android Project, you could just write to the
release-signing.properties file directly and put the passwords there before
executing the build.
> Not be able to sign apk with 6.4.0 and 7.0.0 without specifying passwords in
> build.json
> ---
>
> Key: CB-13684
> URL: https://issues.apache.org/jira/browse/CB-13684
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-android
>Reporter: Kevin Lot
>Assignee: Joe Bowser
>Priority: Major
>
> Since 6.4.0, sign APK without specify passwords in config file does not work.
> Cause gradle 4.1.0 has this issue [#2826] - Use SwingBuilder in customize
> task on Android studio throw java.awt.HeadlessException.
> ([link|https://github.com/gradle/gradle/issues/2826]).
> If you don't specify passwords in config file to sign your APK, compilation
> launches a window with SwingBuilder to prompt passwords.
> {code:java}
> def doPromptForPassword(msg) {
> if (System.console() == null) {
> def ret = null
> new SwingBuilder().edt {
> dialog(modal: true, title: 'Enter password', alwaysOnTop: true,
> resizable: false, locationRelativeTo: null, pack: true, show: true) {
> vbox {
> label(text: msg)
> def input = passwordField()
> button(defaultButton: true, text: 'OK', actionPerformed: {
> ret = input.password;
> dispose();
> })
> }
> }
> }
> if (!ret) {
> throw new GradleException('User canceled build')
> }
> return new String(ret)
> } else {
> return System.console().readPassword('\n' + msg);
> }
> }
> {code}
> On Linux Mint 18.3 and MacOs High sierra, even in terminal, System.console()
> return null and compilation crashes due to gradle issue.
> Thanks for help.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-13684) Not be able to sign apk with 6.4.0 and 7.0.0 without specifying passwords in build.json
[
https://issues.apache.org/jira/browse/CB-13684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Bowser updated CB-13684:
Summary: Not be able to sign apk with 6.4.0 and 7.0.0 without specifying
passwords in build.json (was: Not be able to sign apk with 6.4.0 and 7.0.0)
> Not be able to sign apk with 6.4.0 and 7.0.0 without specifying passwords in
> build.json
> ---
>
> Key: CB-13684
> URL: https://issues.apache.org/jira/browse/CB-13684
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-android
>Reporter: Kevin Lot
>Assignee: Joe Bowser
>Priority: Major
>
> Since 6.4.0, sign APK without specify passwords in config file does not work.
> Cause gradle 4.1.0 has this issue [#2826] - Use SwingBuilder in customize
> task on Android studio throw java.awt.HeadlessException.
> ([link|https://github.com/gradle/gradle/issues/2826]).
> If you don't specify passwords in config file to sign your APK, compilation
> launches a window with SwingBuilder to prompt passwords.
> {code:java}
> def doPromptForPassword(msg) {
> if (System.console() == null) {
> def ret = null
> new SwingBuilder().edt {
> dialog(modal: true, title: 'Enter password', alwaysOnTop: true,
> resizable: false, locationRelativeTo: null, pack: true, show: true) {
> vbox {
> label(text: msg)
> def input = passwordField()
> button(defaultButton: true, text: 'OK', actionPerformed: {
> ret = input.password;
> dispose();
> })
> }
> }
> }
> if (!ret) {
> throw new GradleException('User canceled build')
> }
> return new String(ret)
> } else {
> return System.console().readPassword('\n' + msg);
> }
> }
> {code}
> On Linux Mint 18.3 and MacOs High sierra, even in terminal, System.console()
> return null and compilation crashes due to gradle issue.
> Thanks for help.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Comment Edited] (CB-13684) Not be able to sign apk with 6.4.0 and 7.0.0
[
https://issues.apache.org/jira/browse/CB-13684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16331349#comment-16331349
]
Joe Bowser edited comment on CB-13684 at 1/18/18 10:30 PM:
---
[~eparlier] I was able to get everything working fine using the build.json file
and providing a password for both the key and the keystore, so the keystore
appears to be required now. If you don't provide a password, it should give
you a prompt.
was (Author: bowserj):
[~eparlier] I was able to get everything working fine using the build.json file
and providing a password for both the key and the keystore, so the keystore
appears to be required now.
> Not be able to sign apk with 6.4.0 and 7.0.0
>
>
> Key: CB-13684
> URL: https://issues.apache.org/jira/browse/CB-13684
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-android
>Reporter: Kevin Lot
>Assignee: Joe Bowser
>Priority: Major
>
> Since 6.4.0, sign APK without specify passwords in config file does not work.
> Cause gradle 4.1.0 has this issue [#2826] - Use SwingBuilder in customize
> task on Android studio throw java.awt.HeadlessException.
> ([link|https://github.com/gradle/gradle/issues/2826]).
> If you don't specify passwords in config file to sign your APK, compilation
> launches a window with SwingBuilder to prompt passwords.
> {code:java}
> def doPromptForPassword(msg) {
> if (System.console() == null) {
> def ret = null
> new SwingBuilder().edt {
> dialog(modal: true, title: 'Enter password', alwaysOnTop: true,
> resizable: false, locationRelativeTo: null, pack: true, show: true) {
> vbox {
> label(text: msg)
> def input = passwordField()
> button(defaultButton: true, text: 'OK', actionPerformed: {
> ret = input.password;
> dispose();
> })
> }
> }
> }
> if (!ret) {
> throw new GradleException('User canceled build')
> }
> return new String(ret)
> } else {
> return System.console().readPassword('\n' + msg);
> }
> }
> {code}
> On Linux Mint 18.3 and MacOs High sierra, even in terminal, System.console()
> return null and compilation crashes due to gradle issue.
> Thanks for help.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-13684) Not be able to sign apk with 6.4.0 and 7.0.0
[
https://issues.apache.org/jira/browse/CB-13684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16331349#comment-16331349
]
Joe Bowser commented on CB-13684:
-
[~eparlier] I was able to get everything working fine using the build.json file
and providing a password for both the key and the keystore, so the keystore
appears to be required now.
> Not be able to sign apk with 6.4.0 and 7.0.0
>
>
> Key: CB-13684
> URL: https://issues.apache.org/jira/browse/CB-13684
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-android
>Reporter: Kevin Lot
>Assignee: Joe Bowser
>Priority: Major
>
> Since 6.4.0, sign APK without specify passwords in config file does not work.
> Cause gradle 4.1.0 has this issue [#2826] - Use SwingBuilder in customize
> task on Android studio throw java.awt.HeadlessException.
> ([link|https://github.com/gradle/gradle/issues/2826]).
> If you don't specify passwords in config file to sign your APK, compilation
> launches a window with SwingBuilder to prompt passwords.
> {code:java}
> def doPromptForPassword(msg) {
> if (System.console() == null) {
> def ret = null
> new SwingBuilder().edt {
> dialog(modal: true, title: 'Enter password', alwaysOnTop: true,
> resizable: false, locationRelativeTo: null, pack: true, show: true) {
> vbox {
> label(text: msg)
> def input = passwordField()
> button(defaultButton: true, text: 'OK', actionPerformed: {
> ret = input.password;
> dispose();
> })
> }
> }
> }
> if (!ret) {
> throw new GradleException('User canceled build')
> }
> return new String(ret)
> } else {
> return System.console().readPassword('\n' + msg);
> }
> }
> {code}
> On Linux Mint 18.3 and MacOs High sierra, even in terminal, System.console()
> return null and compilation crashes due to gradle issue.
> Thanks for help.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Comment Edited] (CB-13684) Not be able to sign apk with 6.4.0 and 7.0.0
[
https://issues.apache.org/jira/browse/CB-13684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16331269#comment-16331269
]
Joe Bowser edited comment on CB-13684 at 1/18/18 9:37 PM:
--
OK, for some weird reason we can't use ant.input because it cases the Cordova
build scripts to freeze up. For now, you have to specify passwords in due to
it being a Gradle bug that we can't work around. There's a lot of people
gathering the torches and pitchforks since this breaks their builds, but since
gradle hasn't provided a reliable way of prompting for passwords in a daemon
(which is why the console object is null) when it's being shelled out.
If someone can get Cordova to work well with ant.input, I'd be really happy to
pull that PR in, but whenever I switch to using that to build something, I get
stuck with the CLI hanging. There's no easy fix/workaround for this bug other
than specifying your passwords in build.json.
was (Author: bowserj):
OK, for some weird reason we can't use ant.input because it cases the Cordova
build scripts to freeze up. For now, you have to specify passwords in due to
it being a Gradle bug that we can't work around. There's a lot of people
gathering the torches and pitchforks since this breaks their builds, but since
gradle hasn't provided a reliable way of prompting for passwords in a daemon
(which is why the console object is null) when it's being shelled out.
If someone can get Cordova to work well with ant.input, I'd be really happy to
pull that PR in, but whenever I switch to using that to build something, I get
stuck with the CLI hanging. There's no easy fix/workaround for this bug other
than specifying your passwords in build.json.
> Not be able to sign apk with 6.4.0 and 7.0.0
>
>
> Key: CB-13684
> URL: https://issues.apache.org/jira/browse/CB-13684
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-android
>Reporter: Kevin Lot
>Assignee: Joe Bowser
>Priority: Major
>
> Since 6.4.0, sign APK without specify passwords in config file does not work.
> Cause gradle 4.1.0 has this issue [#2826] - Use SwingBuilder in customize
> task on Android studio throw java.awt.HeadlessException.
> ([link|https://github.com/gradle/gradle/issues/2826]).
> If you don't specify passwords in config file to sign your APK, compilation
> launches a window with SwingBuilder to prompt passwords.
> {code:java}
> def doPromptForPassword(msg) {
> if (System.console() == null) {
> def ret = null
> new SwingBuilder().edt {
> dialog(modal: true, title: 'Enter password', alwaysOnTop: true,
> resizable: false, locationRelativeTo: null, pack: true, show: true) {
> vbox {
> label(text: msg)
> def input = passwordField()
> button(defaultButton: true, text: 'OK', actionPerformed: {
> ret = input.password;
> dispose();
> })
> }
> }
> }
> if (!ret) {
> throw new GradleException('User canceled build')
> }
> return new String(ret)
> } else {
> return System.console().readPassword('\n' + msg);
> }
> }
> {code}
> On Linux Mint 18.3 and MacOs High sierra, even in terminal, System.console()
> return null and compilation crashes due to gradle issue.
> Thanks for help.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-13684) Not be able to sign apk with 6.4.0 and 7.0.0
[
https://issues.apache.org/jira/browse/CB-13684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16331269#comment-16331269
]
Joe Bowser commented on CB-13684:
-
OK, for some weird reason we can't use ant.input because it cases the Cordova
build scripts to freeze up. For now, you have to specify passwords in due to
it being a Gradle bug that we can't work around. There's a lot of people
gathering the torches and pitchforks since this breaks their builds, but since
gradle hasn't provided a reliable way of prompting for passwords in a daemon
(which is why the console object is null) when it's being shelled out.
If someone can get Cordova to work well with ant.input, I'd be really happy to
pull that PR in, but whenever I switch to using that to build something, I get
stuck with the CLI hanging. There's no easy fix/workaround for this bug other
than specifying your passwords in build.json.
> Not be able to sign apk with 6.4.0 and 7.0.0
>
>
> Key: CB-13684
> URL: https://issues.apache.org/jira/browse/CB-13684
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-android
>Reporter: Kevin Lot
>Assignee: Joe Bowser
>Priority: Major
>
> Since 6.4.0, sign APK without specify passwords in config file does not work.
> Cause gradle 4.1.0 has this issue [#2826] - Use SwingBuilder in customize
> task on Android studio throw java.awt.HeadlessException.
> ([link|https://github.com/gradle/gradle/issues/2826]).
> If you don't specify passwords in config file to sign your APK, compilation
> launches a window with SwingBuilder to prompt passwords.
> {code:java}
> def doPromptForPassword(msg) {
> if (System.console() == null) {
> def ret = null
> new SwingBuilder().edt {
> dialog(modal: true, title: 'Enter password', alwaysOnTop: true,
> resizable: false, locationRelativeTo: null, pack: true, show: true) {
> vbox {
> label(text: msg)
> def input = passwordField()
> button(defaultButton: true, text: 'OK', actionPerformed: {
> ret = input.password;
> dispose();
> })
> }
> }
> }
> if (!ret) {
> throw new GradleException('User canceled build')
> }
> return new String(ret)
> } else {
> return System.console().readPassword('\n' + msg);
> }
> }
> {code}
> On Linux Mint 18.3 and MacOs High sierra, even in terminal, System.console()
> return null and compilation crashes due to gradle issue.
> Thanks for help.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-13684) Not be able to sign apk with 6.4.0 and 7.0.0
[
https://issues.apache.org/jira/browse/CB-13684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16331226#comment-16331226
]
Joe Bowser commented on CB-13684:
-
OK, how about we get rid of the swing builder and just ask for the password in
the CLI using the ant properties? How do people feel about that?
> Not be able to sign apk with 6.4.0 and 7.0.0
>
>
> Key: CB-13684
> URL: https://issues.apache.org/jira/browse/CB-13684
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-android
>Reporter: Kevin Lot
>Assignee: Joe Bowser
>Priority: Major
>
> Since 6.4.0, sign APK without specify passwords in config file does not work.
> Cause gradle 4.1.0 has this issue [#2826] - Use SwingBuilder in customize
> task on Android studio throw java.awt.HeadlessException.
> ([link|https://github.com/gradle/gradle/issues/2826]).
> If you don't specify passwords in config file to sign your APK, compilation
> launches a window with SwingBuilder to prompt passwords.
> {code:java}
> def doPromptForPassword(msg) {
> if (System.console() == null) {
> def ret = null
> new SwingBuilder().edt {
> dialog(modal: true, title: 'Enter password', alwaysOnTop: true,
> resizable: false, locationRelativeTo: null, pack: true, show: true) {
> vbox {
> label(text: msg)
> def input = passwordField()
> button(defaultButton: true, text: 'OK', actionPerformed: {
> ret = input.password;
> dispose();
> })
> }
> }
> }
> if (!ret) {
> throw new GradleException('User canceled build')
> }
> return new String(ret)
> } else {
> return System.console().readPassword('\n' + msg);
> }
> }
> {code}
> On Linux Mint 18.3 and MacOs High sierra, even in terminal, System.console()
> return null and compilation crashes due to gradle issue.
> Thanks for help.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-13409) Allow more additional options, for customizing toolbar in cordova/inappbrowser
[ https://issues.apache.org/jira/browse/CB-13409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser resolved CB-13409. - Resolution: Fixed > Allow more additional options, for customizing toolbar in cordova/inappbrowser > -- > > Key: CB-13409 > URL: https://issues.apache.org/jira/browse/CB-13409 > Project: Apache Cordova > Issue Type: Improvement > Components: cordova-plugin-inappbrowser > Environment: iOS, Android >Reporter: Steinar Ágúst Steinarsson >Priority: Minor > Labels: features, newbie > Attachments: Android - 1.png, Android - 2.png, Android - 3.png, > Android - 4.png, Android - 5.png, iOS - 1.PNG > > Original Estimate: 0h > Remaining Estimate: 0h > > I added a couple of customizations to inappbrowser's toolbar: > *Android*: > - Have a custom text for a close button instead of the Default X: > _closebuttoncaption_: "set to a string to use as the close buttons caption > instead of a X. Note that you need to localize this value yourself." > - Change the close button color: > _closebuttoncolor_: "set to a valid hex color string, for example: `#00ff00`, > and it will change the close button color from default, regardless of being a > text or default X. Only has effect if user has location set to `yes`." > - Hide the navigation buttons that go backwards and forwards: > _hidenavigationbuttons_: "set to `yes` to hide the navigation buttons on the > location toolbar, only has effect if user has location set to `yes`. The > default value is `no`." > - Change navigation buttons color: > _navigationbuttoncolor_: "set to a valid hex color string, for example: > `#00ff00`, and it will change the color of both navigation buttons from > default. Only has effect if user has location set to `yes` and not > hidenavigationbuttons set to `yes`." > - Change color of toolbar: > _toolbarcolor_: "set to a valid hex color string, for example: `#00ff00`, and > it will change the color the toolbar from default. Only has effect if user > has location set to `yes`." > *iOS:* > - _closebuttoncolor_ (same as above) > - _hidenavigationbuttons_ (same as above) > - _toolbarcolor_ (same as above) > - Make toolbar non-translucent: > _toolbartranslucent_: "set to `yes` or `no` to make the toolbar > translucent(semi-transparent) (defaults to `yes`). Only applicable if > toolbar is not disabled." > See screenshots in attachments. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-13647) Incomplete plugin restoration
[
https://issues.apache.org/jira/browse/CB-13647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16330976#comment-16330976
]
Joe Bowser commented on CB-13647:
-
[~goffioul] Unfortunately I don't have a timeframe as to when the plugin paths
will be changed. We've tested the core plugins with mobilespec, and all of
them currently install, so that's not a pressing issue currently.
> Incomplete plugin restoration
> -
>
> Key: CB-13647
> URL: https://issues.apache.org/jira/browse/CB-13647
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-android
>Affects Versions: 7.0.0
>Reporter: Michael Goffioul
>Assignee: Joe Bowser
>Priority: Major
> Labels: android-next
>
> I'm having a problem with plugin restoration since cordova-android 7.0.0,
> when plugins use a mix of config-file and edit-config on the same file (e.g.
> AndroidManifest.xml) and only edit-config uses the real path to the file.
> I've tried both cordova-cli 6.5.0 and 7.1.0 with the same result.
> 1) Create a new corodva project and enter top-level direcotyr
> 2) Create subfolder to contain a local plugin: mkdir -p
> localplugins/testplugin1
> 3) Create the following files to define the local plugin:
> - plugin.xml (adds an attribute to and a category to
> )
> {code}
>
> http://apache.org/cordova/ns/plugins/1.0;
> id="com.example.testplugin1" version="1.0.0">
> Test Plugin 1
>
> parent="/manifest/application/activity/intent-filter">
>
>
> target="/manifest/application" mode="merge">
>
>
>
>
> {code}
> - package.json
> {code}
> {
> "name": "com.example.testplugin1",
> "version": "1.0.0"
> }
> {code}
> 4) Add android platform: cordova platform add android@7.0.0 --save
> 5) Add local plugin: cordova plugin add localplugins/testplugin1 --save
> At this point, if you check
> platforms/android/app/src/main/AndroidManifest.xml, it'll contain the 2
> changes defined in the plugin.
> Now attempt to use platform/plugin restoration with thw following:
> {code}
> cordova platform rm android
> cordova prepare android
> {code}
> If you check again AndroidManifest.xml, it will only contain one of the
> changes defined in the plugin (the attribute to ). The other
> change is missing.
> If you use the real path to AndroidManifest.xml for the definition of
> , then the problem does not occur. BUT, the problem can also
> occur when changes to AndroidManifest.xml are coming from multiple plugins,
> including the standard cordova plugin, most of which do not use the real path
> to AndroidManifest.xml yet.
> The problem can affect other files too. For instance I experienced incomplete
> restoration of plugins trying to register themselves in res/xml/config.xml.
> Only one plugin, out of 7, was using the real path
> app/src/main/res/xml/config.xml and I ended up with only one plugin defined
> in res/xml/config.xml, causing the application to fail to start.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-13739) Android build is broken due to libraries with text relocations
[ https://issues.apache.org/jira/browse/CB-13739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16330969#comment-16330969 ] Joe Bowser commented on CB-13739: - [~gabriel-fallen] Cordova doesn't host any guides on this, but you can find it on https://d.android.com. > Android build is broken due to libraries with text relocations > -- > > Key: CB-13739 > URL: https://issues.apache.org/jira/browse/CB-13739 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-android >Affects Versions: cordova-android-7.0.0 > Environment: Build systems: Ubuntu Linux and PhoneGap Build > Android versions: 5.0.2 and 7.1.2 >Reporter: Alexander Tchitchigin >Assignee: Joe Bowser >Priority: Major > Attachments: photo_2018-01-08_12-25-17.jpg > > > When I build an Android app and run it on a device I get the result in the > screenshot: there are a number of libraries with text relocations that > Android refuses to load hence the application is broken and doesn't work. > Release build refuses to start at all. > Before updating Cordova and Android SDK everything worked OK, I was able to > build and run the app and previous version is published to Google Play. But I > didn't memorize the version number when it all worked, unfortunately. App > code was updated either but I don't see how updated JS, CSS and images could > make Cordova link with new libraries with relocations. > Cordova behaves the same to me both locally with the latest version (cordova > 8.0.0, android 7.0.0) and in PhoneGap Build. > I'd like to know the right build settings to produce working build or at > least some workaround. I tried to play with cdvBuildToolsVersion and > cdvCompileSdkVersion but had no success. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-13739) Android build is broken due to libraries with text relocations
[ https://issues.apache.org/jira/browse/CB-13739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser resolved CB-13739. - Resolution: Cannot Reproduce I don't own a modern Samsung Galaxy Tab, but I can't reproduce this on any devices I currently possess. :/ > Android build is broken due to libraries with text relocations > -- > > Key: CB-13739 > URL: https://issues.apache.org/jira/browse/CB-13739 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-android >Affects Versions: cordova-android-7.0.0 > Environment: Build systems: Ubuntu Linux and PhoneGap Build > Android versions: 5.0.2 and 7.1.2 >Reporter: Alexander Tchitchigin >Assignee: Joe Bowser >Priority: Major > Attachments: photo_2018-01-08_12-25-17.jpg > > > When I build an Android app and run it on a device I get the result in the > screenshot: there are a number of libraries with text relocations that > Android refuses to load hence the application is broken and doesn't work. > Release build refuses to start at all. > Before updating Cordova and Android SDK everything worked OK, I was able to > build and run the app and previous version is published to Google Play. But I > didn't memorize the version number when it all worked, unfortunately. App > code was updated either but I don't see how updated JS, CSS and images could > make Cordova link with new libraries with relocations. > Cordova behaves the same to me both locally with the latest version (cordova > 8.0.0, android 7.0.0) and in PhoneGap Build. > I'd like to know the right build settings to produce working build or at > least some workaround. I tried to play with cdvBuildToolsVersion and > cdvCompileSdkVersion but had no success. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-13779) Apache Cordova 8.0.0 not building Android Apps but only prints Android and Java Paths
[
https://issues.apache.org/jira/browse/CB-13779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16330966#comment-16330966
]
Joe Bowser commented on CB-13779:
-
For whatever reason, you don't have gradle working, which is why you're not
getting any output. I'd double-check your gradle installation. As it is, I
can't reproduce your error on this end, so I'm going to have to close this as
"Cannot Reproduce"
> Apache Cordova 8.0.0 not building Android Apps but only prints Android and
> Java Paths
> -
>
> Key: CB-13779
> URL: https://issues.apache.org/jira/browse/CB-13779
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-android
> Environment: I am trying to build a Cordova app with few plugins
> ([InAppBrowser|https://cordova.apache.org/docs/en/latest/reference/cordova-plugin-inappbrowser/],
> [Barcode
> Scanner|https://github.com/phonegap/phonegap-plugin-barcodescanner], [File
> Transfer|https://cordova.apache.org/docs/en/latest/reference/cordova-plugin-file-transfer/index.html],
> [Text-to-Speech|https://github.com/vilic/cordova-plugin-tts], [Document
> Viewer|https://github.com/sitewaerts/cordova-plugin-document-viewer],
> [GeoLocation|https://cordova.apache.org/docs/en/latest/reference/cordova-plugin-geolocation/index.html]).
>
> OS: MacOS High Sierra (10.13.2)
> Cordova version 8.0.0
> Android {{cordova-android@~7.0.0}}
> Android Studio 3.0.1
>
>Reporter: Sumit Soman
>Assignee: Joe Bowser
>Priority: Major
>
> When I run {{cordova build android}} it only shows the {{ANDROID_HOME}} and
> {{JAVA_HOME}} paths but does not build the Android Studio project.
> [!https://i.stack.imgur.com/l7Qat.png!|https://i.stack.imgur.com/l7Qat.png]
> I am using Cordova version 8.0.0 and Android {{cordova-android@~7.0.0}}
> Building in the verbose mode gives the following messages
> [!https://i.stack.imgur.com/rLMSv.png!|https://i.stack.imgur.com/rLMSv.png]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-13779) Apache Cordova 8.0.0 not building Android Apps but only prints Android and Java Paths
[
https://issues.apache.org/jira/browse/CB-13779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Bowser resolved CB-13779.
-
Resolution: Cannot Reproduce
> Apache Cordova 8.0.0 not building Android Apps but only prints Android and
> Java Paths
> -
>
> Key: CB-13779
> URL: https://issues.apache.org/jira/browse/CB-13779
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-android
> Environment: I am trying to build a Cordova app with few plugins
> ([InAppBrowser|https://cordova.apache.org/docs/en/latest/reference/cordova-plugin-inappbrowser/],
> [Barcode
> Scanner|https://github.com/phonegap/phonegap-plugin-barcodescanner], [File
> Transfer|https://cordova.apache.org/docs/en/latest/reference/cordova-plugin-file-transfer/index.html],
> [Text-to-Speech|https://github.com/vilic/cordova-plugin-tts], [Document
> Viewer|https://github.com/sitewaerts/cordova-plugin-document-viewer],
> [GeoLocation|https://cordova.apache.org/docs/en/latest/reference/cordova-plugin-geolocation/index.html]).
>
> OS: MacOS High Sierra (10.13.2)
> Cordova version 8.0.0
> Android {{cordova-android@~7.0.0}}
> Android Studio 3.0.1
>
>Reporter: Sumit Soman
>Assignee: Joe Bowser
>Priority: Major
>
> When I run {{cordova build android}} it only shows the {{ANDROID_HOME}} and
> {{JAVA_HOME}} paths but does not build the Android Studio project.
> [!https://i.stack.imgur.com/l7Qat.png!|https://i.stack.imgur.com/l7Qat.png]
> I am using Cordova version 8.0.0 and Android {{cordova-android@~7.0.0}}
> Building in the verbose mode gives the following messages
> [!https://i.stack.imgur.com/rLMSv.png!|https://i.stack.imgur.com/rLMSv.png]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-13789) Local plugins cannot be installed after a fresh installation
[
https://issues.apache.org/jira/browse/CB-13789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Bowser updated CB-13789:
Priority: Major (was: Blocker)
> Local plugins cannot be installed after a fresh installation
>
>
> Key: CB-13789
> URL: https://issues.apache.org/jira/browse/CB-13789
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-cli
>Affects Versions: 7.0.2
> Environment: It is in Cordova 8.0.0 (but the interface did not allow
> me to select it!)
>Reporter: Olivier Goguel
>Priority: Major
>
> Local plugins fails to install after a fresh installation (from source
> control for example)
> *Steps:*
> {{cordova create sample}}
> {{cordova add plugin local/localplugin}}
> {{rm -rf plugins # to simulate fresh installation}}
> {{cordova platform add ios}}
> {color:#FF}*Failed to restore plugin "localplugin" from config.xml. You
> might need to try adding it again. Error: Failed to fetch plugin
> file:local/localplugin via registry.*{color}
> *Hints:*
> The plugin does not install as cordova is confused by the "file:" prefix
> When adding the plugin, it is referenced in package.json as {{"localplugin":
> "file:local/localplugin", but in the config.xml the file: prefix has been
> stripped ""}}
> However, when restoring the plugin, it uses the file: prefix which is not
> supported by the cli as the protocol is not properly handled: the fetch()
> function just tries to load the plugin from the path being given, cannot find
> it because of the prefix, and then assume it has to be loaded from the
> registry, hence the error
> cf. https://github.com/apache/cordova-lib/blob/master/src/plugman/fetch.js#L86
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-13791) Add Android support for a footer close button.
[ https://issues.apache.org/jira/browse/CB-13791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser resolved CB-13791. - Resolution: Fixed > Add Android support for a footer close button. > -- > > Key: CB-13791 > URL: https://issues.apache.org/jira/browse/CB-13791 > Project: Apache Cordova > Issue Type: Improvement > Components: cordova-plugin-inappbrowser > Environment: Android >Reporter: Dave Alden >Priority: Minor > Labels: features, newbie > > Extending the work done in [PR > #246|https://github.com/apache/cordova-plugin-inappbrowser/pull/246] under > CB-13409, this adds support to Android for a footer close button similar to > the "Done" button on iOS. > The following options are added for Android: > * *footer* - set to "yes" to show a close button in the footer similar to > the iOS "Done" button. > The close button will appear the same as for the header hence use > _closebuttoncaption_ and _closebuttoncolor_ to set its properties. > * *footercolor* - set to a valid hex color string, for example #00ff00 or > #CC00ff00 (#aarrggbb) , and it will change the footer color from default. > Only has effect if user has _footer_ set to "yes". > Here are some example screenshots with the relevant options: > _location=yes,footer=yes_ > > !https://user-images.githubusercontent.com/2345062/33147006-2a602f88-cfbe-11e7-9580-438b07236400.png|width=300! > _location=no,footer=yes_ > > !https://user-images.githubusercontent.com/2345062/33147147-a60efaba-cfbe-11e7-8132-120179e8b43e.png|width=300! > _location=yes,footer=yes,closebuttoncaption=Done_ > > !https://user-images.githubusercontent.com/2345062/33147185-ca8d1e6c-cfbe-11e7-9646-0e1cea52abce.png|width=300! > _location=no,footer=yes,closebuttoncaption=Done,closebuttoncolor=#ff_ > > !https://user-images.githubusercontent.com/2345062/33147285-1aa7bc54-cfbf-11e7-9b9b-576f0d87ed9a.png|width=300! > _location=no,footer=yes,footercolor=#ff,closebuttoncaption=Done_ > > !https://user-images.githubusercontent.com/2345062/33147316-3ab511fe-cfbf-11e7-8b19-d1de80ad289e.png|width=300! > _location=no,footer=yes,footercolor=#00ff00,closebuttoncaption=Done,closebuttoncolor=#ff_ > > !https://user-images.githubusercontent.com/2345062/33147348-581b55c8-cfbf-11e7-9490-c61d83957079.png|width=300! > _location=no,footer=yes,footercolor=#CC00,closebuttoncaption=Done,closebuttoncolor=#00_ > > !https://user-images.githubusercontent.com/2345062/33147377-6ec46c6a-cfbf-11e7-969e-a075142133c4.png|width=300! -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-13724) Bump Target SDK to 27
[ https://issues.apache.org/jira/browse/CB-13724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser resolved CB-13724. - Resolution: Fixed > Bump Target SDK to 27 > - > > Key: CB-13724 > URL: https://issues.apache.org/jira/browse/CB-13724 > Project: Apache Cordova > Issue Type: Task > Components: cordova-android >Affects Versions: cordova-android@7.0.0 >Reporter: Joe Bowser >Assignee: Joe Bowser >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-13793) cordova-plugin-camera.
[ https://issues.apache.org/jira/browse/CB-13793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser resolved CB-13793. - Resolution: Incomplete This issue is empty, closing! > cordova-plugin-camera. > --- > > Key: CB-13793 > URL: https://issues.apache.org/jira/browse/CB-13793 > Project: Apache Cordova > Issue Type: Bug >Reporter: Zeeshan Aslam >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-13684) Not be able to sign apk with 6.4.0 and 7.0.0
[
https://issues.apache.org/jira/browse/CB-13684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16327855#comment-16327855
]
Joe Bowser commented on CB-13684:
-
[~eparlier] You're missing a storePassword, which is most likely causing the
prompt to appear.
> Not be able to sign apk with 6.4.0 and 7.0.0
>
>
> Key: CB-13684
> URL: https://issues.apache.org/jira/browse/CB-13684
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-android
>Reporter: Kevin Lot
>Assignee: Joe Bowser
>Priority: Major
>
> Since 6.4.0, sign APK without specify passwords in config file does not work.
> Cause gradle 4.1.0 has this issue [#2826] - Use SwingBuilder in customize
> task on Android studio throw java.awt.HeadlessException.
> ([link|https://github.com/gradle/gradle/issues/2826]).
> If you don't specify passwords in config file to sign your APK, compilation
> launches a window with SwingBuilder to prompt passwords.
> {code:java}
> def doPromptForPassword(msg) {
> if (System.console() == null) {
> def ret = null
> new SwingBuilder().edt {
> dialog(modal: true, title: 'Enter password', alwaysOnTop: true,
> resizable: false, locationRelativeTo: null, pack: true, show: true) {
> vbox {
> label(text: msg)
> def input = passwordField()
> button(defaultButton: true, text: 'OK', actionPerformed: {
> ret = input.password;
> dispose();
> })
> }
> }
> }
> if (!ret) {
> throw new GradleException('User canceled build')
> }
> return new String(ret)
> } else {
> return System.console().readPassword('\n' + msg);
> }
> }
> {code}
> On Linux Mint 18.3 and MacOs High sierra, even in terminal, System.console()
> return null and compilation crashes due to gradle issue.
> Thanks for help.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-13779) Apache Cordova 8.0.0 not building Android Apps but only prints Android and Java Paths
[
https://issues.apache.org/jira/browse/CB-13779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16327645#comment-16327645
]
Joe Bowser commented on CB-13779:
-
Do you have gradle installed? It looks like your system isn't checking for
gradle.
> Apache Cordova 8.0.0 not building Android Apps but only prints Android and
> Java Paths
> -
>
> Key: CB-13779
> URL: https://issues.apache.org/jira/browse/CB-13779
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-android
> Environment: I am trying to build a Cordova app with few plugins
> ([InAppBrowser|https://cordova.apache.org/docs/en/latest/reference/cordova-plugin-inappbrowser/],
> [Barcode
> Scanner|https://github.com/phonegap/phonegap-plugin-barcodescanner], [File
> Transfer|https://cordova.apache.org/docs/en/latest/reference/cordova-plugin-file-transfer/index.html],
> [Text-to-Speech|https://github.com/vilic/cordova-plugin-tts], [Document
> Viewer|https://github.com/sitewaerts/cordova-plugin-document-viewer],
> [GeoLocation|https://cordova.apache.org/docs/en/latest/reference/cordova-plugin-geolocation/index.html]).
>
> OS: MacOS High Sierra (10.13.2)
> Cordova version 8.0.0
> Android {{cordova-android@~7.0.0}}
> Android Studio 3.0.1
>
>Reporter: Sumit Soman
>Assignee: Joe Bowser
>Priority: Major
>
> When I run {{cordova build android}} it only shows the {{ANDROID_HOME}} and
> {{JAVA_HOME}} paths but does not build the Android Studio project.
> [!https://i.stack.imgur.com/l7Qat.png!|https://i.stack.imgur.com/l7Qat.png]
> I am using Cordova version 8.0.0 and Android {{cordova-android@~7.0.0}}
> Building in the verbose mode gives the following messages
> [!https://i.stack.imgur.com/rLMSv.png!|https://i.stack.imgur.com/rLMSv.png]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Closed] (CB-13786) Failed to create component for 'dialog' reason: java.awt.HeadlessException
[ https://issues.apache.org/jira/browse/CB-13786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser closed CB-13786. --- Resolution: Duplicate CB-13684 > Failed to create component for 'dialog' reason: java.awt.HeadlessException > -- > > Key: CB-13786 > URL: https://issues.apache.org/jira/browse/CB-13786 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-cli >Affects Versions: cordova-android-7.0.0 > Environment: Windows 10 + gradle 4.4.1 + cordova 8 + cordova android > 7 + JSON build file > Used to work perfectly with older version. > >Reporter: Eric Parlier >Priority: Blocker > Labels: newbie > > cordova build android --debug = OK > cordova build android --release = FAIL > > FAILURE: Build failed with an exception. > * Where: > Script 'D:\Server\ROOT\myapp\platforms\android\CordovaLib\cordova.gradle' > line: 143 > * What went wrong: > Failed to create component for 'dialog' reason: java.awt.HeadlessException > > java.awt.HeadlessException (no error message) -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-13190) Potential unreleased resources (HP Fortify SCA: Unreleased Resource: Streams)
[
https://issues.apache.org/jira/browse/CB-13190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Bowser updated CB-13190:
Security: (was: Non-Public)
Not all HP Fortify scans are Security errors, some are just bugs. Removing the
private bit from this issue.
> Potential unreleased resources (HP Fortify SCA: Unreleased Resource: Streams)
> -
>
> Key: CB-13190
> URL: https://issues.apache.org/jira/browse/CB-13190
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-android, cordova-plugin-file,
> cordova-plugin-file-transfer (DEPRECATED)
>Reporter: GSS FED
>Assignee: Joe Bowser
>Priority: Major
>
> Similar issue: [https://issues.apache.org/jira/browse/CB-8253]
> There are several places in the File plugin, File Transfer plugin and
> cordova-android where streams do not use try { fis.closed } catch
> (IOException e) {} in a finally block allowing for the possibility they will
> never be closed if an exception occurs at the wrong place.
> Affected files:
> cordova-android/~CordovaResourceApi.java: line: 166, 377
> cordova-plugin-file/~Filesystem.java: line: 253, 286
> cordova-plugin-file-transfer/~FileTransfer.java: line: 665
> cordova-plugin-file/~LocalFilesystem.java: line: 403, 461, 507
> Recommendations of Fortify:
> {code:java}
> public void processFile(String fName) throws FileNotFoundException,
> IOException {
> FileInputStream fis;
> try {
> fis = new FileInputStream(fName);
> int sz;
> byte[] byteArray = new byte[BLOCK_SIZE];
> while ((sz = fis.read(byteArray)) != -1) { processBytes(byteArray, sz); }
> } finally {
> if (fis != null) {
> safeClose(fis);
> }
> }
> }
> public static void safeClose(FileInputStream fis) {
> if (fis != null) {
> try {
> fis.close();
> } catch (IOException e) {
> log(e);
> }
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-13772) CLI `cordova requirements` printing out [object Object] in place of some version numbers
[
https://issues.apache.org/jira/browse/CB-13772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Bowser updated CB-13772:
Component/s: (was: cordova-cli)
cordova-ios
> CLI `cordova requirements` printing out [object Object] in place of some
> version numbers
>
>
> Key: CB-13772
> URL: https://issues.apache.org/jira/browse/CB-13772
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-ios
>Affects Versions: cordova@8.0.0
> Environment: macOS High Sierra 10.13.2
> npm v5.6.0
> node v9.4.0
> cordova CLI v8.0.0
>Reporter: Darcy Meyer
>Priority: Minor
>
> When `cordova requirements` is executed, the output prints [object Object]
> in place of some of the version numbers.
> e.g.
> {code}
> $ cordova requirements
> Android Studio project detected
> Requirements check results for android:
> Java JDK: installed 1.8.0
> Android SDK: installed true
> Android target: not installed
> avdmanager: Command failed with exit code 1
> Gradle: not installed
> Could not find an installed version of Gradle either in Android Studio,
> or on your system to install the gradle wrapper. Please include gradle
> in your path, or install Android Studio
> Requirements check results for ios:
> Apple macOS: installed darwin
> Xcode: installed [object Object]
> ios-deploy: installed [object Object]
> CocoaPods: installed [object Object]
> {code}
> Here, the versions of the ios requirements are not displayed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-13773) camera.getPicture returns error code 20
[
https://issues.apache.org/jira/browse/CB-13773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16326624#comment-16326624
]
Joe Bowser commented on CB-13773:
-
I would recommend trying it on a standalone Camera app. I don't know what
Error Code 20 means on your device, but if you're not seeing any permission,
maybe the permission was denied too many times and it decided to just give up
and deny it, which is something Android can do. That said, it should handle
that case a lot better than just showing "20".
> camera.getPicture returns error code 20
> ---
>
> Key: CB-13773
> URL: https://issues.apache.org/jira/browse/CB-13773
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-plugin-camera
> Environment: Android platform
>Reporter: Bob Myers
>Priority: Major
>
> A call to `camera.getPicture` returns an error code of "20". This occurs on
> the Android platform. Things work fine on the browser platform.
> This error started suddenly a few days ago, and I cannot identify anything
> specific I did that might have caused it.
> It's very hard for me to present a reproducible case, since this is occurring
> in the context of large app, but I will try to reproduce in a sample app if
> there's no alternative. Meanwhile, I'm posting this issue in the hope that
> someone might know what an error 20 is supposed to mean.
> In case it matters, it strikes me as odd that the device is not asking me for
> access for the camera when I install the app, nor when I try to take the
> first picture.
> This happens on different devices, including Nougat and Oreo. It happens with
> different versions of the camera plugins. What is especially puzzling to me
> is that it happens with a build of my app from a version three months ago,
> even though that application works fine in the field.
> cordova-android version is 6.2.1. Cordova CLI version is 8.0.0.
> Here is some relevant code:
> {code}
> function getPicture(cameraOptions: CameraOptions): Promise {
> const {camera} = navigator;
> if (!camera) throw new Error("missing camera in
> cordova-plugin-camera.util");
> return new Promise((resolve, reject) => camera.getPicture(resolve, reject,
> cameraOptions));
> }
> // Get a picture from the camera, returning a promise for the URL on the
> device.
> private async getPictureCordova(library): Promise {
> const destinationType = isPlatformWindows() ?
> Camera.DestinationType.DATA_URL : Camera.DestinationType.FILE_URI;
> const sourceType = library ? Camera.PictureSourceType.PHOTOLIBRARY :
> Camera.PictureSourceType.CAMERA;
> const cameraOptions: CameraOptions = {
> quality: 50,
> destinationType,
> sourceType,
> allowEdit : false,
> targetWidth: 1280,
> // targetHeight: 960,
> correctOrientation: true,
> saveToPhotoAlbum: false,
> mediaType: Camera.MediaType.PICTURE, // applies only in case of
> library
> };
> this.reset();
> return await getPicture(cameraOptions);
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-13775) cordova-android@6.2.3 failed with android-versionCode="19"
[ https://issues.apache.org/jira/browse/CB-13775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser resolved CB-13775. - Resolution: Won't Fix This appears to be an issue with the npm modules that you have installed. Try doing an npm install to fix your npm setup. dezalgo is used by node, which is what the installation scripts are all written in. I don't think changing the Android SDK had anything to do with the issue that you're currently getting. > cordova-android@6.2.3 failed with android-versionCode="19" > -- > > Key: CB-13775 > URL: https://issues.apache.org/jira/browse/CB-13775 > Project: Apache Cordova > Issue Type: Bug >Reporter: Barry Fawthrop >Priority: Major > > using cordova-android@6.2.3 > with >"cordova-plugin-device": "2.0.1", > "cordova-plugin-file": "4.3.3", > "cordova-plugin-geolocation": "2.4.3", > "cordova-plugin-media": "2.4.1", > if I set in config.xml > it trys to use Android SDK 19 which is good But failed with > npm ERR! path > /Users/Barry/Desktop/Rolling/rsmobile/node_modules/npm/node_modules/dezalgo > npm ERR! code ENOENT > npm ERR! errno -2 > npm ERR! syscall rename > npm ERR! enoent ENOENT: no such file or directory, rename > '/Users/Barry/demo/node_modules/npm/node_modules/dezalgo' -> > '/Users/Barry/demo/node_modules/npm/node_modules/.dezalgo.DELETE' > npm ERR! enoent This is related to npm not being able to find a file. > npm ERR! enoent > npm ERR! A complete log of this run can be found in: > How is cordova-androidtied to dezalgo ? > Thanks in advance -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-10950) Phonegap app in the background when capture and select image for gallery app stop/restart.
[ https://issues.apache.org/jira/browse/CB-10950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser resolved CB-10950. - Resolution: Workaround If onResume isn't being fired, that would be a different issue than the previous issue. I'd recommend filing a new issue on this. The main issue is already known, and a work-around has already been written and documented, so I'm going to close thus one off. > Phonegap app in the background when capture and select image for gallery app > stop/restart. > --- > > Key: CB-10950 > URL: https://issues.apache.org/jira/browse/CB-10950 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-plugin-camera >Affects Versions: 5.0.1 >Reporter: Lokesh Patel >Priority: Major > Labels: android, triaged, wfc > > Hi, > In android application when the user tries for capturing images and select > image from gallery app stop/restart. > I found below details after search lots of google and forums: > " The Phonegap (Cordova) Camera Plugin calls the native camera and this makes > Android Garbage Collector to kill background applications." > Thanks, > Lokesh Patel -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-13739) Android build is broken due to libraries with text relocations
[ https://issues.apache.org/jira/browse/CB-13739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16326616#comment-16326616 ] Joe Bowser commented on CB-13739: - Have you tested this on any device that's not a Samsung Galaxy Tab? > Android build is broken due to libraries with text relocations > -- > > Key: CB-13739 > URL: https://issues.apache.org/jira/browse/CB-13739 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-android >Affects Versions: cordova-android-7.0.0 > Environment: Build systems: Ubuntu Linux and PhoneGap Build > Android versions: 5.0.2 and 7.1.2 >Reporter: Alexander Tchitchigin >Assignee: Joe Bowser >Priority: Major > Attachments: photo_2018-01-08_12-25-17.jpg > > > When I build an Android app and run it on a device I get the result in the > screenshot: there are a number of libraries with text relocations that > Android refuses to load hence the application is broken and doesn't work. > Release build refuses to start at all. > Before updating Cordova and Android SDK everything worked OK, I was able to > build and run the app and previous version is published to Google Play. But I > didn't memorize the version number when it all worked, unfortunately. App > code was updated either but I don't see how updated JS, CSS and images could > make Cordova link with new libraries with relocations. > Cordova behaves the same to me both locally with the latest version (cordova > 8.0.0, android 7.0.0) and in PhoneGap Build. > I'd like to know the right build settings to produce working build or at > least some workaround. I tried to play with cdvBuildToolsVersion and > cdvCompileSdkVersion but had no success. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-13779) Apache Cordova 8.0.0 not building Android Apps but only prints Android and Java Paths
[
https://issues.apache.org/jira/browse/CB-13779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16326614#comment-16326614
]
Joe Bowser commented on CB-13779:
-
What happens when you rip out the third party plugins on your project, like
TTS, Barcode Scanner and Document Viewer?
> Apache Cordova 8.0.0 not building Android Apps but only prints Android and
> Java Paths
> -
>
> Key: CB-13779
> URL: https://issues.apache.org/jira/browse/CB-13779
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-android
> Environment: I am trying to build a Cordova app with few plugins
> ([InAppBrowser|https://cordova.apache.org/docs/en/latest/reference/cordova-plugin-inappbrowser/],
> [Barcode
> Scanner|https://github.com/phonegap/phonegap-plugin-barcodescanner], [File
> Transfer|https://cordova.apache.org/docs/en/latest/reference/cordova-plugin-file-transfer/index.html],
> [Text-to-Speech|https://github.com/vilic/cordova-plugin-tts], [Document
> Viewer|https://github.com/sitewaerts/cordova-plugin-document-viewer],
> [GeoLocation|https://cordova.apache.org/docs/en/latest/reference/cordova-plugin-geolocation/index.html]).
>
> OS: MacOS High Sierra (10.13.2)
> Cordova version 8.0.0
> Android {{cordova-android@~7.0.0}}
> Android Studio 3.0.1
>
>Reporter: Sumit Soman
>Assignee: Joe Bowser
>Priority: Major
>
> When I run {{cordova build android}} it only shows the {{ANDROID_HOME}} and
> {{JAVA_HOME}} paths but does not build the Android Studio project.
> [!https://i.stack.imgur.com/l7Qat.png!|https://i.stack.imgur.com/l7Qat.png]
> I am using Cordova version 8.0.0 and Android {{cordova-android@~7.0.0}}
> Building in the verbose mode gives the following messages
> [!https://i.stack.imgur.com/rLMSv.png!|https://i.stack.imgur.com/rLMSv.png]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-13781) Error requesting permission on Android 8 - Save on photo album issue
[ https://issues.apache.org/jira/browse/CB-13781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser resolved CB-13781. - Resolution: Fixed Tested, able to reproduce issue. Tested PR, accepted PR as fixing the issue. Will be the next version of the plugin. > Error requesting permission on Android 8 - Save on photo album issue > > > Key: CB-13781 > URL: https://issues.apache.org/jira/browse/CB-13781 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-plugin-camera >Reporter: Rubén Panadero >Priority: Critical > > Google has changed how an android application must request permissions on > Android 8. In fact, it is considered as fix by Google due to a wrong behavior > on previous versions. > Related documentation: > [https://developer.android.com/about/versions/oreo/android-8.0-changes.html#rmp] > This change made by Google has affected the cordova-camera-plugin. To save a > photo in Photo Album, the plugin just requests the READ_EXTERNAL_STORAGE > permission right now, but that is not enough on Android 8 because the plugin > writes the photo file into Pictures folder so it has to request the writing > permission, which is missing, as well. > This is the error that the plugin throws when a photo is tried to be saved > into the photo album on Android 8. > > 01-12 11:38:16.757 W/System.err(22321): java.io.FileNotFoundException: open > > failed: EACCES (Permission denied) > > 01-12 11:38:16.758 W/System.err(22321): at > > android.os.ParcelFileDescriptor.openInternal(ParcelFileDescriptor.java:313) > > 01-12 11:38:16.758 W/System.err(22321): at > > android.os.ParcelFileDescriptor.open(ParcelFileDescriptor.java:211) > > 01-12 11:38:16.758 W/System.err(22321): at > > android.content.ContentResolver.openAssetFileDescriptor(ContentResolver.java:1242) > > 01-12 11:38:16.758 W/System.err(22321): at > > android.content.ContentResolver.openOutputStream(ContentResolver.java:1007) > > 01-12 11:38:16.758 W/System.err(22321): at > > android.content.ContentResolver.openOutputStream(ContentResolver.java:983) > > 01-12 11:38:16.758 W/System.err(22321): at > > org.apache.cordova.camera.CameraLauncher.writeUncompressedImage(CameraLauncher.java:979) > > 01-12 11:38:16.758 W/System.err(22321): at > > org.apache.cordova.camera.CameraLauncher.writeUncompressedImage(CameraLauncher.java:1015) > > 01-12 11:38:16.758 W/System.err(22321): at > > org.apache.cordova.camera.CameraLauncher.processResultFromCamera(CameraLauncher.java:603) > > 01-12 11:38:16.758 W/System.err(22321): at > > org.apache.cordova.camera.CameraLauncher.onActivityResult(CameraLauncher.java:919) > > 01-12 11:38:16.758 W/System.err(22321): at > > org.apache.cordova.CordovaInterfaceImpl.onActivityResult(CordovaInterfaceImpl.java:152) > > 01-12 11:38:16.758 W/System.err(22321): at > > org.apache.cordova.CordovaActivity.onActivityResult(CordovaActivity.java:358) > > 01-12 11:38:16.758 W/System.err(22321): at > > android.app.Activity.dispatchActivityResult(Activity.java:7235) > > 01-12 11:38:16.758 W/System.err(22321): at > > android.app.ActivityThread.deliverResults(ActivityThread.java:4336) > > 01-12 11:38:16.758 W/System.err(22321): at > > android.app.ActivityThread.handleSendResult(ActivityThread.java:4383) > > 01-12 11:38:16.758 W/System.err(22321): at > > android.app.ActivityThread.-wrap19(Unknown Source:0) > > 01-12 11:38:16.758 W/System.err(22321): at > > android.app.ActivityThread$H.handleMessage(ActivityThread.java:1652) > > 01-12 11:38:16.758 W/System.err(22321): at > > android.os.Handler.dispatchMessage(Handler.java:105) > > 01-12 11:38:16.758 W/System.err(22321): at > > android.os.Looper.loop(Looper.java:164) > > 01-12 11:38:16.758 W/System.err(22321): at > > android.app.ActivityThread.main(ActivityThread.java:6600) > > 01-12 11:38:16.758 W/System.err(22321): at > > java.lang.reflect.Method.invoke(Native Method) > > 01-12 11:38:16.758 W/System.err(22321): at > > com.android.internal.os.Zygote$MethodAndArgsCaller.run(Zygote.java:240) > > 01-12 11:38:16.758 W/System.err(22321): at > > com.android.internal.os.ZygoteInit.main(ZygoteInit.java:772) > To sum up, if the plugin has to save a photo in the photo album, this one has > to request both READ_EXTERNAL_STORAGE and WRITE_EXTERNAL_STORAGE permissions. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-13777) Add flag to show camera grid (leveling lines)
[ https://issues.apache.org/jira/browse/CB-13777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16322968#comment-16322968 ] Joe Bowser commented on CB-13777: - It doesn't make sense on Android, since we use the Camera app that's installed on the device, and that's not guaranteed to have a Camera grid. > Add flag to show camera grid (leveling lines) > - > > Key: CB-13777 > URL: https://issues.apache.org/jira/browse/CB-13777 > Project: Apache Cordova > Issue Type: New Feature > Components: cordova-plugin-camera >Reporter: Gustavo Schmidt >Priority: Trivial > > Hello everyone, > Do you think it makes sense to add a flag to show the camera grid in this > project? > I know it's possible to implement this using other plugins, I ask because > this is a common feature in most OSs. > Thanks, > Gustavo -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
