<-- Back

Marketplace Module Upload Fails: Checksum Error or Version Fields Not Editable

Issue

  • When attempting to upload a new module for publication in the Marketplace, the following error appears.
The checksum in the manifest.json file is not allowed.
  • If uploading the .mpk file is successful, the Studio Pro version and release version number are no longer editable after uploading the new .mpk file. Both version fields appear locked, preventing a new version number from being specified and the release from being completed.

Environment

  • Studio Pro 11.12.0 and newer
  • Marketplace

Cause

For packages exported from Studio Pro 11.12.0 onwards, the module version must be set in the module settings before exporting the package. The Marketplace no longer allows manually changing the versions during upload. 

It also does not allow uploading a package with an existing version number. The error message displayed in the Marketplace indicates that a module with the same checksum has already been uploaded. This validation is performed by the Marketplace to prevent the same package from being published more than once.

When a module is exported, the .mpk file includes a manifest.json file containing metadata such as the package ID, version, checksum, and model version. If no changes have been made to the module, the checksum remains unchanged, and the Marketplace rejects the package because it is identical to one that has already been uploaded.

To generate a new checksum, at least update the module version in the module settings in Studio Pro and export the module again. The updated package can then be uploaded successfully.

Solution/Workaround

Specify the module version number in Studio Pro before uploading the .mpk file. Follow these steps to set the version correctly:

  1. In Studio Pro, navigate to the module Settings > Module version.
  2. Change the version number to the version to be published.
  3. Export the module package to an .mpk file.
  4. Upload the exported package to the Marketplace
Marketplace upload screen showing Release Version and Studio Pro Version fields

The Release Version now reflects the value configured in the module settings, and the Studio Pro Version reflects the Studio Pro version used to create the module.

When redistributing a module, the version number should always be updated when changes are made.

Internal information related

  • 284660, 284770, 284736
  • C04JZDSNPLP/p1785423169013759

Additional information

Mendix documentation: 

Have more questions? Submit a request

0 Comments

Article is closed for comments.

To provide feedback, please open a ticket here. Don't forget to include the article's URL along with the feedback you would like to provide.