Skip to content

marketplace download <id> --output <dir> fails; only a file path works #1443

Closed
ako/mxcli
#1155

Description

@MendixMau

Environment

  • mxcli: v0.26.0 (release binary, 2026-10-11)
  • Mendix app seen on: ako/mxcli-banking 11.13.0
  • OS: Linux x86_64 cloud container (no Studio Pro; mx/mxbuild only)

Summary

marketplace download <id> --output <dir> fails; only a file path works. Command / document type: marketplace download. Seen on: ako/mxcli-banking. — occurrences: 1

Reproduction

mxcli marketplace download <id> --output <existing dir>

CLI usability

Expected

a directory is accepted, or a clear message.

Actual

rename ... file exists

rename error.

Impact

usability, 1 occurrence(s) in the 2026-10-12 round-trip runs.

Activity

  1. github-actions commented on Oct 12, 2026

    @github-actions

    Issue Triage

    Summary:
    The marketplace download command fails when --output points to an existing directory, producing a “rename … file exists” error instead of accepting the directory or giving a clear message.

    Checklist (bug report)

    Required info Present? Details
    mxcli version ✅ v0.26.0 (release binary, 2026-10-11)
    Mendix version of the project ❌ Only a repository reference (ako/mxcli-banking 11.13.0) is given; the actual Mendix version (e.g., 10.x, 9.x) is missing.
    Scenario (what the user was trying to do) ✅ Running mxcli marketplace download <id> --output <existing dir>
    Expected output ✅ A directory should be accepted (or a clear error message).
    Experienced output ✅ rename … file exists error.
    AI bug report (mxcli diag --bundle or session log) ❌ Not provided.

    Missing information:

    • The Mendix version of the application you’re working with.
    • A diagnostic bundle or session log from mxcli diag --bundle (or at least the relevant log output) to help reproduce the issue.

    Could you please add those details? Thanks for reporting the issue!


    Automated triage via OpenRouter — workflow source

  2. added a commit that references this issue on Oct 12, 2026
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