How to fix the «The "autoload" field is not set or empty in the "composer.json" file; please verify the archive.» issue for a Magento Marketplace metapackage?

dmitrii_fediuk · January 18, 2018, 9:53am

My composer.json file:

mage2pro/marketplace-assets/blob/2018-01-18-1/AlphaCommerceHub/composer.json#L1-L15


      
          {
          	"name": "alphacommercehub/metapackage"
          	,"version": "1.0.4"
          	,"description": "AlphaCommerceHub integration with Magento 2"
          	,"type": "magento2-module"
          	,"homepage": "https://mage2.pro/c/extensions/alphacommercehub"
          	,"license": "The MIT License (MIT)"
          	,"authors": [{
          		"name": "Dmitry Fedyuk",
          		"email": "admin@mage2.pro",
          		"homepage": "https://mage2.pro/users/dmitry_fedyuk",
          		"role": "Developer"
          	}]
          	,"require": {"mage2pro/alphacommercehub": ">=1.0.4"}
          }

The official Magento documentation says:

Metapackages allow you to group an extension that consists of multiple packages into a cohesive unit.
This works exactly as described in standard composer.json documentation.
If you have an extension that uses more than one package you must use a metapackage as the root package. Otherwise you should not use metapackage.
A metapackage that you submit to Magento Marketplace should be a .zip file containing only the metapackage composer.json file.

devdocs.magento.com/guides/v2.0/extension-dev-guide/package/package_module.html#package-metapackage

The official composer.json example of a metapackage does not contain an autoload field:

devdocs.magento.com/guides/v2.0/extension-dev-guide/package/package_module.html#metapackage-example

dmitrii_fediuk · January 18, 2018, 2:20pm

The previous time, it took 40 days for Magento Marketplace team to respond to a contact form message.
Let’s see will it be faster now.

dmitrii_fediuk · January 19, 2018, 9:10am

I have got a response from Magento:

It appears that the issue is with the type field in the composer file.
According to the web page provided, the type is listed as magento2-module instead of metapackage as stated in the documentation.
The reason for autoload error is due to incorrect labeling in the type field.