Cordova

How to resolve cordova conflicts between plugins?

By May 27, 2018 January 14th, 2020 No Comments

Many plugins have the code which requires some specific version of the google library. Say some require 11.2 of google play service and some require 11.3. In order for Gradle to work we must make sure that all the plugins requests same version of the library.

Easier said than done.

First step is to open project.properties file. Look for any easy to find version conflicts.

If the issue still persists, try to narrow down the issue by removing the suspected plugins and see if the build works then. You can also lookup the error library in the entire project and try to find where the issue is.

These days many plugin developers creates some paths through which it is very easy to pick the library version within the install command or as a part of config.xml

Check the cordova plugin list and see make sure it all looks as you expect.

It is important to know the latest version of the plugin. This can easily be known by looking up the library name over Google.

As far as I remember any changes made in plugin.xml requires to remove platform and add again or at least the plugin.

Many a times the issue is with + notation of the version.

For debugging, you can try cordova clean once.

Note: It is wise to stick to the latest version of all the libraries. Latest versions of the libraries has the most recent version of the fixes and for the latest devices.