Installation & Varnish Test Results Failed on magento marketplace

Question

Installation & Varnish Test Results Failed on Magento Marketplace

Magento Marketplace Installation & Varnish Test Results

composer.json

{
 "name": "vendor/preorder",
 "description": "Pre Order",
 "type": "magento2-module",
 "version": "2.0.0",
 "license": [
 "OSL-3.0",
 "AFL-3.0"
 ],
 "require": {
 "php": "~7.1.3||~7.2.0||~7.3.14||~7.3.0||~7.3.1||~7.3.2||~7.3.3||~7.3.4||~7.3.5||~7.3.6||~7.3.7||~7.3.8||~7.3.9||~7.3.10||~7.3.11||~7.3.12||~7.3.13"
 },
 "extra": {
 "installer-paths": {
 "app/code/Vendor/Preorder": ["vendor/preorder"]
 }
 },
 "autoload": {
 "files": ["registration.php"],
 "psr-4": {
 "Vendor\\Preorder\\": ""
 }
 }
}

[Composer\Downloader\TransportException]
The "https://repo.magento.com/packages.json" file could not be downloaded (HTTP/1.1 500 Internal Server Error)

require [--dev] [--prefer-source] [--prefer-dist] [--no-progress] [--no-suggest] [--no-update] [--no-scripts] [--update-no-dev] [--update-with-dependencies] [--update-with-all-dependencies] [--ignore-platform-reqs] [--prefer-stable] [--prefer-lowest] [--sort-packages] [-o|--optimize-autoloader] [-a|--classmap-authoritative] [--apcu-autoloader] [--] []...

• Kamal Asawara: There is an issue from Magento marketplace, they are fixing it.

Answer 1

Updated

I have solved this by adding a auth.json file in the root

{
 "http-basic": {
 "repo.magento.com": {
 "username": "<public_key>",
 "password": "<private_key>"
 }
 }
}

Refer this https://devdocs.magento.com/guides/v2.3/install-gde/prereq/dev_install.html

• Mohit Rane: what do you mean in the root? module directory?
• Divya Sekar: create a auth,json file in root directory
• Mohit Rane: you mean in the marketplace? do you have a path or steps to follow?
• Divya Sekar: yes, you have to add auth.json file in root folder for upload a module package in magento marketplace if you have any doubts
• Divya Sekar: the path is myvendor_mymodule-2.0.2/auth.json used in magento marketplace

Answer 2

I had the same issue, it was from their side, but for someone else having the same issue, I recommend to check this answer and this Devdocs page.