Plugin install error for Android build about cordova-plugin-request-location-accuracy HOT 24 CLOSED

On a side note, after the initial build that produced the above warning/error, I compile again and it does not happen. Only on the install.

Update: this is incorrect. Install plugin, get warning/error on build. build again, no error. add next plugin (cordova-plugin-screensize) and build again and the warning comes back.

from cordova-plugin-request-location-accuracy.

That seems to be an build warning as opposed to a build error which leads to a build failure.

The example project seems to build OK with [email protected] in my dev environment without that warning:

$ cordova -v
8.0.0

$ git clone https://github.com/dpa99c/cordova-plugin-request-location-accuracy-example
Cloning into 'cordova-plugin-request-location-accuracy-example'...
remote: Counting objects: 95, done.
remote: Total 95 (delta 0), reused 0 (delta 0), pack-reused 95
Unpacking objects: 100% (95/95), done.

$ cd cordova-plugin-request-location-accuracy-example/
/cordova-plugin-request-location-accuracy-example

$ cordova platform add [email protected]
Using cordova-fetch for [email protected]
Adding android project...
Creating Cordova project for the Android platform:
        Path: platforms\android
        Package: uk.co.workingedge.phonegap.plugins.example.requestlocationaccuracy
        Name: Request_Location_Accuracy_example
        Activity: MainActivity
        Android target: android-26
Subproject Path: CordovaLib
Android project created with [email protected]
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
Discovered plugin "cordova-plugin-request-location-accuracy" in config.xml. Adding it to the project
Installing "cordova-plugin-request-location-accuracy" for android
Subproject Path: CordovaLib
Adding cordova-plugin-request-location-accuracy to package.json
Saved plugin info for "cordova-plugin-request-location-accuracy" to config.xml
Discovered plugin "cordova.plugins.diagnostic" in config.xml. Adding it to the project
Installing "cordova.plugins.diagnostic" for android
Subproject Path: CordovaLib
Adding cordova.plugins.diagnostic to package.json
Saved plugin info for "cordova.plugins.diagnostic" to config.xml
--save flag or autosave detected
Saving android@~6.3.0 into config.xml file ...
/cordova-plugin-request-location-accuracy-example

$ cordova plugin ls
cordova-plugin-request-location-accuracy 2.2.3 "Request Location Accuracy"
cordova-plugin-whitelist 1.3.3 "Whitelist"
cordova.plugins.diagnostic 4.0.8 "Diagnostic"
/cordova-plugin-request-location-accuracy-example

$ cordova build android
ANDROID_HOME=G:\Users\dpa99\AppData\Local\Android\sdk
JAVA_HOME=C:\Program Files\Java\jdk1.8.0_161
:wrapper

BUILD SUCCESSFUL in 1s
1 actionable task: 1 executed
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_9fr7v5q7757g5nj3mlym8fewf.run(D:\Temp\cordova-plugin-request-location-accuracy-example\platforms\android\build.gradle:141)
The JavaCompile.setDependencyCacheDir() method has been deprecated and is scheduled to be removed in Gradle 4.0.
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 NO-SOURCE
:CordovaLib:compileLint
:CordovaLib:copyDebugLint NO-SOURCE
:CordovaLib:mergeDebugShaders
:CordovaLib:compileDebugShaders
:CordovaLib:generateDebugAssets
:CordovaLib:mergeDebugAssets
:CordovaLib:mergeDebugProguardFiles
:CordovaLib:packageDebugRenderscript NO-SOURCE
: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 NO-SOURCE
:CordovaLib:transformResourcesWithMergeJavaResForDebug
:CordovaLib:transformClassesAndResourcesWithSyncLibJarsForDebug
:CordovaLib:mergeDebugJniLibFolders
:CordovaLib:transformNative_libsWithMergeJniLibsForDebug
:CordovaLib:transformNative_libsWithSyncJniLibsForDebug
:CordovaLib:bundleDebug
:CordovaLib:preReleaseBuild UP-TO-DATE
:CordovaLib:checkReleaseManifest
:CordovaLib:prepareReleaseDependencies
:CordovaLib:compileReleaseAidl
:CordovaLib:compileReleaseNdk NO-SOURCE
:CordovaLib:copyReleaseLint NO-SOURCE
:CordovaLib:mergeReleaseShaders
:CordovaLib:compileReleaseShaders
:CordovaLib:generateReleaseAssets
:CordovaLib:mergeReleaseAssets
:CordovaLib:mergeReleaseProguardFiles
:CordovaLib:packageReleaseRenderscript NO-SOURCE
:CordovaLib:compileReleaseRenderscript
:CordovaLib:generateReleaseResValues
:CordovaLib:generateReleaseResources
:CordovaLib:packageReleaseResources
:CordovaLib:processReleaseManifest
:CordovaLib:generateReleaseBuildConfig
:CordovaLib:processReleaseResources
:CordovaLib:generateReleaseSources
:CordovaLib:incrementalReleaseJavaCompilationSafeguard
:CordovaLib:compileReleaseJavaWithJavac
:CordovaLib:compileReleaseJavaWithJavac - 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:processReleaseJavaRes NO-SOURCE
:CordovaLib:transformResourcesWithMergeJavaResForRelease
:CordovaLib:transformClassesAndResourcesWithSyncLibJarsForRelease
:CordovaLib:mergeReleaseJniLibFolders
:CordovaLib:transformNative_libsWithMergeJniLibsForRelease
:CordovaLib:transformNative_libsWithSyncJniLibsForRelease
:CordovaLib:bundleRelease
:prepareAndroidArchLifecycleRuntime100Library
:prepareComAndroidSupportAnimatedVectorDrawable2610Library
:prepareComAndroidSupportAppcompatV72610Library
:prepareComAndroidSupportSupportCompat2610Library
:prepareComAndroidSupportSupportCoreUi2610Library
:prepareComAndroidSupportSupportCoreUtils2610Library
:prepareComAndroidSupportSupportFragment2610Library
:prepareComAndroidSupportSupportMediaCompat2610Library
:prepareComAndroidSupportSupportV42610Library
:prepareComAndroidSupportSupportVectorDrawable2610Library
:prepareComGoogleAndroidGmsPlayServicesBase1501Library
:prepareComGoogleAndroidGmsPlayServicesBasement1501Library
:prepareComGoogleAndroidGmsPlayServicesLocation1501Library
:prepareComGoogleAndroidGmsPlayServicesPlacesPlacereport1501Library
:prepareComGoogleAndroidGmsPlayServicesTasks1501Library
:prepareOrgApacheCordovaCordovaLib630DebugLibrary
:prepareDebugDependencies
:compileDebugAidl
:compileDebugRenderscript
:generateDebugBuildConfig
:generateDebugResValues
:generateDebugResources
:mergeDebugResources
:processDebugManifest
:processDebugResources
:generateDebugSources
:incrementalDebugJavaCompilationSafeguard
:compileDebugJavaWithJavac
: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.
Note: D:\Temp\cordova-plugin-request-location-accuracy-example\platforms\android\src\cordova\plugins\Diagnostic.java uses unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
:compileDebugNdk NO-SOURCE
:compileDebugSources
:mergeDebugShaders
:compileDebugShaders
:generateDebugAssets
:mergeDebugAssets
:transformClassesWithDexForDebug
:mergeDebugJniLibFolders
:transformNative_libsWithMergeJniLibsForDebug
:transformNative_libsWithStripDebugSymbolForDebug
:processDebugJavaRes NO-SOURCE
:transformResourcesWithMergeJavaResForDebug
:validateSigningDebug
:packageDebug
:assembleDebug
:cdvBuildDebug

BUILD SUCCESSFUL

Total time: 43.917 secs
Built the following apk(s):
        D:/Temp/cordova-plugin-request-location-accuracy-example/platforms/android/build/outputs/apk/android-debug.apk
/cordova-plugin-request-location-accuracy-example
$

You can also check platforms/android/build.gradle to ensure no other plugins are pulling in a different version of Play Services library components. In the example project build above, I have these entries:

compile "com.google.android.gms:play-services-location:15.+"
compile "com.android.support:support-v4:26.+"
compile "com.android.support:appcompat-v7:26.+"

You can use cordova-android-support-gradle-release and cordova-android-play-services-gradle-release to override the versions of the Android Support Library and Play Services Library specified by installing plugins.

from cordova-plugin-request-location-accuracy.

What is the difference between the two gradle-release plugins? I have been using the support one and only over the last few days became aware of the play-services one.

My build.gradle file contains:

dependencies {
    compile fileTree(dir: 'libs', include: '*.jar')
    // SUB-PROJECT DEPENDENCIES START
    debugCompile(project(path: "CordovaLib", configuration: "debug"))
    releaseCompile(project(path: "CordovaLib", configuration: "release"))
    compile "com.android.support:support-v4:26.+"
    compile "com.google.android.gms:play-services-ads:+"
    compile "com.google.android.gms:play-services-location:15.+"
    // SUB-PROJECT DEPENDENCIES END
}

from cordova-plugin-request-location-accuracy.

Oh...do I need both gradle-release and should they be installed before other plugins - or after? Often I find it does make a difference.

from cordova-plugin-request-location-accuracy.

cordova-android-support-gradle-release overrides the Android Support Library (com.android.support) and cordova-android-play-services-gradle-release overrides the Play Services Library (com.google.android.gms).

From your build.gradle, it looks like there's a version conflict so you'll need to use cordova-android-play-services-gradle-release to resolve it:

cordova plugin add cordova-android-play-services-gradle-release  --variable PLAY_SERVICES_VERSION=15.+

Doesn't matter if you install it before or after other plugins since it will override their Gradle config during the Android build process.

from cordova-plugin-request-location-accuracy.

cool. Thanks. I had not used the play-services one before which explains this issue. I will report back in a bit.

from cordova-plugin-request-location-accuracy.

I added:

`cordova plugin add cordova-android-play-services-gradle-release  --variable PLAY_SERVICES_VERSION=15.+`   (ver 1.4.3)
`cordova plugin add cordova-android-support-gradle-release` (ver 1.4.4)

And I am still getting the warning. My build.gradle file still looks the same:

dependencies {
    compile fileTree(dir: 'libs', include: '*.jar')
    // SUB-PROJECT DEPENDENCIES START
    debugCompile(project(path: "CordovaLib", configuration: "debug"))
    releaseCompile(project(path: "CordovaLib", configuration: "release"))
    compile "com.android.support:support-v4:26.+"
    compile "com.google.android.gms:play-services-ads:+"
    compile "com.google.android.gms:play-services-location:15.+"
    // SUB-PROJECT DEPENDENCIES END
}

from cordova-plugin-request-location-accuracy.

The build.gradle will remain unchanged - the plugin works by overriding the specified versions at build time while Gradle is running. The version mismatch is probably not the cause of your warning - I'd ignore that if it's not causing your build to fail.

from cordova-plugin-request-location-accuracy.

Ok...thanks. Lastly:

When compiling now, I notice this message being displayed:

+-----------------------------------------------------------------
| cordova-android-support-gradle-release: 27.+
+-----------------------------------------------------------------

However, I know that [email protected] provides support for SDK 26. Will this cause any problems? I do have Android Studio (2.3.3) SDK Manager installed with SDKs 26, 27 and 28 installed.

Admittedly, I often get confused on the various compatibility issues....so I appreciate the extra help you have provided.

from cordova-plugin-request-location-accuracy.

The Android build process is a dark art these days.

SDK 26 should be fine with Support Library 27, but if you want to align them:

cordova plugin rm cordova-android-support-gradle-release && cordova plugin add cordova-android-support-gradle-release --variable ANDROID_SUPPORT_VERSION=26.+

from cordova-plugin-request-location-accuracy.

On a separate computer I decided to upgrade most everything and am having success with the usual suspects but am having problems with plugins that have never given problems before. Go figure.

Cordova CLI: 8.0
[email protected]

All the google/android/play-service related plugins are installing fine which stunned me - in fact, so far I have not had to add any of the gradle-release SDK alignment plugins - but now its the old plugins that are causing errors because I think the new Cordova stuff is missing \platforms\android\AndriodManifst.xml file and \platforms\android\res\xml and \platforms\android\res\values folders and files.

from cordova-plugin-request-location-accuracy.

Yes the native Android project directory structure has changed in cordova-android@7 in line with Android Studio v3, so plugins which explicitly reference filepaths such as AndroidManifest.xml will not work.

from cordova-plugin-request-location-accuracy.

Is it simply just changing filepaths (and files) for the various plugins - or adding them back in - or does it tend to be much more invasive than that? I still need these plugins. This is so aggravating.

from cordova-plugin-request-location-accuracy.

Main difference is that the generated app files for cordova-android@7 reside in platforms/android/app/ whereas for cordova-android@6 they reside in platforms/android/.

So platforms/android/AndroidManifest.xml => platforms/android/app/AndroidManifest.xml

You can update any plugins which make explicit references to use the new filepaths.

In my own plugins, where explicit references are made, I've made the hook scripts detect the cordova-android version and use the paths appropriate to the current version, for example this script.

from cordova-plugin-request-location-accuracy.

Thanks, I will see if I can fork the various plugins and get these paths corrected.

I HOPE that is the only issue.

from cordova-plugin-request-location-accuracy.

Interesting, just occurred to me that the script you referenced in your last comment could be the very thing that allowed me to install all the old plugins in a test environment with [email protected], [email protected] and [email protected] - it all installed just fine. But after the project start, the very first plugin I installed was cordova-android-support-gradle-release. I did this months ago and everything installed just fine. The problem though is that my app is in Ionic v1 and I need to convert everything to Ionic v3 which I haven't made much progress with.

So as I am upgrading everything now to work with Ionic v1 none of the older plugins were installing due to the app file paths (mentioned above). So I was trying to trying to figure out how months ago the old plugins installed without issue and why they are breaking today - it turns out your gradle-release includes the script to correct old paths.

The new install, that is breaking on the old plugins, however did not need the gradle-release to install and compile correctly. When you posted the example script it dawned on me why the old plugins installed just fine months ago (cause I used the gradle-release then) and why they weren't installing now (cause I didn't need the gradel-release now).

I wonder if you can isolate that script and supply it as cordova-android-v6-tov7-path-alignment stand alone script for general use. I bet you LOTS of ppl would find use for it.

from cordova-plugin-request-location-accuracy.

I just tested the above theory and that's what it is. Though apparently I don't need cordova-android-support-gradle-release for all the plugins that use firebase/play-service/etc, I do need to install it for all the legacy plugins for that one script that does the path alignment for plugins that have not been updated for [email protected]+

It fixed all of the old plugins except for this one: cordova-dialog-gps (related to \platforms\android\res\xml & ..\res\values)

Any chance you could split your alignment script out as a standalone? Maybe add in some code that force checks plugins that need path alignment - even if there is no code to do the auto-alignment, at least have something that outputs "Plugin uses old path, fork plugin and add new path...".

Thoughts?

from cordova-plugin-request-location-accuracy.

Wow...I did it. Installed 41 plugins using [email protected] (upgraded from 7.0.1), [email protected] (upgraded from 6.2.3) and [email protected] (now just commonly known as Ionic v1). Compiled and ran it....and ran it on an older Android phone running 5.1.1 - and it all works. I am stunned. just need to get that cordova-dialog-gps plugin working. I will hard code all the plugin versions for maintenance releases for the production app....and this should give me plenty of time to finally migrate all my code to the latest Ionic v3 (or now even v4). Huge...HUGE...sigh of relief.

PS: Sorry to blow up your plugin "issue" with this thread...I had to cry on some ones shoulder. ;)

from cordova-plugin-request-location-accuracy.

✋ good work. Worth the effort as it now makes adopting new plugin versions that much easier.
Closing this issue in celebration 🎉

from cordova-plugin-request-location-accuracy.

I was trying to private msg you but couldn't see a way to do it. So I posted here again. Sorry about that.

I forked the cordova-dialog-gps plugin and need to modify the target paths for the plugin install, these paths don't exist nor can I seem to find where they have moved to. Would you mind reviewing my changes below, I thought I had it, the forked plugin installed but when I compiled and ran it on my test phone I got the following errors:

Alert: Error initializing Cordova: class not found
then
Application Error: The connection to the server was unsuccessful (file:///android_asset/www/index.html)

Orig:

    <platform name="android">
        <config-file target="res/xml/config.xml" parent="/*">  <!-- target path updated -->
            <feature name="DialogGPS">
                <param name="android-package" value="cl.rmd.cordova.dialoggps.DialogGPS"/>
            </feature>
        </config-file>
 
        <source-file src="src/android/DialogGPS.java" target-dir="src/cl/rmd/cordova/dialoggps" />
        <source-file src="www/icon/drawable-hdpi/ic_location.png"  target-dir="res/drawable-hdpi/"/> <!--  target paths updated -->
        <source-file src="www/icon/drawable-mdpi/ic_location.png"  target-dir="res/drawable-mdpi/"/>
        <source-file src="www/icon/drawable-xhdpi/ic_location.png"  target-dir="res/drawable-xhdpi/"/>
        <source-file src="www/icon/drawable-xxhdpi/ic_location.png"  target-dir="res/drawable-xxhdpi/"/>
        <source-file src="www/icon/drawable-xxxhdpi/ic_location.png"  target-dir="res/drawable-xxxhdpi/"/>

        <config-file target="AndroidManifest.xml"    parent="/manifest">
            <uses-permission android:name="android.permission.ACCESS_COARSE_LOCATION"/>
            <uses-permission android:name="android.permission.ACCESS_FINE_LOCATION"/>
        </config-file>

Changed to:

    <platform name="android">
        <config-file target="app/src/main/res/xml/config.xml" parent="/*">  <!-- target path updated -->
            <feature name="DialogGPS">
                <param name="android-package" value="cl.rmd.cordova.dialoggps.DialogGPS"/>
            </feature>
        </config-file>
 
        <source-file src="src/android/DialogGPS.java" target-dir="src/cl/rmd/cordova/dialoggps" />
        <source-file src="www/icon/drawable-hdpi/ic_location.png"  target-dir="app/src/main/res/drawable-hdpi/"/> <!--  target paths updated -->
        <source-file src="www/icon/drawable-mdpi/ic_location.png"  target-dir="app/src/main/res/drawable-mdpi/"/>
        <source-file src="www/icon/drawable-xhdpi/ic_location.png"  target-dir="app/src/main/res/drawable-xhdpi/"/>
        <source-file src="www/icon/drawable-xxhdpi/ic_location.png"  target-dir="app/src/main/res/drawable-xxhdpi/"/>
        <source-file src="www/icon/drawable-xxxhdpi/ic_location.png"  target-dir="app/src/main/res/drawable-xxxhdpi/"/>

        <config-file target="AndroidManifest.xml"    parent="/manifest">
            <uses-permission android:name="android.permission.ACCESS_COARSE_LOCATION"/>
            <uses-permission android:name="android.permission.ACCESS_FINE_LOCATION"/>
        </config-file>

I think the offending line is:
<source-file src="src/android/DialogGPS.java" target-dir="src/cl/rmd/cordova/dialoggps" />

Just not certain where the target-dir should be. It put the DialogGPS.java file in app/src/main/java/cl/rmd/cordova/dialoggps/

from cordova-plugin-request-location-accuracy.

Looking at how I'm specifying Android files in the Diagnostic plugin, you need to use relative paths which enables Cordova to prepend the relevant filepath prefix. That allows the plugin to work with both cordova-android@6 and cordova-android@7.

So try something like:

<platform name="android">
    <config-file target="config.xml" parent="/*">  <!-- target path updated -->
        <feature name="DialogGPS">
            <param name="android-package" value="cl.rmd.cordova.dialoggps.DialogGPS"/>
        </feature>
    </config-file>

    <source-file src="src/android/DialogGPS.java" target-dir="src/cl/rmd/cordova/dialoggps" />
    <resource-file src="www/icon/drawable-hdpi/ic_location.png"  target-dir="res/drawable-hdpi/"/> <!--  target paths updated -->
    <resource-file src="www/icon/drawable-mdpi/ic_location.png"  target-dir="res/drawable-mdpi/"/>
    <resource-file src="www/icon/drawable-xhdpi/ic_location.png"  target-dir="res/drawable-xhdpi/"/>
    <resource-file src="www/icon/drawable-xxhdpi/ic_location.png"  target-dir="res/drawable-xxhdpi/"/>
    <resource-file src="www/icon/drawable-xxxhdpi/ic_location.png"  target-dir="res/drawable-xxxhdpi/"/>

    <config-file target="AndroidManifest.xml"    parent="/manifest">
        <uses-permission android:name="android.permission.ACCESS_COARSE_LOCATION"/>
        <uses-permission android:name="android.permission.ACCESS_FINE_LOCATION"/>
    </config-file>

from cordova-plugin-request-location-accuracy.

Ok...will try it out. Uninstalling the plugin jacked my build so I am manually scrapping out all references to it before I can try it again.

Do you think this target-dir needs to be changed to? The error I did get was 'class not found' which I assume meant it couldn't find the 'DialogGPS.java' file.
<source-file src="src/android/DialogGPS.java" target-dir="src/cl/rmd/cordova/dialoggps" />

from cordova-plugin-request-location-accuracy.

Tried your method. It installed without issue but it failed to compile...it returned the same compile errors are the original plugin:

could not write to dest file \app\platforms\android\res\xml\config.xml

from cordova-plugin-request-location-accuracy.

My changed to method above installed and compiled without issue, but when running it to the device the app failed to launch with this error message on the phone: Alert: Error initializing Cordova: class not found - which to me implies it has something to do with where the DialogGPS.java file is being written to.

from cordova-plugin-request-location-accuracy.