Found 2 versions of google-play-services.jar

[Mike_C_4]

okay,

based on the sticky link here: https://software.intel.com/en-us/forums/intel-xdk/topic/595059

I should not be having this issue. I'm using CLI 4.1.2  ( as I have always) and all my plugins have worked with that version of CLI.

Just yesterday I did a build and it worked just fine, I installed version 2548 reinstalled the same plugins and now my builds are failing.

I'm now have to waste more time and reload the previous version (again).

I been trying to be patience here with all this issue that’s happening but my project has been delay twice.

I'm not sure if this version has change something in my project that I have to manually change back etc.

Is there anything I can do other that reload the old version of the software?  This is not just happening with CLI 5.xx

I attached my log if need

Mike

[Mike_C_4]

Solution!

After doing some googling,  I figured out that the issue was the new version of XDK (2546). It downloaded the newest version of the com.google.playservices plugin. I also had an older version installed in the plugin folder outside the project folder . I installed the older version of the plugin re-built and everything worked.

I think when a new version of the XDK is installed it should not download any newer version of the plugins, this caused me more lost time in debugging this issue.

Everything works now. for CLI 4.1.2

[PaulF_IntelCorp]

Mike -- the sticky your pointing to is not the failure you were having. If you look at the end of the log that you attached, it is including this error message:

[dependency] Found 2 versions of google-play-services.jar in the dependency list,
[dependency] but not all the versions are identical (check is based on SHA-1 only at this time).
[dependency] All versions of the libraries must be the same at this time.
[dependency] Versions found are:
[dependency] Path: .../FamilyReunion_120/platforms/android/com.google.playservices/google-play-services_lib/libs/google-play-services.jar
[dependency] 	Length: 5415820
[dependency] 	SHA-1: 8d5f3fa25437d7d8ffdfb1a0f251adf682f14649
[dependency] Path: .../FamilyReunion_120/platforms/android/libs/google-play-services.jar
[dependency] 	Length: 2765459
[dependency] 	SHA-1: d71573c9c5ea98a8db47ad6ff993a63d492b3bfa

BUILD FAILED
/Developer/android-sdk-linux/tools/ant/build.xml:573: Jar mismatch! Fix your dependencies

Which is much different that that described in the sticky note you referenced.

Can you provide details regarding which version of the com.google.playservices plugin worked for you and which failed? When you upgrade your project we try to preserve the version of the plugins that were already specified in your project file. Unfortunately, some of the older versions of the XDK did not include that information, so the only option is to include the latest version of the plugin.

[Mike_C_4]

Thnks Paul F.  for the clarification.

The version I’m using is 19.0 what was download by the app was 19.3.

The app did not know what plugin folder to use and found some in one folder and not the other and vice versa. (myproject/plugins or www/plugins) So I removed the plugins from the www/plugin folders leaving the myproject/plugins folder intact.

Thinking it would pull the plugins from the myproject/plugins since it’s the only folder that had plugins. What I think happens is the app goes out to the net and downloads them from your cloud. Which is okay, but the app is not checking to see what plugins (version) are being used. So as far as I can tell it is downloading just the new ones it finds.

If there is a better way of doing this, please let me know because at this point where I’m totally confused.

[PaulF_IntelCorp]

Mike, this makes a little more sense. Were you also referencing that plugin, the one in your www directory, via the additions.xml file?

With the latest version of XDK we actually no longer support putting "local" plugins inside the www directory (at least, it is not a good idea) because we are now putting ALL plugins you use into the plugins directory. During the upgrade, any plugins that you included via the additions.xml file are not seen, so this is likely the reason for confusion. Are you using an AdMob plugin? If so, it was the reason the other version of the plugin got included, because plugins you add via the plugin manager will also pull in their dependent plugins (plugins that they require) and this is likely how that other version was included.

[Mike_C_4]

Hi Paul,

Okay I'm using the plugin called AdMob Pro plugin which I loaded locally,

What I still confused about is after the update is complete there are now plugins back in the www/plugin folder?  I'm guessing thats correct? Or am I still doing something wrong.

Thanks again for your help.

[PaulF_IntelCorp]

The update to your project will not remove any plugins that were located in your www directory -- locating plugins there was a "temporary measure" that you had to use to import local plugins, due to the way plugins were handled by the XDK and build system with older versions of the XDK.

With the new project setup and new build system you no longer should store plugins in your www directory. If there are plugins you want to reference locally on your filesystem, rather than via the Cordova registry or GitHub, then place them anywhere you like EXCEPT in the www or plugins directories inside your project directory. This means you can, if you wish, put them in some other directory in your projects folder or even in some location outside of your projects folder. You will need to use the "import local" feature of the plugin manager (see the image below) to add those plugins to your project. This also means you should quit using the additions.xml file to reference those plugins.

I realize this is confusing.