Conflicting component dependencies – Magento Help Center

This article provides a solution for conflicting component dependencies. When trying to setup or update Magento Commerce using the Web Setup Wizard, you see the "We found conflicting component dependencies" Composer error message.

Affected products and versions

Magento Commerce v.2.2.x, v.2.3.x
Magento Commerce Cloud v.2.2.x, v.2.3.x
Magento Open Source 2.2.x, 2.3.x

Issue

A conflicting component dependencies error message similar to the following (actual package names and versions will vary):

We found conflicting component dependencies.
You are trying to update package(s) magento/module-sample-data to 1.0.0-beta
We've detected conflicts with the following packages:
- magento/sample-data version 0.74.0-beta15. Please try to update it to one of the following package versions: 0.74.0-beta16, 0.74.0-beta14, 0.74.0-beta13, 0.74.0-beta12, 0.74.0-beta11, 0.74.0-beta10, 0.74.0-beta9, 0.74.0-beta8, 0.74.0-beta7

Cause

This message is displayed if Composer cannot determine which components to install or update.

Solution

Two main scenarios can lead to conflicting component dependencies. Click on your scenario to get troubleshooting steps.

Upgrading Magento

If you are upgrading Magento Commerce Cloud, try the following to resolve conflicting component dependencies:• Check the keys being used to upgrade. Are the keys being generated from the correct email account?• Check permissions and make sure that they match the Magento upgrade requirements. Review DevDocs' Magento Upgrade Overview > Update and Upgrade Checklist > File System Permissions .

Incompatibility with third-party modules:

Conflicting component dependencies can also be caused by third-party modules that depend on earlier Magento components than the ones you have installed. Try the following:

In the preceding example , the installed package magento/sample-data version 0.74.0-beta15 cannot be upgraded to 1.0.0-beta. However, 0.74.0-beta15 can be upgraded to 0.74.0-beta16 (or others). Edit composer.json to make any of these changes. * * Typically, the versions your project is requesting will be defined in the require or require-dev property of the object in that JSON file. Depending on the options of package versions provided, they might specify a specific version or a constraint. For general guidance on how to use composer, if you are on Magento Commerce Cloud, you can refer to DevDocs Magento Commerce Cloud > Technologies and Requirements > Composer . If you are on Magento Commerce, refer to DevDocs Magento > Installation Guide > Install Magento Using the Composer .
Now try the readiness check. Review DevDocs' Magento Upgrade Overview > Run the Module Manager > Step 1 Readiness Check .
If the readiness check fails with another Component dependency check failure message, click on the following links depending on whether you are using Magento Commerce and Magento Commerce Cloud or Magento Open Source, to get further troubleshooting steps.

Magento Commerce and Magento Commerce Cloud

Reach out to the developer of the extension so they can assist you. You can find their contact information on the page you purchased the extension from on the Magento Marketplace. Look for the Contact Seller button shown on the right panel. All Magento developers are required to provide a user's and installation guide when they publish an extension on Marketplace. You can find both on the right side of their landing page.
If you do not receive a response from the Seller in a reasonable amount of time, please let Magento Marketplace know so that we can remind them of their customer support commitments.

Magento Open Source

Request assistance at our main forum or contact a Magento Partner that assists in Open Source issues.

Articles in this section