Skip to content

marketplace install does not install module dependencies and leaves CE0463 widget definitions #1527

Open

Description

@MendixMau

Summary

marketplace install does not install module dependencies and leaves CE0463 widget definitions. install --file (#1150 / PR #1151) is a workaround, not the fix. Related: #1487 (open, marketplace update writes files into the app root), #1382 (open, marketplace package), #1087 (closed, widget app ids after upgrade). No issue found for dependency resolution.

Repro

  1. Blank app. mxcli marketplace install <connector content id> for a connector that depends on another Marketplace module that is not installed.
  2. mxbuild reports about 50 CE errors from the missing module.
  3. Install a module that ships pluggable widgets by content id: CE0463 until mxcli fix widgets runs.

Expected

Dependencies are installed first (or listed and refused); the widget fix runs as part of install.

Actual

No dependency resolution; widgets need a manual fix widgets (41 units in the field run). install --file with a downloaded mpk worked for the dependency.

Tested with: Mendix 11.15.0, mxcli v0.26.0 on macOS (code also read in the v0.27.0 source). Not retested on v0.27.0.

Activity

  1. github-actions commented on Oct 16, 2026

    @github-actions

    Issue Triage

    Summary:
    The marketplace install command fails to automatically install dependent modules and does not run the widget‑fix step, leaving CE errors after installation.

    Checklist (bug report)

    Required info Present? Details
    mxcli version ✅ v0.26.0 (tested)
    Mendix version ✅ 11.15.0
    Scenario (what was tried) ✅ mxcli marketplace install <connector content id> on a blank app
    Expected output ✅ Dependencies installed first; widget fix runs as part of install
    Experienced output ✅ No dependency resolution; manual fix widgets needed; mxbuild shows ~50 CE errors
    AI bug report (mxcli diag --bundle or session log) ❌ Not provided

    Missing information:
    Could you please attach the output of mxcli diag --bundle (or at least the relevant session log) so we can see the exact environment and any internal errors? This will help us reproduce and fix the issue. Thank you!


    Automated triage via OpenRouter — workflow source

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions